Re: Apache Royale

[Alex Harui]

Google Translate says that Daniel said:

Dzień dobry, pracuję na przykładach z Apache royale w szczególności
Jewel, aby przeanalizować możliwość migracji naszego systemu
zrobione elastycznie wobec tej nowej platformy, ale mam problem, kiedy myślę
nowy projekt z wykorzystaniem maven'a tworzy projekt, ale nie mogę
Skompiluj, ponieważ brakuje mi pliku build.xml. Patrzyłem w
dokumentacja, ale nie znalazłem sposobu wygenerowania tego pliku. Czy możesz 
mnie wspierać?

Or in other words:

Good day, I'm working with the examples of Apache royale in particular
those of Jewel, to analyze the possibility of migrating our system in
done in flex to this new platform, but I have a problem, when I think
a new project using maven creates me the project, but I can not
Compile because I'm missing the build.xml file. I was looking in the
documentation but I did not find how to generate that file. Could you support 
me?

-Alex

On 9/20/18, 11:29 PM, "Piotr Zarzycki"  wrote:

Hi Alex,

That's true. I didn't have bat intention. I just wanted to understand all
of that.

Piotr

On Fri, Sep 21, 2018, 8:00 AM Alex Harui  wrote:

> Hi Piotr,
>
> IMO, it isn't required for the email to be in English.  Google Translate
> is good enough to translate for us if needed.  I only took one semester of
> Spanish lessons but I could tell this was about Royale and Jewel so it is
> fine if Carlos and Daniel communicate in Spanish.  We've had LIzhi send
> emails in Chinese.I don't want someone's skills in English to be a
> barrier to using or contributing to Royale.  Google Translate has worked
> for me in the past.
>
> My 2 cents,
> -Alex
>
> On 9/20/18, 9:46 PM, "Piotr Zarzycki"  wrote:
>
> Hi Daniel,
>
> It would be great if you could send that email in English. Most of the
> contributors doesn't know Spanish. :)
>
> Maybe Carlos can translate :)
>
> Thanks,
> Piotr
>
> On Fri, Sep 21, 2018, 12:35 AM Daniel Hernandez Alvarado <
> alvarado.programa...@gmail.com> wrote:
>
> > Buen dia, estoy trabajando con los ejemplos de Apache royale en
> especial
> > los de Jewel, para analizar la posibilidad de migrar nuestro sistema
> en
> > hecho en flex a esta nueva plataforma, pero tengo un problema,
> cuando creo
> > un nuevo proyecto usando maven me crea el projecto, pero no lo puedo
> > compilar por que me falta el archivo build.xml. Estube buscando en 
la
> > documentacion pero no encontre como generar ese archivo. ¿Me podrian
> > apoyar?
> >
> > --
> >
> > *Lic. en Sistemas ComputacionalesDaniel Hernández AlvaradoCel.
> > 937-126-45-70Hotmail: daniel_...@hotmail.com  > >Gmail:
> > alvarado.programa...@gmail.com  >Skype:
> > Daniel_h09*
> >
>
>
>

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[Piotr Zarzycki]

Hey Om,

If you have capacity please finish that release. Users of VSCode and
Moonshine will be happy!

Thanks,
Piotr

On Thu, Sep 20, 2018, 5:08 PM OmPrakash Muppirala 
wrote:

> The last time I tried to release, it was on  Windows PC.  Some tweaks were
> required.  Also, I would say that the release process was too automated 😊
> As a result I was not able to figure out what exaxtly broke, etc.
>
> FWIW, I have a Mac now.  I can try again if Piotr wants to take a break.
>
> Getting an automated release script working flawlessly takes multiple
> releases.  Remember, as with any software, such scripts will have bugs and
> we need to catch them and fix them.
>
> Unfortunately, one such bug was that for the 0.9.2 release, what got
> published to npm was versioned at 0.9.3.  We have since fixed that issue in
> our script.  But npm does not allow do overs for released artifacts.
>
> We have learnt our lesson, lets move on please ☺
>
> Thanks,
> Om
>
> On Thu, Sep 20, 2018, 12:53 AM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> > thanks you see it in the list of unread messages and will go to say that
> I
> > found it.
> > I'll take a look  now
> >
> >
> > El jue., 20 sept. 2018 a las 9:44, Alex Harui ( >)
> > escribió:
> >
> > >
> > >
> > > On 9/19/18, 11:49 PM, "Carlos Rovira" 
> wrote:
> > >
> > > Hi Alex,
> > >
> > > what Zend-AMF issue you refer? can you post the link to that issue?
> > > thanks
> > >
> > > https://lists.apache.org/list.html?us...@royale.apache.org
> > >
> > > PD: about your preoccupation, we'll have issues for many months to
> > > come. I
> > > see each day in Jewel as I go here and there fixing or completing
> > > issues I
> > > find, so I think is ok release with that issues so people can "play
> > > with
> > > the toy".
> > >
> > >
> > >
> > > So, my opinion is that, if someone what to release, we should not
> > wait
> > > for
> > > anything...we have many things to add, solve, fix, that one or two
> > > will not
> > > make a difference for me. As I said, maybe wait for release, could
> be
> > > worse
> > > in terms of potential users we can loose in that time.
> > >
> > > Of course there will be lots of issues to fix.  But some seem bigger
> than
> > > others, and IMO, make the difference between whether Royale leaves the
> > > impression of being a product or a toy.  If your app won't run because
> > the
> > > dependencies aren't right, or AMF doesn't work, will they help fix it,
> or
> > > wait, or go somewhere else?
> > >
> > > If you want to release now, then you have to promise to delay what you
> > > were planning to work on to handle new customer issues.  Because that's
> > > what always happens to me.   By waiting until Alina hits an important
> > > milestone helps keep a user we know and want to make successful.
> > >
> > > -Alex
> > >
> > >
> > >
> > >
> > > El jue., 20 sept. 2018 a las 2:47, Alex Harui
> > > ()
> > > escribió:
> > >
> > > > The key question for me is what Carlos wrote:  " I'm trying to
> fix
> > > and get
> > > > things as most usable as possible in
> > > > Jewel to avoid many changes post release"
> > > >
> > > > I always wonder if it helps or hurts to draw attention to the
> > > release when
> > > > we know there's good chance someone is going to hit a known bug.
> > > I'd like
> > > > to see if we can fix the issues brought up by some new users.
> Such
> > > as:
> > > >
> > > > 1)
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=0
> > > >
> > > > 2) the Zend-AMF issue.  A more robust AMF might be worth the
> wait.
> > > >
> > > > Those of you who want to release soon should promise to
> investigate
> > > any
> > > > dependency or AMF issues brought up by new users.  When we
> release
> > > with
> > > > issues like these, not only does it cost me the time to be the
> RM,
> > > but also
> > > > seems to cost me the time to investigate and respond to the
> issues
> > > brought
> > > > up afterwards.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 9/19/18, 2:59 PM, "Carlos Rovira" 
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I certainly can position clearly: Community is waiting and we
> > are
> > > > getting
> > > > momentum, each day we get 1-2 new people in twitter
> following,
> > > so it
> > > > seems
> > > > we are getting some traction. If we release now, those
> > > interested in
> > > > Royale
> > > > would finally start to get its hands dirty and try things,
> > > releasing
> > > > later
> > > > could make we loose that peop

