framework is in
> >>place,
> >> >>>>>>>>in
> >> >>>>> case
> >> >>>>>>>> of Maven during release process three repositories will land as
> >> >>> staging
> >> >>>>>>>> artifacts and we can vote.
&
gt;>>>>>
>> >>>>>>>> 2017-11-15 8:09 GMT+01:00 Alex Harui
>><aha...@adobe.com.invalid>:
>> >>>>>>>>
>> >>>>>>>>> Royale will be using artifacts from royale-compiler, not
>> >>> flex-falcon.
>&g
;>>> Maven and Ant work together to create all of the artifacts so
> >>>>>>>>>making
> >>>>>>>>> other
> >>>>>>>>> adjustments for npm is an option too. Maybe the first question
> >>>>>>&
;>>>>is:
>>>>> how
>>>>>>>>> many vote threads do we want? I believe eventually we rate of
>>> change
>>>>> in
>>>>>>>>> royale-compiler will slow compared to ro
akash
>>>>>>>> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com>
>>>> wrote:
>>>>>>>>
>>>>>>>>> I'm in the middle of updating the npm scripts. Are we planning t
lanning to
> >>>>>>> continue
> >>>>>>> to download flex-falcon from the current release? Or are we
> planning
> >>>>>> on
> >>>>>>> pushing out a new release of falcon/royale-compiler?
> >>>
gt;>> -Alex
> >>>>>>
> >>>>>> On 11/13/17, 12:50 AM, "Harbs" <harbs.li...@gmail.com> wrote:
> >>>>>>
> >>>>>>> Sounds good.
> >>>>>>>
> >>&
; >> >> BTW, I just realized that we don't have a royale-utilities git
> >>repo.
> >> >> I
> >> >> >>am
> >> >> >> tempted to simply put the npm related code into royale-asjs/npm
> >> >> >>directory
> >> >> >> and add it as an ex
?
>> >> >>
>> >> >> Thanks,
>> >> >> Om
>> >> >>
>> >> >> On Sun, Nov 12, 2017 at 1:58 PM, Harbs <harbs.li...@gmail.com>
>> wrote:
>> >> >>
>> >> >>> If you
t 0.10.0, I think it’s pretty clear.
> >> >>>
> >> >>>> On Nov 12, 2017, at 11:46 PM, Idylog - Nicolas Granon <
> >> >>> ngra...@idylog.com> wrote:
> >> >>>>
> >> >>>> In develop
t; >> >> Om
> >> >>
> >> >> On Sun, Nov 12, 2017 at 1:58 PM, Harbs <harbs.li...@gmail.com>
> wrote:
> >> >>
> >> >>> If you call it 0.10.0, I think it’s pretty clear.
> >> >>>
> >> >>>> On Nov
;>>>> I'm working on the website content and want to know
>>about
>> >>>>>>>>>>>>>>>>> NPM
>> >>>>>>>>>> to
>> >>>>>>>>>>>>>>>>> upd
t;>>
> >>>> On Nov 12, 2017, at 11:46 PM, Idylog - Nicolas Granon <
> >>> ngra...@idylog.com> wrote:
> >>>>
> >>>> In developer's eyes, "0.10" is "lower" than "0.9".
> >>>>
> >>>> You'd b
t; people.
>>>>>>>>>>>>>> If
>>>>>>>>>>>>>>>> I
>>>>>>>>>>>>>>>>> came to this project for the first time, and try to
>>>> search
>>>>>
better number it as "0.91".
> >
> > Nicolas Granon
> >
> >
> >
> >> -Message d'origine-
> >> De : Harbs [mailto:harbs.li...@gmail.com]
> >> Envoyé : dimanche 12 novembre 2017 10:15
> >> À : dev@royale.apache.org
>
gt;
> Nicolas Granon
>
>
>
>> -Message d'origine-
>> De : Harbs [mailto:harbs.li...@gmail.com]
>> Envoyé : dimanche 12 novembre 2017 10:15
>> À : dev@royale.apache.org
>> Objet : Re: Publishing royale to npm
>>
>> We’ve fixe
In developer's eyes, "0.10" is "lower" than "0.9".
You'd better number it as "0.91".
Nicolas Granon
> -Message d'origine-
> De : Harbs [mailto:harbs.li...@gmail.com]
> Envoyé : dimanche 12 novembre 2017 10:15
> À : dev@roya
quot;npm install" downloads a tarball from npmjs.org.
>> The
>>>>>>>>>>>>>>>> package
>>>>>>>>>>>>>>> usually
>>>>>>>>>>>>>>>> contains the c
gt; >> >>>>>>>> our
> > >> >> >>>>>>>>> non-npmjs.org dependencies (royale sdk, fonts, flash
> > >>player,
> > >> >> air,
> > >> >> >>>>>&
gt;>>> 2. Publish only the jsonly package.
>> >> >>>>>>>>> Then the command the users would run would look like:
>> >> >>>>>>>>> npm install royale-jsonly -g
>> >> >>>>>>>>>
>> >>
>>
> >> >>>>>>>>> Then the command the users would run would (possibly) look
> >>like:
> >> >>>>>>>>> npm install royale -- -include-swf-support -g
> >> >>>>>&
sonly -g
>> >>>>>>>>> and then
>> >>>>>>>>> ./update-royale-include-swf-support
>> >>>>>>>>>
>> >>>>>>>>> In all three cases, we can definitely run a script that alters
>>
> <aha...@adobe.com.invalid
> >>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Om,
> >>>>>>>>>>
> >>>>>>>>>
gt;>> work
>>>>>>>>> in Moonshine and VSCode, but to fully make it work in Flash Builder
>>>>>> (and
>>>>>>>>> maybe some other IDEs) you will need to run a script of some sort
>>>>>> that
>>>>>&
;>> (and
> > >>>>>>> maybe some other IDEs) you will need to run a script of some sort
> > >>>> that
> > >>>>>>> fixes up some FB launch configurations that convert Flex projects
> > >> to
> > >>>&g
; >>>>>>> Royale projects.
> >>>>>>>
> >>>>>>> The current plan for a "FlexJS" package that has SWF support (for
> >>>> users
> >>>>>>> that want use SWF for testing or as a migrati
pt to bring down Adobe
>>>>>>> dependencies. I'm thinking we won't use the Flex installer.
>>>>>>>
>>>>>>> I'm still working through why one of our users isn't getting code
>>>>>>> completion working in FB and the an
; >> packages (flexjs-with-swf-support and js-only), whether NPM allows
> >> us to
> >> > >> have two different packages or whether it is better to structure
> NPM
> >> > >> releases as js-only package and a swf-support-add-on package.
> >> &
>> up
>> > >> those launch configs. Maybe it is better to continue to leave them
>> as
>> > "FB
>> > >> users have to run this additional Ant script" or something like that.
>> > I'm
>> > >> not sure how important
<archeme...@mac.com>
Sent: Monday, October 30, 2017 11:46:44 AM
To: dev@royale.apache.org
Subject: Re: Publishing royale to npm
Just as an outsider: isn’t the whole point of royale to get rid of flash
dependency? I’m eagerly waiting for the first full royale release to finally
start convert
Just as an outsider: isn’t the whole point of royale to get rid of flash
dependency? I’m eagerly waiting for the first full royale release to finally
start converting my projects to html/js but the last thing I want is any
dependency towards flash/swf. So I’m in favor of a jsonly package
Dany
31 matches
Mail list logo
