Carlos, 2018-01-03 15:50 GMT+01:00 Carlos Rovira <[email protected]>:
> I agree as well with what Olaf said. For me having parts of the Royale > website done with royale is sufficient. > > @Alex, the icons in website are as well free and open source from various > icons sets out there like font awesome and line icons and others. Again, > nothing that you should waste your valuable time. > > As Josh, with VSCode, I'm as well on hold waiting for the first release to > push latest touches on website and we'll have that as well. > > *I think most of the PMCs are saying that website should be published NOW, without waiting for the release. Am I miss something ? Updates with NPM details can come later on.* > Regarding, Adobe, I think I express it badly. I didn't want to say that. > What I want to say is that if you need to "sell" the value of your work to > Adobe you can do it with a good looking simple example so they pay you and > Peter fro your work here. I know, and don't expect Adobe sell Royale > anytime anywhere. > > Carlos > > > > 2018-01-03 13:07 GMT+01:00 Gabe Harbs <[email protected]>: > > > I agree. > > > > > On Jan 3, 2018, at 6:57 AM, Olaf Krueger <[email protected]> wrote: > > > > > > Hi, > > > I would just like to mention that from my point of view it I would be > > really > > > helpful to have a first Royale release soon, e.g. 0.9.0. > > > After that, Royale could evolve by minor versions like 0.9.1, 0.9.2, > etc. > > > > > > I agree with Carlos that there is still a way to go regarding missing > > stuff > > > and the developer experience but I think we should address those things > > to > > > the first major release 1.0.0. > > > I also agree that there is a danger that folks who starts with > exploring > > > Royale will be dissapointed and leave. To avoid this we should mention > > > anywhere and as often as possible that Royale is still under > > development... > > > but also ready for building apps. > > > > > > AFAIK Josh is on hold with his VSCode extension until the first Royale > > > version is released. > > > And maybe other users from the Flex lists who doesn't follow all those > > posts > > > are lost cause Royale acts a bit in the dark at the moment. > > > I could imagine that users who would like to get in touch with Royale > > don't > > > want to start with the FlexJS version but also don't know where to > find a > > > appropriate Royale version. > > > > > > I am trying to work as often as possible on our little TryItNow app > using > > > Royale. > > > I started from scratch and I really hope to provide this app with a > nice > > > look and feel which follows Carlos website design. If this will be > > > successful we'll have one part of the Royale website that is > implemented > > by > > > using Royale at least. > > > > > > Just my 2 cents, > > > Olaf > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > > > > > > > -- > Carlos Rovira > http://about.me/carlosrovira > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
