On 1/3/18, 6:50 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote:
>I agree as well with what Olaf said. For me having parts of the Royale >website done with royale is sufficient. Great, so please help us create those parts by telling more about the fonts and colors you are using. > >@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. In order for us to make the other parts look consistent we need to know the fonts being used. The ruler-and-pencil icon appears to be using font family "et-line". Can you tell me where I can get a free and open source et-line font? > >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. IMO, we will get to the first release faster and better with a better site that attracts more developers instead of users. > >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. I am not an official spokesperson for Adobe or its business strategies, but from my perspective, Adobe is not very interested in traditional web applications so a good looking simple example probably isn't going to convince them to keep paying me and Peter. Adobe is way more interested in creatives, and in helping these folks create web content and mobile applications. Otherwise, I would think Adobe would be pushing some sort of migration solution for its Flex customers. Also, Adobe has to produce a ton of web content itself to market and support its customers. That is one reason I put some time into mocking up the Royale website in Royale. I think what might be more interesting to Adobe is showing that Royale can help these creatives create web content or help Adobe create its web content. I would like to not spend too much more time on my Royale Website POC, so if you can help me bring it closer to looking like your WP version of the site by telling me the fonts and colors, then not only will we be able to make the other parts of our site like the TryItNow and ASDoc look more consistent, but I will have a better story if I need to try to convince Adobe that Royale is worth the money they are spending on it. Right now, the POC doesn't look close enough, so it is unlikely to be convincing. Of course, I could be wrong, but I am always looking for other ways to justify my full-time assignment to Apache, and I would appreciate your help instead of telling me not to work on it. Thanks, -Alex > >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: >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro >>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com >>%7Cd8b185e854b74ee1fdd908d552b9681b%7Cfa7b1b5a7b34438794aed2c178decee1%7C >>0%7C0%7C636505878630565332&sdata=v11mPW8we9iRyky%2BgOHm5MuO9gFPZhLltmrpKx >>G5TR0%3D&reserved=0 >> >> > > >-- >Carlos Rovira >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2 >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd8b185e854b74ee1fdd908d5 >52b9681b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636505878630565332&s >data=m7q6OxWrgWTx9USLwzqVeQotZ%2Fvgm2eB7Ys0XpkxaSU%3D&reserved=0
