+1 from my side ... A quick reminder of my former post [1] ... I have created a petition regarding this issue for the "Design View" in Flash Builder and Flash Catalyst [2].
Discontinuing "Design View" in Flash Builder and Flash Catalyst means: • This is bad news for all people who prefer to design and think visually: http://en.wikipedia.org/wiki/Visual_learning • This is bad news for all Flex developers which have to navigate and code large-scale Flex apps. • This is bad news for all Flex designers that need to interact with Flex developers. • This is bad news for all Flex beginners because it adds another barrier while learning Flex development … and this is bad again because we need more highly skilled Flex developers around. -- Sebastian [1] http://markmail.org/search/?q=+list%3Aorg.apache.incubator.flex-dev+Petition%3A+Flash+Catalyst+must+survive+++++#query:%20list%3Aorg.apache.incubator.flex-dev%20Petition%3A%20Flash%20Catalyst%20must%20survive%20%20%20%20%20+page:1+mid:h5ecjc66tn7lgczz+state:results [2] http://www.change.org/petitions/adobe-systems-flash-catalyst-must-survive http://masuland.wordpress.com/ On Thu, Feb 23, 2012 at 7:53 AM, Pierangelo Mancusi < pierangelo.manc...@gmail.com> wrote: > +1 of course > > > > > Il giorno 22 febbraio 2012 11:03, Dimitri k. <k...@noos.fr> ha scritto: > > > After the discussion on the ML about the Design View, I thought it would > > be a good idea to ask Deepa at the Flex Paris meeting if Adobe could > > consider to open-source it after the removal from next version of Flash > > Builder. > > Frédéric Thomas, also on the ML, was quicker than me and ask Deepa about > > that. > > She said that Adobe hasn't thought about it because they didn't believe > we > > were interested, but she was thinking it could be a good idea. > > In fact, the Design View is a Flex app, so the community can easily > > contribute to it, and legal scrubbing should not be such a drag. > > > > She concluded that the best thing to make it happen would be to show > > interrest for the open-sourcing of DV on this list. > > > > I know that lots of people don't care about the Design View (I rarely use > > it myself), but here are 4 reasons I think it could be a good move for > > Apache Flex: > > > > - DV is a great tool to understand the MXML paradigm, particularly for > > people coming for a Flash Pro background (timeline+stage), and its > removal > > would increase the barrier of entry to Flex. > > > > - I heard several times about devs for which the DV is central to their > > Flex workflow. It's often the case for heavy form-based application, > where > > standard Flex components are use exclusively and the Design View help > > avoiding "design re-compilation". > > In fact, I was told by an Adobe enterprise evangelist that he sold Flex > to > > some big companies mainly because of the Design View and the ease they > see > > in it to train their employees. > > > > - DV can be really helpful when designing Mobile apps, because you can > > test quickly your design with different resolutions and orientations > > > > - If we have access to the Design View code, maybe we could improve it in > > a way that even current Design View haters would use it ;) > > > > Dimitri K. > > > -- Best regards, Sebastian Mohr Adobe Flex Developer, Interaction Designer & Software Architect http://www.linkedin.com/in/masuland Mobile Belgium: +32 (0) 48 887 55 22 Mobile Germany: +49 (0) 170 722 24 87 Skype name: masuland
