[PROPOSAL] How to continue to simplify things?

Hi all, congrats to the successful release of 0.9.7 … it greatly simplified the last PLC4X release to have the artifacts out there in the wild. I would really like to see Royale as the tool in my toolbox for building industrial UI applications as I sort of am not that happy with the other exis

Re: [PROPOSAL] How to continue to simplify things?

Hi Chris, Thanks for you work helping with the 0.9.7 release as well. I’m definitely open to improving the structure and the process. My biggest hesitation is that I don’t understand the current release process well enough. Until recently Alex was the only one who really understood it. Yishay

Re: [PROPOSAL] How to continue to simplify things?

Hi Harbs, makes sense. Chris Am 28.05.20, 10:48 schrieb "Harbs" : Hi Chris, Thanks for you work helping with the 0.9.7 release as well. I’m definitely open to improving the structure and the process. My biggest hesitation is that I don’t understand the current release pro

Re: [PROPOSAL] How to continue to simplify things?

Hi Harbs, I would like to be a release manager as well, but using Chri's implementation which as far as I know is in place. I would like to use his mentioned 3 steps and see how much things I will have to do on my own to make release happen. I know that I will have to do that on Mac, cause there s

Re: [PROPOSAL] How to continue to simplify things?

Hi Piotr, we could change the configuration to use the jgit plugin on the CI machine and to use the default on local machines. In that case you could do it on any machine you want (also windows) Who does releases in which order using which tooling ... I don't really care ... I'm just happy th

Re: [PROPOSAL] How to continue to simplify things?

Chris, I think I would like to be after Harbs and eventually Greg. Yes you can send me a link, write a document with absolutely EVERY step which I have to do in order to get release done. Even if you think that I know some steps like signing - you can in such places point into some existing docume

Re: [PROPOSAL] How to continue to simplify things?

Hi Piotr, I think the Royale project could grant my user write permissions to confluence. Then I could write such a document there. But I could also do a google doc outside, if this is more convenient. Chris Am 28.05.20, 13:39 schrieb "Piotr Zarzycki" : Chris, I think I would like

Re: [PROPOSAL] How to continue to simplify things?

Chris, We are not using confluence at all. We are using Wiki [1], but you can write document in whatever place you wanted to if you are not comfortable with wiki. Andrew, Will you be willing to translate that document into our Wiki manner ? [1] https://github.com/apache/royale-asjs/wiki Thanks

Re: [PROPOSAL] How to continue to simplify things?

Oh, of course! Chris, I am trying to move up to the website stuff that Royale users would want quick access to, and keep on the wiki stuff that the development team needs, or that is "tl:dr" details. I would be happy to work with you to get your material on the github wiki and to curate it so it a

Change in MXRoyale

Alex, I hope you are ok with this change: https://github.com/apache/royale-asjs/commit/26d4b9cf7c1968160278754a01bd612946ddf41d It makes a big difference in a large codebase I am working on, many components with bindings that were not working suddenly started working. In the absence of 'this is

Re: [PROPOSAL] How to continue to simplify things?

I also wanted to say that I would be happy to take my turn as release manager once the process has stabilized enough that it is mainly a matter of shepherding the new release through a reliable series of steps. I spent several years as RM for various companies, and often understood very little of t

Re: Change in MXRoyale

I’m surprised that Closure Compiler renaming doesn’t break this. > On May 28, 2020, at 3:00 PM, Greg Dove wrote: > > Alex, > > I hope you are ok with this change: > https://github.com/apache/royale-asjs/commit/26d4b9cf7c1968160278754a01bd612946ddf41d > > > It makes a big difference in a large

New mailing list royale-bui...@royale.apache.org to follow results of Jenkins/builds.a.o

Hi, I'm happy to announce that we have new mailing list called royale-bui...@royale.apache.org. List will be used for gathering all the build fail/fix from our builds systems. *Please Subscribe by sending email to:* royale-builds-subscr...@royale.apache.org Following builds will be reported to

Re: Change in MXRoyale

There are a few things like this where it does not. I forget exactly the rules for that. We are already using this exact same check elsewhere in bindings code, possibly since its inception. On Fri, May 29, 2020 at 12:33 AM Harbs wrote: > I’m surprised that Closure Compiler renaming doesn’t break

Re: Change in MXRoyale

Actually maybe I need to double double-check this more, thanks for the prompt. I will do that now. On Fri, May 29, 2020 at 12:36 AM Greg Dove wrote: > > There are a few things like this where it does not. I forget exactly the > rules for that. We are already using this exact same check elsewher

Re: Change in MXRoyale

