Hi, Richard- [EMAIL PROTECTED] wrote: > Doug > > Yeh it would be good to perhaps have some idea of where we are going, our > apps rely heavily on SVG (closed apps that have logins) but my head is > spinning at the moment what to do. Maybe I should leave it for another 12 > months and then start to worry 8 months or so before ASV gewts pulled, > hopefully there will be good news around the corner, unfortunatley all our > users use IE, we are rewriting a new version to include FF, Opera and > Safari, but IE is still the main browser. > > I hear Ajax , Dojo2d, laszlo, emiasys....which is the right path.....oh > dear.
Well, I don't think it's all that confusing. The choices really break down to 3 options: 1) hope/work toward SVG support in IE, either native or via a plugin (EmiaSys and all others mentioned on this list fall into this category) 2) use an abstracted framework that delivers whatever graphics format is appropriate for the target platform (Ajax, Dojo2d, laszlo all fall into this category) 3) use some other technology (XAML and Flash [possibly laszlo?] fall into this category) I'm avoiding category 3 like the plague. The nice thing is that categories 1 and 2 are orthogonal... a business can use a framework, and when IE SVG support is stable, reexamine if they still need that framework. It can be a permanent commitment (dojo has a lot of advantages apart from SVG) or a stopgap. I can tell you what my company is considering doing, and maybe that might help inform your choices. We are already using dojo, so we will be investigating how well our content can be presented in dojo2D. I admit to some initial skepticism; VML is really limited, but I will follow up on it and see how much can be done. If it is designed correctly, it could deliver SVG to FF, Opera, Safari, etc., VML to base IE, and SVG to IE+SVG (either via plug-in or native, down the line). dojo2D pros: * abstracted development layer * browser independent * doesn't matter if IE has an SVG plug-in or not dojo2D cons: * dependence on dojo framework (not so bad for my company) * new abstracted layer to learn * may not be as full-featured as programming to native SVG implementations (lowest common denominator) But my real aim is finding a replacement for ASV. Having spent a few days taking stock of our options, I am pretty confident that with the will behind this group, the commercial opportunities and incentives for other companies, and the available resources (both open and closed source), we will be able to get at least fair SVG support for IE. Of course, Adobe could help this along by providing the code to help us do this, rather than aggressively attacking SVG. As has been said before, they have every right to stop supporting ASV, but their next move determines how they will be seen in doing so. Regards- -Doug ----- 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/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
