Re: Publishing royale to npm

That might work. One question: we want the same bits that were published as 0.9.0-rc1 to become the final bits where you would do: npm install -g apache-royale We aren't supposed to rebuild anything. For Maven the same bits from staging get copied to Maven central, for Ant/IDE the same

Re: Publishing royale to npm

For staging builds, we could do : Publish: npm publish --tag 0.9.0-rc1 Install: npm install -g apache-royale@0.9.0-rc1 For nightly builds Publish: npm publish --tag nightly Install: npm install -g apache-royale@nightly Thoughts? BTW, if we want to integrate this as part of our release

Re: [Website] Getting content ready to publish

Hi, > Great job. I think we have all links on the mailing list web page. The one > thing which I really really miss is place on the download site where I will > be able to download Nightly Build - Please read this [1] about linking to nightly builds. Justin 1.

Re: Publishing royale to npm

What would be great is, when we push artifacts to Maven staging repos and dist/dev, we also push something to wherever we need to push it so npm works. Then we say in the vote emails: Maven: Use these staging 'coordinates' in your pom.xml Ant/IDE users: Get artifacts from dist.a.o/dev/royale

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

Right. That’s what I meant. > On Nov 10, 2017, at 12:18 AM, Alex Harui wrote: > > Don't forget that we use composition to simplify things. > > So an AccordionItem can be a Container subclass with a TitleBarModel built > in and a title property. > > HTH, > -Alex > >

Re: Publishing royale to npm

On Thu, Nov 9, 2017 at 2:15 PM, Alex Harui wrote: > Can you remind me what the issues are with npm and nightly builds? IOW, I > would think we would want to automate the generation of the HPM release so > it can go out with the regular Apache release artifacts and be

Re: [royale-asjs] branch develop updated: Fixed asconfigc files We now get full code intelligence in VS Code for the framework project code. This will work for even JS and SWF blocks.

Hi Harbs, I did that, and see that code is referring the SDK ok now (Apache Royale 0.9.0-SNAPSHOT), I created the SDK with maven from sources. but intelligence seems not going very accurate. I didn't test it too much. hope Josh release is soon since I think this extension is very important.

[Website] Getting content ready to publish

Hi, I'm working on setting up real content on the website preview. I think I'll be posting in this thread finished pages for you to review. For example the first one: http://royale.codeoscopic.com/mailing-lists/ Here, you could check if we have all expected content, if content is ok, if no

Re: Publishing royale to npm

OK. You’re probably right. > On Nov 9, 2017, at 9:34 PM, OmPrakash Muppirala wrote: > > On Thu, Nov 9, 2017 at 11:27 AM, Harbs wrote: > >> Did you reserve the name yet? >> > > No I did not. If we are going to be using apache-royale as the

Re: Publishing royale to npm

Hi Om, for me it's ok, I suppose you refer to 0.9 right? I'll be creating new thread to talk about first website release and what to include, since some things are not ready yet thanks 2017-11-09 20:34 GMT+01:00 OmPrakash Muppirala : > On Thu, Nov 9, 2017 at 11:27 AM,

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

I think the architecture is sound. The use of it could probably be improved. Making an AccordionItem which encapsulates a title model would be a good idea. How do we get AccordionItems without putting them in an array? > On Nov 9, 2017, at 9:40 PM, Peter Ent wrote: > >

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

I wonder if that's not a little too complex. I really couldn't figure out how to use it without experimentation and even then, didn't realize about the itemRenderer aspect. How about something like this: This way we don't have to do much

Re: Publishing royale to npm

On Thu, Nov 9, 2017 at 11:27 AM, Harbs wrote: > Did you reserve the name yet? > No I did not. If we are going to be using apache-royale as the package name, we should be fine. Unless you are worried someone else might claim it? > > > On Nov 9, 2017, at 9:25 PM,

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

The rendering of the items is done by ItemRenderers (which in the default I believe is a Panel). > On Nov 9, 2017, at 9:31 PM, Harbs wrote: > > Accordion was designed to not care what specific components the individual > panels are. For a title, it needs a

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

