The interesting question here is whether the compiler should somehow help
the generation of the html wrapper since the compiler knows some
information that the developer would otherwise have to duplicate, such as
the width, height, and potentially the title and maybe other properties.
These are MXML properties and the compiler can automatically see that you
set width="500" or width="100$" and copy that to the output.  Otherwise,
if you decide to change your width to 700, you will have to change it in
two places.

-Alex 

On 12/5/16, 2:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
<carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:

>We should think if compiler should make the task of process the
>html...maybe this is a task for build systems (maven, ant,...)
>Since there's much to do, maybe we could left this issue for later since
>right now the problem is solved...
>
>2016-12-05 9:26 GMT+01:00 Christofer Dutz <christofer.d...@c-ware.de>:
>
>> Hi Guys,
>>
>> well in general „Yes“ the order in which things are done in Maven is:
>> - Generate Resources
>> - Process Resources
>> - Compile
>>
>> Unfortunately the falcon compiler also does some sort of generate and
>> process within the compile phase. It would be great if we could split
>>this
>> up so we could have a generate resources, that does the part that was
>>part
>> of the compiler logic (Or provide a custom template) and use the maven
>> parts for this.
>>
>> Maven would replace ${header} and ${body}, if you would define
>>properties
>> with the name „header“ and „body“, but I don’t know if this makes sense.
>>
>> Chris
>>
>>
>> Am 01.12.16, 23:58 schrieb "carlos.rov...@gmail.com im Auftrag von
>>Carlos
>> Rovira" <carlos.rov...@gmail.com im Auftrag von
>> carlos.rov...@codeoscopic.com>:
>>
>>     That make the trick! Thanks Alex! :)
>>     Now MDLExample could be customized with this:
>>     https://getmdl.io/customize/index.html
>>     using the two vars is pom.xml suited for that task :)
>>
>>     2016-12-01 23:51 GMT+01:00 Alex Harui <aha...@adobe.com>:
>>
>>     >
>>     >
>>     > On 12/1/16, 2:32 PM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>>     > <carlos.rov...@gmail.com on behalf of
>>carlos.rov...@codeoscopic.com>
>>     > wrote:
>>     >
>>     > >Ok,
>>     > >
>>     > >so let say I have
>>     > >
>>     > ><htmlTemplate>${basedir}/src/main/resources/mdl-js-index-
>>     > template.html</ht
>>     > >mlTemplate>
>>     > >
>>     > >so "mdl-js-index-template.html" is the file processed by the
>> compiler,
>>     > >that
>>     > >file does not have the vars "primary" and "accent" inside (since
>>it
>> will
>>     > >be
>>     > >overridden) and so this will not be used.
>>     > >
>>     > >If I create another file (i.e: index.html) with the same code as
>>     > >"mdl-js-index-template.html", but with the vars ${primary} and
>> ${accent},
>>     > >I
>>     > >will get translated since is in resource folder, but the ones
>>from
>>     > >compiler
>>     > >${header}, ${body} will not processed right?
>>     > >
>>     >
>>     > AIUI, ${header} and ${body} will not be processed by the Maven
>> resource
>>     > plugin.  I don't know much about Maven, but don't you get to tell
>>the
>>     > resource plugin where to put the resulting file?  Like
>>     > target/resources/mdl-js-index-template.html?  If so, then you
>>would
>> use
>>     > the resource plugin to grab src/main/resources/mdl-js-
>> index-template.html,
>>     > fill in "primary" and "accent" and put it in
>>     > target/resources/mdl-js-index-template.html then use the
>> -html-template
>>     > config for the compiler to have it look in target/resources
>>instead
>> of
>>     > src/main/resources and the compiler should pick that up, fill in
>> ${header}
>>     > and ${body} and put the results in target/index.html.
>>     >
>>     > Of course, I could be wrong, especially about what the resource
>> plug-in
>>     > will let you do.
>>     >
>>     > -Alex
>>     >
>>     >
>>
>>
>>     --
>>
>>     Carlos Rovira
>>     Director General
>>     M: +34 607 22 60 05
>>     http://www.codeoscopic.com
>>     http://www.avant2.es
>>
>>     Este mensaje se dirige exclusivamente a su destinatario y puede
>> contener
>>     información privilegiada o confidencial. Si ha recibido este mensaje
>> por
>>     error, le rogamos que nos lo comunique inmediatamente por esta misma
>> vía y
>>     proceda a su destrucción.
>>
>>     De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>> comunicamos
>>     que sus datos forman parte de un fichero cuyo responsable es
>> CODEOSCOPIC
>>     S.A. La finalidad de dicho tratamiento es facilitar la prestación
>>del
>>     servicio o información solicitados, teniendo usted derecho de
>>acceso,
>>     rectificación, cancelación y oposición de sus datos dirigiéndose a
>> nuestras
>>     oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la
>>documentación
>>     necesaria.
>>
>>
>>
>
>
>-- 
>
>Carlos Rovira
>Director General
>M: +34 607 22 60 05
>http://www.codeoscopic.com
>http://www.avant2.es
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.

Reply via email to