Ok Alex,
I end with that change for home
best,
Carlos
2018-01-05 2:54 GMT+01:00 Alex Harui :
> Yes, looks ok to me.
>
> Thanks for making the changes.
>
> -Alex
>
> On 1/4/18, 4:05 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> wrote:
>
> >Hi Alex,
> >
> >this one is MIT:
> >http
Yes, looks ok to me.
Thanks for making the changes.
-Alex
On 1/4/18, 4:05 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi Alex,
>
>this one is MIT:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fundraw.co
>%2Fillustrations&data=02%7C01%7Caharui%40adobe.c
I changed the second to test that sag icons (multiple target and devices)
let me know if it's ok
2018-01-05 1:05 GMT+01:00 Carlos Rovira :
> Hi Alex,
>
> this one is MIT: https://undraw.co/illustrations
>
> so I think this ok for us right?
>
>
>
> 2018-01-05 1:01 GMT+01:00 Carlos Rovira :
>
>> Hi
Hi Alex,
this one is MIT: https://undraw.co/illustrations
so I think this ok for us right?
2018-01-05 1:01 GMT+01:00 Carlos Rovira :
> Hi Alex,
>
> I'll see other options. In fact that part of the home was done only as
> something temporal and I want to replace for other material
>
> 2018-01-
Hi Alex,
I'll see other options. In fact that part of the home was done only as
something temporal and I want to replace for other material
2018-01-04 18:46 GMT+01:00 Alex Harui :
> Carlos,
>
> Even if we "can" use ET-Line on the website, can we replace it now with
> something ALv2 compatible?
Carlos,
Even if we "can" use ET-Line on the website, can we replace it now with
something ALv2 compatible? That way we won't have to revisit this topic
later, and I can make my mockup look more like your site, which might help
me continue to keep working on Royale full-time.
Please?
-Alex
On 1/
Hi Justin,
as stated by apache legal in the ticket where we discussed the website, is
perfectly legal, since our website is only a marketing tool and no
something that users will download as part of Apache Royale technology that
we build.
In case we want to make a website build with royale and pr
Hi,
> Fonts are perfectly legal! They are available in Google Fonts! :)\
Most of the fonts used (e.g. Hind Siliguri, Open Sans Condensed, Oswald,
Signika and Source Sans Pro) are available from google fonts and under either
the open font license or the APv2 license so there’s no issue with thos
Piotr,
Fonts are perfectly legal! They are available in Google Fonts! :)
I created a Release website thread to get it published ASAP
let's get move on
2018-01-04 12:41 GMT+01:00 Piotr Zarzycki :
> If fonts have incompatible license and it looks like it has, we
> unfortunately have to replace
Hi Olaf,
my global opinion always was that the website is only marketing thing. We
are not releasing it as a product, and that's what apache legal said, so we
should not we worried about it. We are not publishing nothing ilegal, and
with things that we can't use. All is based on WP and a theme tha
2018-01-03 21:22 GMT+01:00 Alex Harui :
>
> Great, so please help us create those parts by telling more about the
> fonts and colors you are using.
>
Hi Alex,
inside the WP admin interface, in theme options you have a font section
where all of you can see what fonts are used for each part (Appea
If fonts have incompatible license and it looks like it has, we
unfortunately have to replace it by some other one. If we would like to
confirm we should raise a jira for Legal.
That's my thoughts. Let's move forward, because that discussion takes too
long and I don't see any end.
Thanks, Piotr
As for your questions:
1) Yes we should do as Alex suggested. We should remove, or put in that
place information that it will be filled once we release things. We can put
there link to the section with Nightly Build.
2) Nightly build is enough for now.
Thanks, Piotr
2018-01-04 12:24 GMT+01:00 C
Carlos,
During past 4 weeks I have sent link to nightly build of Royale at least 20
times to several people. :) Yes for me it is worth to have website right
now.
I'm not sure what do you mean that people can't use Royale at all. Yes they
can - I'm working every day on my examples using Nightly bu
Hi Piotr,
site has the right info right now. But there's key points to release. For
example:
* Should we remove NPM zones as Alex suggest? or wait for Om to end NPM
version?, but to do this, first we need to release
* I think many people here said that we need at least a first release, so
people c
Hi,
> Maybe you can get it here but it seems to me that licensing is not really
> clear [1].
It’s reasonably clear that it's GPL as I said the other day. See [1] (see point
6 under registration) and [2] which states "As always, these icons are
completely free to use, and have been released unde
> Can you tell me where I can get a free and open source
> et-line font?
Maybe you can get it here but it seems to me that licensing is not really
clear [1].
If this is an issue, maybe we could find a replacement for the icons at font
awesome?
>I would appreciate your
>help instead of telling
On 1/3/18, 6:50 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
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.
Carlos,
2018-01-03 15:50 GMT+01:00 Carlos Rovira :
> 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 ico
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 valua
I agree.
> On Jan 3, 2018, at 6:57 AM, Olaf Krueger 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 wi
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 de
I really like doing things and moving forward.
I see only one problem in case of website which has been raised - License.
If you guys figure out whether problematic stuff is ok, we should export
and public that website now. There is no point to wait, building new one
using Royale can always happen
On 1/2/18, 9:48 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
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 w
Hi -
> On Jan 2, 2018, at 9:48 AM, Carlos Rovira wrote:
>
> 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.
Royale is not an Adobe project. At Apache we are about software for the public
good w
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
Yes, Happy New Year to one and all.
I couldn't figure out what to snip, so I'm top-posting...
I've been buried with compiler and build process work, so it has been
months since I actually tried to build something from the very beginning.
Maybe we can get some other folks to try to build something
Hi Alex and all, And first of all Happy new year to all of you! Hope 2018
be a great year for all of you! :)
2017-12-30 8:50 GMT+01:00 Alex Harui :
>
> I agree with what you say. What I am suggesting is making enough changes
> to the site to attract people who can help us create a "most usable
Hi Carlos,
Comments inline..
On 12/29/17, 5:21 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi,
>
>thinking about all of this this days...to be honest my point of view is to
>release a cool image (website and more) of Royale as soon as we have the
>most usable product.
>
>I
Hi,
thinking about all of this this days...to be honest my point of view is to
release a cool image (website and more) of Royale as soon as we have the
most usable product.
I think we don't have yet and for that reason (and due to a ton of work) I
didn't make more progress.
My fear is that putti
Hi Alex,
+1 for point 1. I think we don't have to wait for the NPM if we go to with
your IDEA. Let's see what Carlos will say.
I do also agree with you that we should slowly start create replacement in
Royale of our website.
Thanks, Piotr
2017-12-29 9:04 GMT+01:00 Alex Harui :
> Couple of tho
Couple of thoughts:
1) Should we alter what Carlos has in some way so that we can put a copy
of it up on royale.a.o now and update it again after the first Royale
release? I would rather have a nicer site now that has links to useful
things. If a better site can bring in more folks between now a
Hi Alex,
Many things to cover here, I agree with some and not with others:
* About the MXML initiative to search a way for more productive HTML
layouts, that's very cool.
* The repetition in HTML as you said is so cumbersome. The way Flex always
handled that was through components, dataproviders,
I also think this is a great initiative. Regarding SEO there are some
optimizations that can be applied to single page apps as well so maybe it's
worth testing that before we convert it to a multipage. I'm not in front of
the computer but when I am I'll share the links I read, if there's interest
i
FYI, with cache enabled the page load was so fast that there was no noticeable
browser redraw! I’m blown away by the performance!
> On Dec 22, 2017, at 12:19 PM, Harbs wrote:
>
> 2. The speed that the page loaded is incredible. First draw was less than a
> second and fully loaded was less than
Some thoughts:
1. This is a great initiative!
2. The speed that the page loaded is incredible. First draw was less than a
second and fully loaded was less than 2 seconds — with cache disabled.
3. Ultimately I think this is the way we want to go, but getting the polish on
this right will take a s
Hi,
First, thanks to Carlos for all of the work he's been putting into the
future Royale web site.
While waiting on something from Infra, I decided to try to approximate the
home page that Carlos has been working on [1]. I wanted to do so for the
following reasons:
-try to eliminate the dependen
37 matches
Mail list logo