Re: Apache Royale

[Piotr Zarzycki]

Hi Alex,

That's true. I didn't have bat intention. I just wanted to understand all
of that.

Piotr

On Fri, Sep 21, 2018, 8:00 AM Alex Harui  wrote:

> Hi Piotr,
>
> IMO, it isn't required for the email to be in English.  Google Translate
> is good enough to translate for us if needed.  I only took one semester of
> Spanish lessons but I could tell this was about Royale and Jewel so it is
> fine if Carlos and Daniel communicate in Spanish.  We've had LIzhi send
> emails in Chinese.I don't want someone's skills in English to be a
> barrier to using or contributing to Royale.  Google Translate has worked
> for me in the past.
>
> My 2 cents,
> -Alex
>
> On 9/20/18, 9:46 PM, "Piotr Zarzycki"  wrote:
>
> Hi Daniel,
>
> It would be great if you could send that email in English. Most of the
> contributors doesn't know Spanish. :)
>
> Maybe Carlos can translate :)
>
> Thanks,
> Piotr
>
> On Fri, Sep 21, 2018, 12:35 AM Daniel Hernandez Alvarado <
> alvarado.programa...@gmail.com> wrote:
>
> > Buen dia, estoy trabajando con los ejemplos de Apache royale en
> especial
> > los de Jewel, para analizar la posibilidad de migrar nuestro sistema
> en
> > hecho en flex a esta nueva plataforma, pero tengo un problema,
> cuando creo
> > un nuevo proyecto usando maven me crea el projecto, pero no lo puedo
> > compilar por que me falta el archivo build.xml. Estube buscando en la
> > documentacion pero no encontre como generar ese archivo. ¿Me podrian
> > apoyar?
> >
> > --
> >
> > *Lic. en Sistemas ComputacionalesDaniel Hernández AlvaradoCel.
> > 937-126-45-70Hotmail: daniel_...@hotmail.com  > >Gmail:
> > alvarado.programa...@gmail.com  >Skype:
> > Daniel_h09*
> >
>
>
>

Re: Apache Royale

[Alex Harui]

Hi Piotr,

IMO, it isn't required for the email to be in English.  Google Translate is 
good enough to translate for us if needed.  I only took one semester of Spanish 
lessons but I could tell this was about Royale and Jewel so it is fine if 
Carlos and Daniel communicate in Spanish.  We've had LIzhi send emails in 
Chinese.I don't want someone's skills in English to be a barrier to using 
or contributing to Royale.  Google Translate has worked for me in the past.

My 2 cents,
-Alex

On 9/20/18, 9:46 PM, "Piotr Zarzycki"  wrote:

Hi Daniel,

It would be great if you could send that email in English. Most of the
contributors doesn't know Spanish. :)

Maybe Carlos can translate :)

Thanks,
Piotr

On Fri, Sep 21, 2018, 12:35 AM Daniel Hernandez Alvarado <
alvarado.programa...@gmail.com> wrote:

> Buen dia, estoy trabajando con los ejemplos de Apache royale en especial
> los de Jewel, para analizar la posibilidad de migrar nuestro sistema en
> hecho en flex a esta nueva plataforma, pero tengo un problema, cuando creo
> un nuevo proyecto usando maven me crea el projecto, pero no lo puedo
> compilar por que me falta el archivo build.xml. Estube buscando en la
> documentacion pero no encontre como generar ese archivo. ¿Me podrian
> apoyar?
>
> --
>
> *Lic. en Sistemas ComputacionalesDaniel Hernández AlvaradoCel.
> 937-126-45-70Hotmail: daniel_...@hotmail.com  >Gmail:
> alvarado.programa...@gmail.com Skype:
> Daniel_h09*
>

Build failed in Jenkins: royale-typedefs #722

[apacheroyaleci]

See 


--
Started by timer
Building on master in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs.git # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress 
 > https://github.com/apache/royale-typedefs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 58667e73f672a2315d8acd15acf33aba7e2d193c 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 58667e73f672a2315d8acd15acf33aba7e2d193c
Commit message: "fix up versions"
 > git.exe rev-list --no-walk 58667e73f672a2315d8acd15acf33aba7e2d193c # 
 > timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat main && 
exit %%ERRORLEVEL%%"
Buildfile: 


main:

download:
 [echo] 

[mkdir] Created dir: 


BUILD FAILED
:54:
 The following error occurred while executing this line:
:86:
 src 
'
 doesn't exist.

Total time: 2 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xmx512m
Build step 'Invoke Ant' marked build as failure

Build failed in Jenkins: royale-asjs_jsonly #1585

[apacheroyaleci]

See 


--
[...truncated 139.91 KB...]

compiler.downloads:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

prepare:
 [echo] Making lib directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external

all:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//antlr.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-cli.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-io.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-lang-2.6.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//guava.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//jburg.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//jflex.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//lzma-sdk.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//flex-tool-api.jar

download-dependency:

main:

IASNodeAdapter:

main:

compiler.test.downloads.cache:

compiler.test.downloads:

prepare:

junit-jar-check:

Re: Apache Royale

[Piotr Zarzycki]

Hi Daniel,

It would be great if you could send that email in English. Most of the
contributors doesn't know Spanish. :)

