--- In [email protected], "Hannes Fleischer" <[EMAIL PROTECTED]> wrote: ... Hannes, up front, I feel sorry for you adding the following comment to your post. I got strong counters from Alastair concerning a similar topic, so please don't feel hold cheap if people's thoughts differ on the matter. Your svg bike simulation is a very impressive showcase for a svg expenditure. In fact, it's one of these hefty tome applications using the svg applet as a runtime engine. I'm eager to learn why you did choose svg for your bike simulation. On the one hand there're more productive application platforms to choose from, on the other hand taking the hassle of building a javascripted webapp from ground would take it for granted having reasonable reach for the app? I'm curious to know, most of the talk in this group is about scripting svg. I'm even more curios about svg's roadmap, so the following words are only indirectly related to your simulation: We know that browsers aren't built as a platform engine for webapplications. The w3c graphics group was/is about evolving a platform for helping out web developers with a platform for arbitrary (web-)apps? I mean arbitrary in a literal sense since svg will foster one missing almost any common sense, usability and design rules the web typifies to some degree these days? To put it in slightly exaggerated terms: Is a 'svg+javascript enabled web' the ultimate way to 'break the web' employing w3c web standards? No, this would be basically a distortion of facts, obviously talking a lot of nonsense. Anyway, it's adobe that bought in the flash-app svg aspects into w3c ($). The adobe svg viewer still rules svg today. But the viewer was built as adobes pendant to macromedias flash player. It's a damned runtime engine, greedy and slow, bears it own script realization and server communication, and hardly talks to it's surrounding dom implementation. And please, don't tell me they couldn't do any better. At least for the major browser it's straightforward and ordinary difficult to implement inline svg though binary behaviors.
So please, someone tell me that svg was evolved to add better graphics to a web page rather than replacing the web page with a bulky proprietary application. Is svg going to end as the flash for students and the poor? Will we need a svg-spoofed-window popup blocker in future? One shouldn't demand too much of the ordinary web user, but expect resistance if a web user feels helpless in the face of a web page. On the contrary, svg needs to convince the public to call for svg enabled browsers!? curios cheers Paul ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
