> > Now if we get some revolution going with AS -> JS compiling that is not > using the Flash API, then it's time to really start thinking about a design > inspector. ;-)Now if we get some revolution going with AS -> JS compiling > that is not using the Flash API, then it's time to really start thinking > about a design inspector. ;-)
why is that compelling ? If I wanted to compile to JS in general why not use something like coffee-script that is elegant or use Appcelerator which has all the tooling there. AS -> JS , to me just seems like a way of porting away from AS. The reason why I care about Flex is because AIR runs on all the platforms I care about and secondarily yes, in general I like the framework. -Charles On Tue, Oct 2, 2012 at 10:13 AM, Michael Schmalle <apa...@teotigraphix.com>wrote: > I was going to say the exact same thing. > > I think why people have not said this is because a lot of developers are > used to a design view being located "inside" their IDE as with Design View. > > This is definitely not that hard to do, back in the Flex 2 days I > experimented in creating such tools in Flex. > > Thinking about it, I guess FlashCatalyst "wasn't" in and IDE perse so, the > paradigm of an external editor has been around. > > Seeing as Google's Android design view is decent in Eclipse, I don't see > why something couldn't be started in an IDE either. > > The trick is starting with something SMALL and prototype, get the idea to > work and slowly build on. You know, if I was actually making some type of > money from Flex right now I would consider this project but, my spare time > will be devoted to the compiler and extensions of. > > Now if we get some revolution going with AS -> JS compiling that is not >> using the Flash API, then it's time to really start thinking about a design >> inspector. ;-) > > > Mike > > > > Quoting Peter Ent <p...@adobe.com>: > > This is a good opportunity for [someone in] the Apache Flex community to >> develop such a tool. Using Apache Flex, an AIR app would be able to >> present UI components rendered correctly, in real-time, and be able to >> read and write local files. If Adobe does not contribute UI tools, the >> community can make their own. There are many talented people here with the >> background to do this. Of course, time and resources are probably the >> biggest constraints. >> >> Peter Ent >> Flex SDK Team >> Adobe Systems. >> >> On 10/2/12 6:52 AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote: >> >> Quoting Sebastian Mohr <masul...@gmail.com>: >>> >>> Nope ... I am seeing Flash Catalyst as being the representation for >>>> Adobe's work on the Spark-Component model, FXG and Flash Catalyst >>>> (formerly codenamed Thermo) with the Designer-Developer workflow >>>> started in 2007 [1]. For whatever reasons it took ages to finish it. >>>> >>> >>> >>> For the same reason the Spark component set isn't finished and the >>> same reason why Flex is now an Apache project and the same reason why >>> they axed design view in Flash Builder and the same reason they >>> renamed Flex Builder to Flash Builder. >>> >>> >>> -- >>> Michael Schmalle - Teoti Graphix, LLC >>> http://www.teotigraphix.com >>> http://blog.teotigraphix.com >>> >>> >> >> > -- > Michael Schmalle - Teoti Graphix, LLC > http://www.teotigraphix.com > http://blog.teotigraphix.com > > -- Charles A. Monteiro www.monteirosfusion.com sent from the road