Maybe Carlos can translate :)

Thanks,
Piotr

On Fri, Sep 21, 2018, 12:35 AM Daniel Hernandez Alvarado <
alvarado.programa...@gmail.com> wrote:

> Buen dia, estoy trabajando con los ejemplos de Apache royale en especial
> los de Jewel, para analizar la posibilidad de migrar nuestro sistema en
> hecho en flex a esta nueva plataforma, pero tengo un problema, cuando creo
> un nuevo proyecto usando maven me crea el projecto, pero no lo puedo
> compilar por que me falta el archivo build.xml. Estube buscando en la
> documentacion pero no encontre como generar ese archivo. ¿Me podrian
> apoyar?
>
> --
>
> *Lic. en Sistemas ComputacionalesDaniel Hernández AlvaradoCel.
> 937-126-45-70Hotmail: daniel_...@hotmail.com  >Gmail:
> alvarado.programa...@gmail.com Skype:
> Daniel_h09*
>

Build failed in Jenkins: royale-asjs #1365

[apacheroyaleci]

See 


Changes:

[aharui] change name so it isn't a duplicate

--
[...truncated 321.02 KB...]
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

fail-if-not-found:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

download-dependency-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-cache:

download-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

get-if-not-cached:
  [get] Getting: 
https://repo1.maven.org/maven2/com/google/guava/guava/20.0/guava-20.0.jar
  [get] To: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\lib\guava.jar
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

double-check-file:
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

fail-if-not-found:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-sum:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

put-in-cache:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

copy-if-cached:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

download-dependency-zip:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-dependency:

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

echo-project-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\lib\flex-tool-api-LICENSE.txt
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

double-check-file:
 [echo] Need file: ${still_no_fil

Jenkins build is back to normal : royale-asjs_jsonly #1584

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs_jsonly #1583

[apacheroyaleci]

See 


Changes:

[aharui] update some versions

[aharui] oops

[aharui] fix clean targets

--
[...truncated 89.64 KB...]
   [delete] Deleting: 


clean:
   [delete] Deleting: 


clean:
   [delete] Deleting: 


clean:
   [delete] Deleting: 


clean:
   [delete] Deleting directory 


package-clean:
   [delete] Deleting directory 


clean-temp:
   [delete] Deleting directory 


checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 

   [delete] Deleting directory 

   [delete] Deleting directory 

 [echo] ROYALE_HOME = 

 [echo] royalelib = 

 [echo] doc_output = 

 [echo] compiler.source-path = 


clean:

super-clean:
   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting: 

   [delete] Deleting: 

   [delete] Deleting: 

   [delete] Deleting: 

   [delete] Deleting: 

   [delete] Deleting: 

   [delete] Deleting: 


create-description:
 [echo] build.number is 20180921

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

creat

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[Alex Harui]

I made some adjustments to the repos so that they "should" be ready to run the 
scripts and produce the 0.9.4 release.  Of course, I could be wrong.  We'll see 
how Om fares.

I also put in a change that should fix the dependencies issue.  So the 
remaining questions are around the AMF problem.  I'm thinking of looking into 
what it takes to support Small Messages.  However, I don't know anything about 
them.  How often will migrating people be using Small Messages?  Is it fair to 
tell them to turn off Small Messages?

Thanks,
-Alex

On 9/20/18, 8:29 AM, "Carlos Rovira"  wrote:

Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)

Thanks!

Carlos



El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:

> The last time I tried to release, it was on  Windows PC.  Some tweaks were
> required.  Also, I would say that the release process was too automated 😊
> As a result I was not able to figure out what exaxtly broke, etc.
>
> FWIW, I have a Mac now.  I can try again if Piotr wants to take a break.
>
> Getting an automated release script working flawlessly takes multiple
> releases.  Remember, as with any software, such scripts will have bugs and
> we need to catch them and fix them.
>
> Unfortunately, one such bug was that for the 0.9.2 release, what got
> published to npm was versioned at 0.9.3.  We have since fixed that issue 
in
> our script.  But npm does not allow do overs for released artifacts.
>
> We have learnt our lesson, lets move on please ☺
>
> Thanks,
> Om
>
> On Thu, Sep 20, 2018, 12:53 AM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> > thanks you see it in the list of unread messages and will go to say that
> I
> > found it.
> > I'll take a look  now
> >
> >
> > El jue., 20 sept. 2018 a las 9:44, Alex Harui ( >)
> > escribió:
> >
> > >
> > >
> > > On 9/19/18, 11:49 PM, "Carlos Rovira" 
> wrote:
> > >
> > > Hi Alex,
> > >
> > > what Zend-AMF issue you refer? can you post the link to that 
issue?
> > > thanks
> > >
> > > 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Flist.html%3Fusers%40royale.apache.org&data=02%7C01%7Caharui%40adobe.com%7C7d734bb076fc4aa694eb08d61f0de787%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730541915655402&sdata=H72NLqj1sCExgvsb9ZSO7CYeh3uGh76saw1rkACEGtU%3D&reserved=0
> > >
> > > PD: about your preoccupation, we'll have issues for many months to
> > > come. I
> > > see each day in Jewel as I go here and there fixing or completing
> > > issues I
> > > find, so I think is ok release with that issues so people can 
"play
> > > with
> > > the toy".
> > >
> > >
> > >
> > > So, my opinion is that, if someone what to release, we should not
> > wait
> > > for
> > > anything...we have many things to add, solve, fix, that one or two
> > > will not
> > > make a difference for me. As I said, maybe wait for release, could
> be
> > > worse
> > > in terms of potential users we can loose in that time.
> > >
> > > Of course there will be lots of issues to fix.  But some seem bigger
> than
> > > others, and IMO, make the difference between whether Royale leaves the
> > > impression of being a product or a toy.  If your app won't run because
> > the
> > > dependencies aren't right, or AMF doesn't work, will they help fix it,
> or
> > > wait, or go somewhere else?
> > >
> > > If you want to release now, then you have to promise to delay what you
> > > were planning to work on to handle new customer issues.  Because 
that's
> > > what always happens to me.   By waiting until Alina hits an important
> > > milestone helps keep a user we know and want to make successful.
> > >
> > > -Alex
> > >
> > >
> > >
> > >
> > > El jue., 20 sept. 2018 a las 2:47, Alex Harui
> > > ()
> > > escribió:
> > >
> > > > The key question for me is what Carlos wrote:  " I'm trying to
> fix
> > > and get
> > > > things as most usable as possible in
> > > > Jewel to avoid many changes post release"
> > > >
> > > > I always wonder if it helps or hurts to draw attention to the
> > > release when
> > > > we know there's good chance someone is going to hit a known bug.
> > > I'd like
> > > > to see if we can fix the issues brought up by some new users.
> Such
> > > as:
> > > >
> > > > 1)
> > >
> >
> 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%

