Font-size *is* transform. A scale to be exact. One of the benefits of GLyphy is that you don't need to rasterize the font at every scale. Imagine pinch-zoom for example.
As mentioned in the QA section, at some point I had GLyphy compiled through Emscripten to Javascript+WebGL. It was working rather fine. I should try that again.
Ie. I offered to fix it, before the report was published. And the report is deliberately misinformed to make it look like I said I don't have any intention to fix it. And the report author tweetted [1] "Apparently not a lot of people read Slashdot anymore or RTFA. I've only had 971 hits to the article so far.:-(", which makes me believe that his true intention was to get Slashdot / Reddit / Hacker News bragging rights. Comes handy if you are a sysadmin I guess...
And I offered to fix it, but the reporter decided to ignore that and public the report, claiming that I said I won't fix it. I think the slashdot bragging rights were more interesting to him.:)
You have to read the bugzilla report carefully to see what this story is about. I'm the developer being [bf]lamed. I offered to find time on a weekend and fix the issue. But the reporter ignored my offer and went ahead to post this on as many places as it could. In the report, he masks that, and instead says I don't consider it a bug. The report is intentionally written misinformed IMO. Which makes me think the true story is that he wanted to get some publicity...
That's misinformed. Vte creates files in/tmp, and immediately delete them. So, the space will be reclaimed as soon as the terminal tab in question is closed. I know this is how it works, because that's how I wrote it.
Because we don't believe that Microsoft doesn't exist. If you think by playing pro-ODF the rest of the world can keep MS from making OOXML an ISO standard, well, you are wrong. I'm sure you saw what wonders they did to governments days prior to the final vote was due...
It's about the details however, how much pain we give them in the process and how useful documentation we get out of it. Ignoring the committee is not the best strategy. NIH anyone?
I've had this problem of links not passing on Y! for a few months now. It happens with random links, mostly the ones with request strings. It only happens when sent from gaim. Couldn't identify more details.
Indeed they are opening some of their small projects, moving development to SourceForge.net. See http://code.google.com/ for a list. Small still, but nonzero.
Slashdot Mirror
Thanks for the constructive feedback.
Font-size *is* transform. A scale to be exact. One of the benefits of GLyphy is that you don't need to rasterize the font at every scale. Imagine pinch-zoom for example.
As mentioned in the QA section, at some point I had GLyphy compiled through Emscripten to Javascript+WebGL. It was working rather fine. I should try that again.
What do you mean? The presentation is pretty much *all* screenshots!
I take it as a compliment ;).
See my other comment also:
http://linux.slashdot.org/comments.pl?sid=2714201&cid=39291633
Anonymous Coward,
You may want to read the end of this comment before jumping to conclusions:
https://bugzilla.gnome.org/show_bug.cgi?id=664611#c10
Ie. I offered to fix it, before the report was published. And the report is deliberately misinformed to make it look like I said I don't have any intention to fix it. And the report author tweetted [1] "Apparently not a lot of people read Slashdot anymore or RTFA. I've only had 971 hits to the article so far. :-(", which makes me believe that his true intention was to get Slashdot / Reddit / Hacker News bragging rights. Comes handy if you are a sysadmin I guess...
behdad
[1] https://twitter.com/#!/climagic/status/177796284755873793
And I offered to fix it, but the reporter decided to ignore that and public the report, claiming that I said I won't fix it. I think the slashdot bragging rights were more interesting to him. :)
You have to read the bugzilla report carefully to see what this story is about. I'm the developer being [bf]lamed. I offered to find time on a weekend and fix the issue. But the reporter ignored my offer and went ahead to post this on as many places as it could. In the report, he masks that, and instead says I don't consider it a bug. The report is intentionally written misinformed IMO. Which makes me think the true story is that he wanted to get some publicity...
That's misinformed. Vte creates files in /tmp, and immediately delete them. So, the space will be reclaimed as soon as the terminal tab in question is closed. I know this is how it works, because that's how I wrote it.
> Why?
Because we don't believe that Microsoft doesn't exist. If you think by playing pro-ODF the rest of the world can keep MS from making OOXML an ISO standard, well, you are wrong. I'm sure you saw what wonders they did to governments days prior to the final vote was due...
It's about the details however, how much pain we give them in the process and how useful documentation we get out of it. Ignoring the committee is not the best strategy. NIH anyone?
-- Behdad Esfahbod
Director, GNOME Foundation
I've had this problem of links not passing on Y! for a few months now. It happens with random links, mostly the ones with request strings. It only happens when sent from gaim. Couldn't identify more details.
That's because there's a lot to do on that front, you know, to catch up... :)
Indeed they are opening some of their small projects, moving development to SourceForge.net. See http://code.google.com/ for a list. Small still, but nonzero.
'Search the F Web' it means.