Accordion was designed to not care what specific components the individual panels are. For a title, it needs a TitleBarModel. That’s it. Here’s an example: https://github.com/yishayw/Examples/blob/Accordion_Express/Examples.mxml

Re: Publishing royale to npm

Did you reserve the name yet? > On Nov 9, 2017, at 9:25 PM, OmPrakash Muppirala wrote: > > On Thu, Nov 9, 2017 at 10:08 AM, Carlos Rovira > wrote: > >> Hi Om, >> >> I'm working on the website content and want to know about NPM to update >> pages

Re: Publishing royale to npm

On Thu, Nov 9, 2017 at 10:08 AM, Carlos Rovira wrote: > Hi Om, > > I'm working on the website content and want to know about NPM to update > pages with real info. > could you share your plans about releasing Apache Royale in NPM? > I suppose you can't still make this due

Re: [royale-asjs] branch develop updated: Fixed asconfigc files We now get full code intelligence in VS Code for the framework project code. This will work for even JS and SWF blocks.

I imagine Josh will release it soon, but it’s pretty easy to build if you don’t want to wait. I’m using the snapshot right now. The current release does not work with Royale. To use the snapshot: 1. Remove the release extension if it’s installed. 2. Run: mvn clean package 3. In the Extensions

Re: [royale-asjs] branch develop updated: Fixed asconfigc files We now get full code intelligence in VS Code for the framework project code. This will work for even JS and SWF blocks.

Hi Harbs, so following the issue I suppose that we need to build our own extension right? (I mean we still can't use released version with Royale right now?) 2017-11-09 17:09 GMT+01:00 Harbs : > OK. > > I think I’m done fixing up the asconfigc files. Currently, the only >

Re: Publishing royale to npm

Hi Om, I'm working on the website content and want to know about NPM to update pages with real info. could you share your plans about releasing Apache Royale in NPM? I suppose you can't still make this due to some final renaming? Let me know in order to remove this info if you think we'll need

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

I saw that Container worked, but how do you get labels on them? —peter On 11/9/17, 9:54 AM, "Harbs" wrote: >Inside the js:Array should be Container elements. > >I’m using it in production. > >> On Nov 9, 2017, at 4:28 PM, Peter Ent wrote: >> >>

Re: [royale-asjs] branch develop updated: Fixed asconfigc files We now get full code intelligence in VS Code for the framework project code. This will work for even JS and SWF blocks.

OK. I think I’m done fixing up the asconfigc files. Currently, the only problems being reported are in the GoogleMaps project. (not sure how to fix those), and some .pbj files in GRaphics. Hopefully Josh will make those errors go away. FYI, the first target in the targets list is the one which

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

Inside the js:Array should be Container elements. I’m using it in production. > On Nov 9, 2017, at 4:28 PM, Peter Ent wrote: > > I tested my change. I don't think it adversely affects Accordion at all, > but Accordion doesn't seem to be working correctly anyway. > >

Re: [royale-asjs] branch develop updated: PanelView no longer removes beads. Instead, it transfers beads from the Panel to its Container content area.

I tested my change. I don't think it adversely affects Accordion at all, but Accordion doesn't seem to be working correctly anyway. I'm getting Panels inside of Panels. So if in the supplied to Accordion, I have a , that Panel gives title to the Accordion header, but then a panel becomes a child

mxmlc/asjsc command line arguments

Hi, Would someone please be so kind to tell me which command line arguments will allow me to build a simple application from one .as file, using mxmlc or asjsc or any of the 'straight from the compiler jars' executables, so I can use that as a reference project/build for my new WASM compiler)? I

Re: [Royale Wiki] User Manual

Hi Peter, as Harbs said, is better to introduce all info we need and use the organization you think is better. Then as we start to set up all website and documentation we can make a "reorganization" work so we focus on getting the info as easy as possible for new comers. Thanks 2017-11-08