Apache Royale

[Daniel Hernandez Alvarado]

Buen dia, estoy trabajando con los ejemplos de Apache royale en especial
los de Jewel, para analizar la posibilidad de migrar nuestro sistema en
hecho en flex a esta nueva plataforma, pero tengo un problema, cuando creo
un nuevo proyecto usando maven me crea el projecto, pero no lo puedo
compilar por que me falta el archivo build.xml. Estube buscando en la
documentacion pero no encontre como generar ese archivo. ¿Me podrian apoyar?

-- 

*Lic. en Sistemas ComputacionalesDaniel Hernández AlvaradoCel.
937-126-45-70Hotmail: daniel_...@hotmail.com Gmail:
alvarado.programa...@gmail.com Skype:
Daniel_h09*

Jenkins build is back to normal : royale-asjs #1363

[apacheroyaleci]

See 

Jenkins build is back to normal : royale-asjs_jsonly #1581

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs #1362

[apacheroyaleci]

See 


Changes:

[carlosrovira] remove linear-gradient on dropdownlist until fix in compiler 
since iOS

--
[...truncated 722.68 KB...]
[junit] environment property - GOOG_HOME = null
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestAnnotationEnum
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] baz parameters not found!  0
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] baz parameters not found!  0
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.225 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestCollectImports
[junit] foo parameters not found!  0
[junit] API parameters not found!  0
[junit] BASE parameters not found!  0
[junit] foo parameters not found!  0
[junit] foo parameters not found!  0
[junit] foo parameters not found!  0
[junit] API parameters not found!  0
[junit] BASE parameters not found!  0
[junit] foo parameters not found!  0
[junit] foo parameters not found!  0
[junit] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.305 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestConstructor
[junit] FinalClass parameters not found!  0
[junit] FinalClass parameters not found!  0
[junit] FinalClass parameters not found!  0
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.074 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestExternChrome
[junit] Math parameters not found!  0
[junit] Reflect parameters not found!  0
[junit] chrome parameters not found!  0
[junit] app parameters not found!  0
[junit] webstore parameters not found!  0
[junit] runtime parameters not found!  0
[junit] Math parameters not found!  0
[junit] Reflect parameters not found!  0
[junit] chrome parameters not found!  0
[junit] app parameters not found!  0
[junit] webstore parameters not found!  0
[junit] runtime parameters not found!  0
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.852 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestExternES3
[junit] Math parameters not found!  0
[junit] Math parameters not found!  0
[junit] Math parameters not found!  0
[junit] Math parameters not found!  0
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.121 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestExternJSMissing
[junit] C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target\downloads
[junit] Math parameters not found!  0
[junit] C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target\downloads
[junit] Math parameters not found!  0
[junit] C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target\downloads
[junit] Math parameters not found!  0
[junit] C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target\downloads
[junit] Math parameters not found!  0
[junit] C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-externc\target\downloads
[junit] Math parameters not found!  0
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.356 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestPackageNamespace
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestReferenceModel
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.003 sec
[junit] Running 
org.apache.royale.compiler.internal.codegen.typedefs.TestTypeTypedefs
[junit] foo parameters not found!  0
[junit] bar parameters not found!  0
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.091 sec
[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xmx512m

main:

jar-test:
 [echo] using externc.jar from C:/Program Files 
(x86)/Jenkins/workspace/royale-compiler/compiler-jx/lib
 [java] Math parameters not found!  0
 [java] Reflect parameters not found!  0
 [java] chrome parameters not found!  0
 [java] app parameters not found!  0
 [java] webstore parameters not found!  0
 [java] runtime parameters not found!  0
 [java] Intl parameters not found!  0
 [java] 6.119177599 seconds
 [java] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xmx512m

download:
 [echo] basedir is C:\Program Files 
(x8

Build failed in Jenkins: royale-asjs_jsonly #1580

[apacheroyaleci]

See 


Changes:

[carlosrovira] remove linear-gradient on dropdownlist until fix in compiler 
since iOS

--
[...truncated 136.09 KB...]

unknown.tree.pattern.input.output:

main:

compiler.downloads.cache:

compiler.downloads:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

prepare:
 [echo] Making lib directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external

all:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//antlr.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-cli.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-io.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//commons-lang-2.6.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//guava.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//jburg.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//jflex.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler/lib/external//lzma-sdk.jar

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler

check-dependency:
 [echo] checking for C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[Carlos Rovira]

Hi Om,
that's great! :)
Hope you could take on the release and get it out of the door :)

Thanks!

Carlos



El jue., 20 sept. 2018 a las 17:08, OmPrakash Muppirala (<
bigosma...@gmail.com>) escribió:

> The last time I tried to release, it was on  Windows PC.  Some tweaks were
> required.  Also, I would say that the release process was too automated 😊
> As a result I was not able to figure out what exaxtly broke, etc.
>
> FWIW, I have a Mac now.  I can try again if Piotr wants to take a break.
>
> Getting an automated release script working flawlessly takes multiple
> releases.  Remember, as with any software, such scripts will have bugs and
> we need to catch them and fix them.
>
> Unfortunately, one such bug was that for the 0.9.2 release, what got
> published to npm was versioned at 0.9.3.  We have since fixed that issue in
> our script.  But npm does not allow do overs for released artifacts.
>
> We have learnt our lesson, lets move on please ☺
>
> Thanks,
> Om
>
> On Thu, Sep 20, 2018, 12:53 AM Carlos Rovira 
> wrote:
>
> > Hi Alex,
> > thanks you see it in the list of unread messages and will go to say that
> I
> > found it.
> > I'll take a look  now
> >
> >
> > El jue., 20 sept. 2018 a las 9:44, Alex Harui ( >)
> > escribió:
> >
> > >
> > >
> > > On 9/19/18, 11:49 PM, "Carlos Rovira" 
> wrote:
> > >
> > > Hi Alex,
> > >
> > > what Zend-AMF issue you refer? can you post the link to that issue?
> > > thanks
> > >
> > > https://lists.apache.org/list.html?us...@royale.apache.org
> > >
> > > PD: about your preoccupation, we'll have issues for many months to
> > > come. I
> > > see each day in Jewel as I go here and there fixing or completing
> > > issues I
> > > find, so I think is ok release with that issues so people can "play
> > > with
> > > the toy".
> > >
> > >
> > >
> > > So, my opinion is that, if someone what to release, we should not
> > wait
> > > for
> > > anything...we have many things to add, solve, fix, that one or two
> > > will not
> > > make a difference for me. As I said, maybe wait for release, could
> be
> > > worse
> > > in terms of potential users we can loose in that time.
> > >
> > > Of course there will be lots of issues to fix.  But some seem bigger
> than
> > > others, and IMO, make the difference between whether Royale leaves the
> > > impression of being a product or a toy.  If your app won't run because
> > the
> > > dependencies aren't right, or AMF doesn't work, will they help fix it,
> or
> > > wait, or go somewhere else?
> > >
> > > If you want to release now, then you have to promise to delay what you
> > > were planning to work on to handle new customer issues.  Because that's
> > > what always happens to me.   By waiting until Alina hits an important
> > > milestone helps keep a user we know and want to make successful.
> > >
> > > -Alex
> > >
> > >
> > >
> > >
> > > El jue., 20 sept. 2018 a las 2:47, Alex Harui
> > > ()
> > > escribió:
> > >
> > > > The key question for me is what Carlos wrote:  " I'm trying to
> fix
> > > and get
> > > > things as most usable as possible in
> > > > Jewel to avoid many changes post release"
> > > >
> > > > I always wonder if it helps or hurts to draw attention to the
> > > release when
> > > > we know there's good chance someone is going to hit a known bug.
> > > I'd like
> > > > to see if we can fix the issues brought up by some new users.
> Such
> > > as:
> > > >
> > > > 1)
> > >
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=0
> > > >
> > > > 2) the Zend-AMF issue.  A more robust AMF might be worth the
> wait.
> > > >
> > > > Those of you who want to release soon should promise to
> investigate
> > > any
> > > > dependency or AMF issues brought up by new users.  When we
> release
> > > with
> > > > issues like these, not only does it cost me the time to be the
> RM,
> > > but also
> > > > seems to cost me the time to investigate and respond to the
> issues
> > > brought
> > > > up afterwards.
> > > >
> > > > My 2 cents,
> > > > -Alex
> > > >
> > > > On 9/19/18, 2:59 PM, "Carlos Rovira" 
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I certainly can position clearly: Community is waiting and we
> > are
> > > > getting
> > > > momentum, each day we get 1-2 new people in twitter
> following,
> > > so it
> > > > seems
> > > > we are getting some traction. If we release now, those
> > > interested in
> > > > Royale
> > > > would finally start to get its hands dirty and try things,
> > > releasing
> > > > later
> > > > could

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[OmPrakash Muppirala]

