You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Olaf Krueger <ma...@olafkrueger.net> on 2018/01/05 07:20:56 UTC
Developer experience / compilation process
Hi,
I am curious about others experience regarding your developer experience:
What I am doing all the time in a loop is changing a bit of the code,
compiling, waiting..., checking the output, next iteration.
BTW, this is the same with Flex but because I am less experienced with
Royale I need to compile a bit more.
If I remember it corrrectly the compilation process was already optimized in
the past so I wonder if there's still potential to improve it or if there
are basically other possibilities to get a faster result.
(I also remember that Alex had worked on a Live editor POC which was
promising)
I know there are tons of other tasks at the moment so for now, I am still
interested what your experience is or if somebody has tips or ideas how to
improve this 'workflow'.
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Developer experience / compilation process
Posted by Carlos Rovira <ca...@apache.org>.
That's right :)
7 secs are very good...30sec for a little app it's not, if you didn't have
that solution that will be a real problem ;)
2018-01-06 20:12 GMT+01:00 Olaf Krueger <ma...@olafkrueger.net>:
> After setting -debug=true in Moonshine the compilation time for our little
> TryItNow app decreases from approximately 30s to 7s, ... I just forgot
> about
> this compiler option since using/testing Moonshine.
>
> >As always, I want to order things by priority...
> I agree and it's of for me now ;-)
>
> Thanks,
> Olaf
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Developer experience / compilation process
Posted by Olaf Krueger <ma...@olafkrueger.net>.
After setting -debug=true in Moonshine the compilation time for our little
TryItNow app decreases from approximately 30s to 7s, ... I just forgot about
this compiler option since using/testing Moonshine.
>As always, I want to order things by priority...
I agree and it's of for me now ;-)
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Developer experience / compilation process
Posted by Carlos Rovira <ca...@apache.org>.
When I was developing MDL library, I was with debug= true and for me
compilation was quick.
When I tried things this months here and there I don't think it was slow.
So for me this could be something to look later.
As always, I want to order things by priority and we should attack what we
don't already have yet that improve something that is already working
that's always my strategy in all lines of work for a project that is not
100% in all its features
My 2 ctns :)
2018-01-05 22:17 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> The compiler has not been optimized at all. It was a full rewrite to use
> a different (and more traditional) parsing front-end, but the SWF output
> also uses a newer and unproven technology, and the JS output was written
> at Apache and has not been optimized at all.
>
> I'm quite certain the compiler could be made faster, but we don't have the
> people power to do it. I think the -debug=true compile time is sufficient
> for now and we have bigger fish to fry. But if you are having unexpected
> slowness, we should take a look.
>
> The MXML Live Editor might be a better and easier place to spend some
> energy. Any volunteers?
>
> -Alex
>
> On 1/5/18, 12:56 PM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>
> >>If you compile using debug=true and only JSRoyale
> >That's a good hint, I am currently testing Moonshine and I guess I forgot
> >about this...
> >
> >>Developing that more would be a nice project at some point
> >Agree :-)
> >
> >Thanks,
> >Olaf
> >
> >
> >
> >
> >
> >--
> >Sent from:
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-roy
> >ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com
> %7
> >C642afdeb569f440a7b4408d5547ed595%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7
> >C0%7C636507826090204102&sdata=vDLa6fYw3cBODwDcxO0szDWUIncIgy
> Vv8HDUR5kPWgQ%
> >3D&reserved=0
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Developer experience / compilation process
Posted by Alex Harui <ah...@adobe.com.INVALID>.
The compiler has not been optimized at all. It was a full rewrite to use
a different (and more traditional) parsing front-end, but the SWF output
also uses a newer and unproven technology, and the JS output was written
at Apache and has not been optimized at all.
I'm quite certain the compiler could be made faster, but we don't have the
people power to do it. I think the -debug=true compile time is sufficient
for now and we have bigger fish to fry. But if you are having unexpected
slowness, we should take a look.
The MXML Live Editor might be a better and easier place to spend some
energy. Any volunteers?
-Alex
On 1/5/18, 12:56 PM, "Olaf Krueger" <ma...@olafkrueger.net> wrote:
>>If you compile using debug=true and only JSRoyale
>That's a good hint, I am currently testing Moonshine and I guess I forgot
>about this...
>
>>Developing that more would be a nice project at some point
>Agree :-)
>
>Thanks,
>Olaf
>
>
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C642afdeb569f440a7b4408d5547ed595%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636507826090204102&sdata=vDLa6fYw3cBODwDcxO0szDWUIncIgyVv8HDUR5kPWgQ%
>3D&reserved=0
Re: Developer experience / compilation process
Posted by Olaf Krueger <ma...@olafkrueger.net>.
>If you compile using debug=true and only JSRoyale
That's a good hint, I am currently testing Moonshine and I guess I forgot
about this...
>Developing that more would be a nice project at some point
Agree :-)
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Developer experience / compilation process
Posted by Gabe Harbs <ha...@gmail.com>.
If you compile using debug=true and only JSRoyale, the compile times should be very fast. Even very large apps take me less than 10 seconds for a debug build.
Make sure you don’t clean between compiles, because that adds on time.
Alex at one point created a POC for live reload when apps are rebuilt. Developing that more would be a nice project at some point.
HTH,
Harbs
> On Jan 5, 2018, at 2:01 PM, Olaf Krueger <ma...@olafkrueger.net> wrote:
>
>> Do you think that could be improved? how?
>
> A near real-time compilation would increase productivity a lot :-)))
> But joking aside, I just would like to make sure that I don't miss
> something, e.g. additional compiler arguments to speed up the compilation
> process or whatever other things that increase the compilation time.
>
> Thanks,
> Olaf
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Developer experience / compilation process
Posted by Olaf Krueger <ma...@olafkrueger.net>.
>Do you think that could be improved? how?
A near real-time compilation would increase productivity a lot :-)))
But joking aside, I just would like to make sure that I don't miss
something, e.g. additional compiler arguments to speed up the compilation
process or whatever other things that increase the compilation time.
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Developer experience / compilation process
Posted by Carlos Rovira <ca...@apache.org>.
Hi Olaf,
that's what I do. If I'm developing something in Royale framework, I
compile as well the libraries affected.
But that's basically the workflow for me too.
Do you think that could be improved? how?
thanks!
2018-01-05 8:20 GMT+01:00 Olaf Krueger <ma...@olafkrueger.net>:
> Hi,
> I am curious about others experience regarding your developer experience:
>
> What I am doing all the time in a loop is changing a bit of the code,
> compiling, waiting..., checking the output, next iteration.
> BTW, this is the same with Flex but because I am less experienced with
> Royale I need to compile a bit more.
>
> If I remember it corrrectly the compilation process was already optimized
> in
> the past so I wonder if there's still potential to improve it or if there
> are basically other possibilities to get a faster result.
> (I also remember that Alex had worked on a Live editor POC which was
> promising)
>
> I know there are tons of other tasks at the moment so for now, I am still
> interested what your experience is or if somebody has tips or ideas how to
> improve this 'workflow'.
>
> Thanks,
> Olaf
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Carlos Rovira
http://about.me/carlosrovira