Re: Royale in a Week

[Dany Dhondt]

Great you started this Andrew. I’ll try to follow along.

I’ve just had time to do a quick glance on the wiki page.

Did you decide ‘what’ will be build? I’d prefer NOT to build a todo list 
(everyone is doing that :)).
Because from the moment you decide what to build, there you have your story.

Great work
Dany


> Op 10 mei 2019, om 13:34 heeft Andrew Wetmore  het 
> volgende geschreven:
> 
> Hi, all:
> 
> There is a wiki page [1] that has the structure of the old "Flex in a Week"
> video course [2], some notes about what I think we need to add for a
> similar course for Royale, and my proposed structure for "Royale in a Week".
> 
> Before I go further, it would be helpful if people could cast a quick eye
> over the notes and proposed structure and identify key elements that the
> material must cover and that I may have overlooked. You could share your
> thoughts in this thread, or just add them to the "Stuff to include in
> Royale in a Week" section of the wiki page.
> 
> Next chance I get, I will build out each day's curriculum for Royale in a
> Week a little further. Then I think I will identify the stuff I think I can
> create and the sections for which I will need help.
> 
> The eventual deliverable will be a series of videos with transcripts and
> downloadable code. Do all the assets get hosted on Github? I would expect
> that we would publish the videos to a YouTube channel, as well as giving
> access to them on our website.
> 
> Thanks!
> 
> a
> 
> [1]  https://github.com/apache/royale-asjs/wiki/Royale-in-a-Week-project
> [2]  https://www.adobe.com/devnet/flex/videotraining.html
> 
> 
> On Thu, May 9, 2019 at 12:51 PM Andrew Wetmore  wrote:
> 
>> I am going to lay out my proposed table of contents for Royale in a Week
>> on a wiki page and get some feedback about its order and what I am
>> forgetting to include.
>> 
>> On Tue, Apr 30, 2019 at 8:12 PM Alex Harui 
>> wrote:
>> 
>>> Hi Andrew,
>>> 
>>> Thanks for taking this on.
>>> 
>>> We have repos for code and for docs (royale-docs) and dev@ for
>>> communication.  And we have a wiki.  We should try to use these tools as
>>> much as possible unless there is a significant productivity gain to be
>>> using some other way.  That's because by using these tools, even if they
>>> make you 10% slower, they automatically generate notices in the right
>>> places, and hopefully others will join in and make the whole thing faster.
>>> When we use other tools it might make a few folks faster, but it is harder
>>> for others to follow along on dev@ and commits@.
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> On 4/30/19, 12:41 PM, "Andrew Wetmore"  wrote:
>>> 
>>>I would be happy to work on creating a Royale equivalent to "Flex in a
>>>Week".
>>> 
>>>My first step would be to review the old curriculum and see where it
>>> needs
>>>updating to eliminate Flex-specific stuff that Royale does not have
>>> or need
>>>to worry about. I would then want to assemble a new curriculum (what
>>> we
>>>teach each of the seven days) and get confirmation from the group
>>> that the
>>>list looks adequate.
>>> 
>>>My question is, where should I post such a document for feedback and
>>>comments? My immediate impulse  is to create a mind map or document in
>>>Google Docs and share it, but I think I have seen people suggest that
>>> is
>>>not the correct method.
>>> 
>>>a
>>> 
>>>--
>>>Andrew Wetmore
>>> 
>>> 
>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.blogspot.com%2Fdata=02%7C01%7Caharui%40adobe.com%7C5e6f1266e7384aa2831c08d6cda3c6a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922500628304365sdata=b%2BhDtiykkxmq9c83dOP%2FF9RrucysABFyICNXaulhjqw%3Dreserved=0
>>> 
>>> 
>>> 
>> 
>> --
>> Andrew Wetmore
>> 
>> http://cottage14.blogspot.com/
>> 
>> 
>> 
>> 
>> 
> 
> -- 
> Andrew Wetmore
> 
> http://cottage14.blogspot.com/

Re: Royale docs website integration

[Dany Dhondt]

In the proof of concept I made yesterday, I used the raw links to the .md files 
which works perfectly.
When you go to any file on GitHub, there’s a ‘raw’ button which will show you 
the raw content of the file. Then just copy the link and you can use that one 
wherever you like.
An example here [1]
It’s just a hyperlink so I don’t think there’s any limitation here.
The only thing we have to do is to parse the markdown content into html but 
there are plenty of js libs on npm to do that, so we wouldn’t have to write it 
ourselves.

Dany

[1] https://raw.githubusercontent.com/apache/royale-docs/master/index.md


> Op 5 mei 2019, om 16:49 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi Danny,
> 
> One question about the workflow: the new doc page viewer, will be a royale
> app that retrieve the GitHub content on demand, in the same way as I did in
> TDJ with source code? Will do this on demand? If we can do in that way, not
> saving new files to repo, I think that would be great, since viewer will
> pick fresh content each time. Maybe this could face some limitation of the
> Github Rest API (don't know how many petitions it will allow per hour or
> day)
> 
> If we do in this way, we can reuse part of the code in TDJ and the main
> problem will be to create the Sticky menu on the Right. That as well could
> be based on current Navigator component. I could create that component as
> part of Jewel.
> 
> So having a main content part and the right stick menu with the ability to
> load content as we select on the main content part, will be the "engine" we
> need
> Then we and others could help with the generation of "stories" to fill the
> content.
> 
> Thoughts?
> 
> 
> El dom., 5 may. 2019 a las 12:23, Dany Dhondt ()
> escribió:
> 
>> HI,
>> 
>> I’d like to propose a project to re-implement the docs.
>> 
>> The project would consist of two parts:
>> 
>> 1. Build a Royale webpage that consists of a ‘doc page viewer’ to the left
>> and a sticky toc content list on the right.
>> The content is pulled out from our docs repo on GitHub using this basic
>> scheme [1]
>> The page would then be integrated into our WP site so the user doesn’t get
>> pulled away from the main site.
>> The look and feel would be identical to the main site too.
>> 
>> 2. Re-arrange and extend the doc pages into more encapsulated ’stories’.
>> Every story has a distinct beginning and end and covers one major part of
>> Royale’s workflow.
>> I don’t know what’s the best way to do this. I don’t want to mess up what
>> exists so should I make a new folder inside the current repo to put the
>> stories?
>> All stories should off course be agreed upon before they get published.
>> 
>> I will do this work in cooperation with Carlos.
>> Carlos and me would also be working on extending TourDeJewel
>> 
>> Thoughts?
>> 
>> Dany
>> 
>> 
>> 
>> 
>> [1] https://drive.google.com/open?id=1BwAEnTFnGf5k-hjvp1XUSdBdO2viALd2
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Trying to master SOF

[Dany Dhondt]

Hi Carlos,

Regarding notification from SO
Maybe you can try this [1] but I don’t know if RSS is still an option.
I don’t know if you can get notified by mail when a tag is used in new 
questions. I’m looking for a solution as well. 
When you ‘watch’ a particular question in SO, you will get email when something 
changes for that question.

Dany


[1] https://meta.stackoverflow.com/questions/254318/how-to-subscribe-to-tags