The last time I tried to release, it was on  Windows PC.  Some tweaks were
required.  Also, I would say that the release process was too automated 😊
As a result I was not able to figure out what exaxtly broke, etc.

FWIW, I have a Mac now.  I can try again if Piotr wants to take a break.

Getting an automated release script working flawlessly takes multiple
releases.  Remember, as with any software, such scripts will have bugs and
we need to catch them and fix them.

Unfortunately, one such bug was that for the 0.9.2 release, what got
published to npm was versioned at 0.9.3.  We have since fixed that issue in
our script.  But npm does not allow do overs for released artifacts.

We have learnt our lesson, lets move on please ☺

Thanks,
Om

On Thu, Sep 20, 2018, 12:53 AM Carlos Rovira 
wrote:

> Hi Alex,
> thanks you see it in the list of unread messages and will go to say that I
> found it.
> I'll take a look  now
>
>
> El jue., 20 sept. 2018 a las 9:44, Alex Harui ()
> escribió:
>
> >
> >
> > On 9/19/18, 11:49 PM, "Carlos Rovira"  wrote:
> >
> > Hi Alex,
> >
> > what Zend-AMF issue you refer? can you post the link to that issue?
> > thanks
> >
> > https://lists.apache.org/list.html?us...@royale.apache.org
> >
> > PD: about your preoccupation, we'll have issues for many months to
> > come. I
> > see each day in Jewel as I go here and there fixing or completing
> > issues I
> > find, so I think is ok release with that issues so people can "play
> > with
> > the toy".
> >
> >
> >
> > So, my opinion is that, if someone what to release, we should not
> wait
> > for
> > anything...we have many things to add, solve, fix, that one or two
> > will not
> > make a difference for me. As I said, maybe wait for release, could be
> > worse
> > in terms of potential users we can loose in that time.
> >
> > Of course there will be lots of issues to fix.  But some seem bigger than
> > others, and IMO, make the difference between whether Royale leaves the
> > impression of being a product or a toy.  If your app won't run because
> the
> > dependencies aren't right, or AMF doesn't work, will they help fix it, or
> > wait, or go somewhere else?
> >
> > If you want to release now, then you have to promise to delay what you
> > were planning to work on to handle new customer issues.  Because that's
> > what always happens to me.   By waiting until Alina hits an important
> > milestone helps keep a user we know and want to make successful.
> >
> > -Alex
> >
> >
> >
> >
> > El jue., 20 sept. 2018 a las 2:47, Alex Harui
> > ()
> > escribió:
> >
> > > The key question for me is what Carlos wrote:  " I'm trying to fix
> > and get
> > > things as most usable as possible in
> > > Jewel to avoid many changes post release"
> > >
> > > I always wonder if it helps or hurts to draw attention to the
> > release when
> > > we know there's good chance someone is going to hit a known bug.
> > I'd like
> > > to see if we can fix the issues brought up by some new users.  Such
> > as:
> > >
> > > 1)
> >
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=0
> > >
> > > 2) the Zend-AMF issue.  A more robust AMF might be worth the wait.
> > >
> > > Those of you who want to release soon should promise to investigate
> > any
> > > dependency or AMF issues brought up by new users.  When we release
> > with
> > > issues like these, not only does it cost me the time to be the RM,
> > but also
> > > seems to cost me the time to investigate and respond to the issues
> > brought
> > > up afterwards.
> > >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 9/19/18, 2:59 PM, "Carlos Rovira" 
> > wrote:
> > >
> > > Hi,
> > >
> > > I certainly can position clearly: Community is waiting and we
> are
> > > getting
> > > momentum, each day we get 1-2 new people in twitter following,
> > so it
> > > seems
> > > we are getting some traction. If we release now, those
> > interested in
> > > Royale
> > > would finally start to get its hands dirty and try things,
> > releasing
> > > later
> > > could make we loose that people interested and potential
> > community. In
> > > the
> > > other hand, I'm trying to fix and get things as most usable as
> > > possible in
> > > Jewel to avoid many changes post release. For example today
> make
> > some
> > > needed changes to jewel layouts that make more robust now, and
> > > although we
> > > make changes later, many of them will be more internally (or at
> > least I
> > > want to ge

Build failed in Jenkins: royale-asjs #1361

[apacheroyaleci]

See 


--
[...truncated 315.33 KB...]
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

double-check-file:
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

fail-if-not-found:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

download-dependency-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-cache:

download-jar:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

get-if-not-cached:
  [get] Getting: 
https://repo1.maven.org/maven2/com/google/guava/guava/20.0/guava-20.0.jar
  [get] To: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\lib\guava.jar
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

double-check-file:
 [echo] Need file: ${still_no_file}

get-from-cache-if-needed:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

fail-if-not-found:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-sum:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

put-in-cache:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

copy-if-cached:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

download-dependency-zip:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-dependency:

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

echo-project-jar:
  [get] Getting: http://www.apache.org/licenses/LICENSE-2.0
  [get] To: C:\Program Files 
(x86)\Jenkins\w

Jenkins build is back to normal : royale-typedefs #720

[apacheroyaleci]

See 

Jenkins build is back to normal : royale-compiler #452

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs #1360

[apacheroyaleci]

See 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/1360/display/redirect?page=changes>

Changes:

[yishayjobs] Add type declaration, plus make sure callback is defined

[carlosrovira] change "window.outerWidth" for

--
[...truncated 92.02 KB...]
checkintests-clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/tests/basicTests/BasicTestsApp.swf>

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/royale-sdk-description.xml>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/js/libs>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/temp>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/projects/*/src/main/royale>

clean:

super-clean:
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/tests/basicTests/bin>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/locale>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mx>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/rsls>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Halo>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Spark>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/airmobile-config.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/macfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/winfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/localfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mxml-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/spark-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/ide/flashbuilder/flashbuilder-config.xml>

create-description:
 [echo] build.number is 20180920

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:
[mkdir] Created dir: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Spark>

stage-source:

clean-temp:
[mkdir] Created dir: 
<http://apacheroya

Re: [royale-asjs] branch develop updated: Add type declaration, plus make sure callback is defined

[Carlos Rovira]

Thanks Harbs,
If nobody comes first I'll add that class as I try to add the theme
selector to Jewel Example, hopefully some time in the next days

El jue., 20 sept. 2018 a las 12:22, Harbs ()
escribió:

> The only thing we have for css is addDynamicSelector which I don’t think
> does what you want.
>
> Loading a css file should be almost the same as JS.
>
> > On Sep 20, 2018, at 1:12 PM, Carlos Rovira 
> wrote:
> >
> > Hi,
> >
> > do we have something like this for CSS files?
> > I was thinking in add to JewelExample a "theme selector", and I think it
> > could be great to add the css on the fly
> >
> > thanks
> >
> > Carlos
> >
> >
> > El jue., 20 sept. 2018 a las 12:03,  escribió:
> >
> >> This is an automated email from the ASF dual-hosted git repository.
> >>
> >> yishayw pushed a commit to branch develop
> >> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >>
> >>
> >> The following commit(s) were added to refs/heads/develop by this push:
> >> new 7441707  Add type declaration, plus make sure callback is
> defined
> >> 7441707 is described below
> >>
> >> commit 7441707fb929c0c43b11c8a9088c78b24eccac7d
> >> Author: DESKTOP-RH4S838\Yishay 
> >> AuthorDate: Thu Sep 20 13:03:27 2018 +0300
> >>
> >>Add type declaration, plus make sure callback is defined
> >> ---
> >> .../src/main/royale/org/apache/royale/utils/js/loadJavascript.as   | 7
> >> +--
> >> 1 file changed, 5 insertions(+), 2 deletions(-)
> >>
> >> diff --git
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> >>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> >> index 26b2d70..b6ade28 100644
> >> ---
> >>
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> >> +++
> >>
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> >> @@ -28,10 +28,13 @@ package org.apache.royale.utils.js
> >>* @royaleignorecoercion HTMLScriptElement
> >>*/
> >>   COMPILE::JS
> >> -  public function loadJavascript(url:String,callback:Function=null)
> >> +  public function
> loadJavascript(url:String,callback:Function=null):void
> >>   {
> >> var script:HTMLScriptElement = document.createElement('script') as
> >> HTMLScriptElement;
> >> -script.onload = callback;
> >> +   if (callback)
> >> +   {
> >> +   script.onload = callback;
> >> +   }
> >> script.src = url;
> >> document.head.appendChild(script);
> >>   }
> >>
> >>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>

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

Re: [royale-asjs] branch develop updated: Add type declaration, plus make sure callback is defined

[Harbs]

The only thing we have for css is addDynamicSelector which I don’t think does 
what you want.

Loading a css file should be almost the same as JS.

> On Sep 20, 2018, at 1:12 PM, Carlos Rovira  wrote:
> 
> Hi,
> 
> do we have something like this for CSS files?
> I was thinking in add to JewelExample a "theme selector", and I think it
> could be great to add the css on the fly
> 
> thanks
> 
> Carlos
> 
> 
> El jue., 20 sept. 2018 a las 12:03,  escribió:
> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> yishayw pushed a commit to branch develop
>> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>> 
>> 
>> The following commit(s) were added to refs/heads/develop by this push:
>> new 7441707  Add type declaration, plus make sure callback is defined
>> 7441707 is described below
>> 
>> commit 7441707fb929c0c43b11c8a9088c78b24eccac7d
>> Author: DESKTOP-RH4S838\Yishay 
>> AuthorDate: Thu Sep 20 13:03:27 2018 +0300
>> 
>>Add type declaration, plus make sure callback is defined
>> ---
>> .../src/main/royale/org/apache/royale/utils/js/loadJavascript.as   | 7
>> +--
>> 1 file changed, 5 insertions(+), 2 deletions(-)
>> 
>> diff --git
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
>> index 26b2d70..b6ade28 100644
>> ---
>> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
>> +++
>> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
>> @@ -28,10 +28,13 @@ package org.apache.royale.utils.js
>>* @royaleignorecoercion HTMLScriptElement
>>*/
>>   COMPILE::JS
>> -  public function loadJavascript(url:String,callback:Function=null)
>> +  public function loadJavascript(url:String,callback:Function=null):void
>>   {
>> var script:HTMLScriptElement = document.createElement('script') as
>> HTMLScriptElement;
>> -script.onload = callback;
>> +   if (callback)
>> +   {
>> +   script.onload = callback;
>> +   }
>> script.src = url;
>> document.head.appendChild(script);
>>   }
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: [royale-asjs] branch develop updated: Add type declaration, plus make sure callback is defined

[Carlos Rovira]

Hi,

do we have something like this for CSS files?
I was thinking in add to JewelExample a "theme selector", and I think it
could be great to add the css on the fly

thanks

Carlos


El jue., 20 sept. 2018 a las 12:03,  escribió:

> This is an automated email from the ASF dual-hosted git repository.
>
> yishayw pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/develop by this push:
>  new 7441707  Add type declaration, plus make sure callback is defined
> 7441707 is described below
>
> commit 7441707fb929c0c43b11c8a9088c78b24eccac7d
> Author: DESKTOP-RH4S838\Yishay 
> AuthorDate: Thu Sep 20 13:03:27 2018 +0300
>
> Add type declaration, plus make sure callback is defined
> ---
>  .../src/main/royale/org/apache/royale/utils/js/loadJavascript.as   | 7
> +--
>  1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> index 26b2d70..b6ade28 100644
> ---
> a/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> +++
> b/frameworks/projects/Core/src/main/royale/org/apache/royale/utils/js/loadJavascript.as
> @@ -28,10 +28,13 @@ package org.apache.royale.utils.js
> * @royaleignorecoercion HTMLScriptElement
> */
>COMPILE::JS
> -  public function loadJavascript(url:String,callback:Function=null)
> +  public function loadJavascript(url:String,callback:Function=null):void
>{
>  var script:HTMLScriptElement = document.createElement('script') as
> HTMLScriptElement;
> -script.onload = callback;
> +   if (callback)
> +   {
> +   script.onload = callback;
> +   }
>  script.src = url;
>  document.head.appendChild(script);
>}
>
>

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

Next Blog Example: Please Vote! :)

