On Sun, Apr 29, 2018 at 3:50 AM, Dany Dhondt <archeme...@mac.com> wrote:
> 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? > > We do have such a thing. Please check out the royale cli tool. Setup instructions here: https://github.com/apache/royale-asjs/tree/develop/npm/cli I think it does what you are asking for and more :-) For example, it monitors your src folder and recompiles the Royale app and reloads the browser as well! One of these days we need to make a blog post about this. I would really really like feedback so we can make this tool better. > 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. > Right now, the cli installs a very simple hello-world app. I am planning on replacing this with a Jewel themed app soon. Volunteers are more than welcome to help out here. > > 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 < > piotrzarzyck...@gmail.com> het volgende geschreven: > > > > +1 for Olaf's email and Alex's changes. > > > > Piotr > > > > On Sun, Apr 29, 2018, 7:15 AM Alex Harui <aha...@adobe.com.invalid> > 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" <m...@olafkrueger.net> 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&data=02%7C01%7Caharui%40adobe.com%7C3e3259b920be40097fca08d5ad44 > 2a1f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0% > 7C636605430693133595&sdata=Rc1UvmlbDwC2clAZc2nFAijvr6kaVr > JtlOhlk2e1mr0%3D&reserved=0 > >> > >> > >> > >