> Op 5 mei 2019, om 16:39 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi,
> 
> I'm trying to get notified watching the "apache-royale" tag, but I never
> get a mail.
> I suppose I must do some config to notify via email but can't find anything
> about this. All that I tried failed.
> Can someone help me with this?
> 
> In the other hand, I answered this question [1]
> And I wanted to put some MXML code, but the only way I found is via the
> internal tool to post HTML/JS/CSS code, that s ok to me since I can add the
> code to the HTML part,
> (I don't expect SOF provide a MXML editor of course)
> But I want to remove the blue button to "Run the code snippet"
> Is there a way to do it?
> 
> Thanks
> 
> [1]
> https://stackoverflow.com/questions/55981261/how-to-create-a-big-header-in-apache-royale/55993059#55993059
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Trying to master SOF

[Dany Dhondt]

Hi Carlos

If you post code that way, people are expecting runnable code which you should 
avoid when it’s not.
Displaying code style is possible by using ticks (`) or buy indenting text with 
4 spaces or more.

Dany

> Op 5 mei 2019, om 16:39 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi,
> 
> I'm trying to get notified watching the "apache-royale" tag, but I never
> get a mail.
> I suppose I must do some config to notify via email but can't find anything
> about this. All that I tried failed.
> Can someone help me with this?
> 
> In the other hand, I answered this question [1]
> And I wanted to put some MXML code, but the only way I found is via the
> internal tool to post HTML/JS/CSS code, that s ok to me since I can add the
> code to the HTML part,
> (I don't expect SOF provide a MXML editor of course)
> But I want to remove the blue button to "Run the code snippet"
> Is there a way to do it?
> 
> Thanks
> 
> [1]
> https://stackoverflow.com/questions/55981261/how-to-create-a-big-header-in-apache-royale/55993059#55993059
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Royale docs website integration

[Dany Dhondt]

HI,

I’d like to propose a project to re-implement the docs.

The project would consist of two parts:

1. Build a Royale webpage that consists of a ‘doc page viewer’ to the left and 
a sticky toc content list on the right.
The content is pulled out from our docs repo on GitHub using this basic scheme 
[1]
The page would then be integrated into our WP site so the user doesn’t get 
pulled away from the main site.
The look and feel would be identical to the main site too.

2. Re-arrange and extend the doc pages into more encapsulated ’stories’. Every 
story has a distinct beginning and end and covers one major part of Royale’s 
workflow.
I don’t know what’s the best way to do this. I don’t want to mess up what 
exists so should I make a new folder inside the current repo to put the 
stories? 
All stories should off course be agreed upon before they get published.

I will do this work in cooperation with Carlos. 
Carlos and me would also be working on extending TourDeJewel

Thoughts?

Dany




[1] https://drive.google.com/open?id=1BwAEnTFnGf5k-hjvp1XUSdBdO2viALd2

Re: Royale video tutorials

[Dany Dhondt]

Hi Piotr,

Very good news!
I just made a doc proposal too. Your video’s will be stories too, so we good 
join thoughts and idea’s on the stories?

Dany

> Op 5 mei 2019, om 12:12 heeft Piotr Zarzycki  het 
> volgende geschreven:
> 
> Hi Team,
> 
> FYI: About a week ago, thanks to Prominic’s support, me and my friend
> Adrian started working on a video tutorial about Royale Framework and
> Moonshine IDE. We have heard all the voices on the mailing list and social
> media and decided to help newcomers start their journey with
> Moonshine/Royale in the easiest way possible.
> 
> We are hoping to present the framework in the best light possible and
> enrich our tutorial with detailed examples of Royale usage.
> 
> To be able to achieve this goal we are going to improve existing
> documentation in the areas we find most important. Changes will be provided
> by Adrian through a pull requests and some emails on this list.
> 
> We hope to get your support and lots of help on the mailing list. :)
> 
> Thanks,
> -- 
> 
> Piotr Zarzycki
> 
> Patreon: *https://www.patreon.com/piotrzarzycki
> *

Re: [JOB] Moonshine-IDE.com is hiring contractors to bring Apache Royale to version 1.0

[Dany Dhondt]

Hi Piotr,
It’s an amazing offer and I’m sorry if there’s not much response. I am working 
on the doc section and spent some time on SO. I can’t meet the deadline though 
since my time is limited. You asked me to write an article on Royale vs React 
and I would like to do so but again need more time. 
So I hope you’ll get more response to your call. 
Succes
Dany

Verstuurd vanaf mijn iPhone

> Op 3 mei 2019 om 11:46 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> I tweet about it:
> 
> https://twitter.com/ApacheRoyale/status/1124248372569944065
> 
> Hopefully we can get more people to know about this offer
> 
> Share and retweet! :)
> 
> 
> 
> 
> 
> El vie., 3 may. 2019 a las 9:33, Piotr Zarzycki ()
> escribió:
> 
>> Too bad that this proposition is not being answered in any way. However
>> there is still time today submit your expectations and help this project
>> grow.
>> 
>> wt., 30 kwi 2019 o 08:24 Justin M. Hill  napisał(a):
>> 
>>> Hi Alex,
>>> 
>>> Thank you very much for providing insight into the proper way to approach
>>> these matters in the Apache way.  I will be mindful of the specific
>> wording
>>> in the future.
>>> 
>>> 
>>> Hi Dany,
>>> 
>>> It sounds to me like you know a lot about React!
>>> 
>>> Maybe you could start the React part of the comparison document or FAQ
>>> section, and then someone else who knows Royale better could fill in the
>>> comparison pieces.
>>> 
>>> If Royale hopes to have any wider adoption beyond traditional Flex
>>> developers, I personally think it must communicate clearly WHY
>> technically
>>> the development community should care.  This - to me at least - means a
>>> pros/cons list compared to other market incumbents, without being
>> marketing
>>> nonsense.  It should be based in facts about the technical architectures
>> --
>>> exactly as you start to describe in your message.
>>> 
>>> As Alex mentioned, we need these points to be factual and not opinion
>>> based to maintain the Apache way.   And actually, the facts are a lot
>> more
>>> useful than opinions, because otherwise technical conversations degrade
>>> into "I think X way is better", instead of X way requires A instead of B
>>> which is the method Y uses.  Exactly like your DOM rendering discussion.
>>> And that is precisely what it seems to me like you are starting to share
>>> below about things like JQuery not being usable with React.  A lot of
>>> people know JQuery and like it, so that seems to me something in the "+"
>>> column for Royale vs. React.
>>> 
>>> 
>>> Regarding command lines and power users / script -- I'm all for that.  I
>>> love UNIX / Linux / Mac Terminal ... However, I also hate forcing new
>> users
>>> who have limited time to learn unrelated things to their immediate task.
>>> Nobody using Mac for the first time starts with Terminal.  They ease
>> their
>>> way into it.  My hope is that we can achieve the easing in with Royale.
>>> Otherwise, I think too much brain power around the world right now is
>> being
>>> spent re-learning this stuff over and over again, when it could be point
>>> and click while still having the knobs to adjust behind the scenes.
>>> 
>>> 
>>> It is a minor personal mission of mine to make it easier for people like
>>> me who like to program, but have very little time to do so, and don't
>> have
>>> time to figure out all the nonsense I don't care about like NPM when I do
>>> have time to program.   I just want to be able to launch an IDE and tweak
>>> the Hello World example to see how to build useful things that I can
>> start
>>> to tailor for my needs.  That is one reason why I'm involved in
>>> Moonshine-IDE.com and it is one of the reasons I care about Royale:  we
>> can
>>> avoid the Javascript flavor of the month syndrome with Royale.   If I
>> later
>>> need to get under the hood and script some things together, I'm glad I
>> have
>>> that option.  But I don't want to start my learning experience with it.
>>> 
>>> 
>>> Anyway, back to the topic at hand -- I'd encourage you to submit a bid
>> for
>>> spending some of your professional time on this documentation effort on
>>> React.   Anything you can do to illuminate these differences would be
>> much
>>> appreciated, even if someone else has to fill in the Ro

Re: The start of a FullCalendar Royale component...

[Dany Dhondt]

The (very) good news is that is IS possible. To me as a developer (and others 
we’re hoping to use Royale), it is vital to know that it can be done. At some 
point in developing an application with Royale, we’ll stumble on some 
functionality or component which just isn’t available in Royale. At that point, 
it is simply not acceptable to say ‘well hey, it can’t be done right now but 
come back in a year or so’. 
FullCalendar is a good example because every developer will need a calendar 
component sooner or later. FC is becoming a standard in javascript (+70k 
downloads a week).
@Andrew, I’ll post the FullCalendar question on StackOverflow. Could you answer 
it? That way, Royale will emerge too when people search on the FullCalendar tag.
Another question: did you use the 4.x version of FC or the (older) 3.x version?

Thanks
Dany

> Op 3 mei 2019, om 07:55 heeft Piotr Zarzycki  het 
> volgende geschreven:
> 
> Hi Andrew,
> 
> First of all Thank you for using Moonshine! I think there is one good
> advantage to going by your approach instead typedefs. You can redefine API
> to completely new if you don't like in the original component. Those new
> API may have a bit more of a AS3 style etc.
> 
> Thanks,
> Piotr
> 
> On Fri, May 3, 2019, 6:26 AM Alex Harui  wrote:
> 
>> Hi Andrew,
>> 
>> That's cool!  Thank you for demonstrating that such a thing can be done.
>> 
>> I'm not sure there is a "best approach" for doing something like this.  It
>> really depends on how much time you want to put into it.  If you want to
>> use a 3rd-party component in your app and only want to use a few APIs, then
>> the approach you took is fine and solves your problem quickly.
>> 
>> On the other hand, if you want to make it complete and offer it to others
>> to use you may find that creating typedefs for the options and calendar
>> objects and other objects you are wrapping will eliminate the need to use
>> bracket access such as  'options["defaultView"] = _defaultView;' and thus
>> allow the IDE to offer better code-assist and catch typos so you don't
>> later waste time debugging why 'options["defaultview"]' is not working.
>> 
>> Thanks,
>> -Alex
>> 
>> On 5/2/19, 2:07 PM, "Frost, Andrew"  wrote:
>> 
>>Hi
>> 
>>Something that Dany Dhondt wrote recently, about using the
>> "fullcalendar" React component, got me to wondering how easy it was to wrap
>> these sorts of third party components into Royale.
>> 
>>The answer turned out to be: it's pretty straightforward. I'm not sure
>> I've used the best approach (no 'typedefs' or anything) but I've created
>> some wrapper classes that can be used from MXML to drop in a calendar
>> component and add events etc. Lots of extra work to do to get it to the
>> stage where it's as functional as the JS/React etc versions, but the lack
>> here is (a) time and (b) documentation (I can't see a full API for the
>> various FullCalendar classes..!)
>> 
>>Hope it's useful for folk to see how quickly this can be done...
>> 
>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fajwfrost%2Froyale-playground%2Ftree%2Fmaster%2FCalendarProjectdata=02%7C01%7Caharui%40adobe.com%7C19735c4310c64d1152b808d6cf423d43%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636924280737194314sdata=xmrL7z1UB9Mh3FpmbD6iGy9JORZ0YDmXjdiZvDJRm1Y%3Dreserved=0
>>(the wrapper classes are in src/io/fullcalendar, and the mxml file
>> that uses them is just src/CalendarProject.mxml .. I've been using
>> Moonshine and just uploaded the whole project so there's lots of irrelevant
>> files in there too!)
>> 
>> 
>>thanks
>> 
>>   Andrew
>> 
>> 
>> 
>> 
>> 

Re: Using @extrens ( RE: Example of access external JS using Apache Royale)

[Dany Dhondt]

Hi Josh,

Aren’t most of the packages just functions?
In ES6, you’d import packages as
Import { myFunct, myVar } from ‘my-package’
In older javascript you’d:
const myPackagePointer = require(‘my-package’)

So your ‘fun’ example sounds like heaven to me! This is exactly what we need.

About Typescript: do we need that at all? I think, but maybe this goes beyond 
my technical knowledge, all node packages are compiled into plain old 
javascript functions. Typescript is only needed for authoring the packages. 
Once compiled there’s no trace of Typescript at all. If this is indeed true, 
then we shouldn’t bother about Typescript at all, and just concentrate on 
incorporating the pure javascript libs. 

Dany

> Op 2 mei 2019, om 19:57 heeft Josh Tynjala  het 
> volgende geschreven:
> 
> Just for fun, here's another way that you could create a typedef for hljs so 
> that the highlightBlock() function is directly in a package (similar to 
> flash.net.navigateToURL), instead of as a static method on a class:
> 
> https://paste.apache.org/khVI
> 
> If you did it this way, you'd need to import it before you can call the 
> function, like this:
> 
> import hljs.highlightBlock;
> 
> Or this should work too, if you prefer:
> 
> import hljs.*;
> 
> And then you can call the function directly (without the hljs. prefix):
> 
> highlightBlock(block);
> 
> As you can see, the way that you choose to expose a JS library to 
> ActionScript is pretty flexible. Some JavaScript libraries are just a 
> function, and some have APIs that work more like classes. Depending on the 
> library, one way may work better than the other.
> 
> - Josh
> 
> On 2019/05/02 17:48:49, Josh Tynjala  wrote: 
>> Exactly right. When you create a typedef class, you're trying to simulate 
>> how you would access the API as if you were writing in plain JavaScript. You 
>> call hljs.highlightBlock() in JavaScript, so you need a class that works the 
>> same way in ActionScript.
>> 
>> Another option for organization would be to keep all of your typedefs in a 
>> separate folder from your app's source files, and reference the typedefs 
>> folder using the source-path compiler option.
>> 
>> - Josh
>> 
>> On 2019/05/02 16:23:45, Alex Harui  wrote: 
>>> Hi Carlos,
>>> 
>>> I don’t think hljs is in a package called "externs".  In Josh's example, 
>>> hljs was in the top-level package.  And that's because hljs is found at 
>>> runtime off of the global window object, not some sub-object called 
>>> "externs".  So, the hljs.as file containing the externs has to go in the 
>>> root of a source-path, not in some folder called "externs" (which is why 
>>> some folks will take the time to create a separate typedefs SWC so as not 
>>> to clutter the root of their application's source directory).
>>> 
>>> Then instead of "import externs.hljs", it should be "import hljs" (or 
>>> shouldn’t be needed at all).
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 5/2/19, 9:11 AM, "Carlos Rovira"  wrote:
>>> 
>>>Hi,
>>> 
>>>in my latest commit I added hljs extern class like Josh show in package
>>>externs in TDJ
>>> 
>>>Then I didn't commit the following since is not working for me:
>>> 
>>>1.- In HighlightCode class (in utils package TDJ)
>>> 
>>>added:
>>> 
>>>import externs.hljs;
>>> 
>>>changed the method highlightBlock to:
>>> 
>>>COMPILE::JS
>>>/**
>>>* block is the element (WrappedHTMLElement) inside the component (the
>>> tag)
>>>*/
>>>public function highlightBlock(block:Element):void
>>>{
>>>hljs.highlightBlock(block);
>>>}
>>> 
>>>and running it I get:
>>> 
>>>Uncaught ReferenceError: externs is not defined
>>>at utils.HighlightCode.highlightBlock (HighlightCode.as:53)
>>>at
>>>
>>> WelcomeSection.components.ExampleAndSourceCodeTabbedSectionContent.dataReadyHandler
>>>(ExampleAndSourceCodeTabbedSectionContent.as:138)
>>>at services.GitHubService.goog.events.EventTarget.fireListeners
>>>(eventtarget.js:284)
>>>at Function.goog.events.EventTarget.dispatchEventInternal_
>>>(eventtarget.js:381)
>>>at services.GitHubService.goog.events.EventTarget.dispatchEvent
>>>(eventtarget.js:196)
>>>at
>>>
>>> services.GitHubService.org.apache.royale.events.EventDispatcher.dispatchEvent
>>>(EventDispatcher.js:71)
>>>at services.GitHubService.services_GitHubService_completeHandler
>>>(GitHubService.as:54)
>>>at
>>>org.apache.royale.net.HTTPService.goog.events.EventTarget.fireListeners
>>>(eventtarget.js:284)
>>>at Function.goog.events.EventTarget.dispatchEventInternal_
>>>(eventtarget.js:381)
>>>at
>>>org.apache.royale.net.HTTPService.goog.events.EventTarget.dispatchEvent
>>>(eventtarget.js:196)
>>> 
>>>What I'm doing wrong?
>>> 
>>>thanks!
>>> 
>>> 
>>>El jue., 2 may. 2019 a las 18:02, Carlos Rovira 
>>> ()
>>>escribió:
>>> 
 Hi 

Re: Building a Faq for Royale

[Dany Dhondt]

Hi Alex,

The most important point in your answer to me is the distinction between dev 
and user.
We should indeed make this distinction. Maybe we shouldn’t contaminate the dev 
list with too many user questions.

To me, once we’re at user level, it’s all about ‘Usability’ and ‘Experience’.
People who ‘use’ Royale should get a great experience and feel comfortable.
And that’s why some of us think we’re not at v1.0 phase yet. The experience is 
too scrambled and confusing at this moment.

A faq is literally an aggregation of questions that get asked over and over 
again and therefore, I agree that the questions should be asked on SO first and 
that the accepted answer (or a digest of the accepted answer) is copied over 
the faq section of our website. @Carlos: could you agree with that?

I went through the docs section on our website (which is generated 
automatically form the royale-docs repo?) and I don’t have a satisfying 
experience yet. We should make ’stories’ instead of ‘pages’. 

If you switch between royale.apache.org and apache.github.io, you’ll see what I 
mean. It’s subtle but it’s there.
Once you get at the ‘Welcome to Apache Royale’ page, I’m expecting the full TOC 
at the right hand size which stays there all the time. I’d like to see at any 
moment where I am. This TOC should be the same all the way. It shouldn’t change 
depending on the page I am viewing at the moment.

Look at the doc section at reactjs.org [1] or angular.io [2]  (I think we 
should use VAR (Vue, Angular, React) as our benchmarks)

One subject is one page (our docs are too much separated into individual pages) 
even if the page is very long. You just scroll down until you’ve read the whole 
story. At all times, the navigation section should be sticky on the left 
(angular) or the right (react)
In the Royale docs, most ’steps’ are a separate page. 

So it’s mostly re-arranging content, though some pages are still empty. .md 
pages are fine. React docs are at GitHub too (you can even edit them!).

Code examples should stand out very clearly (I like the way react does: black 
background)

Another example of great documentation is on semantic-ui-react [3]
There, they make it possible to alter the react code inline. It is immediately 
re-rendered in the html page!

Which bring me to a side track: will it be possible to post royale snippets of 
code on codesandbox [4] or jsfiddle [5]? On SO, if you ask a particular 
question concerning code, you’ll be asked to post a working example somewhere.

So what I would like to propose:

- We focus on asking all user questions on SO. Everyone of us who is willing 
answers questions. Don’t forget to upvote answer AND the question itself! TIP: 
if you are on SO, go to the tag section and look for apache-royale, then hit 
the ‘watch tag’ button underneath so you get notified of new question regarding 
royale.
- When a question’s is accepted, and the question itself is important enough, 
we digest it to the faq section on our website.
- We agree on a TOC for the docs. 
- Make a fixed navigation aside on the website.
- Doc ’stories’ are written and maintained at the GitHub repo.
- Docs are re-organized into well encapsulated stories and someone writes a 
script to update them in apache.royale.org (?). @Carlos: to me, it sounds like 
linking the .md file to a docs page in WordPress? Is that possible?

[1] https://reactjs.org/docs/getting-started.html
[2] https://angular.io/docs
[3] https://react.semantic-ui.com
[4] https://codesandbox.io
[5] https://jsfiddle.net

And a final question: do we post this kind of threads on u...@royale.org from 
now on?

Dany



> Op 1 mei 2019, om 08:55 heeft Alex Harui  het 
> volgende geschreven:
> 
> Hi Dany,
> 
> I don't have any formed opinion on the best way to collect FAQ.
> 
> FWIW, in theory, dev@ is for questions related to the development of the 
> framework code that goes in the Apache Royale repos.  Users@ and 
> StackOverflow (SO) are intended to support folks using Royale to build 
> applications.  Some Apache projects don't even have a users@ list, they only 
> use SO and vice-versa.  I'm assuming you want to build a FAQ for application 
> developers and maybe SO is a good enough way to determine FAQ since folks can 
> upvote questions.
> 
> Or maybe the FAQ should be about getting started and SO will cover harder 
> questions.  I'm not sure it matters.  I'll be happy if folks are asking 
> questions because it means they are using Royale.  So try something, let's 
> see how it feels and adjust as we go.
> 
> My main point in my previous post was to encourage us to use the public repos 
> and wikis to lower the effort for others to contribute.
> 
> My 2 cents,
> -Alex
> 
> On 4/30/19, 10:14 PM, "Dany Dhondt"  wrote:
> 
>Hi Alex,
> 
>Would it be an idea to launch every new question on this list with a [FAQ] 
> prefix, discuss it and wh

Re: Example of access external JS using Apache Royale

[Dany Dhondt]

Wouldn’t it be a nice proof of concept if we tried to implement a widely used 
js lib into Royale?
There are a lot of js packages that are used thousands of times a day, like 
moment.js, lodash, …

Dany

> Op 1 mei 2019, om 01:13 heeft Alex Harui  het 
> volgende geschreven:
> 
> Isn't the ACE editor already an example?  Or maybe there are different 
> scenarios for external JS usage.
> 
> -Alex
> 
> On 4/30/19, 2:42 PM, "Carlos Rovira"  > wrote:
> 
>Hi,
> 
>I'm planing to make a blog example about using external JS or CSS in Apache
>Royale since people ask for it, and I think is one of the key points for
>people that wants to use Royale.
>My plan is to create a simple example that imports a JS script and then use
>bracket access. The example in concrete will use the script for coloring
>code that we use in TDJ that is external to Royale to show how we do it.
> 
>But I think that's just one of the ways to use external JS (bracket
>notation access).
>I think there's more:
>- dot notation -> but this required typedefs (Let me know if I'm wrong).
>and in that case, I don't have clear where we can add code to typedefs to
>do this. In the other way, how users can do something like this in their
>codebases. For me this is unexplored terrain, so hope others that knows
>about it could give some techniques, or point to some docs if we already
>has something. Maybe it could be great they could write some doc in our
>GitHub pages
> 
>- More ways?? Let me know.
> 
>I can work on this in few days , hope you could let me know about those
>alternate methods I didn't control
> 
>thanks
> 
>-- 
>Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C91b86d3f05e94a7fad1a08d6cdb4b310%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922573317036871sdata=48234zx%2FlriaHuhJcqvUq05R1cZNJgkP8y5Jh3K2IKM%3Dreserved=0
>  
> 

Re: Building a Faq for Royale

[Dany Dhondt]

Hi Alex,

Would it be an idea to launch every new question on this list with a [FAQ] 
prefix, discuss it and when the answer is accepted, post it to the Faq section?

Dany

> Op 1 mei 2019, om 00:45 heeft Alex Harui  het 
> volgende geschreven:
> 
> FWIW, I would much prefer that the FAQ be part of the royale-docs so we can 
> get PRs from folks.
> 
> Thoughts?
> -Alex
> 
> On 4/30/19, 2:08 PM, "Carlos Rovira"  <mailto:carlosrov...@apache.org>> wrote:
> 
>Hi Dany,
> 
>just created you account. I write it to your @mac.com account now to send
>you user/pass
>if you don't get nothing let me know privately
>thanks
> 
>El mar., 30 abr. 2019 a las 17:19, Dany Dhondt 
> ()
>escribió:
> 
>> No. It IS the right address. Don’t know why it marked as INVALID
>> Dany
>> 
>> Verstuurd vanaf mijn iPhone
>> 
>>> Op 30 apr. 2019 om 17:04 heeft Carlos Rovira 
>> het volgende geschreven:
>>> 
>>> Dany,
>>> please sent me the email I must use privately, since yours in the list
>> puts
>>> "invalid" so I think is not the want you use.
>>> thanks!
>>> 
>>> El mar., 30 abr. 2019 a las 17:03, Carlos Rovira (<
>> carlosrov...@apache.org>)
>>> escribió:
>>> 
>>>> Hi Dany,
>>>> 
>>>> I already shared the actual FAQ link [1], maybe you missed it.
>>>> You can change it whatever you want, just think that changes will need
>>>> approve of the rest.
>>>> 
>>>> I'll sent you know credentials in private
>>>> 
>>>> thanks!
>>>> 
>>>> [1] 
>>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ffaq%2Fdata=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295sdata=2m2QWWXA9BP3OQv2LcDmL9qfyyuO7GxUjPlhGWdZ28k%3Dreserved=0
>>>>  
>>>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Ffaq%2Fdata=02%7C01%7Caharui%40adobe.com%7C8ca60f9fa4c347b4a30f08d6cdaff832%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636922553002484295sdata=2m2QWWXA9BP3OQv2LcDmL9qfyyuO7GxUjPlhGWdZ28k%3Dreserved=0>
>>>> 
>>>> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt
>> (mailto:archeme...@mac.com.invalid>>)
>>>> escribió:
>>>> 
>>>>> Hi Carlos,
>>>>> 
>>>>> That’s ok.
>>>>> Maybe you could setup a Faq section and create the empty base page so I
>>>>> don’t mess anything up?
>>>>> 
>>>>> Thx
>>>>> Dany
>>>>> 
>>>>>> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira <
>> carlosrov...@apache.org <mailto:carlosrov...@apache.org>>
>>>>> het volgende geschreven:
>>>>>> 
>>>>>> Hi Dany,
>>>>>> 
>>>>>> I can give you access to our pre production web site, so you can
>> change
>>>>>> text content. Then as you finish others can review and see if all is
>> ok
>>>>> or
>>>>>> needs any adjustment, etc... then we willl publish it to the public
>>>>> site.
>>>>>> If you are ok I can make you and user in private. Just a warning:
>> since
>>>>> we
>>>>>> use Wordpress that use to be very sensitive to global changes, you
>>>>> should
>>>>>> try just to touch "content" (add a section, add rows, add text,...),
>>>>> but if
>>>>>> you see other changes are needed please first ask about it, since some
>>>>>> times this could lead to other derivate problems.
>>>>>> 
>>>>>> thanks!
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
>>>>> (mailto:archeme...@mac.com.invalid>>)
>>>>>> escribió:
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> Seems the idea of having a faq section on our website is supported.
>>>>>>> I’m willing to start such a faq.
>>>>>>> How do we tackle this? Do we need a database or keep it plain text?
>>>>> Anyone
>>>>>>> know of an online tool to manage it?
>>>>>>> Who’s managing the website itself?
>&

Re: Building a Faq for Royale

[Dany Dhondt]

No. It IS the right address. Don’t know why it marked as INVALID
Dany

Verstuurd vanaf mijn iPhone

> Op 30 apr. 2019 om 17:04 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Dany,
> please sent me the email I must use privately, since yours in the list puts
> "invalid" so I think is not the want you use.
> thanks!
> 
> El mar., 30 abr. 2019 a las 17:03, Carlos Rovira ()
> escribió:
> 
>> Hi Dany,
>> 
>> I already shared the actual FAQ link [1], maybe you missed it.
>> You can change it whatever you want, just think that changes will need
>> approve of the rest.
>> 
>> I'll sent you know credentials in private
>> 
>> thanks!
>> 
>> [1] https://royale.apache.org/faq/
>> 
>> El mar., 30 abr. 2019 a las 16:54, Dany Dhondt ()
>> escribió:
>> 
>>> Hi Carlos,
>>> 
>>> That’s ok.
>>> Maybe you could setup a Faq section and create the empty base page so I
>>> don’t mess anything up?
>>> 
>>> Thx
>>> Dany
>>> 
>>>> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira 
>>> het volgende geschreven:
>>>> 
>>>> Hi Dany,
>>>> 
>>>> I can give you access to our pre production web site, so you can change
>>>> text content. Then as you finish others can review and see if all is ok
>>> or
>>>> needs any adjustment, etc... then we willl publish it to the public
>>> site.
>>>> If you are ok I can make you and user in private. Just a warning: since
>>> we
>>>> use Wordpress that use to be very sensitive to global changes, you
>>> should
>>>> try just to touch "content" (add a section, add rows, add text,...),
>>> but if
>>>> you see other changes are needed please first ask about it, since some
>>>> times this could lead to other derivate problems.
>>>> 
>>>> thanks!
>>>> 
>>>> 
>>>> 
>>>> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt
>>> ()
>>>> escribió:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> Seems the idea of having a faq section on our website is supported.
>>>>> I’m willing to start such a faq.
>>>>> How do we tackle this? Do we need a database or keep it plain text?
>>> Anyone
>>>>> know of an online tool to manage it?
>>>>> Who’s managing the website itself?
>>>>> 
>>>>> Thoughts?
>>>>> 
>>>>> thx
>>>>> Dany
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Carlos Rovira
>>>> http://about.me/carlosrovira
>>> 
>>> 
>> 
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Re: Building a Faq for Royale

[Dany Dhondt]

Hi Carlos,

That’s ok.
Maybe you could setup a Faq section and create the empty base page so I don’t 
mess anything up?

Thx
Dany

> Op 30 apr. 2019, om 16:42 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi Dany,
> 
> I can give you access to our pre production web site, so you can change
> text content. Then as you finish others can review and see if all is ok or
> needs any adjustment, etc... then we willl publish it to the public site.
> If you are ok I can make you and user in private. Just a warning: since we
> use Wordpress that use to be very sensitive to global changes, you should
> try just to touch "content" (add a section, add rows, add text,...), but if
> you see other changes are needed please first ask about it, since some
> times this could lead to other derivate problems.
> 
> thanks!
> 
> 
> 
> El mar., 30 abr. 2019 a las 16:30, Dany Dhondt ()
> escribió:
> 
>> Hi,
>> 
>> Seems the idea of having a faq section on our website is supported.
>> I’m willing to start such a faq.
>> How do we tackle this? Do we need a database or keep it plain text? Anyone
>> know of an online tool to manage it?
>> Who’s managing the website itself?
>> 
>> Thoughts?
>> 
>> thx
>> Dany
> 
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

Building a Faq for Royale

[Dany Dhondt]

Hi,

Seems the idea of having a faq section on our website is supported.
I’m willing to start such a faq. 
How do we tackle this? Do we need a database or keep it plain text? Anyone know 
of an online tool to manage it?
Who’s managing the website itself?

Thoughts?

thx
Dany

Re: Let's bump Royale version to 1.0 -- submit your bid for assistance to the group by Friday May 3

[Dany Dhondt]

los specifically need to be convinced to push 
> to 1.0 release
> 
> THEN
> 
> Please submit to this public group your commitment and cost.
> 
> We will then do this democratically:  
> deadline for bid submissions is 7 days from now -- Friday May 3.
> Carlos (or someone who knows Twitter enough to create another poll) will then 
> do another Twitter vote poll for 3 days to decide who gets the bids
> 
> 
> 
> Ideally multiple people will commit to doing something "small" for $500 each 
> and we can award 5 people the projects.
> 
> The $2,500 USD total will be paid via PayPal.  No exceptions.
> 
> 
> IF within 30 days Apache Royale 1.0 is released to the public then the 
> Moonshine IDE team will again donate $2,500 for the month of June in an 
> identical voting scenario (assuming this one works well) to bring home a 1.1 
> release.
> 
> 
> By 60 days from now, a new user who has never seen Royale before or 
> programmed in ActionScript should be able to:
> 1) Arrive at the Apache Royale web page
> 
> 2) Understand from the home page why they should care about the project if 
> they come from React, Vue, Angular, Flex, or ActionScript worlds
> 
> 3) Be able to within 5 mouse clicks (download button, install button, launch 
> button, build button, run button) go from having nothing on their machine to 
> having an IDE (we of course volunteer Moonshine but Visual Studio Code should 
> be a goal for this, too) on their machine with a successful build of their 
> first "hello world".  No command line nonsense.  No learning NPM, Git, 
> downloading 20 required packages.   See Royale website.  Want to try it.  5 
> clicks later build your Hello World.
> 
> If the above 3 goals are met, then the Moonshine IDE team will run a 3rd 
> donation round of $2,500 for the month of July in a manner to the description 
> above to bring home a 1.2 release, to be published no later than the end of 
> July 2019 for the awards to be paid.
> 
> 
> Hopefully this helps motivate the team.
> 
> Thank you,
> 
> Justin Hill
> 
> 
> 
> 
> dev-digest-help---04/26/2019 11:04:17 PM---dev Digest 27 Apr 2019 04:04:13 
> - Issue 1966 Topics (messages 9894 through 9902)
> 
> From: dev-digest-h...@royale.apache.org
> To:   dev@royale.apache.org
> Date: 04/26/2019 11:04 PM
> Subject:  [External] dev Digest 27 Apr 2019 04:04:13 - Issue 1966 - 
> Dany replies about React, Vue, Angular
> 
> 
> 
> 
> dev Digest 27 Apr 2019 04:04:13 - Issue 1966
> 
> Topics (messages 9894 through 9902)
> 
> Re: Let's bump Royale version to 1.0
> 9894 by: Dany Dhondt
> 9896 by: Carlos Rovira
> 
> Re: Version property (was: Let's bump Royale version to 1.0)
> 9895 by: Alex Harui
> 
> Release Step 001 Succeeded
> 9897 by: Apache Royale CI Server
> 
> Release Step 001a Succeeded
> 9898 by: Apache Royale CI Server
> 
> Release Step 002 Succeeded
> 9899 by: Apache Royale CI Server
> 
> Release Step 002a Succeeded
> 9900 by: Apache Royale CI Server
> 
> Release Step 003 Succeeded
> 9901 by: Apache Royale CI Server
> 
> Build failed in Jenkins: royale-asjs_MXTests #722
> 9902 by: Apache Royale CI Server
> 
> Administrivia:
> 
> -
> To post to the list, e-mail: dev@royale.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscr...@royale.apache.org
> For additional commands, e-mail: dev-digest-h...@royale.apache.org
> 
> --
> 
> 
> - Message from Dany Dhondt  on Fri, 26 Apr 
> 2019 16:06:59 +0200 -
> To:
> dev@royale.apache.org
> Subject:
> Re: Let's bump Royale version to 1.0
> I’m all for buikding a knowledge base in Stack Overflow! The mailing list 
> should only be used for developing Royale. Questions about using Royale 
> should go to SO
> 
> The competitors of Royale are React, Vue, Angular, ...
> Lots of developers are now used to those workflows. 
> In case of React, create-react-app sets you up with a brand new, ready to go 
> project in less than 30 seconds. That should be a benchmark for Royale imo. 
> 
> Dany
> 
> 
> Verstuurd vanaf mijn iPhone
> 
> > Op 26 apr. 2019 om 12:42 heeft Frost, Andrew  het 
> > volgende geschreven:
> > 
> > One other thought ... currently the way people ask for support is via these 
> > mailing lists. Which are okay but I'm always conscious that I'm potentially 
> > spamming people, plus the volume of mails is such that I have a rule to 
> > push all these into a folder that I then review every day or two..
> > 
> > But if I w

Re: StackOverflow tips

[Dany Dhondt]

Yes, you’re right.


Verstuurd vanaf mijn iPhone

> Op 29 apr. 2019 om 20:20 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi Danny,
> 
> I think "as3" and "mxml" should be on itself. if people wants to relate to
> Royale they should add "apache-royale", if not I think we'll end with many
> tags, and we should try to "concentrate" knowledge as much as possible.
> 
> 
> El lun., 29 abr. 2019 a las 19:24, Dany Dhondt ()
> escribió:
> 
>> Great idea!
>> If we have our tag(s), we’re on our way.
>> And what about ‘royale-mxml’ and ‘royale-as3’?
>> 
>> Dany
>> 
>>> Op 29 apr. 2019, om 19:18 heeft Carlos Rovira 
>> het volgende geschreven:
>>> 
>>> Should I ask on our twitter account for someone that could create stack
>>> over flow "apache-royals" tag?
>>> I can share that we want to start participating there...
>>> thoughts?
>>> 
>>> El lun., 29 abr. 2019 a las 19:06, Dany Dhondt
>> ()
>>> escribió:
>>> 
>>>> Hi, has anyone more than 1500 reputation points on SO?
>>>> 
>>>> To create tags on SO you need 1500 reps [1]
>>>> How to gain reputation [2]
>>>> Answering your own question [3]
>>>> 
>>>> 
>>>> [1]
>>>> 
>> https://meta.stackexchange.com/questions/103676/how-to-add-a-new-tag-on-stack-overflow
>>>> [2] https://stackoverflow.com/help/whats-reputation
>>>> [3] https://stackoverflow.com/help/self-answer
>>> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>> 
>> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira

StackOverflow tips

[Dany Dhondt]

Hi, has anyone more than 1500 reputation points on SO?

To create tags on SO you need 1500 reps [1]
How to gain reputation [2]
Answering your own question [3]


[1] 
https://meta.stackexchange.com/questions/103676/how-to-add-a-new-tag-on-stack-overflow
[2] https://stackoverflow.com/help/whats-reputation
[3] https://stackoverflow.com/help/self-answer

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Carlos,

Everyone can add a comment to a question. Once you’ve earned enough reputation, 
you can actually ‘answer’ a question.

Reputation points are earned mainly through being upvoted by someone else. So, 
If your read a question which is interesting, upvote the question.
If you read a comment or an answer which is good, upvote that.
If you want to comment on a question or on a comment, don’t hesitate because 
that’s when other people can upvote your comment!

Dany

> Op 29 apr. 2019, om 18:50 heeft Carlos Rovira  het 
> volgende geschreven:
> 
> Hi,
> agree too, I think the most convenient is "apache-royale", so go ahead.
> 
> If I want to respond a question you post, I can do it directly? or I must
> earn some points first doing something?
> 
> thanks!
> 
> 
> 
> El lun., 29 abr. 2019 a las 18:41, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
> 
>> Dany,
>> 
>> Thanks. I'm personally fine if it is common to use apache-royale tag.
>> Anyone is not in favor of that ?
>> 
>> Piotr
>> 
>> pon., 29 kwi 2019 o 18:38 Dany Dhondt 
>> napisał(a):
>> 
>>> Piotr,
>>> 
>>> If you do a search on apache, here are some of the tags:
>>> 
>>> apache-camel
>>> apache-flink
>>> apache-spark
>>> apache-storm
>>> …
>>> 
>>> A few other examples:
>>> 
>>> react-native
>>> create-react-app
>>> …
>>> 
>>> Is you browse the tags on SO, you’ll see it’s very common.
>>> 
>>> Also, npm naming conventions are all dash separated, or hyphen separated.
>>> 
>>> I think we should follow this naming convention.
>>> 
>>> Dany
>>> 
>>> 
>>> 
>>>> Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com> het volgende geschreven:
>>>> 
>>>> Dany,
>>>> 
>>>> Is it a common way on stack overflow ? It looks too me to complicated,
>>> have
>>>> something additional between two word.
>>>> 
>>>> Thanks,
>>>> Piotr
>>>> 
>>>> pon., 29 kwi 2019 o 18:01 Dany Dhondt 
>>>> napisał(a):
>>>> 
>>>>> Shouldn’t it be better to name it apache-royale?
>>>>> That’s the way most tags are build I think
>>>>> 
>>>>> Dany
>>>>> 
>>>>> 
>>>>>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
>>>>> piotrzarzyck...@gmail.com> het volgende geschreven:
>>>>>> 
>>>>>> Hi Dany,
>>>>>> 
>>>>>> We have agreed on "apacheroyale" tag in different thread. I think you
>>>>> could
>>>>>> use that.
>>>>>> 
>>>>>> Thanks,
>>>>>> Piotr
>>>>>> 
>>>>>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
>>>>>> napisał(a):
>>>>>> 
>>>>>>> Can somebody create some royale tags please? I don’t have enough
>> rep.
>>>>>>> points at this moment.
>>>>>>> Also, shouldn’t we agree on some basic royale tags?
>>>>>>> When the tags are made, I’ll start posting some questions.
>>>>>>> 
>>>>>>> Dany
>>>>>>> 
>>>>>>>> Op 29 apr. 2019, om 17:27 heeft Alex Harui
>> >>> 
>>>>>>> het volgende geschreven:
>>>>>>>> 
>>>>>>>> I agree we want to develop a presence on Stack Overflow.  I still
>>> can't
>>>>>>> figure out how to earn enough points be able to answer any questions
>>> so
>>>>> I
>>>>>>> won't be of much help until that happens.
>>>>>>>> 
>>>>>>>> -Alex
>>>>>>>> 
>>>>>>>> On 4/29/19, 7:32 AM, "Carlos Rovira" 
>>> wrote:
>>>>>>>> 
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> about StackOverFlow, we already discussed to start creating
>>> questions
>>>>>>> in
>>>>>>>> SOF, but finally nobody does. I think I should not create one and
>>>>>>> respond
>>>>>>>> myself right? it will be very sad to do in that way. So if someone
>>>>>>> start to

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Piotr,

If you do a search on apache, here are some of the tags:

apache-camel
apache-flink
apache-spark
apache-storm
…

A few other examples:

react-native
create-react-app
…

Is you browse the tags on SO, you’ll see it’s very common.

Also, npm naming conventions are all dash separated, or hyphen separated.

I think we should follow this naming convention.

Dany



> Op 29 apr. 2019, om 18:14 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> Dany,
> 
> Is it a common way on stack overflow ? It looks too me to complicated, have
> something additional between two word.
> 
> Thanks,
> Piotr
> 
> pon., 29 kwi 2019 o 18:01 Dany Dhondt 
> napisał(a):
> 
>> Shouldn’t it be better to name it apache-royale?
>> That’s the way most tags are build I think
>> 
>> Dany
>> 
>> 
>>> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki <
>> piotrzarzyck...@gmail.com> het volgende geschreven:
>>> 
>>> Hi Dany,
>>> 
>>> We have agreed on "apacheroyale" tag in different thread. I think you
>> could
>>> use that.
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
>>> napisał(a):
>>> 
>>>> Can somebody create some royale tags please? I don’t have enough rep.
>>>> points at this moment.
>>>> Also, shouldn’t we agree on some basic royale tags?
>>>> When the tags are made, I’ll start posting some questions.
>>>> 
>>>> Dany
>>>> 
>>>>> Op 29 apr. 2019, om 17:27 heeft Alex Harui 
>>>> het volgende geschreven:
>>>>> 
>>>>> I agree we want to develop a presence on Stack Overflow.  I still can't
>>>> figure out how to earn enough points be able to answer any questions so
>> I
>>>> won't be of much help until that happens.
>>>>> 
>>>>> -Alex
>>>>> 
>>>>> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
>>>>> 
>>>>>  Hi,
>>>>> 
>>>>>  about StackOverFlow, we already discussed to start creating questions
>>>> in
>>>>>  SOF, but finally nobody does. I think I should not create one and
>>>> respond
>>>>>  myself right? it will be very sad to do in that way. So if someone
>>>> start to
>>>>>  post questions in SOF, I promise to respond, at least if it's
>>>> something I
>>>>>  can know how to respond. It could be things you already know, but we
>>>> must
>>>>>  start in some way.
>>>>> 
>>>>>  SOF is crucial for us, I talked with customers that pointed me that
>>>> Apache
>>>>>  Royale is not on SOF, so his devs can easily search problems there.
>>>> And
>>>>>  this is the google for developers. If we are not there, Royale will
>>>> never
>>>>>  succeed, So if you want Royale to succeed we all should put some
>>>> work, what
>>>>>  we can, in SOF. @dany, if you want to start this effort we can follow
>>>> you.
>>>>>  Just let's know in a mail here so we can go to that link and respond.
>>>> If
>>>>>  you start that your work will be follow :)
>>>>> 
>>>>>  @Andrew, "Flex In a Week" is a very good idea too. I think we can
>>>> work on
>>>>>  that, but again, we need some kind of plan. A team to work on that.
>>>> Things
>>>>>  like that can't be create by only one man's work. Volunteers?
>>>>> 
>>>>>  @Om, I not use NPM but will try Royale CLI since we need something
>>>> really
>>>>>  fast to compete with React or others, or people will never jump to
>> out
>>>>>  wagon.
>>>>> 
>>>>>  thanks for all the thoughts! :)
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>>  El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
>>>> bigosma...@gmail.com>)
>>>>>  escribió:
>>>>> 
>>>>>> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt
>> >>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>> I’m all for buikding a knowledge base in Stack Overflow! The mailing
>>>> list
>>>>>>> should only be used for developing Royale. Questions about using
>> Roy

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Alex,

By commenting on questions, and when somebody upvotes your comment, you’ll earn 
points and at some point, you’ll get a badge permitting you to answer questions

Dany

> Op 29 apr. 2019, om 17:56 heeft Dany Dhondt  het 
> volgende geschreven:
> 
>> I agree we want to develop a presence on Stack Overflow.  I still can't 
>> figure out how to earn enough points be able to answer any questions so I 
>> won't be of much help until that happens.

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Shouldn’t it be better to name it apache-royale?
That’s the way most tags are build I think

Dany


> Op 29 apr. 2019, om 17:58 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> Hi Dany,
> 
> We have agreed on "apacheroyale" tag in different thread. I think you could
> use that.
> 
> Thanks,
> Piotr
> 
> pon., 29 kwi 2019 o 17:56 Dany Dhondt 
> napisał(a):
> 
>> Can somebody create some royale tags please? I don’t have enough rep.
>> points at this moment.
>> Also, shouldn’t we agree on some basic royale tags?
>> When the tags are made, I’ll start posting some questions.
>> 
>> Dany
>> 
>>> Op 29 apr. 2019, om 17:27 heeft Alex Harui 
>> het volgende geschreven:
>>> 
>>> I agree we want to develop a presence on Stack Overflow.  I still can't
>> figure out how to earn enough points be able to answer any questions so I
>> won't be of much help until that happens.
>>> 
>>> -Alex
>>> 
>>> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
>>> 
>>>   Hi,
>>> 
>>>   about StackOverFlow, we already discussed to start creating questions
>> in
>>>   SOF, but finally nobody does. I think I should not create one and
>> respond
>>>   myself right? it will be very sad to do in that way. So if someone
>> start to
>>>   post questions in SOF, I promise to respond, at least if it's
>> something I
>>>   can know how to respond. It could be things you already know, but we
>> must
>>>   start in some way.
>>> 
>>>   SOF is crucial for us, I talked with customers that pointed me that
>> Apache
>>>   Royale is not on SOF, so his devs can easily search problems there.
>> And
>>>   this is the google for developers. If we are not there, Royale will
>> never
>>>   succeed, So if you want Royale to succeed we all should put some
>> work, what
>>>   we can, in SOF. @dany, if you want to start this effort we can follow
>> you.
>>>   Just let's know in a mail here so we can go to that link and respond.
>> If
>>>   you start that your work will be follow :)
>>> 
>>>   @Andrew, "Flex In a Week" is a very good idea too. I think we can
>> work on
>>>   that, but again, we need some kind of plan. A team to work on that.
>> Things
>>>   like that can't be create by only one man's work. Volunteers?
>>> 
>>>   @Om, I not use NPM but will try Royale CLI since we need something
>> really
>>>   fast to compete with React or others, or people will never jump to out
>>>   wagon.
>>> 
>>>   thanks for all the thoughts! :)
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala (<
>> bigosma...@gmail.com>)
>>>   escribió:
>>> 
>>>> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt >> 
>>>> wrote:
>>>> 
>>>>> I’m all for buikding a knowledge base in Stack Overflow! The mailing
>> list
>>>>> should only be used for developing Royale. Questions about using Royale
>>>>> should go to SO
>>>>> 
>>>>> The competitors of Royale are React, Vue, Angular, ...
>>>>> Lots of developers are now used to those workflows.
>>>>> In case of React, create-react-app sets you up with a brand new, ready
>> to
>>>>> go project in less than 30 seconds. That should be a benchmark for
>> Royale
>>>>> imo.
>>>>> 
>>>>> Dany
>>>>> 
>>>>> 
>>>> The Royale CLI is modeled closely after the create-react-app.  The docs
>> for
>>>> the alpha version is available here:
>>>> 
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
>>>> If I get more feedback, I am keep improving this tool.
>>>> 
>>>> Thanks,
>>>> Om
>>>> 
>>>> 
>>>> 
>>>>> Verstuurd vanaf mijn iPhone
>>>>> 
>>>>>> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew >> 
>>>>> het volgende geschreven:
>>>>>> 
>>>>>> One other thought ... currently the way peo

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

Can somebody create some royale tags please? I don’t have enough rep. points at 
this moment.
Also, shouldn’t we agree on some basic royale tags?
When the tags are made, I’ll start posting some questions.

Dany

> Op 29 apr. 2019, om 17:27 heeft Alex Harui  het 
> volgende geschreven:
> 
> I agree we want to develop a presence on Stack Overflow.  I still can't 
> figure out how to earn enough points be able to answer any questions so I 
> won't be of much help until that happens.
> 
> -Alex
> 
> On 4/29/19, 7:32 AM, "Carlos Rovira"  wrote:
> 
>Hi,
> 
>about StackOverFlow, we already discussed to start creating questions in
>SOF, but finally nobody does. I think I should not create one and respond
>myself right? it will be very sad to do in that way. So if someone start to
>post questions in SOF, I promise to respond, at least if it's something I
>can know how to respond. It could be things you already know, but we must
>start in some way.
> 
>SOF is crucial for us, I talked with customers that pointed me that Apache
>Royale is not on SOF, so his devs can easily search problems there. And
>this is the google for developers. If we are not there, Royale will never
>succeed, So if you want Royale to succeed we all should put some work, what
>we can, in SOF. @dany, if you want to start this effort we can follow you.
>Just let's know in a mail here so we can go to that link and respond. If
>you start that your work will be follow :)
> 
>@Andrew, "Flex In a Week" is a very good idea too. I think we can work on
>that, but again, we need some kind of plan. A team to work on that. Things
>like that can't be create by only one man's work. Volunteers?
> 
>@Om, I not use NPM but will try Royale CLI since we need something really
>fast to compete with React or others, or people will never jump to out
>wagon.
> 
>thanks for all the thoughts! :)
> 
> 
> 
> 
> 
>El lun., 29 abr. 2019 a las 9:17, OmPrakash Muppirala 
> ()
>escribió:
> 
>> On Fri, Apr 26, 2019 at 7:37 PM Dany Dhondt 
>> wrote:
>> 
>>> I’m all for buikding a knowledge base in Stack Overflow! The mailing list
>>> should only be used for developing Royale. Questions about using Royale
>>> should go to SO
>>> 
>>> The competitors of Royale are React, Vue, Angular, ...
>>> Lots of developers are now used to those workflows.
>>> In case of React, create-react-app sets you up with a brand new, ready to
>>> go project in less than 30 seconds. That should be a benchmark for Royale
>>> imo.
>>> 
>>> Dany
>>> 
>>> 
>> The Royale CLI is modeled closely after the create-react-app.  The docs for
>> the alpha version is available here:
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Ftree%2Fdevelop%2Fnpm%2Fclidata=02%7C01%7Caharui%40adobe.com%7C950f12a2b0f24cad192508d6ccaf8241%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636921451512477017sdata=4VN8JejglMeW08ZcNV6fCJ%2BdYJjOHcvfGDL099jives%3Dreserved=0
>> If I get more feedback, I am keep improving this tool.
>> 
>> Thanks,
>> Om
>> 
>> 
>> 
>>> Verstuurd vanaf mijn iPhone
>>> 
>>>> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew 
>>> het volgende geschreven:
>>>> 
>>>> One other thought ... currently the way people ask for support is via
>>> these mailing lists. Which are okay but I'm always conscious that I'm
>>> potentially spamming people, plus the volume of mails is such that I
>> have a
>>> rule to push all these into a folder that I then review every day or
>> two..
>>>> 
>>>> But if I want to find something out, I tend not to go search the
>> mailing
>>> list, I tend to search online. Looking through mailing list threads isn't
>>> the easiest (and search engines don't necessarily pick things up from
>> them
>>> very well) but a major source of support is Stack Overflow... I use this
>> a
>>> lot with my other work and there's a lot of information there.
>>>> 
>>>> Apache Royale doesn't appear to have a tag; when I search for "royale"
>>> all I got was stuff about "Clash Royale"; there are however 8 questions
>>> with "flexjs" tags.
>>>> 
>>>> But wouldn't it be good for people to add questions and to contribute
>>> answers there, both from the user perspective and perhaps also the dev
>>> perspective? Would be interested in peopl

Re: Let's bump Royale version to 1.0

[Dany Dhondt]

I’m all for buikding a knowledge base in Stack Overflow! The mailing list 
should only be used for developing Royale. Questions about using Royale should 
go to SO

The competitors of Royale are React, Vue, Angular, ...
Lots of developers are now used to those workflows. 
In case of React, create-react-app sets you up with a brand new, ready to go 
project in less than 30 seconds. That should be a benchmark for Royale imo. 

Dany


Verstuurd vanaf mijn iPhone

> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew  het 
> volgende geschreven:
> 
> One other thought ... currently the way people ask for support is via these 
> mailing lists. Which are okay but I'm always conscious that I'm potentially 
> spamming people, plus the volume of mails is such that I have a rule to push 
> all these into a folder that I then review every day or two..
> 
> But if I want to find something out, I tend not to go search the mailing 
> list, I tend to search online. Looking through mailing list threads isn't the 
> easiest (and search engines don't necessarily pick things up from them very 
> well) but a major source of support is Stack Overflow... I use this a lot 
> with my other work and there's a lot of information there.
> 
> Apache Royale doesn't appear to have a tag; when I search for "royale" all I 
> got was stuff about "Clash Royale"; there are however 8 questions with 
> "flexjs" tags.
> 
> But wouldn't it be good for people to add questions and to contribute answers 
> there, both from the user perspective and perhaps also the dev perspective? 
> Would be interested in people's thoughts... (and perhaps I'll have to dig out 
> my SO credentials to start contributing there)
> 
> thanks
> 
>  Andrew
> 
> 
> -Original Message-
> From: Carlos Rovira [mailto:carlosrov...@apache.org] 
> Sent: 26 April 2019 10:39
> To: dev@royale.apache.org
> Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
> 
> Hi Angelo, that's great! :)
> 
> any help here is very appreciated.
> 
> Share in a new mail a concrete contribution before starting to work on it, so 
> we can know about it and help you on the task so your work fit perfectly in 
> the overall picture.
> 
> I'd like to create videos too, and people asked about it in facebook and 
> twitter. Do you have skills in creating videos?
> 
> 
> 
> El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari ()
> escribió:
> 
>> Yes, i can give some slots to help with documentation or example 
>> project or so... I think tutorial videos could be help to understand 
>> rapidly the platform and could help new user to get ready in a few 
>> hours to start build their project.
>> 
>> Angelo
>> 
>> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira 
>> 
>> wrote:
>> 
>>> Agree with latest comments.
>>> 
>>> I think we should work in docs and ease the start of new users to 
>>> target
>>> 1.0
>>> And in the process fix some few things (i.e: don't want to reach 1.0 
>>> with Jewel Table in its current state and API)
>>> 
>>> What do you think?
>>> 
>>> If you all agree could you think on how to contribute to that 
>>> effort? Can we have as a near goal to bring 1.0 planing ourselves to 
>>> donate some
>> hours
>>> to Apache Royale to make this happen? If some of us help in the 
>>> current state I think we can get to it sooner.
>>> 
>>> Thanks
>>> 
>>> 
>>> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
>>> lazzari.ang...@gmail.com>)
>>> escribió:
>>> 
 I am completely agree with Olaf: start using a new platform where 
 the documentation is not complete, clean and updated it is a 
 really bad thing...and it would be a potential reason to increase 
 the difficulty
>> to
 adopt the platform...
 
 Angelo
 
 El vie., 26 abr. 2019 8:54, Olaf Krueger 
>>> escribió:
 
> Hi,
> 
> Basically, I think it's important to provide a great developer
 experience.
> IMO, that's more important than trying to implement missing features.
> 
> One thing to achieve this is documentation of course.
> Thanks to all of you there already exist a lot of docs, but it 
> feels
>> a
 bit
> messy because they are hosted at different places, e.g.:
> 
> - royale-docs repo
> - royale-asjs wiki
> - royale-asjs Readme
> - 
> https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
> s%3A%2F%2Froyale.apache.org
> - ...?
> 
> As a user, it's hard to get an overview of what is available... 
> and
 where.
> Maybe it's a good idea to consolidate the docs before releasing 1.0.
> 
> Just my 2 cents,
> Olaf
> 
> 
> 
> 
> 
> 
> 
> --
> Sent from: 
> https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
> %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> 
 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
>>> 2F%2Fabout.me%2Fcarlosrovira
>>> 
>> 
>> 

Re: Royale CLI issues

[Dany Dhondt]

Hi Om

I uninstalled royale-js and cli
the first gave the same 'invalid entry' errors but installed anyway

the cli gave these errors (I did install with sudo!):


node-pre-gyp ERR! Pre-built binaries not installable for fsevents@1.2.3 and 
node@10.0.0 (node-v64 ABI, unknown) (falling back to source compile with 
node-gyp) 
node-pre-gyp ERR! Hit error EACCES: permission denied, mkdir 
'/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/lib/binding/Release/node-v64-darwin-x64'
 
gyp ERR! clean error 
gyp ERR! stack Error: EACCES: permission denied, rmdir 'build'
gyp ERR! System Darwin 17.5.0
gyp ERR! command "/usr/local/bin/node" 
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "clean"
gyp ERR! cwd 
/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents
gyp ERR! node -v v10.0.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node 
/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
node-pre-gyp ERR! stack     at ChildProcess. 
(/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:947:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit 
(internal/child_process.js:236:5)
node-pre-gyp ERR! System Darwin 17.5.0
node-pre-gyp ERR! command "/usr/local/bin/node" 
"/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp"
 "install" "--fallback-to-build"
node-pre-gyp ERR! cwd 
/usr/local/lib/node_modules/@apache-royale/cli/node_modules/fsevents
node-pre-gyp ERR! node -v v10.0.0
node-pre-gyp ERR! node-pre-gyp -v v0.9.1
node-pre-gyp ERR! not ok 
Failed to execute '/usr/local/bin/node 
/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js clean' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 
(node_modules/@apache-royale/cli/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 install: `node 
install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1




Thoughts?

Dany

Op 8 mei 2018 om 08:40 uur uur schreef OmPrakash Muppirala 
<bigosma...@gmail.com>:

Dany,

I updated my pushed a new version of cli a couple days ago. This was
published using the latest versions of npm and node.js

Can you please try these commands and let me know how it goes?

npm install -g @apache-royale/royale-js
npm install -g @apache-royale/cli

royale new new-test
cd new-test
royale serve:debug



Thanks,
Om

On Wed, May 2, 2018 at 1:05 AM, Dany Dhondt <archeme...@mac.com> wrote:

:) nice to know that messing things up makes your day

My aim is to expand the Hello world app to a real boilerplate app in which
a basic layout is used and where most common components are shown.
I would also like to implement one server call (which might return some
json) to get people started.

-Dany

Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala <
bigosma...@gmail.com>:

Okay, I bumped my versions and the good news is that everything is messed
up on my computer as well :-)