I think it is because we are using _strand["_bindings"] in some places it keeps it without renaming On Fri, May 29, 2020 at 12:38 AM Greg Dove wrote: > > Actually maybe I need to double double-check this more, thanks for the > prompt. I will do that now. > > > On Fri, May 29, 2020 at 12:36 AM G

Re: Change in MXRoyale

OK. Cool. > On May 28, 2020, at 3:39 PM, Greg Dove wrote: > > I think it is because we are using > _strand["_bindings"] > in some places it keeps it without renaming > > > On Fri, May 29, 2020 at 12:38 AM Greg Dove wrote: > >> >> Actually maybe I need to double double-check this more, thank

Application Extend generate compile error in version 0.9.7

Hi , I paste a sampe code to demostrate an error message at compile with version 0.9.7 the code pass the compilation in version 9.0.6. The MXML code extend a custom class instead of Standard Application Class The error message is: C:\Royale_SDK\royale_source\royale-asjs\examples\royal

Re: [PROPOSAL] How to continue to simplify things?

Hi all, so I just had a look ... it seems as if the "fork" feature on github doesn't fork the wiki too ... So I could create my own pages, but not create PRs for documentation ... or I just didn't find the docs on how to do it. Do you have any pointers for me? Chris Am 28.05.20, 13:55 schrie

Re: Application Extend generate compile error in version 0.9.7

Hi Spiros, there was a bug in 0.9.6 where childnodes could not have the same prefix than the parent node. You must ensure in fix your code, since as you can see you have "app" root node and then "js" as prefix in child nodes HTH Carlos El jue., 28 may. 2020 a las 15:48, Spiros Aggelopoulos (<

Re: [PROPOSAL] How to continue to simplify things?

Hi Chris, FWIK, there's no way to do a PR for wiki in Github. I think should be done other way, maybe google doc or something HTH Carlos El jue., 28 may. 2020 a las 16:00, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi all, > > so I just had a look ... it seems as if the "fork"

Re: [PROPOSAL] How to continue to simplify things?

Hmm. That’s a problem I was not aware of... What do folks think about enabling public editing of wikis?[1] Harbs [1]https://help.github.com/en/github/building-a-strong-community/changing-access-permissions-for-wikis

RE: Application Extend generate compile error in version 0.9.7

Hi Carlos Yes it works now. Thanks -Original Message- From: Carlos Rovira [mailto:carlosrov...@apache.org] Sent: Thursday, May 28, 2020 5:11 PM To: Apache Royale Development Subject: Re: Application Extend generate compile error in version 0.9.7 Hi Spiros, there was a bug in 0.9.6

Re: [PROPOSAL] How to continue to simplify things?

Hi all, well perhaps searching for some experiences with this ... my gut-feeling would make me expect to have the wiki content replaced by Viagra ads ;-) But it would be in git, so easily undoable I did find this however: https://www.growingwiththeweb.com/2016/07/enabling-pull-requests-on

Re: [PROPOSAL] How to continue to simplify things?

Hi, I think a google doc that have collaborative commenting and editing with concurrency will be more suited and easy, while you don't need to mount anything special. El jue., 28 may. 2020 a las 16:36, Christofer Dutz (< christofer.d...@c-ware.de>) escribió: > Hi all, > > well perhaps searchin

Re: [PROPOSAL] How to continue to simplify things?

I’m going offline for two days so I’ll be quiet for a while, but it might be a good idea to ask infra whether they have a solution to this problem. Harbs > On May 28, 2020, at 5:36 PM, Christofer Dutz > wrote: > > Hi all, > > well perhaps searching for some experiences with this ... > my gu

Re: [PROPOSAL] How to continue to simplify things?

Hi all, Infra says there's nothing in-between all or nothing with github :-( So I'll probably go down the google doc route and have the text imported by one of you folks. Chris Am 28.05.20, 17:38 schrieb "Harbs" : I’m going offline for two days so I’ll be quiet for a while, but it might

Re: [PROPOSAL] How to continue to simplify things?

Seems like the simplest way. On Thu, May 28, 2020 at 12:55 PM Christofer Dutz wrote: > Hi all, > > Infra says there's nothing in-between all or nothing with github :-( > > So I'll probably go down the google doc route and have the text imported > by one of you folks. > > Chris > > > Am 28.05.20

Re: Change in MXRoyale

Not opposed if it works, but do you know why it is needed? It makes me worry that the mxmlDocument chain isn't set up properly and we'll end up with other related bugs. Is the problem in mx:Container-based itemrenderers? If so, the factories may need to propagate mxmlDocument across the gaps

Re: Change in MXRoyale

This is not really about itemRenderers. More to do with regular mxml components I think, but tbh that is 'gut feel' and I didn't try to check a lot of the details so far, just was happy to make more things work. I will try to investigate/understand the potential mxmlDocument mismatch today and eith