On 1/2/18, 9:48 AM, "[email protected] on behalf of Carlos Rovira" <[email protected] on behalf of [email protected]> wrote:
>Hi Alex, > >Please explain what is ET-Line, I don't know what you refer with that. >The fonts used are from Google Fonts, so I think there's no problem at all >since is what 99% of the sites use today. >Colors as well are impossible to be keep by a license, and I used what I >thought was right to me. So that's my work. When I go to [1], where it says "Enterprise Class Level" there is an icon with a rule and a pencil. What icons or icon font is that? [1] http://royale.codeoscopic.com > >In the end, think that a site "face" use to fresh for some time (maybe a >couple of years?), so the other point to not worry about this is >that if we get the rest done a people come, we'll need to go back a make a >new "fresh" version of the site that will rework all that is done. >And mostly maybe only a few part will remain beyond content (maybe 10%?). > >So if we use the current site, we hace 1-2 year to focus on what's >important and then with a robust tech, come back to the site and rework it >in MXML-AS3 > >About incremental. I'm with you, but with a minimum state. I think we >still >don't have the minimum to make incremental work. As I said you, people >coming to us right now will find they can't make an raw app with what we >have and so, they will be unhappy users telling other users that Royale >doesn't work or something like that. That's my fear right now. Carlos, Adobe may not pay me and/or Peter to work on Royale full time for another 1 or 2 years. I don't see how we will get to any minimum state by not recruiting more folks like Harbs, Yishay, Josh, and Piotr. Folks who understand how to work on the bleeding-edge of development. We can only do little bits of improvement at a time. There is no team even 10% of the size of the Adobe Flex team to get a ton of code done and then release it. If you think otherwise, then prove it to me by getting people to get a ton of code done. > >For Adobe, to sell Royale, I think will be easy if we build a basic app >that looks pretty good. Adobe likes things done simple with good graphics. >And that's what many of us wants since right now Royale produces ugly >interfaces. Don't you think that's a great goal for many of us? I think you are still in the Adobe Flex mindset of traditional product development and marketing. If so, that needs to change. Adobe will not sell Royale. Royale is free open source. Thus Adobe is generously donating Peter and me to Royale. They could change their minds at any time. It is a donation and not a long-term strategic investment and probably never will be. My goal is to show Adobe that they can save money (not make money) and have happier customers by using Royale to produce their web applications and mobile applications. And maybe save money producing web content as well, which is why I want to show that we can produce the Royale site in Royale. That way they may continue to donate Peter and I to Royale. If you think what Royale produces today is ugly, then help us make it better, by doing the work yourself, or tweaking our site to try to attract a few more folks like our current committers, and/or producing a sample app and telling us what you don't like about it. Our current site at royale.apache.org is not helping to attract folks, IMO. My 2 cents, -Alex