Thanks for your patience Dany. I will try to debug this issue soon and
make a new release.

Regards,
Om

On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt <archeme...@mac.com> wrote:

my-royale-app dany$ > node -v


v8.11.1


my-royale-app dany$ > npm -v


6.0.0



-Dany



Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <

bigosma...@gmail.com>:


Ah that makes more sense. It looks like mxmlc (the compiler) is not able

to access the Main.mxml file. So, it fails at the compilation step.

Instead of erroring out right away, the server tries to load a non existent

index.html.


As someone mentioned earlier, this might be because of the npm version

mismatch.

Can you please let me know what your npm and node.js versions are?


Mine are:

C:\temp\royale-test\my-app>npm -v

4.3.0


C:\temp\royale-test\my-app>node -v

v7.7.1


Thanks,

Om


On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt <archeme...@mac.com> wrote:


this is the complete error listing:



my-royale-app dany$ > royale serve:debug



Compiling...



WARNING: An illegal reflective access operation has occurred



WARNING: Illegal reflective access by com.google.common.base.

internal.Finalizer


(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/

royale-asjs/js/lib/guava.jar)


to field java.lang.Thread.inheritableThreadLocals



WARNING: Please consider reporting this to the maintainers of


com.google.common.base.internal.Finalizer



WARNING: Use --illegal-access=warn to enable warnings of further illegal


