You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2013/01/29 18:58:08 UTC
Should the compiler also fix up the HTML wrapper?
Any objections to adding a feature to Falcon/FalconJS/FalconJX to take additional arguments and fix up the HTML wrapper (or –app.xml for AIR)? I know compilers really should just compile, but the compiler knows much of the information that needs to be substituted into those files.
For Falcon, I would add an option like –html.template=<path to html template> and –air.template=<path to –app.xml template>
FalconJS/FalconJX would also support –js.source-path=<path to more JS source> to point to the framework (and goog if we use that) files.
Thoughts?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Should the compiler also fix up the HTML wrapper?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
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
<ap...@teotigraphix.com> 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 <ah...@adobe.com>:
>
>>
>>
>>
>> On 1/29/13 10:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> 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
Re: Should the compiler also fix up the HTML wrapper?
Posted by Alex Harui <ah...@adobe.com>.
On 1/29/13 10:20 AM, "Michael Schmalle" <ap...@teotigraphix.com> 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.
>
I was unable to follow that thread. I don't think we have three compilers
right now. MXMLC and COMPC are pretty small front-ends to a common set of
classes and have their own configuration options. What isn't modular about
that?
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Should the compiler also fix up the HTML wrapper?
Posted by Michael Schmalle <ap...@teotigraphix.com>.
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 <ah...@adobe.com>:
>
>
>
> On 1/29/13 10:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> 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
Re: Should the compiler also fix up the HTML wrapper?
Posted by Alex Harui <ah...@adobe.com>.
On 1/29/13 10:06 AM, "Erik de Bruin" <er...@ixsoftware.nl> 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
Re: Should the compiler also fix up the HTML wrapper?
Posted by Erik de Bruin <er...@ixsoftware.nl>.
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?
EdB
On Tue, Jan 29, 2013 at 6:58 PM, Alex Harui <ah...@adobe.com> wrote:
> Any objections to adding a feature to Falcon/FalconJS/FalconJX to take additional arguments and fix up the HTML wrapper (or –app.xml for AIR)? I know compilers really should just compile, but the compiler knows much of the information that needs to be substituted into those files.
>
> For Falcon, I would add an option like –html.template=<path to html template> and –air.template=<path to –app.xml template>
>
> FalconJS/FalconJX would also support –js.source-path=<path to more JS source> to point to the framework (and goog if we use that) files.
>
> Thoughts?
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl