htmlTemplate is a compiler directive. In that way you customize the
index.html that loads you app. There's some tokens that compiler uses to
inject the js code that will load the royale app, so you can decorate the
html page. So this is "out" the application code and is normal html ok?

In the other hand, html:Div is an MXML tag and that's Royale code that you
can add as always using AS3/MXML in your code. You can combine it with
states, bindings, and many other things. You can see uses of HTML tags in
Tour de jewel too. So this way is normal Royale coding that happens
"inside" the royale application.




El dom., 21 jul. 2019 a las 20:46, gkk gb (<[email protected]>)
escribió:

> Thanks so much Carlos. Just to be sure, both methods below would work to
> insert into an existing website that was not created using Royale, right?
> That is, the Royale part of the web page (which can include view states,
> etc.) can get inserted within a set of tags, such as <htmlTemplate> or
> <html:Div> tags, directly into the Drupal-produced HTML code. Is that
> right?
>
> On July 21, 2019 at 11:17 AM Carlos Rovira <[email protected]>
> wrote:
>
> Hi,
>
> some options to do that:
>
> 1.- use htmlTemplate compiler option to add html to the html template that
> loads the app. Check Tour De Jewel. It uses it to setup fonts from google
>
> for example in Maven pom.xml you can see this line:
>
> < htmlTemplate 
> >${basedir}/target/javascript/bin/js-debug/jewel-example-index-template.html
> </ htmlTemplate >
>
> 2.- you can use JS API inside royale with HTML.swc adding for example
> <html:Div> tag and more, and then using CSS to make those div change
> visuals
>
> maybe others could imagine more ways to do that...
>
> HTH
>
> Carlos
>
>
>
> El dom., 21 jul. 2019 a las 2:17, gkk gb (< [email protected]>)
> escribió:
>
> The company I work for has a website that is created/maintained via Drupal
> templates, wherein all the web pages share the same header (navigation) and
> footer on every page.
>
>
> If I create a "web app" in Royale, can it integrate inside a pair of <div>
> ... </div> tags or other way so that it just inserts into one part of the
> web page in a self-contained manner? If so, how does that work in practice?
>
>
> Or, must I place the web app elsewhere on the website and then use an
> IFrame (I prefer not) to make it sit nicely inside an existing webpage with
> corporate header and footer around it? The Tour de Jewel "View States"
> example gives me hope...
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to