reflective access operations



WARNING: All il

Re: New blog example to review

[Dany Dhondt]

Hi Carlos,

I mean a widget like putting a vimeo video on your site or a google map

-Dany

Op 3 mei 2018 om 09:43 uur uur schreef Carlos Rovira <carlosrov...@apache.org>:

Hi Dany,

thanks! I'm creating the examples in "examples/blog" folder and uploading
the "js-release" html/js/css output to the website. Then showing it in an
iFrame so people could look at the code and the final result. Don't know
what you mean exactly with "widget", can you elaborate more about this?
since a widget can be many things and depends to the context (wordpress,
mobile, desktop OS,...)

thanks!



2018-05-03 8:08 GMT+02:00 Dany Dhondt <archeme...@mac.com>:

Hi Carlos,

thanks for these great examples.


To show the component, is it as easy as linking the compiled js file in an
iFrame?

So would this be the way to create a widget?


thx

Dany



Op 3 mei 2018 om 06:41 uur uur schreef Olaf Krueger <m...@olafkrueger.net

:


Hi Carlos,
thanks for another nice Blog example!!!

I would just like to mention that your example doesn't work properly in
IE11
(styles/layout issues) [1].
This is no issue for myself (No need to support IE11) but if I remember it
correctly you would like
to support IE11 also someday...

