Sorry the formatting of my post seems to have gone. Hope it's still kind of readable
-----Original Message----- From: Glenn Williams [mailto:i...@tinylion.co.uk] Sent: 22 February 2012 14:14 To: flex-dev@incubator.apache.org Subject: RE: Adobe might think of open-sourcing the Design View if there is sufficient interest I think the point the 'experienced user' dont use DV is only true because DV was and is basically broken. I would have used it if: When I clicked into DV it actually did display what that part of my project looked like When I clicked into DV I didnt just get a 'broken image' and a list of reason why DV can't render my project If I could select a component skin and click DV and get a view of just that skin with its default sizes and then change colours\gradients sub component positions That I could click into DV and then toggle through page or component states and actually see that same think I would see if I ran the app. Basically if when I pressed DV in anything other than a couple of screens test app that it actually displayed the same thing that I would see when running the app itself IMO it's not that a DV isnt useful to even the most experienced users is just that the incarnation of DV thats in builder just doesnt work. I can think of 1000s of times that I would have liked to quickly be able to view a page or component or a skin and either modify it slightly with design tools or just get a visual confirmation that the code I'd just written was doing what I expected it to regarding UI I think the question of if a DV is useful shouldnt be being based on the DV as it is now, which is patently not useful, but on a DV that actually worked. I really think even the most experienced user would like a single button press that would show them an accurate rendering of the page of source they were viewing -----Original Message----- From: piter...@gmail.com [mailto:piter...@gmail.com] On Behalf Of Peter HO Sent: 22 February 2012 10:28 To: flex-dev@incubator.apache.org Subject: Re: Adobe might think of open-sourcing the Design View if there is sufficient interest I add my vote to this thread. Even if most of us "experienced flexers" don't use it very often, design view is useful for beginners and for mobile application layouting. +1 for me Peter On 22 February 2012 11:17, Jason Batten <i...@jasonbatten.com> wrote: > Another +1, it's good for quick wireframes and getting started > > > > On 22/02/2012 6:14 PM, Bruce Lane wrote: > >> Right, Design View is very important to learn the Flex components >> behaviours. >> +1 >> Bruce Lane >> >> On 22 February 2012 11:11, Avinash >> Narayanan<avinashapr9@gmail.**com<avinashapr9@gmai l.com>> >> wrote: >> >>> I completely agree. I personally loved the design view alot >>> especially when I first started out since I had no idea what flex >>> was all about. Its also brilliant for understanding the various >>> containers, components etc from a learning perspective. definitely a >>> +1 from my side. >>> >>> Thanks >>> Avinash Y >>> >>> >>> On Wed, Feb 22, 2012 at 3:33 PM, Dimitri k.<k...@noos.fr> wrote: >>> >>> 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. >>>> >>>>
