Re: Last few problems converting browser project to JS

Oh yes of course, silly me. I've actually used this method to replace missing parameters like 'data' in lots of other places in the app. Many thanks for all your help. Doug -- Sent from: http://apache-royale-users.20374.n8.nabble.com/

Re: Last few problems converting browser project to JS

Good idea. I’ll try to do that… > On Mar 8, 2018, at 9:04 PM, Alex Harui wrote: > > It would be great to identify a bead from this pattern so others can just > drop a bead in their code instead of having to add a parameter and use > bracket access. > > I forgot that

Re: Last few problems converting browser project to JS

It would be great to identify a bead from this pattern so others can just drop a bead in their code instead of having to add a parameter and use bracket access. I forgot that EscapedFragmentBead extends URLParameterBead. The URLParameter bead currently just returns the entire query string, but

Re: Last few problems converting browser project to JS

Just add the following to your main class: public var parameters:Object; Also: Make sure you use bracket access (i.e. this.parameters[“anything”] instead of this.parameters.anything) to the parameters var to prevent renaming problems when it’s minified. HTH, Harbs > On Mar 8, 2018, at 3:48

Re: Last few problems converting browser project to JS

> On Mar 7, 2018, at 5:35 AM, doug777 wrote: > > I have almost finished converting my old Flex browser app to FlexJS (js > only), but I have 4 problems left that I can't find a way to convert. Can > anyone help to suggest a way to go with these items? > > 1.

Re: Last few problems converting browser project to JS

Hi, > It will work, but IMO it is a bit of a hack. No real need to add a class > to your app just to inject HTML in your app. It reads well in the application I think which counts for something, I’m sure there are many other ways of doing the same thing. > That's why we have the

Re: Last few problems converting browser project to JS

It will work, but IMO it is a bit of a hack. No real need to add a class to your app just to inject HTML in your app. That's why we have the -html-template compiler option. Normally inject_html is used to inject HTML needed to operate the rest of the code in the class. Not sure it makes sense

Re: Last few problems converting browser project to JS

Cool! I just wanted to have clarification. Maybe Royale JS only ;) Not sure. I'm really happy that you were able to goes so far and you are using Moonshine. :) Thanks, Piotr 2018-03-07 7:10 GMT+01:00 doug777 : > Piotr > > I guarantee everything is Royale - I just wanted

Re: Last few problems converting browser project to JS

Hi Piotr, I hope I can do that but I think I'm still some way from finishing. Although I've been testing snippets as I've gone along, I'm pretty sure there will still be lots of problems once it all has to work together. But I can't test that till I can get the whole thing to compile. But having

Re: Last few problems converting browser project to JS

I'll certainly give that a try. Thanks very much Justin. Doug -- Sent from: http://apache-royale-users.20374.n8.nabble.com/

Re: Last few problems converting browser project to JS

Hi, Sorry this bounced, so my emails will be out of order, trying again. > Re EmbedFont : Actually it's not that important. We use it to get special > characters In that case something like this may work: ... In fonts/Catamara.as package fonts { import

Re: Last few problems converting browser project to JS

Hi Doug, Great to hear that! Once you finished and if it will be possible share with us link, screens etc. Maybe we can place it somewhere as a great news. :) Thanks, Piotr On Wed, Mar 7, 2018, 05:47 doug777 wrote: > Ok that is all very helpful. > > Thanks so much, Alex.