Hi Aldo, thanx for a very usefull comments. I'm sorry I have no much experience with Flex 2 since it is alpha now and will require Flash 8.5 plugin, thus will require most of users to download plugin. It is not a problem for a corporate sites but in our case it is a very big problem because we have to buiid site that is oriented on mass user and it will take about a year to get 90% of users use 8.5 player. However now our application is much faster on 8.5 plugin. About your comments:
>In Flex2 you will have an eclipse plugin ( which is more than enough >for any J2EE developer ). Moreover, the SWF format is open, the MXML >format is based on XML, and the standalone compiler can be integrated >to any other third party IDE. It's just a matter of time till we have >3rd party IDEs showing up. Personaly I use FDT plugin for AS since it is the most mature and Java like (automatic imports, code completion, AS Docs and lots of other features) It does not support Mxml but the idea is to remove scripts from mxml so MXML is very easy in our framework not like the AS code >BTW, Cell Renderer is not a hack, in the sense that it was meant to do >just that. It is a documented feature. ( OTOH, it is not quite >straightforward and suffers of the nuances of Flex 1.5 component >development... ) I'd better like mx:Column to support internal tags like it is in Struts displaytag library. Since it is almost impossible to reuse cell renderers. The idea of component is that it is reusable component that can be easily tuned to suuport your requirements. Adding button to the row is a kind of tuning and must not require extra coding. That is my opinion but I guess most of the community will agree with me >Flex2 runs on Flash8.5, which does support Runtime Error detection. I >have found it to be amazingly useful and enhances my productivity >dramatically. Agree 8.5 is much faster >Cairngorm is the FIRST framework donated to the flex opensource >community (yes, there is ARP, but it was born for Flash). If you have >any contributions to make, I'm sure Steven and everyone else from >Macromedia Consulting would be eager to listen and develop a new >framework. >I believe you can still influence on the new integrated development >approach planned for Flex2. Just keep on your discussions on the >subject alive. Totally agree but EJB was also first technology for enterprise development in Java and it worth us to be blind for a 5 years. EJB was the same overcomplicated that Cairngorm is and as far as I understand Cairngorm uses the same patterns and fully inspired by J2EE. So I just want Flex do not repeat previous mistakes. You do not need to get things that complex like thy are now with Commands FrontControllers and other stuff. Now I have a kind of framework that is much easier than Cairngorm and I'll try to share it with the community when it will pass internal sainity testing in our team (now guys are happy but lets wait more serious testing). >> - no i18n support on mxml level >I believe Macromedia did not want to risk a strategy upfront, before >realizing what the real requirements were... >Could someone from macromedia develop on this? >What is the state of things now? Will the new Cairngorm support it? >will it be integrated into Flex2 later? IDE Support? >You know, it is a critical common requirement ( every app nowadays is intlzed ) Again we've added it to our framework. But I see no reason why MM guys haven't done it themselves >> - No kickstart examples like Appfuse in Java >Hopefully time wil bring them. Flex2 will drive a radically larger community. It is a huge problem cause when you need team development you need unittesting, framework, build strategy etc. And I'm sure that every team create it from scratch now. The idea is to publish some approach and evolve it to support and show best practices on it. Just like appfuse does in Java community. I guess we have to create our own appfuse Spring + Hibernate + Flex, maybe also Spring + Hibernate + Laszlo to have fully open source alternative. >> - Async call model. Sure it is a great feature but it makes development more >complicated >Ok. This is the way things work. It is not that hard to get used to >this sort of programming once you gain some practice. Again, I hope >new frameworks provide easier/simpler ways of doing this. I'm not saying it is hard to get used to it but some things are almost impossible in such model. For example unittesting. I managed to write unitests for our approach but it was very hard and if your approach evolves test need to be greatly changed not like it is with the sync calls. >> The question is if we have to launch our site in less than a year and >> site is really big what are our chances? >Tricky question. How about going for Flex2? >It is soooo much better in many many ways that it makes sense to start >developing and, when the final release hits the streets, make the >appropriate changes ( if any ). It is a very big risk and also we have to consider the plugin problem since most of users will not use 8.5 when we launch. But I think it definitely worth consideration. >I would like to see more people contributing to this thread ;) Me too :) Best Regards, Mykola ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> 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/