Thanks,
Olaf

[1]
https://snag.gy/Jw8nTB.jpg



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/




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

Re: New blog example to review

[Dany Dhondt]

Hi Carlos,

thanks for these great examples.

To show the component, is it as easy as linking the compiled js file in an 
iFrame?
So would this be the way to create a widget?

thx
Dany


Op 3 mei 2018 om 06:41 uur uur schreef Olaf Krueger :

Hi Carlos,
thanks for another nice Blog example!!!

I would just like to mention that your example doesn't work properly in IE11
(styles/layout issues) [1].
This is no issue for myself (No need to support IE11) but if I remember it
correctly you would like
to support IE11 also someday...

Thanks,
Olaf

[1]
https://snag.gy/Jw8nTB.jpg



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/

Re: Newest little Harbs (was Re: Null pointer errors)

[Dany Dhondt]

Congratulations!!! That's definitely a royale gift!

-d

Op 2 mei 2018 om 15:35 uur uur schreef Harbs :

Well, how about a baby sister? ;-)

We just had a baby girl about a half hour ago. :-)

(I’ll post a picture as soon as I take one.)

Harbs

On May 1, 2018, at 11:33 PM, Alex Harui  wrote:

I can think of better graduation gifts than the chance to learn the compiler 
code __.

Re: Royale CLI issues

[Dany Dhondt]

:) nice to know that messing things up makes your day

My aim is to expand the Hello world app to a real boilerplate app in which a 
basic layout is used and where most common components are shown. 
I would also like to implement one server call (which might return some json) 
to get people started.

-Dany

Op 2 mei 2018 om 09:59 uur uur schreef OmPrakash Muppirala 
<bigosma...@gmail.com>:

Okay, I bumped my versions and the good news is that everything is messed
up on my computer as well :-)

Thanks for your patience Dany. I will try to debug this issue soon and
make a new release.

Regards,
Om

On Wed, May 2, 2018 at 12:23 AM, Dany Dhondt <archeme...@mac.com> wrote:

my-royale-app dany$ > node -v

v8.11.1

my-royale-app dany$ > npm -v

6.0.0


-Dany


Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala <
bigosma...@gmail.com>:

Ah that makes more sense. It looks like mxmlc (the compiler) is not able
to access the Main.mxml file. So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt <archeme...@mac.com> wrote:

this is the complete error listing:


my-royale-app dany$ > royale serve:debug


Compiling...


WARNING: An illegal reflective access operation has occurred


WARNING: Illegal reflective access by com.google.common.base.
internal.Finalizer

(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
royale-asjs/js/lib/guava.jar)

to field java.lang.Thread.inheritableThreadLocals


WARNING: Please consider reporting this to the maintainers of

com.google.common.base.internal.Finalizer


WARNING: Use --illegal-access=warn to enable warnings of further illegal

reflective access operations


WARNING: All illegal access operations will be denied in a future release


Error: unable to open 'HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml'.





Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml -debug=true


WARNING: An illegal reflective access operation has occurred


WARNING: Illegal reflective access by com.google.common.base.
internal.Finalizer

(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/
royale-asjs/js/lib/guava.jar)

to field java.lang.Thread.inheritableThreadLocals


WARNING: Please consider reporting this to the maintainers of

com.google.common.base.internal.Finalizer


WARNING: Use --illegal-access=warn to enable warnings of further illegal

reflective access operations


WARNING: All illegal access operations will be denied in a future release


Error: unable to open 'HD/Documents/ARCHEMEDIA/

ROYALE/my-royale-app/src/Main.mxml'.






fs.js:646


return binding.open(pathModule._makeLong(path), stringToFlags(flags),

mode);


^



Error: ENOENT: no such file or directory, open '/Volumes/Macintosh

HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'


at Object.fs.openSync (fs.js:646:18)


at Object.fs.readFileSync (fs.js:551:33)


at updateIndex (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:125:24)


at compileDebug (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:106:9)


at serveDebug (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:88:5)


at Object. (/usr/local/lib/node_modules/@

apache-royale/cli/index.js:59:13)


at Module._compile (module.js:652:30)


at Object.Module._extensions..js (module.js:663:10)


at Module.load (module.js:565:32)


at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[Dany Dhondt]

my-royale-app dany$  > node -v
v8.11.1
my-royale-app dany$  > npm -v
6.0.0


-Dany


Op 2 mei 2018 om 09:19 uur uur schreef OmPrakash Muppirala 
<bigosma...@gmail.com>:

Ah that makes more sense. It looks like mxmlc (the compiler) is not able
to access the Main.mxml file. So, it fails at the compilation step.
Instead of erroring out right away, the server tries to load a non existent
index.html.

As someone mentioned earlier, this might be because of the npm version
mismatch.
Can you please let me know what your npm and node.js versions are?

Mine are:
C:\temp\royale-test\my-app>npm -v
4.3.0

C:\temp\royale-test\my-app>node -v
v7.7.1

Thanks,
Om

On Wed, May 2, 2018 at 12:09 AM, Dany Dhondt <archeme...@mac.com> wrote:

this is the complete error listing:

my-royale-app dany$ > royale serve:debug

Compiling...

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
to field java.lang.Thread.inheritableThreadLocals

WARNING: Please consider reporting this to the maintainers of
com.google.common.base.internal.Finalizer

WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations

WARNING: All illegal access operations will be denied in a future release

Error: unable to open 'HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml'.




Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml -debug=true

WARNING: An illegal reflective access operation has occurred

WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
to field java.lang.Thread.inheritableThreadLocals

WARNING: Please consider reporting this to the maintainers of
com.google.common.base.internal.Finalizer

WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations

WARNING: All illegal access operations will be denied in a future release

Error: unable to open 'HD/Documents/ARCHEMEDIA/
ROYALE/my-royale-app/src/Main.mxml'.





fs.js:646

return binding.open(pathModule._makeLong(path), stringToFlags(flags),
mode);

^


Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'

at Object.fs.openSync (fs.js:646:18)

at Object.fs.readFileSync (fs.js:551:33)

at updateIndex (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:125:24)

at compileDebug (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:106:9)

at serveDebug (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:88:5)

at Object. (/usr/local/lib/node_modules/@
apache-royale/cli/index.js:59:13)

at Module._compile (module.js:652:30)

at Object.Module._extensions..js (module.js:663:10)

at Module.load (module.js:565:32)

at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[Dany Dhondt]

this is the complete error listing:

my-royale-app dany$  > royale serve:debug
Compiling...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 
'HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml'.



Command failed: mxmlc /Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml -debug=true
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/Users/dany/Downloads/apache-royale-0.9.2-bin-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 
'HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/Main.mxml'.




fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at updateIndex 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:125:24)
    at compileDebug 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:106:9)
    at serveDebug (/usr/local/lib/node_modules/@apache-royale/cli/index.js:88:5)
    at Object. 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:59:13)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)

Re: Royale CLI issues

[Dany Dhondt]

Hi Om,

I tried both ways, none of them works.
Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/bin/js-debug/index.html'
   


My question is: shouldn't the 'new' command create more than just one mxml file?
What script is responsible for creating the bin folder? Should it be the 'new' 
script or the 'serve' script?

-Dany


Op 2 mei 2018 om 08:36 uur uur schreef OmPrakash Muppirala 
<bigosma...@gmail.com>:

On Tue, May 1, 2018 at 11:15 PM, Dany Dhondt <archeme...@mac.com> wrote:

Alex,

The version number here came from package.json so it should have been
updated by someone.

I reinstalled from the link you provided with no problem.
But running the royale server:debug [1] command gives me the same errors
as before.

I noticed that when running: royale new my-royale-app, only an app folder
is created with a src folder in it.In this src folder, there is a main.mxml
file. So no other files or folders whatsoever are created by the 'new'
command.


