I definitely agree with you, if Flex stops something else will appear and we will have it to learn.
I think that Adobe makes the things more confused, as we were doing the same things much easiest with our developed infrastructure. As your said, we are waiting from SDK better performance to our application (like multithreading :) ), better database connections. and many other things where yet is poor, instead of create the new spark. Ok, I don't blame because I haven't learn this feature; it is my first time in the history of Flex where I complain for something. I hope to be wrong and continue to trust Adobe. By the way, according this message > "Spark provides a much more expressive mechanism for developers and > designers to work together on the appearance of their Flex applications". In > other topic they saying that designer and developer could work for the same > project, separately. Could someone explain me (it this is possible), what the designer can do only and what the developer? Some example(s). Thank you in advance dennis ...we are what we are doing... P Think! before you print. From: [email protected] [mailto:[email protected]] On Behalf Of t0ml33 Sent: Thursday, August 19, 2010 3:56 PM To: [email protected] Subject: [flexcoders] Re: does Flex 5 upgrade? or downgrade in practice? REFdn7076142784 Same as with anything else. We want Adobe to continually make things better - that means that we have to pay some cost to learn the new tech, port our existing apps, patch around any new issues, remove hacks and workarounds that are no longer necessary, etc. Would you like them to stop releasing new versions? Just develop the Flex 3 feature set forever? If Adobe did not move the platform forward, somebody else would come up with some new platform that does something Flex doesn't - and then our bosses would be asking us to rewrite for that new platform. Only you can decide whether the upgrade is "worth it" on your individual projects. My criteria for making that decision are pretty much as follows: Is your software reaching "end of life"? Probably don't upgrade. New project? Definitely upgrade. Project has a lot of new development left to do? Probably upgrade. Finally, Flex has its limitations and it's your job as a developer to understand those limitations and guide your project management accordingly. If you have a boss that is pushing you to do something which you know will not perform well, you have to convince her/him that it's a bad idea. Also, if you have not structured your project with performance in mind, you will see poor startup performance - but that's not Flex's fault. That said, I too would like to see some progress in the overall performance of the Flex SDK. --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "dennis" <den...@...> wrote: > > Dear all > > > > At http://www.adobe.com/devnet/flex/articles/flex4sdk_whatsnew.html , at the > beginning they telling us: > > "Spark provides a much more expressive mechanism for developers and > designers to work together on the appearance of their Flex applications". In > other topic they saying that designer and developer could work for the same > project, separately. > > > > It sounds good, but which way in practice Adobe suggests? Does anybody > knows? > > Because, all of us (more or less) have developed ways for developer and > designed to work together for the same project. > > Does Adobe suggest something smartest and does it worth? Does it really > worth? > > > > In our business we must estimate if a new product they sell us, if a new > suggested technology really worth. We have no time (see money) to invest to > something that finally doesn't worth. Imagine to invest to learn something > (you or your people) and after one year Adobe will abandon it, in case where > they see that it is not "merchandisable" anymore or generally is failed! The > history of software development is full with this kind of stories. > > > > I think. that Flex is becoming too complex for this kind of software that > generates. Even more where Flex doesn't support multithreading (what are you > doing Adobe with too heavy infrastructures in our swf???). Too complex like > .net has become, where a simple applications requires a lot of power CPU, at > least on its first execution, where a new developer is completely lost in > too many libraries where they doing the same things, with different bugs. > > > > Share your thoughts. .. > > > > Take care. > > dennis > > ...we are what we are doing... P Think! before you print. >