[Carlos Rovira]

Hi,

since there are many things we can expose in blog post, just for prioritize
I put only 3 of them in a little tweet pool

https://twitter.com/ApacheRoyale/status/1042681072406937600

So, if you want to give your opinion, please vote! :)

thanks

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

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[Carlos Rovira]

Hi Alex,
thanks you see it in the list of unread messages and will go to say that I
found it.
I'll take a look  now


El jue., 20 sept. 2018 a las 9:44, Alex Harui ()
escribió:

>
>
> On 9/19/18, 11:49 PM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> what Zend-AMF issue you refer? can you post the link to that issue?
> thanks
>
> https://lists.apache.org/list.html?us...@royale.apache.org
>
> PD: about your preoccupation, we'll have issues for many months to
> come. I
> see each day in Jewel as I go here and there fixing or completing
> issues I
> find, so I think is ok release with that issues so people can "play
> with
> the toy".
>
>
>
> So, my opinion is that, if someone what to release, we should not wait
> for
> anything...we have many things to add, solve, fix, that one or two
> will not
> make a difference for me. As I said, maybe wait for release, could be
> worse
> in terms of potential users we can loose in that time.
>
> Of course there will be lots of issues to fix.  But some seem bigger than
> others, and IMO, make the difference between whether Royale leaves the
> impression of being a product or a toy.  If your app won't run because the
> dependencies aren't right, or AMF doesn't work, will they help fix it, or
> wait, or go somewhere else?
>
> If you want to release now, then you have to promise to delay what you
> were planning to work on to handle new customer issues.  Because that's
> what always happens to me.   By waiting until Alina hits an important
> milestone helps keep a user we know and want to make successful.
>
> -Alex
>
>
>
>
> El jue., 20 sept. 2018 a las 2:47, Alex Harui
> ()
> escribió:
>
> > The key question for me is what Carlos wrote:  " I'm trying to fix
> and get
> > things as most usable as possible in
> > Jewel to avoid many changes post release"
> >
> > I always wonder if it helps or hurts to draw attention to the
> release when
> > we know there's good chance someone is going to hit a known bug.
> I'd like
> > to see if we can fix the issues brought up by some new users.  Such
> as:
> >
> > 1)
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=0
> >
> > 2) the Zend-AMF issue.  A more robust AMF might be worth the wait.
> >
> > Those of you who want to release soon should promise to investigate
> any
> > dependency or AMF issues brought up by new users.  When we release
> with
> > issues like these, not only does it cost me the time to be the RM,
> but also
> > seems to cost me the time to investigate and respond to the issues
> brought
> > up afterwards.
> >
> > My 2 cents,
> > -Alex
> >
> > On 9/19/18, 2:59 PM, "Carlos Rovira" 
> wrote:
> >
> > Hi,
> >
> > I certainly can position clearly: Community is waiting and we are
> > getting
> > momentum, each day we get 1-2 new people in twitter following,
> so it
> > seems
> > we are getting some traction. If we release now, those
> interested in
> > Royale
> > would finally start to get its hands dirty and try things,
> releasing
> > later
> > could make we loose that people interested and potential
> community. In
> > the
> > other hand, I'm trying to fix and get things as most usable as
> > possible in
> > Jewel to avoid many changes post release. For example today make
> some
> > needed changes to jewel layouts that make more robust now, and
> > although we
> > make changes later, many of them will be more internally (or at
> least I
> > want to get the most stable API I can so things are as most
> organized
> > and
> > well named as possible).
> >
> > If someone could continue the effort will be very good, but if
> none of
> > us
> > can do, it I think nothing can be done but continue working hard
> to get
> > things done.
> >
> > just my 2
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> >
> > El mié., 19 sept. 2018 a las 22:57, Harbs (<
> harbs.li...@gmail.com>)
> > escribió:
> >
> > > Jewel is another reason.
> > >
> > > Carlos wrote a lot of blog posts which can’t be run until we
> release.
> > >
> > > (Plus lots of little things that were fixed…)
> > >
> > > > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > wrote:
> > > >
> > > > I personally express important reason. Releasing can help
> community
> > > around
> > > > VSCod