Yes, that is the expected behavior. Currently, we ship a very simple
`Hello World` app with the royale-cli tool. We can make it fancier app
once we iron out all the issues.



This explains the error:

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'


Hmm, the path does not seem correct. it should be
.../my-royale-app/bin/js-debug/index.html instead of what is shown here.

It appears that you are running the royale serve:debug command from the
.../my-royale-app/src directory instead of from the .../my-royale-app
directory.

Thanks,
Om


-Dany

[1] https://github.com/apache/royale-asjs/tree/develop/npm/cli

Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui <aha...@adobe.com.INVALID

:


That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3? I'm trying to remember if I published the package
to NPM or if you did. Maybe the scripts are running or were run after some
versions got updated in the repos. I have not run a build on my windows
machine since the release.

-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" <
omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:


Om,

I got the warnings when we released 0.9.2 but it appeared to leave a
functional SDK. Now it is hanging for me and Dany.

I don't think I've run a publish and I don't think the CI server is
either, but you never know. Try grabbing one of the SWCs. Unzip it and
swfdump the library.swf. There should be debugfile bytecodes with paths

to

the source that give us a clue.



Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;
org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om



-Alex

On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server. No humans
> involved, and no special packaging for NPM. NPM says it can install
any
> tar.gz file. Try downloading the file at that link and using Mac
Finder to
> expand it into a folder. For me it expands without errors. This is
why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install"
the
> folder. Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that @apache-royale/royale-js@0.9.3 was
installed. It
should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this
moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨ ░░░⸩ ⠸ extract:@apache-royale/royale-js:
verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea
of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui
<aha...@adobe.com.INVALID
> <mailto:aha...@adobe.com.INVALID>> het volgende gesc

Re: NPM Issues (was Re: [Discussion] "Life after FlashPlayer" post @flex lists)

[Dany Dhondt]

Hi Alex,

package.json which is the default file npm picks up

-Dany



Op 2 mei 2018 om 06:45 uur uur schreef Alex Harui <aha...@adobe.com.INVALID>:

OK, but what file would contain that string such that it shows up then?

Thanks,
-Alex

On 5/1/18, 9:32 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:

On Tue, May 1, 2018, 8:13 PM Alex Harui <aha...@adobe.com.invalid> wrote:


That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3?



It shows up after the npm install completes.


I'm trying to remember if I published the package to NPM or if you did.

Maybe the scripts are running or were run after some versions got updated
in the repos. I have not run a build on my windows machine since the
release.








-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
<omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Om,
>
> I got the warnings when we released 0.9.2 but it appeared to leave a
> functional SDK. Now it is hanging for me and Dany.
>
> I don't think I've run a publish and I don't think the CI server is
> either, but you never know. Try grabbing one of the SWCs. Unzip it
and
> swfdump the library.swf. There should be debugfile bytecodes with
paths to
> the source that give us a clue.
>
>
Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile

"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om


> -Alex
>
> On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
> Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com>
wrote:
>
> On Tue, May 1, 2018 at 8:57 AM, Alex Harui
<aha...@adobe.com.invalid>
> wrote:
>
> > Hi Dany,
> >
> > The link is directly to a tar.gz built by our CI server. No
humans
> > involved, and no special packaging for NPM. NPM says it can
install
> any
> > tar.gz file. Try downloading the file at that link and using
Mac
> Finder to
> > expand it into a folder. For me it expands without errors.
This is
> why I
> > believe it is some incompatibility with NPM.
> >
> > If the tar.gz expands for you on Mac, you can try to "npm
install"
> the
> > folder. Running:
> >
> > sudo npm install -g 
> >
> > seemed to work for me.
> >
> > -Alex
> >
>
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
>
> Although, I notice that @apache-royale/royale-js@0.9.3 was
> installed. It
> should have installed 0.9.2. Did we publish 0.9.3 to npm by
mistake?
> Could that be related?
>
> Thanks,
> Om
>
>
> >
> > On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
> >
> > Hi Alex,
> >
> > I tried the direct link you provided: same result
(hundreds of
> > ‘invalid entry’ messages)
> >
> > My version of npm is 6.0.0
> >
> > downgrading to a lower npm version is not an option at this
> moment
> > because I’m on a production mac with crucial projects on it.
> >
> > Amids all the invalid entry messages, now and then is a
somewhat
> > longer message like
> >
> > WARN⸨ ░░░⸩ ⠸ extract:@apache-royale
/royale-js:
> verb
> > lock using /Users/ tar invalid entry
> >
> >
> >
> >
> > Is it Om that created this package? This might give him an
idea
> of
> > what’s going on?
> >
> > -Dany
> >
> >
> >
> > > Op 30 apr. 2018, om 18:39 heeft Alex Harui
> <aha...@adobe.com.INVALID
> > <mailto:aha...@adobe.com.INVALID>> het volgende geschreven:
> > >
> > > Hmm. I'm getting that too on my Mac. It used to
complete
> anyway
> > and work, but now it appears to be hanging.
> > >
> > > The internet hints that it might have to do with the
version
> of NPM
> > used to create the package vs the NPM we are using to
install. Om,
> did
> > you create the packages for publishing to NPM? If so, what
version
> did you
> > use?
> > >
> > > On the other hand, just installing the nightly build also
> gives a
> > ton of those warnings but seems to complete and produce a
runnable
> compiler.
> > >
> > > sudo npm install -g
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608060969636900=sgZ

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Alex,

The version number here came from package.json so it should have been updated 
by someone.

I reinstalled from the link you provided with no problem.
But running the royale server:debug [1] command gives me the same errors as 
before.

I noticed that when running: royale new  my-royale-app, only an app folder is 
created with a src folder in it.
In this src folder, there is a main.mxml file. So no other files or folders 
whatsoever are created by the 'new' command.

This explains the error:
Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/my-royale-app/src/bin/js-debug/index.html'

-Dany

[1] https://github.com/apache/royale-asjs/tree/develop/npm/cli

Op 2 mei 2018 om 05:13 uur uur schreef Alex Harui <aha...@adobe.com.INVALID>:

That's my windows machine that I used for 0.9.2.

Where did it say 0.9.3? I'm trying to remember if I published the package to 
NPM or if you did. Maybe the scripts are running or were run after some 
versions got updated in the repos. I have not run a build on my windows machine 
since the release.

-Alex

On 5/1/18, 2:14 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala" 
<omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

On Tue, May 1, 2018 at 1:36 PM, Alex Harui <aha...@adobe.com.invalid> wrote:


Om,

I got the warnings when we released 0.9.2 but it appeared to leave a
functional SDK. Now it is hanging for me and Dany.

I don't think I've run a publish and I don't think the CI server is
either, but you never know. Try grabbing one of the SWCs. Unzip it and
swfdump the library.swf. There should be debugfile bytecodes with paths to
the source that give us a clue.



Good idea. Here is what I see in swfdump:

2) + 0:1 debugfile
"C:\temp\rc\royale-asjs\frameworks\projects\Collections\src\main\royale;org\apache\royale\collections;FlattenedList.as"

Any idea whose machine this could have been?

Thanks,
Om



-Alex

On 5/1/18, 10:49 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote:

On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Hi Dany,
>
> The link is directly to a tar.gz built by our CI server. No humans
> involved, and no special packaging for NPM. NPM says it can install
any
> tar.gz file. Try downloading the file at that link and using Mac
Finder to
> expand it into a folder. For me it expands without errors. This is
why I
> believe it is some incompatibility with NPM.
>
> If the tar.gz expands for you on Mac, you can try to "npm install"
the
> folder. Running:
>
> sudo npm install -g 
>
> seemed to work for me.
>
> -Alex
>

I just tried
npm install @apache-royale/royale-js -g
on windwos and it installed just fine.

Although, I notice that @apache-royale/royale-js@0.9.3 was
installed. It
should have installed 0.9.2. Did we publish 0.9.3 to npm by mistake?
Could that be related?

Thanks,
Om


>
> On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
>
> Hi Alex,
>
> I tried the direct link you provided: same result (hundreds of
> ‘invalid entry’ messages)
>
> My version of npm is 6.0.0
>
> downgrading to a lower npm version is not an option at this
moment
> because I’m on a production mac with crucial projects on it.
>
> Amids all the invalid entry messages, now and then is a somewhat
> longer message like
>
> WARN⸨ ░░░⸩ ⠸ extract:@apache-royale/royale-js:
verb
> lock using /Users/ tar invalid entry
>
>
>
>
> Is it Om that created this package? This might give him an idea
of
> what’s going on?
>
> -Dany
>
>
>
> > Op 30 apr. 2018, om 18:39 heeft Alex Harui
<aha...@adobe.com.INVALID
> <mailto:aha...@adobe.com.INVALID>> het volgende geschreven:
> >
> > Hmm. I'm getting that too on my Mac. It used to complete
anyway
> and work, but now it appears to be hanging.
> >
> > The internet hints that it might have to do with the version
of NPM
> used to create the package vs the NPM we are using to install. Om,
did
> you create the packages for publishing to NPM? If so, what version
did you
> use?
> >
> > On the other hand, just installing the nightly build also
gives a
> ton of those warnings but seems to complete and produce a runnable
compiler.
> >
> > sudo npm install -g 
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks=02%7C01%7Caharui%40adobe.com%7Ca57dd23c4db24e0a18d008d5afa88c6b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636608060969636900=sgZBuZoOmRwla%2Bti%2FwtU0vRemJMy7MjB5sRC9d0Qdic%3D=0.
protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&
data=02%7C01%7Caharui%40adobe.com%7C00079fd32a194a4caf1b08d5af8bd09e%
7Cfa7b1b5a7b34438794aed2

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om

I also noticed that 0.9.3 was installeren so I tried ...@0.9.2 but that was non 
existing. ...@0.9.1 did exist but gave the same result/errors

-Dany

Verstuurd vanaf mijn iPhone

> Op 1 mei 2018 om 19:48 heeft OmPrakash Muppirala <bigosma...@gmail.com> het 
> volgende geschreven:
> 
>> On Tue, May 1, 2018 at 8:57 AM, Alex Harui <aha...@adobe.com.invalid> wrote:
>> 
>> Hi Dany,
>> 
>> The link is directly to a tar.gz built by our CI server.  No humans
>> involved, and no special packaging for NPM.  NPM says it can install any
>> tar.gz file.  Try downloading the file at that link and using Mac Finder to
>> expand it into a folder.  For me it expands without errors.  This is why I
>> believe it is some incompatibility with NPM.
>> 
>> If the tar.gz expands for you on Mac, you can try to "npm install" the
>> folder.  Running:
>> 
>>sudo npm install -g 
>> 
>> seemed to work for me.
>> 
>> -Alex
>> 
> 
> I just tried
> npm install @apache-royale/royale-js -g
> on windwos and it installed just fine.
> 
> Although, I notice that  @apache-royale/royale-js@0.9.3 was installed.  It
> should have installed 0.9.2.  Did we publish 0.9.3 to npm by mistake?
> Could that be related?
> 
> Thanks,
> Om
> 
> 
>> 
>> On 5/1/18, 1:51 AM, "Dany Dhondt" <archeme...@mac.com> wrote:
>> 
>>Hi Alex,
>> 
>>I tried the direct link you provided: same result (hundreds of
>> ‘invalid entry’ messages)
>> 
>>My version of npm is 6.0.0
>> 
>>downgrading to a lower npm version is not an option at this moment
>> because I’m on a production mac with crucial projects on it.
>> 
>>Amids all the invalid entry messages, now and then is a somewhat
>> longer message like
>> 
>>WARN⸨   ░░░⸩ ⠸ extract:@apache-royale/royale-js: verb
>> lock using /Users/ tar invalid entry
>> 
>> 
>> 
>> 
>>Is it Om that created this package? This might give him an idea of
>> what’s going on?
>> 
>>-Dany
>> 
>> 
>> 
>>> Op 30 apr. 2018, om 18:39 heeft Alex Harui <aha...@adobe.com.INVALID
>> <mailto:aha...@adobe.com.INVALID>> het volgende geschreven:
>>> 
>>> Hmm.  I'm getting that too on my Mac.  It used to complete anyway
>> and work, but now it appears to be hanging.
>>> 
>>> The internet hints that it might have to do with the version of NPM
>> used to create the package vs the  NPM we are using to install.  Om, did
>> you create the packages for publishing to NPM?  If so, what version did you
>> use?
>>> 
>>> On the other hand, just installing the nightly build also gives a
>> ton of those warnings but seems to complete and produce a runnable compiler.
>>> 
>>> sudo npm install -g https://na01.safelinks.
>> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
>> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
>> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
>> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
>> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
>> 2FfXBUXmGQ49qdY0aM%3D=0 <https://na01.safelinks.
>> protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci.
>> westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs_
>> jsonly%2FlastSuccessfulBuild%2Fartifact%2Fout%2Fapache-
>> royale-0.9.3-bin-js.tar.gz=02%7C01%7Caharui%40adobe.com%
>> 7C0c405d2ff9134638451608d5af40c2f1%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636607615050264364=zKrYmme3fourKgDPSyULPEiiR5%
>> 2FfXBUXmGQ49qdY0aM%3D=0>
>>> 
>>> I haven't tried downgrading or upgrading my version of NPM (5.6).
>> Dany which version are you running?  Can you try different versions of NPM?
>>> 
>>> HTH,
>>> -Alex
>>> 
>>> On 4/30/18, 1:11 AM, "Dany Dhondt" <archeme...@mac.com > archeme...@mac.com>> wrote:
>>> 
>>>   Hi Om,
>>> 
>>>   I did that!
>>> 
>>>   In the mean time I tried all sorts of things:
>>>   install 0.9.1 instead of 0.9.3
>>>   reinstalled npm
>>> 
>>>   nothing works
>>> 
>>>   -Dany
>>> 
>>> 
>>>> Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala <
>> bigosma...@gmail.com <mailto:bigosma...@gmail.com>> het volgende
>> geschreven:
>>>> 
>>>> Dany,
>>>>

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om,

I did that!

In the mean time I tried all sorts of things:
install 0.9.1 instead of 0.9.3
reinstalled npm

nothing works

-Dany


