Also, the Closure Compiler has plenty of configuration options (not in the least the level of optimisation). The various output types might want/need to make their calls differently. The solution we're looking for should take that into account, if possible.
EdB On Tue, Jan 29, 2013 at 7:20 PM, Michael Schmalle <[email protected]> wrote: > If you view a discussion started by Roland and commented on by myself, you > will see that configuration is what we are after and FLEXC compiler will > answer this question. > > Yeah, I know... head in the clouds, but this is the EXACT reason we are > going to do what we were talking about with a modular compiler. It's > ridiculous to even ask this question and then go implement it in 3 different > compilers. > > Mike > > > Quoting Alex Harui <[email protected]>: > >> >> >> >> On 1/29/13 10:06 AM, "Erik de Bruin" <[email protected]> wrote: >> >>> I agree that building everything in one command should be the goal. I >>> do not think that HTML should be part of the compiler. Isn't there a >>> way to wrap both the compile step and the HTML generation into one >>> script, like I did in ant with the publisher, but maybe in an extended >>> version of MXMLC? >> >> Yes, but then you have to duplicate the parsing of the MXML file to >> determine things like app dimensions that go in the templates. >> >> I'm not fond of having ANT be a requirement. For shell scripts, I might >> be >> able to use sed/awk but I don't know how to do that on Windows, and I >> don't >> want to make Cygwin a requirement either. >> >> Maybe I'll play around with a java app that calls MXMLC and can get back >> the >> information it needs and then updates the wrappers. >> >> -- >> Alex Harui >> Flex SDK Team >> Adobe Systems, Inc. >> http://blogs.adobe.com/aharui >> >> > > -- > Michael Schmalle - Teoti Graphix, LLC > http://www.teotigraphix.com > http://blog.teotigraphix.com > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
