It may bring some confusion if you will have in one package -bin-js-swf and
-bin-flexjs - I see questions - what is doing this and this. We should stay
with js-swf or flexjs.
If you stay with the idea of copying to flexjs some thing I would be for
copying js-swf, for sure not jsonly package.
Hi Piotr,
just done right now
thanks
2018-01-14 13:49 GMT+01:00 Piotr Zarzycki :
> Carlos,
>
> I'm still thinking that maybe Getting Started should be in the main menu
> and Try It Now more hidden. - It's not ready yet.
>
> Thanks, Piotr
>
> 2018-01-14 13:46 GMT+01:00
Carlos,
I'm still thinking that maybe Getting Started should be in the main menu
and Try It Now more hidden. - It's not ready yet.
Thanks, Piotr
2018-01-14 13:46 GMT+01:00 Carlos Rovira :
> Hi, if you want that I help inserting something in "Getting Started" let me
>
Hi, if you want that I help inserting something in "Getting Started" let me
about the text and where to insert it.
You can as well insert it yourself if you want. Choose whatever you feel
more confortable
thanks
2018-01-12 18:29 GMT+01:00 Piotr Zarzycki :
> Alex,
>
>
Alex,
I don't have such problems in case of jsonly package. Agree that it have to
be in the Readme and Getting Started.
Readme talking only about building Royale, but definitely have to have
section how to use it.
I'm ok with both options Flexjs and output. In case of that I'm for voting.
If you grab the jsonly package do you have the same problem?
Maybe we need to change the package names. I realized the other day that
I originally proposed to put 'flexjs' in the package name and hadn't
gotten around to that. Then we also discussed putting output format in
the package names.