> Op 30 apr. 2018, om 09:59 heeft OmPrakash Muppirala <bigosma...@gmail.com> 
> het volgende geschreven:
> 
> Dany,
> 
> I haven't tested this on a Mac.  I am told that Mac users need to use "sudo
> install npm  " depending on how they installed npm.  Perhaps
> you can try that out?
> 
> Thanks,
> Om
> 
> On Mon, Apr 30, 2018 at 12:54 AM, Dany Dhondt <archeme...@mac.com> wrote:
> 
>> Hi Om,
>> 
>> Thanks for pointing that out.
>> 
>> I’ll have a go with that scenario.
>> 
>> 1. (re) installing royale
>> npm install @apache-royale/royale-js -g
>> WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using
>> /Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for
>> /usr/local/lib/node_modules/.staging
>> WARN tar invalid entry
>> 
>> Then hundreds of ‘invalid entry’ lines in the terminal.
>> 
>> And finally
>> 
>> …
>> 
>> WARN tar invalid entry
>> /usr/local/bin/asjscompc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
>> /usr/local/bin/asjsc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
>> /usr/local/bin/compc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/compcnpm
>> /usr/local/bin/externc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/externcnpm
>> /usr/local/bin/asnodec -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
>> /usr/local/bin/mxmlc -> /usr/local/lib/node_modules/@
>> apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
>> + @apache-royale/royale-js@0.9.3
>> updated 1 package in 17.395s
>> 
>> 
>> What are those invalid entries??
>> 
>> 2. install cli tool
>> 
>> npm install @apache-royale/cli@alpha -g
>> no problem here
>> 
>> 3. create royale app
>> 
>> royale new helloWorld
>> cd helloWorld
>> 
>>>> no problem
>> 
>> 4. running the app
>> 
>> royale serve:debug
>> 
>> Didn’t work:
>> 
>> helloWorld dany$  > royale serve:debug
>> Compiling...
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by 
>> com.google.common.base.internal.Finalizer
>> (file:/usr/local/lib/node_modules/@apache-royale/royale-
>> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
>> inheritableThreadLocals
>> WARNING: Please consider reporting this to the maintainers of
>> com.google.common.base.internal.Finalizer
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
>> mxml'.
>> 
>> 
>> 
>> Command failed: mxmlc /Volumes/Macintosh HD/Documents/ARCHEMEDIA/
>> ROYALE/helloWorld/src/Main.mxml -debug=true
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by 
>> com.google.common.base.internal.Finalizer
>> (file:/usr/local/lib/node_modules/@apache-royale/royale-
>> js/royale-asjs/js/lib/guava.jar) to field java.lang.Thread.
>> inheritableThreadLocals
>> WARNING: Please consider reporting this to the maintainers of
>> com.google.common.base.internal.Finalizer
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.
>> mxml'.
>> 
>> 
>> 
>> 
>> fs.js:646
>>  return binding.open(pathModule._makeLong(path), stringToFlags(flags),
>> mode);
>> ^
>> 
>> Error: ENOENT: no such file or directory, open '/Volumes/Macintosh
>> HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
>>at Object.fs.openSync (fs.js:646:18)
>>at Object.fs.readFileSync (fs.js:551:33)
>>at updateIndex (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:125:24)
>>at compileDebug (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:106:9)
>>at serveDebug (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:88:5)
>>at Object. (/usr/local/lib/node_modules/@
>> apache-royale/cli/index.js:59:13)
>>at Module._compile (module.js:652:30)
>>at Object.Module._extensions..js (module.js:663:10)
>>at Module.load (module.js:565:32)
>>at tryModuleLoad (module.js:505:12)
>> helloWorld dany$  >
>> 
>> 
>> 
>> 
>> Any ideas?
>> 
>> -Dany
>> 
>> 
>> 
>> 
>> 

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi Om,

Thanks for pointing that out.

I’ll have a go with that scenario.

1. (re) installing royale
npm install @apache-royale/royale-js -g
WARN tar invalid entry extract:@apache-royale/royale-js: verb lock using 
/Users/dany/.npm/_locks/staging-3a08f0df5026584d.lock for 
/usr/local/lib/node_modules/.staging
WARN tar invalid entry

Then hundreds of ‘invalid entry’ lines in the terminal.

And finally

…

WARN tar invalid entry
/usr/local/bin/asjscompc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asjscompcnpm
/usr/local/bin/asjsc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asjscnpm
/usr/local/bin/compc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/compcnpm
/usr/local/bin/externc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/externcnpm
/usr/local/bin/asnodec -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/asnodecnpm
/usr/local/bin/mxmlc -> 
/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/bin/mxmlcnpm
+ @apache-royale/royale-js@0.9.3
updated 1 package in 17.395s


What are those invalid entries??

2. install cli tool

npm install @apache-royale/cli@alpha -g
no problem here

3. create royale app

royale new helloWorld
cd helloWorld

>> no problem

4. running the app

royale serve:debug

Didn’t work:

helloWorld dany$  > royale serve:debug
Compiling...
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml'.



Command failed: mxmlc /Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml -debug=true
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.common.base.internal.Finalizer 
(file:/usr/local/lib/node_modules/@apache-royale/royale-js/royale-asjs/js/lib/guava.jar)
 to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of 
com.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error: unable to open 'HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/src/Main.mxml'.




fs.js:646
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
 ^

Error: ENOENT: no such file or directory, open '/Volumes/Macintosh 
HD/Documents/ARCHEMEDIA/ROYALE/helloWorld/bin/js-debug/index.html'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.readFileSync (fs.js:551:33)
at updateIndex 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:125:24)
at compileDebug 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:106:9)
at serveDebug (/usr/local/lib/node_modules/@apache-royale/cli/index.js:88:5)
at Object. 
(/usr/local/lib/node_modules/@apache-royale/cli/index.js:59:13)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
helloWorld dany$  > 




Any ideas?

-Dany

Re: [Discussion] "Life after FlashPlayer" post @flex lists (Was: Royale Frameworks and More)

[Dany Dhondt]

Hi all,

A few thoughts:


In our organization, I built a big backoffice web application in Flex about 2 
years ago. Now, we are obliged to make it future proof, which means, no Flash 
dependency at all.
We chose react.js. So the last couple of months, I studied react, npm, node, 
webpack, babel, …
It’s clear that the most popular technologies for creating web applications 
nowadays are cli driven packages like react, angular, (vue)
I really think royale should be in this list!
The whole thing is about getting people up and running in no time. And getting 
started quickly is all about configuration. 
An example: for react, a npm package create-react-app is available which is as 
simple as:

create-react-app my-app
cd my-app
yarn start (or npm start)

These commands setup a whole file structure, configures webpack and babel, runs 
a local dev server and start up a boilerplate app. Ready to go!

couldn’t we make a create-royale-app package?

This boilerplate could contain a ready-to-go set of components:
Navigationheader on top, then a left pane and content pane, which are 
responsive and a set of basic components like drop down, button, list, …

All this packed with a clean but robust set of css styling.

I spent the last couple of days searching for a component library for react. A 
few examples: material-ui, React bootstrap, Ant design, Blueprint, …
So far I didn’t find any package which meet my 2 most important criteria:

- Complete set of components
- Well written component api documentation

I think that a lot of (former) flex developers chose a similar path like me but 
are more than willing to give royale a go. 

It is important to know that the majority of these developers (like myself) 
have quite a lot of ‘development skills and experience’ but have far less 
knowledge of what’s going on under the hood. 
We can’t expect them to go through days of configuration frustrations before 
getting started with what is their core business.

So, as much as I agree with the ‘Life after FlashPlayer’ questionnaire, I would 
like to see it posted with a big button at the end saying ‘TRY ROYALE NOW'


-Dany





> Op 29 apr. 2018, om 10:52 heeft Piotr Zarzycki  
> het volgende geschreven:
> 
> +1 for Olaf's email and Alex's changes.
> 
> Piotr
> 
> On Sun, Apr 29, 2018, 7:15 AM Alex Harui  wrote:
> 
>> Hi Olaf,
>> 
>> Great first draft!  It is fine as is, and I really like that it is short.
>> 
>> The only thing I'm tempted to try to add is an earlier introduction to who
>> "we" are, that it is the Royale/FlexJS folks asking and not the Flex PMC or
>> some other group.
>> 
>> So one idea is to just to start with "Hello from the Royale (FlexJS) team"
>> instead of "Hi".
>> Or enhancing "So, we are really interested..." with "So, we, the Royale
>> (FlexJS) team, are really interested..."
>> 
>> My 2 cents,
>> -Alex
>> 
>> On 4/28/18, 1:11 PM, "Olaf Krueger"  wrote:
>> 
>>   Hi,
>> 
>>> IMO, we don’t need a survey, just the right words in the subject and
>> body
>>> of emails that will start > > > discussion and elicit responses...
>> 
>>   After thinking about it a bit more I came to the conclusion that
>> there's no
>>   need to mention Royale as an alternative to Flex in order to start a
>>   discussion.
>>   I guess what we all want to know is what all those Flex users and apps
>> are
>>   doing out there.
>>   So I've focused on this and wrote a first draft [1], please take a
>> look at
>>   it and make your comments.
>>   Feel free to revise it.
>> 
>>   Thanks,
>>   Olaf
>> 
>> 
>>   [1]
>> 
>>   Life after FlashPlayer, are you prepared?
>> 
>>   Hi,
>>   even if Flex with AIR is still an awesome and outstanding technology,
>> Flex
>>   in the browser ends with the end of FlashPlayer in 2020.
>>   To be clear: There will be no way to run your Flex apps in current
>> Browser
>>   versions around 2020!
>> 
>>   The Flex mailing lists are followed by a few hundred people and we
>> assume
>>   that there are still a lot of Flex browser apps out there.
>> 
>>   So, we are really interested in what you are planning to do with your
>> Flex
>>   apps, e.g.
>> 
>>   - Do you need to stick with the browser at all?
>>   - Do you plan to migrate your Flex apps to whatever other technology?
>>   - Did you already migrate your Flex apps to whatever other technology?
>>   - ...
>> 
>>   If you are reading this post and have a Flex app, please speak up
>> about what
>>   your plans are.
>> 
>>   Thanks,
>>   Olaf
>>   On behalf of the Apache Royale (FlexJS) PMC
>> 
>> 
>> 
>> 
>>   --
>>   Sent from:
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F=02%7C01%7Caharui%40adobe.com%7C3e3259b920be40097fca08d5ad442a1f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636605430693133595=Rc1UvmlbDwC2clAZc2nFAijvr6kaVrJtlOhlk2e1mr0%3D=0
>> 
>> 
>> 

Re: Re: Re: Re: Moonshine new mxml file

[Dany Dhondt]

ok piotr. In the mean time, I can change main file using the method you 
described.

I think rat_moonshine will add the request to GitHub

thx,
Dany


Op 5 dec 2017 om 13:48 uur uur schreef Piotr Zarzycki 
<piotrzarzyck...@gmail.com>:

I was just saying that it maybe an configuration miss, cause we have
possibility to point Main file during project creation. One not to have
such option once project has been created? :)

We will see once you raise an issue. It is definitely not for upcoming
1.7.0 release.

Piotr

On Tue, Dec 5, 2017, 13:00 Dany Dhondt <archeme...@mac.com> wrote:

my mistake Piotr, off course you meant the Moonshine GitHub instead of
Royale

-d

Op 5 dec 2017 om 12:53 uur uur schreef Dany Dhondt <archeme...@mac.com>:

Hi Piotr,

Before raising this in GitHub, isn't this scenario something to tackle in
Moonshine itself? I think this could be handled by implementing run
configurations, no?

Dany

Op 5 dec 2017 om 12:40 uur uur schreef Piotr Zarzycki <
piotrzarzyck...@gmail.com>:

Please raise on our GitHub an issue with your scenario. Maybe I'm not aware
of some settings - other from team will help you more.

Thanks, Piotr

2017-12-05 12:38 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:

Dany,


I would gowith following way. Close the project or Moonshine, remove old

file. Open in some editor file with extension *.as3proj and change there

name of mxml main file.









Maybe we should have in the settings of project possibility to change main

file application.


Try and let me know I didn't check myself it it will work. I will do this

in about two hours.


Thanks, Piotr



2017-12-05 12:32 GMT+01:00 Dany Dhondt <archeme...@mac.com>:


Hi Piotr,


Indeed. I create an empty mxml file of type application and want to

compile that one.


thx

Dany


Op 5 dec 2017 om 12:28 uur uur schreef Piotr Zarzycki <

piotrzarzyck...@gmail.com>:


Hi Dany,


What do you mean by compile the new mxml file ? Are you talking about new

main fail ? New :


Hi,



I have a project in Moonshine based on one of the examples in the SDK


(DataBindingExample.mxml). When I add a new mxml file in the src folder,

is


there a (simple) way to compile that new file instead of the default one?



thx


Dany






--


Piotr Zarzycki


Patreon: *https://www.patreon.com/piotrzarzycki

<https://www.patreon.com/piotrzarzycki>*





--


Piotr Zarzycki


Patreon: *https://www.patreon.com/piotrzarzycki

<https://www.patreon.com/piotrzarzycki>*





--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Re: Re: Moonshine new mxml file

[Dany Dhondt]

my mistake Piotr, off course you meant the Moonshine GitHub instead of Royale

-d

Op 5 dec 2017 om 12:53 uur uur schreef Dany Dhondt <archeme...@mac.com>:

Hi Piotr,

Before raising this in GitHub, isn't this scenario something to tackle in 
Moonshine itself? I think this could be handled by implementing run 
configurations, no?

Dany

Op 5 dec 2017 om 12:40 uur uur schreef Piotr Zarzycki 
<piotrzarzyck...@gmail.com>:

Please raise on our GitHub an issue with your scenario. Maybe I'm not aware
of some settings - other from team will help you more.

Thanks, Piotr

2017-12-05 12:38 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:

Dany,

I would gowith following way. Close the project or Moonshine, remove old
file. Open in some editor file with extension *.as3proj and change there
name of mxml main file.





Maybe we should have in the settings of project possibility to change main
file application.

Try and let me know I didn't check myself it it will work. I will do this
in about two hours.

Thanks, Piotr


2017-12-05 12:32 GMT+01:00 Dany Dhondt <archeme...@mac.com>:

Hi Piotr,

Indeed. I create an empty mxml file of type application and want to
compile that one.

thx
Dany

Op 5 dec 2017 om 12:28 uur uur schreef Piotr Zarzycki <
piotrzarzyck...@gmail.com>:

Hi Dany,

What do you mean by compile the new mxml file ? Are you talking about new
main fail ? New :

Hi,


I have a project in Moonshine based on one of the examples in the SDK

(DataBindingExample.mxml). When I add a new mxml file in the src folder,
is

there a (simple) way to compile that new file instead of the default one?


thx

Dany





--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*




--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*




--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Re: Re: Moonshine new mxml file

[Dany Dhondt]

ok, will do that

Dany

Op 5 dec 2017 om 12:40 uur uur schreef Piotr Zarzycki 
<piotrzarzyck...@gmail.com>:

Please raise on our GitHub an issue with your scenario. Maybe I'm not aware
of some settings - other from team will help you more.

Thanks, Piotr

2017-12-05 12:38 GMT+01:00 Piotr Zarzycki <piotrzarzyck...@gmail.com>:

Dany,

I would gowith following way. Close the project or Moonshine, remove old
file. Open in some editor file with extension *.as3proj and change there
name of mxml main file.





Maybe we should have in the settings of project possibility to change main
file application.

Try and let me know I didn't check myself it it will work. I will do this
in about two hours.

Thanks, Piotr


2017-12-05 12:32 GMT+01:00 Dany Dhondt <archeme...@mac.com>:

Hi Piotr,

Indeed. I create an empty mxml file of type application and want to
compile that one.

thx
Dany

Op 5 dec 2017 om 12:28 uur uur schreef Piotr Zarzycki <
piotrzarzyck...@gmail.com>:

Hi Dany,

What do you mean by compile the new mxml file ? Are you talking about new
main fail ? New :

Hi,


I have a project in Moonshine based on one of the examples in the SDK

(DataBindingExample.mxml). When I add a new mxml file in the src folder,
is

there a (simple) way to compile that new file instead of the default one?


thx

Dany





--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*




--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*




--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*

Re: Re: Moonshine new mxml file

[Dany Dhondt]

Hi Piotr,

Indeed. I create an empty mxml file of type application and want to compile 
that one.

thx
Dany

Op 5 dec 2017 om 12:28 uur uur schreef Piotr Zarzycki 
:

Hi Dany,

What do you mean by compile the new mxml file ? Are you talking about new
main fail ? New :

Hi,

I have a project in Moonshine based on one of the examples in the SDK
(DataBindingExample.mxml). When I add a new mxml file in the src folder, is
there a (simple) way to compile that new file instead of the default one?

