Slashdot Mirror
Vector Graphics Lead Wish List For Future Browsers
Coach Wei writes "Community voting results and a summary report have been published from
OpenAjax Alliance's recent "community wishlist for future browsers" effort. When the voting closed on July 13th, 222 people participated in this open community initiative, with 143 people voted, 55 feature requests being written up, and contribution from many industry leaders. The voting indentified and prioritized 37 features. The top 10 are related to vector graphics, security, performance, layout, rich text editing, Comet, audio and video. Among all the feature requests, 2D Drawing/Vector Graphics is clearly the most desired feature by the community. It received most votes (110 people voted for it), and highest total score (over 10% higher than the second feature request). Looks like that it is time for all browsers, in particular, IE, to seriously consider supporting standards-based vector graphics."
I tought SVG is already implemented in most modern browsers...
Not when you weigh each browser by its usage share on home and business workstations. As long as Windows Internet Explorer doesn't implement SVG, and as long as Windows Internet Explorer has more than 50 percent usage share, "most modern browsers" don't implement SVG.
As an end user and a project manager, I'd have to ask you why your code doesn't allow such a possibility. Not that I don't understand the added effort and difficulties (okay, technically, I don't; I don't program for the web), and it would suck to have to make it all work properly, but that's kinda your job.
Is it just my observation, or are there way too many stupid people in the world?
I'm glad Firefox has SVG and is improving it. I really want to see SVG animation. It sucks to use java script just to cause a diagram to have a few moving parts when animate transform would do the trick.
<sarcasm>Well, you see... our new, half-assed, pieced-together technology will only properly work if we force users to use it the way we want. Remember: it's OUR content, so we get to determine how the USERS use it!</sarcasm>
<serious>UseIt.com.</serious>
"The fight for freedom has only just begun." - Geert Wilders
If you consider yourself a "web developer" and don't know how to manipulate the URI fragment to make the back button work with AJAX, then you should just quit right now and become a politician or a lawyer or something. The back button is fundamental and all AJAX applications should work with it.
There, fixed that for you. The only thing MS is ever first on are the things that can't be implemented in any other browser because MS owns the technology.
I stole this sig from someone cleverer than me.
Then I right-click the link to the webapp and choose "Open in new window". In fact, as a browser user, the number one feature I'd like to add is an item in that popup menu: "Open in this tab".
You realize adobe has released an official flash player for Linux right? How did such an ignorant post get modded insightful?
Microsoft is not to be trusted, they have proven this time and time again. Silverlight itself is built on a platform designed to screw everyone in the IT world over.
Microsoft tried to corrupt Java and make it Windows only... and got stopped. So they cloned Java, e.g. .NET, and made it Windows only.
Mono is a few major revisions behind Microsoft's implementation. It doesn't support a large part of Microsoft's software stack. It is basically "Managed Wine."
It's not the kind of thing I'd want to rely on and no one in their right mind should let Silverlight put Microsoft in a position to take over the Internet.
So in short: avoid Silverlight like the plague that it is.
All that is nice, but what we need is a vector graphics kit that's not shipped by yet another fucking vendor. Something that's a spec, not a binary.
The problem is the back button causes a very very very large break in the sanity of web applications. You can kiss a consistent state goodbye.
I know I'm contradicting my sig, but I want to explain why you are wrong.
Session state is maintained on the server, not the client.
If you trust the client to provide you valid data about the state of the application, you are very stupid. This is how people get owned.
As such, you should remember what the user was doing, and if they open the application again, return them to where they were.
Disabling the back button is wrong. If your application cannot handle me leaving it any any time gracefully, it is a piece of shit. And if you absolutely must have control of my system, well, that's why we have xulrunner. In fact, I would go so far as to say that the web is probably not even the best way to deliver an application of that nature, but you could argue that one back and forth all day - my main argument is that users expect web pages to behave in a certain way.
The real issue here is that a webpage is not a standalone application, and you run into problems like these when you try to make it one. Webpages are forms, like screens on mainframes, and are request-oriented. Your web applications should be the same.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"