Re: Potential gotcha

[Harbs]

Good idea.

> On Sep 20, 2018, at 10:46 AM, Alex Harui  wrote:
> 
> Feel free to add a warning to the compiler.
> 
> On 9/20/18, 12:41 AM, "Harbs"  wrote:
> 
>I was just hit by a strange error in IE. It turns out that I was using 
> “new Event” without importing org.apache.royale.events.Event. This became a 
> browser Event instead of a Royale event and you can’t “new” events in IE…
> 
>I’m not sure if there’s something we can do about this, but it’s not a bad 
> idea to at least document the potential problem.
> 
>Harbs
> 

Re: Potential gotcha

[Alex Harui]

Feel free to add a warning to the compiler.

On 9/20/18, 12:41 AM, "Harbs"  wrote:

I was just hit by a strange error in IE. It turns out that I was using “new 
Event” without importing org.apache.royale.events.Event. This became a browser 
Event instead of a Royale event and you can’t “new” events in IE…

I’m not sure if there’s something we can do about this, but it’s not a bad 
idea to at least document the potential problem.

Harbs

Re: ***UNCHECKED*** Re: [Discuss] Start release process 0.9.3

[Alex Harui]

On 9/19/18, 11:49 PM, "Carlos Rovira"  wrote:

Hi Alex,