thx
Dany




--

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Moonshine new mxml file

[Dany Dhondt]

Hi,

I have a project in Moonshine based on one of the examples in the SDK 
(DataBindingExample.mxml). When I add a new mxml file in the src folder, is 
there a (simple) way to compile that new file instead of the default one? 

thx
Dany

Re: Re: Re: Building a repository front end with Royale

[Dany Dhondt]

Hi Piotr,

I did what you said.
SDK folder and project folder are in my downloads folder.
When I try to compile I get this permission denied error [1]

When creating the project itself I got this console output [2]

thx, Dany

[1] http://www.archemedia.eu/royale/img2.png
[2] http://www.archemedia.eu/royale/img3.png


Op 4 dec 2017 om 10:29 uur uur schreef Piotr Zarzycki 
<piotrzarzyck...@gmail.com>:

Hi Dany,

It should be recognized. Try to reset settings for Moonshine - Go to
General -> Reset to Default. Moonshine should work with current version of
Royale SDK. - Let me know whether reset helped.

In case of opening examples: You need to locate "Main source folder" [1] -
This is the folder where Main file of application is located. If main file
of application is located in "src" folder browse there. For example for
HelloWorld example you need to point in that section folder
"HelloWorld\src\main\royale\"

[1] https://github.com/apache/royale-asjs/wiki/Moonshine-IDE

Thanks, Piotr


2017-12-04 8:28 GMT+01:00 Dany Dhondt <archeme...@mac.com>:

Hi Piotr

Thx for the help. I'm looking forward to version 1.7.0.
Also, MS doesn't recongnize the Royale SDK as valid [1], so it can't
activate code completion for as. Will this be fixed in the next version?

As for the examples, how can I build them in Moonshine? None of the
examples has a mxml file in the src folder and Moonshine needs that. Do I
have to build them first? And if so, how?

Should I rename this thread to 'Royale setup' or something similar?

thx,
Dany

[1] http://www.archemedia.eu/royale/img1.png



Op 3 dec 2017 om 11:37 uur uur schreef Piotr Zarzycki <
piotrzarzyck...@gmail.com>:

Hi Dany,

Thanks for trying Moonshine! We will release 1.7.0 version in the next week
or so. You will have many useful things. Examples should be available in
the downloaded royale-asjs package or on our github [1]. If you will have
any problem with recognizing downloaded SDK in Moonshine you can download
binary package from following links [2] (js only version) [3] (js and swf
version).

[1] https://github.com/apache/royale-asjs/tree/develop/examples/royale
[2]
http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
lastSuccessfulBuild/artifact/out/
[3]
http://apacheflexbuild.cloudapp.net:8080/job/royale-
asjs/lastSuccessfulBuild/artifact/out/

Thanks, Piotr


2017-12-03 10:33 GMT+01:00 Dany Dhondt <archeme...@mac.com>:

Thanks Piotr, Harbs for your answers.


I decided to give it a shot during my spare time.

I updated / installed everything I should (maven, node, jdk, …) and

installed Moonshine IDE. I’ll try IntelliJ later because it’s more complex

to configure I guess.


Also I installed royale-compiler, ..asjs and …typedefs through npm.


Since Moonshine at this point will only be able to start from an existing

project, I’d like to know where to find ready-to-use example projects?


@harbs: it will be a multipage project! Does Royale support viewstacks? Or

how multiple pages would be managed?


thx,

Dany






Op 1 dec. 2017, om 12:47 heeft Piotr Zarzycki <piotrzarzyck...@gmail.com



het volgende geschreven:






Hi Dany,







First of all this is wonderful news that you are considering Royale as


one


of the technology to build your application. Answering to your questions


(I


think others will shot you also with more thoughts)







*- will Royale be production ready by february/march?*



Apache Royale team is consist with volunteers which in most cases not



working as a full time developers on framework. In that case it is hard


to


answer whether we will be ready for the production. - I can say that in



some way we are now, but there are plenty of things to do to be more


robust


and easy to use as Flex framework was. The more people and projects will


be


built with Royale we will be better and better.



*- is it possible to easily integrate javascript only components into



Royale? Example: FullCalendar.js*



The answer is yes. As one of the bigger example is MaterialDesignLite [1]



module which is part of the Royale and this is actually integration of



existing MDL library. Additionally Harbs wrote awesome article how to use



existing JS library into the project [2]



-* could anyone provide an IntelliJ template to start with?*



I can provide you an old instruction how to use Intellij with FlexJS [3]


-


I think instruction wasn't check with Royale yet. I can only tell that


I'm


using intellij to develop Royale and previously use Intellij for



development of FlexJS applications itself. You can also work a bit IDE



agnostic using Maven to build your applications and Intellij can be used


as


code assistance only.



You have also two actively developed IDE which supports Royale VSCode



[4][6] and Moonshine [5][7].



*- I'll definitely need help during the development proces, will this be



available?*



I can say that definitely anyone

Re: Re: Building a repository front end with Royale

[Dany Dhondt]

Hi Piotr

Thx for the help. I'm looking forward to version 1.7.0.
Also, MS doesn't recongnize the Royale SDK as valid [1], so it can't activate 
code completion for as. Will this be fixed in the next version?

As for the examples, how can I build them in Moonshine? None of the examples 
has a mxml file in the src folder and Moonshine needs that. Do I have to build 
them first? And if so, how?

Should I rename this thread to 'Royale setup' or something similar?

thx,
Dany

[1] http://www.archemedia.eu/royale/img1.png



Op 3 dec 2017 om 11:37 uur uur schreef Piotr Zarzycki 
<piotrzarzyck...@gmail.com>:

Hi Dany,

Thanks for trying Moonshine! We will release 1.7.0 version in the next week
or so. You will have many useful things. Examples should be available in
the downloaded royale-asjs package or on our github [1]. If you will have
any problem with recognizing downloaded SDK in Moonshine you can download
binary package from following links [2] (js only version) [3] (js and swf
version).

[1] https://github.com/apache/royale-asjs/tree/develop/examples/royale
[2]
http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/lastSuccessfulBuild/artifact/out/
[3]
http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/

Thanks, Piotr


2017-12-03 10:33 GMT+01:00 Dany Dhondt <archeme...@mac.com>:

Thanks Piotr, Harbs for your answers.

I decided to give it a shot during my spare time.
I updated / installed everything I should (maven, node, jdk, …) and
installed Moonshine IDE. I’ll try IntelliJ later because it’s more complex
to configure I guess.

Also I installed royale-compiler, ..asjs and …typedefs through npm.

Since Moonshine at this point will only be able to start from an existing
project, I’d like to know where to find ready-to-use example projects?

@harbs: it will be a multipage project! Does Royale support viewstacks? Or
how multiple pages would be managed?

thx,
Dany





Op 1 dec. 2017, om 12:47 heeft Piotr Zarzycki <piotrzarzyck...@gmail.com>

het volgende geschreven:


Hi Dany,

First of all this is wonderful news that you are considering Royale as

one

of the technology to build your application. Answering to your questions

(I

think others will shot you also with more thoughts)

*- will Royale be production ready by february/march?*
Apache Royale team is consist with volunteers which in most cases not
working as a full time developers on framework. In that case it is hard

to

answer whether we will be ready for the production. - I can say that in
some way we are now, but there are plenty of things to do to be more

robust

and easy to use as Flex framework was. The more people and projects will

be

built with Royale we will be better and better.
*- is it possible to easily integrate javascript only components into
Royale? Example: FullCalendar.js*
The answer is yes. As one of the bigger example is MaterialDesignLite [1]
module which is part of the Royale and this is actually integration of
existing MDL library. Additionally Harbs wrote awesome article how to use
existing JS library into the project [2]
-* could anyone provide an IntelliJ template to start with?*
I can provide you an old instruction how to use Intellij with FlexJS [3]

-

I think instruction wasn't check with Royale yet. I can only tell that

I'm

using intellij to develop Royale and previously use Intellij for
development of FlexJS applications itself. You can also work a bit IDE
agnostic using Maven to build your applications and Intellij can be used

as

code assistance only.
You have also two actively developed IDE which supports Royale VSCode
[4][6] and Moonshine [5][7].
*- I'll definitely need help during the development proces, will this be
available?*
I can say that definitely anyone who is active on that list and in this
project will give an hints and help in any kind of way!

Remember that development list is an public one, so avoid to share some
confident information here, but rather by sending them directly to anyone
interested.

Looking forward to more of your questions and answer from others! :)

[1]
https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/

MaterialDesignLite

[2]
https://github.com/ok-at-github/flexjs-docs/wiki/

Adapting-HTML-CSS-JS-project

[3]
https://cwiki.apache.org/confluence/display/FLEX/Using+

FlexJS+with+IntelliJ+IDEA

[4] https://nextgenactionscript.com/
[5] http://moonshine-ide.com/
[6] https://github.com/apache/royale-asjs/wiki/Visual-Studio-Code
[7] https://github.com/apache/royale-asjs/wiki/Moonshine-IDE

Thanks, Piotr


2017-12-01 12:17 GMT+01:00 Dany Dhondt <archeme...@mac.com>:


Hi all,

I'm working for the library department of a big University college in
Belgium (+13k students). We have spent a year on making a concept for an
institutional repository.
Now, we're in the phase of making a tender for the backbone software

which

will handle storage, DOI's etc. High on our list is figshare [1].

Re: Building a repository front end with Royale

[Dany Dhondt]

Thanks Piotr, Harbs for your answers.

I decided to give it a shot during my spare time.
I updated / installed everything I should (maven, node, jdk, …) and installed 
Moonshine IDE. I’ll try IntelliJ later because it’s more complex to configure I 
guess.

Also I installed royale-compiler, ..asjs and …typedefs through npm.

Since Moonshine at this point will only be able to start from an existing 
project, I’d like to know where to find ready-to-use example projects?

@harbs: it will be a multipage project! Does Royale support viewstacks? Or how 
multiple pages would be managed?

thx,
Dany




> Op 1 dec. 2017, om 12:47 heeft Piotr Zarzycki <piotrzarzyck...@gmail.com> het 
> volgende geschreven:
> 
> Hi Dany,
> 
> First of all this is wonderful news that you are considering Royale as one
> of the technology to build your application. Answering to your questions (I
> think others will shot you also with more thoughts)
> 
> *- will Royale be production ready by february/march?*
> Apache Royale team is consist with volunteers which in most cases not
> working as a full time developers on framework. In that case it is hard to
> answer whether we will be ready for the production. - I can say that in
> some way we are now, but there are plenty of things to do to be more robust
> and easy to use as Flex framework was. The more people and projects will be
> built with Royale we will be better and better.
> *- is it possible to easily integrate javascript only components into
> Royale? Example: FullCalendar.js*
> The answer is yes. As one of the bigger example is MaterialDesignLite [1]
> module which is part of the Royale and this is actually integration of
> existing MDL library. Additionally Harbs wrote awesome article how to use
> existing JS library into the project [2]
> -* could anyone provide an IntelliJ template to start with?*
> I can provide you an old instruction how to use Intellij with FlexJS [3] -
> I think instruction wasn't check with Royale yet. I can only tell that I'm
> using intellij to develop Royale and previously use Intellij for
> development of FlexJS applications itself. You can also work a bit IDE
> agnostic using Maven to build your applications and Intellij can be used as
> code assistance only.
> You have also two actively developed IDE which supports Royale VSCode
> [4][6] and Moonshine [5][7].
> *- I'll definitely need help during the development proces, will this be
> available?*
> I can say that definitely anyone who is active on that list and in this
> project will give an hints and help in any kind of way!
> 
> Remember that development list is an public one, so avoid to share some
> confident information here, but rather by sending them directly to anyone
> interested.
> 
> Looking forward to more of your questions and answer from others! :)
> 
> [1]
> https://github.com/apache/royale-asjs/tree/develop/frameworks/projects/MaterialDesignLite
> [2]
> https://github.com/ok-at-github/flexjs-docs/wiki/Adapting-HTML-CSS-JS-project
> [3]
> https://cwiki.apache.org/confluence/display/FLEX/Using+FlexJS+with+IntelliJ+IDEA
> [4] https://nextgenactionscript.com/
> [5] http://moonshine-ide.com/
> [6] https://github.com/apache/royale-asjs/wiki/Visual-Studio-Code
> [7] https://github.com/apache/royale-asjs/wiki/Moonshine-IDE
> 
> Thanks, Piotr
> 
> 
> 2017-12-01 12:17 GMT+01:00 Dany Dhondt <archeme...@mac.com>:
> 
>> Hi all,
>> 
>> I'm working for the library department of a big University college in
>> Belgium (+13k students). We have spent a year on making a concept for an
>> institutional repository.
>> Now, we're in the phase of making a tender for the backbone software which
>> will handle storage, DOI's etc. High on our list is figshare [1]. We would
>> use figshare as a repository backbone and build our own front end using
>> figshare's api's.
>> It will be my responsibility to develop, implement and maintain this front
>> end. I  think development will start around february/march 2018 and it will
>> be up to me to choose a front end technology. So far, choices are Angular,
>> React or Vue. Since I have quite some experience with Flex, I would like to
>> add Royale to this list.
>> I have been following the Flex/Royale dev lists very closely and I'm
>> convinced of the quality of the product but:
>> 
>> - will Royale be production ready by february/march?
>> - is it possible to easily integrate javascript only components into
>> Royale? Example: FullCalendar.js [2]
>> - could anyone provide an IntelliJ template to start with?
>> - I'll definitely need help during the development proces, will this be
>> available?
>> - and last but not least: is Roy

Building a repository front end with Royale

[Dany Dhondt]

Hi all,

I'm working for the library department of a big University college in Belgium 
(+13k students). We have spent a year on making a concept for an institutional 
repository. 
Now, we're in the phase of making a tender for the backbone software which will 
handle storage, DOI's etc. High on our list is figshare [1]. We would use 
figshare as a repository backbone and build our own front end using figshare's 
api's.
It will be my responsibility to develop, implement and maintain this front end. 
I  think development will start around february/march 2018 and it will be up to 
me to choose a front end technology. So far, choices are Angular, React or Vue. 
Since I have quite some experience with Flex, I would like to add Royale to 
this list.
I have been following the Flex/Royale dev lists very closely and I'm convinced 
of the quality of the product but:

- will Royale be production ready by february/march?
- is it possible to easily integrate javascript only components into Royale? 
Example: FullCalendar.js [2]
- could anyone provide an IntelliJ template to start with?
- I'll definitely need help during the development proces, will this be 
available?
- and last but not least: is Royale the right choice?

If it is convenient, I can provide a full front end wireframe (built in Adobe 
XD CC) although that should be treated as highly confidential

There is much at stake here so please advise...

thanks in advance

Dany

[1] https://figshare.com/services/institutions
[2] https://fullcalendar.io

Re: Publishing royale to npm

[Dany Dhondt]

Just as an outsider: isn’t the whole point of royale to get rid of flash 
dependency? I’m eagerly waiting for the first full royale release to finally 
start converting my projects to html/js but the last thing I want is any 
dependency towards flash/swf. So I’m in favor of a jsonly package

Dany



> Op 30 okt. 2017, om 09:15 heeft OmPrakash Muppirala  
> het volgende geschreven:
> 
> I was wondering if we should publish the apache.royale-jsonly verson via
> npm instead of the full version with swf support.
> After all, users coming in vial npm would most likely not expect swf
> support.
> 
> Any thoughts on this proposal?
> 
> Thanks,
> Om