what Zend-AMF issue you refer? can you post the link to that issue?
thanks

https://lists.apache.org/list.html?us...@royale.apache.org

PD: about your preoccupation, we'll have issues for many months to come. I
see each day in Jewel as I go here and there fixing or completing issues I
find, so I think is ok release with that issues so people can "play with
the toy".
 
   

So, my opinion is that, if someone what to release, we should not wait for
anything...we have many things to add, solve, fix, that one or two will not
make a difference for me. As I said, maybe wait for release, could be worse
in terms of potential users we can loose in that time.

Of course there will be lots of issues to fix.  But some seem bigger than 
others, and IMO, make the difference between whether Royale leaves the 
impression of being a product or a toy.  If your app won't run because the 
dependencies aren't right, or AMF doesn't work, will they help fix it, or wait, 
or go somewhere else?

If you want to release now, then you have to promise to delay what you were 
planning to work on to handle new customer issues.  Because that's what always 
happens to me.   By waiting until Alina hits an important milestone helps keep 
a user we know and want to make successful.

-Alex




El jue., 20 sept. 2018 a las 2:47, Alex Harui ()
escribió:

> The key question for me is what Carlos wrote:  " I'm trying to fix and get
> things as most usable as possible in
> Jewel to avoid many changes post release"
>
> I always wonder if it helps or hurts to draw attention to the release when
> we know there's good chance someone is going to hit a known bug.  I'd like
> to see if we can fix the issues brought up by some new users.  Such as:
>
> 1) 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues%2F297%23issuecomment-422870607&data=02%7C01%7Caharui%40adobe.com%7C7b170880a70a4b8d340c08d61ec539b7%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636730229757292613&sdata=54aFEiUJ%2FRTCiBooZaJADt9CvYamAcvzNyWY1wP0%2Fjg%3D&reserved=0
>
> 2) the Zend-AMF issue.  A more robust AMF might be worth the wait.
>
> Those of you who want to release soon should promise to investigate any
> dependency or AMF issues brought up by new users.  When we release with
> issues like these, not only does it cost me the time to be the RM, but 
also
> seems to cost me the time to investigate and respond to the issues brought
> up afterwards.
>
> My 2 cents,
> -Alex
>
> On 9/19/18, 2:59 PM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I certainly can position clearly: Community is waiting and we are
> getting
> momentum, each day we get 1-2 new people in twitter following, so it
> seems
> we are getting some traction. If we release now, those interested in
> Royale
> would finally start to get its hands dirty and try things, releasing
> later
> could make we loose that people interested and potential community. In
> the
> other hand, I'm trying to fix and get things as most usable as
> possible in
> Jewel to avoid many changes post release. For example today make some
> needed changes to jewel layouts that make more robust now, and
> although we
> make changes later, many of them will be more internally (or at least 
I
> want to get the most stable API I can so things are as most organized
> and
> well named as possible).
>
> If someone could continue the effort will be very good, but if none of
> us
> can do, it I think nothing can be done but continue working hard to 
get
> things done.
>
> just my 2
>
> Carlos
>
>
>
>
>
>
>
> El mié., 19 sept. 2018 a las 22:57, Harbs ()
> escribió:
>
> > Jewel is another reason.
> >
> > Carlos wrote a lot of blog posts which can’t be run until we 
release.
> >
> > (Plus lots of little things that were fixed…)
> >
> > > On Sep 19, 2018, at 11:26 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > wrote:
> > >
> > > I personally express important reason. Releasing can help 
community
> > around
> > > VSCode and Moonshine.
> > >
> > > Piotr
> > >
> > > On Wed, Sep 19, 2018, 9:41 PM Alex Harui  >
> > wrote:
> > >
> > >> What do you see as the important reasons?  I know the Apache
> mantra is
> > to
> > >> release early and often, but if it were up to me, we would 
release
> > after we
> > >> hit some interesting milestone, like getting Al

Potential gotcha

[Harbs]

I was just hit by a strange error in IE. It turns out that I was using “new 
Event” without importing org.apache.royale.events.Event. This became a browser 
Event instead of a Royale event and you can’t “new” events in IE…

I’m not sure if there’s something we can do about this, but it’s not a bad idea 
to at least document the potential problem.

Harbs