You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Peter Ent <pe...@adobe.com.INVALID> on 2017/10/09 20:55:21 UTC
Flex2Royale
I've built a little app that produces a table that looks through the ASDoc JSON files. This app is driven by a config file that contains a map from Flex components to Royale Express components. For each Royale component listed in the config file, the corresponding ASDoc JSON file is loaded and if it has a new ASDoc tag, @commentary, it shows that in the last column.
I would like to show this to you, but I cannot figure out how to post the site (about 6 MB, its js-debug) to my home.apache.org account. I can transfer the file there as a .tar but it looks like ssh is prevented on home.apache.org at this point.
Using ASDoc + a driver file is one way to do this. Another way is to just scan all of the ASDoc JSON files looking for some clues about which classes could be compared to Flex components. I would say this would mean adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it may take longer to scan through all the JSON files and build the table.
I need to sync up with changes to the repos and then I'll publish my example in the royale-as/examples directory so you can build it for yourselves and take a look.
—peter
Re: Flex2Royale
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Right Alex,
If by the time I finish on website there's no work proposed by Angelo or
other, I'll put that task on my plate and work on some proposal. But since
Angelo said he was doing something, hope he could give some us some word on
his progress
Thanks
2017-10-17 18:06 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> My understanding is that we would see proposals consisting of artwork and
> not necessarily CSS/SVG/code.
>
> I am hopeful that Carlos's #2 task would inform us on, given some artwork,
> we would implement the artwork via CSS or SVG or something else.
>
> Looking forward to seeing things,
> -Alex
>
> On 10/17/17, 6:49 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
>
> >Right.
> >
> >Hope Angelo could share the state of his work and know if he's doing some
> >progress
> >
> >2017-10-17 15:18 GMT+02:00 Piotr Zarzycki <pi...@gmail.com>:
> >
> >> Yes! It was discussed here [1]. Remember that Angelo said that hey are
> >>in
> >> progress, but do not have to much time for that.
> >>
> >> [1]
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-fl
> >>ex-users.2333346.n4.nabble.com%2FRe-&data=02%7C01%7C%
> 7Ce45d56f1013e486bb9
> >>8008d51565e394%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364384497406
> >>72437&sdata=Az3yGGBBtbevPZCpqSKFLRs7fZ4SVrOwWy6LkfaP42M%3D&reserved=0
> >> FlexJS-Wanted-UX-UI-Design-Proposals-td14439.html
> >>
> >> Piotr
> >>
> >> 2017-10-17 12:19 GMT+02:00 Olaf Krueger <ma...@olafkrueger.net>:
> >>
> >> > If I remember it correctly some other guys already started the work
> >>on a
> >> > default theme.
> >> > There is a thread at the Flex users or dev list about this but I can
> >>not
> >> > find it... my bandwitdh is too bad at the moment.
> >> > Just to make sure that you keep this in mind...
> >> >
> >> > 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%7C%
> 7Ce45d56f1013e486
> >>bb98008d51565e394%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364384497
> >>40672437&sdata=xVcBbPgjaVleOZNEDtarLen18DyW8%
> 2F5Se0kM37spK5M%3D&reserved=
> >>0
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> mobile: +48 880 859 557
> >> skype: zarzycki10
> >>
> >> LinkedIn:
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.linke
> >>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565
> e39
> >>4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636438449740672437&sdata=U
> >>vjQvwrEbWgF0r9VhfCJBTbEHhDsLatVVGqMAC%2FOxD0%3D&reserved=0
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpl.link
> >>edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02%
> 7C01%7C%7Ce45d56f1013e486
> >>bb98008d51565e394%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364384497
> >>40672437&sdata=nLvnI9A0VPfV2ddegRd4AW72Gl7ks%
> 2FY1JLa4HYisRiU%3D&reserved=
> >>0>
> >>
> >> GitHub:
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgithub.c
> >>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565
> e394%7
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=
> fuYq
> >>4uvYUshx9CSur7eEKCIlcTe2kDrH%2F7g2d4%2FN26I%3D&reserved=0
> >>
> >
> >
> >
> >--
> >
> ><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565
> e394%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636438449740672437&
> sdata=sJZrPBwR7nupSrCT
> >oweS6%2FoHskWGmkwDlVbQj5DF6YU%3D&reserved=0>
> >
> >Carlos Rovira
> >
> >Director General
> >
> >M: +34 607 22 60 05
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeos
> >copic.com&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565
> e394%7Cfa7b1b5a7b3
> >4438794aed2c178decee1%7C0%7C0%7C636438449740672437&
> sdata=sJZrPBwR7nupSrCTo
> >weS6%2FoHskWGmkwDlVbQj5DF6YU%3D&reserved=0
> >
> >
> >Conocenos Avant2 en 1 minuto!
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> >s%2F%23video&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565
> e394%7Cfa7b1b5a
> >7b34438794aed2c178decee1%7C0%7C0%7C636438449740672437&
> sdata=fGPHedZqzbwRol
> >ramyQ8MWgegSDXJnsWuqvAJjggPlY%3D&reserved=0>
> >
> >
> >Este mensaje se dirige exclusivamente a su destinatario y puede contener
> >información privilegiada o confidencial. Si ha recibido este mensaje por
> >error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> >proceda a su destrucción.
> >
> >De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> >comunicamos
> >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> >S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> >servicio o información solicitados, teniendo usted derecho de acceso,
> >rectificación, cancelación y oposición de sus datos dirigiéndose a
> >nuestras
> >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> >necesaria.
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: Flex2Royale
Posted by Alex Harui <ah...@adobe.com.INVALID>.
My understanding is that we would see proposals consisting of artwork and
not necessarily CSS/SVG/code.
I am hopeful that Carlos's #2 task would inform us on, given some artwork,
we would implement the artwork via CSS or SVG or something else.
Looking forward to seeing things,
-Alex
On 10/17/17, 6:49 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Right.
>
>Hope Angelo could share the state of his work and know if he's doing some
>progress
>
>2017-10-17 15:18 GMT+02:00 Piotr Zarzycki <pi...@gmail.com>:
>
>> Yes! It was discussed here [1]. Remember that Angelo said that hey are
>>in
>> progress, but do not have to much time for that.
>>
>> [1]
>>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>ex-users.2333346.n4.nabble.com%2FRe-&data=02%7C01%7C%7Ce45d56f1013e486bb9
>>8008d51565e394%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364384497406
>>72437&sdata=Az3yGGBBtbevPZCpqSKFLRs7fZ4SVrOwWy6LkfaP42M%3D&reserved=0
>> FlexJS-Wanted-UX-UI-Design-Proposals-td14439.html
>>
>> Piotr
>>
>> 2017-10-17 12:19 GMT+02:00 Olaf Krueger <ma...@olafkrueger.net>:
>>
>> > If I remember it correctly some other guys already started the work
>>on a
>> > default theme.
>> > There is a thread at the Flex users or dev list about this but I can
>>not
>> > find it... my bandwitdh is too bad at the moment.
>> > Just to make sure that you keep this in mind...
>> >
>> > 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%7C%7Ce45d56f1013e486
>>bb98008d51565e394%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364384497
>>40672437&sdata=xVcBbPgjaVleOZNEDtarLen18DyW8%2F5Se0kM37spK5M%3D&reserved=
>>0
>> >
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> mobile: +48 880 859 557
>> skype: zarzycki10
>>
>> LinkedIn:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565e39
>>4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=U
>>vjQvwrEbWgF0r9VhfCJBTbEHhDsLatVVGqMAC%2FOxD0%3D&reserved=0
>>
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.link
>>edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02%7C01%7C%7Ce45d56f1013e486
>>bb98008d51565e394%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364384497
>>40672437&sdata=nLvnI9A0VPfV2ddegRd4AW72Gl7ks%2FY1JLa4HYisRiU%3D&reserved=
>>0>
>>
>> GitHub:
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565e394%7
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=fuYq
>>4uvYUshx9CSur7eEKCIlcTe2kDrH%2F7g2d4%2FN26I%3D&reserved=0
>>
>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565e394%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=sJZrPBwR7nupSrCT
>oweS6%2FoHskWGmkwDlVbQj5DF6YU%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565e394%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=sJZrPBwR7nupSrCTo
>weS6%2FoHskWGmkwDlVbQj5DF6YU%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Ce45d56f1013e486bb98008d51565e394%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636438449740672437&sdata=fGPHedZqzbwRol
>ramyQ8MWgegSDXJnsWuqvAJjggPlY%3D&reserved=0>
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: Flex2Royale
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Right.
Hope Angelo could share the state of his work and know if he's doing some
progress
2017-10-17 15:18 GMT+02:00 Piotr Zarzycki <pi...@gmail.com>:
> Yes! It was discussed here [1]. Remember that Angelo said that hey are in
> progress, but do not have to much time for that.
>
> [1]
> http://apache-flex-users.2333346.n4.nabble.com/Re-
> FlexJS-Wanted-UX-UI-Design-Proposals-td14439.html
>
> Piotr
>
> 2017-10-17 12:19 GMT+02:00 Olaf Krueger <ma...@olafkrueger.net>:
>
> > If I remember it correctly some other guys already started the work on a
> > default theme.
> > There is a thread at the Flex users or dev list about this but I can not
> > find it... my bandwitdh is too bad at the moment.
> > Just to make sure that you keep this in mind...
> >
> > Olaf
> >
> >
> >
> > --
> > Sent from: http://apache-royale-development.20373.n8.nabble.com/
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
>
> GitHub: https://github.com/piotrzarzycki21
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: Flex2Royale
Posted by Piotr Zarzycki <pi...@gmail.com>.
Yes! It was discussed here [1]. Remember that Angelo said that hey are in
progress, but do not have to much time for that.
[1]
http://apache-flex-users.2333346.n4.nabble.com/Re-FlexJS-Wanted-UX-UI-Design-Proposals-td14439.html
Piotr
2017-10-17 12:19 GMT+02:00 Olaf Krueger <ma...@olafkrueger.net>:
> If I remember it correctly some other guys already started the work on a
> default theme.
> There is a thread at the Flex users or dev list about this but I can not
> find it... my bandwitdh is too bad at the moment.
> Just to make sure that you keep this in mind...
>
> Olaf
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
--
Piotr Zarzycki
mobile: +48 880 859 557
skype: zarzycki10
LinkedIn: http://www.linkedin.com/piotrzarzycki
<https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
GitHub: https://github.com/piotrzarzycki21
Re: Flex2Royale
Posted by Olaf Krueger <ma...@olafkrueger.net>.
If I remember it correctly some other guys already started the work on a
default theme.
There is a thread at the Flex users or dev list about this but I can not
find it... my bandwitdh is too bad at the moment.
Just to make sure that you keep this in mind...
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Flex2Royale
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Carlos,
I agree that themes like in Flex would be very attractive. I'm not sure
it belongs in Express. Express is a pre-composition of Basic which is
tuned to use CSS for visual customization. For example, Express and Basic
Checkbox is an HTMLInputElement.
I think we learned in the MDL and Flat work that a Basic/Express CheckBox
cannot be fully visually customized, and so the Flat/Bootstrap folks
re-composed their CheckBox as a tree of HTMLElements. Didn't you have to
do that for MDL as well? I'm not sure the topology of the MDL and
Flat/Bootstrap Checkboxes are the same or need to be the same.
Flat/Bootstrap uses a custom icon font, for example. But for PAYG
reasons, we don't want the Basic/Express Checkboxes to carry around that
topology. That's why we want to support a variety of component sets.
A Skinnable Component set would probably choose some topology for its
controls and all themes would have to be implemented as customizations of
those topologies. I think that might still require an extra wrapping DIV,
which would be pretty much like the extra UIComponent for each component
skin, but that might be the price you pay for generic vector
customization. All we need is a volunteer to try to make it work. I know
Om was interested, but not sure how available he is. Peter will let us
know if he's interested.
IMO, the most efficient way to do this is to first decide on how to
implement this in pure HTML/JS/CSS/SVG. So maybe start a new thread and
make sure we have general consensus that SVG is going to be the choice for
now (as opposed to bitmaps, or some other graphics API like Canvas, WebGL,
etc). Then, without Royale, manually build a small set of "components" in
pure HTML/JS/CSS that you can customize by swapping in just what SVG each
component is supposed to use. You shouldn't need any infrastructure from
others to do that. The goal is just to prove that you can create visuals
separately from a component's HTMLElement topology, and then we can see
what the "change points" are when swapping and then we can see how that
matches up against our tooling. IOW, I think we want to see how good two
different themes look and how small the differences between themes can be
before we invest in infrastructure/tooling. We may learn that SVG sucks
and we need to instead require Canvas to do skinning, and I think you can
find that out just with your current web development tools.
My 2 cents,
-Alex
On 10/16/17, 10:02 AM, "carlos.rovira@gmail.com on behalf of Carlos
Rovira" <carlos.rovira@gmail.com on behalf of
carlos.rovira@codeoscopic.com> wrote:
>Hi Alex,
>
>I think the piece that is still missing is "themeing". We created some
>subset based on external frameworks (MDL, CreateJS,...), but I always said
>this was only as an exercise and to fill a gap we have with our custom UI
>set. For me all efforts should go in the Express set direction to have one
>set and many "themes". external UI sets will always work differently and
>have their own controls (that will not match ours in many cases) and for
>this reason themeing is not standarizable.
>
>In the other hand Flex Skins was something very powerful, and I think we
>should not lose that in Royale, so Royale could end declaring skins in a
>similar way as Flex did, but implementing in a better way that provides
>better performance. the generated code in HTML/JS could be far way simple
>that in Flex that need a complete UIComponent that means a huge object to
>deal with it at runtime.
>
>I'd love to work in the visuals of themeing for Express when finish royale
>website if some theme infrastructure is setup. IMHO, for this to be done,
>we will need at least be two contributors, maybe Peter or you and me with
>the visuals. I could work in two visuals to put the themeing feature on
>the
>plate, one could be wireframe theme and another something more elaborated.
>
>
>
>
>2017-10-16 18:04 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> IIRC, Om was working on this to some degree. One plan was to convert
>>FXG
>> to SVG.
>>
>> AIUI, a SkinnableContainer wouldn't be that hard. Container already has
>> an inner div to hold the children, so a different view could have the
>> outer div display SVG behind the children. I think there were more
>> questions about SkinnableComponent because not every component is
>>already
>> implemented to support a skin by default, and SVG as a backgroundImage
>>for
>> some HTMLElements don't work well in all browsers.
>>
>> Flex Skinning was pretty expensive because it added a UIComponent child
>>to
>> every component. Because we are PAYG, we don't want to force that on
>> everyone, and as the MDL work showed, CSS Themes may be just as good at
>> creating nice visual experiences and more standard/common. But as
>>Yishay
>> said, in theory, a new set of views could add that extra DIV behind each
>> component if that's what it takes to implement SVG "skins". And we also
>> know from MDL and Flat that we can also just re-factor components into
>> enough pieces that they can have a different look.
>>
>> Of course, I could be wrong...
>> -Alex
>>
>> On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>>
>> >We need to have a "skinning story" - something about alternate views,
>>CSS,
>> >that sort of thing. Adding to my list.
>> >‹peter
>> >
>> >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
>> >
>> >>I like it.
>> >>
>> >>
>> >>> There is no direct equivalent of SkinnableContainer in Royale (at
>>this
>> >>> time). A reasonable alternative is the Container.
>> >>
>> >>Maybe we could mention that Royale components typically have views
>>which
>> >>can
>> >>be used to control appearance without changing behavior. To me, spark
>> >>skins
>> >>sort of played the same role.
>> >>
>> >>
>> >>
>> >>--
>> >>Sent from:
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-ro
>> >>y
>> >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
>> 7C1f660ab8e3b74b1c
>> >>a
>> >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636437321952
>> >>4
>>
>>>>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&reserved=0
>> >
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7C6a1ec2e043e349c3bd3c08d514b7cd3f%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636437702013883585&sdata=riiqXWeyfD%2FwR1
>uM2lMqH%2BAkvOMk%2B5%2B0nASrlRvNLN4%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7C6a1ec2e043e349c3bd3c08d514b7cd3f%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636437702013883585&sdata=riiqXWeyfD%2FwR1u
>M2lMqH%2BAkvOMk%2B5%2B0nASrlRvNLN4%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7C6a1ec2e043e349c3bd3c08d514b7cd3f%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636437702013883585&sdata=fx0ooji2xZbinH
>F%2FCdY85V1DTc9mApiNiRDVRCbWrrs%3D&reserved=0>
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: Flex2Royale
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex,
I think the piece that is still missing is "themeing". We created some
subset based on external frameworks (MDL, CreateJS,...), but I always said
this was only as an exercise and to fill a gap we have with our custom UI
set. For me all efforts should go in the Express set direction to have one
set and many "themes". external UI sets will always work differently and
have their own controls (that will not match ours in many cases) and for
this reason themeing is not standarizable.
In the other hand Flex Skins was something very powerful, and I think we
should not lose that in Royale, so Royale could end declaring skins in a
similar way as Flex did, but implementing in a better way that provides
better performance. the generated code in HTML/JS could be far way simple
that in Flex that need a complete UIComponent that means a huge object to
deal with it at runtime.
I'd love to work in the visuals of themeing for Express when finish royale
website if some theme infrastructure is setup. IMHO, for this to be done,
we will need at least be two contributors, maybe Peter or you and me with
the visuals. I could work in two visuals to put the themeing feature on the
plate, one could be wireframe theme and another something more elaborated.
2017-10-16 18:04 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> IIRC, Om was working on this to some degree. One plan was to convert FXG
> to SVG.
>
> AIUI, a SkinnableContainer wouldn't be that hard. Container already has
> an inner div to hold the children, so a different view could have the
> outer div display SVG behind the children. I think there were more
> questions about SkinnableComponent because not every component is already
> implemented to support a skin by default, and SVG as a backgroundImage for
> some HTMLElements don't work well in all browsers.
>
> Flex Skinning was pretty expensive because it added a UIComponent child to
> every component. Because we are PAYG, we don't want to force that on
> everyone, and as the MDL work showed, CSS Themes may be just as good at
> creating nice visual experiences and more standard/common. But as Yishay
> said, in theory, a new set of views could add that extra DIV behind each
> component if that's what it takes to implement SVG "skins". And we also
> know from MDL and Flat that we can also just re-factor components into
> enough pieces that they can have a different look.
>
> Of course, I could be wrong...
> -Alex
>
> On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
> >We need to have a "skinning story" - something about alternate views, CSS,
> >that sort of thing. Adding to my list.
> >‹peter
> >
> >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
> >
> >>I like it.
> >>
> >>
> >>> There is no direct equivalent of SkinnableContainer in Royale (at this
> >>> time). A reasonable alternative is the Container.
> >>
> >>Maybe we could mention that Royale components typically have views which
> >>can
> >>be used to control appearance without changing behavior. To me, spark
> >>skins
> >>sort of played the same role.
> >>
> >>
> >>
> >>--
> >>Sent from:
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-ro
> >>y
> >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
> 7C1f660ab8e3b74b1c
> >>a
> >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636437321952
> >>4
> >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&reserved=0
> >
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: Flex2Royale
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Maybe I'm scaring everyone by saying "new component set", but IMO, you all
are saying the same thing without realizing it. Each Component adds
certain things to the DOM. A simple Basic component only adds one
HTMLElement to the DOM and that HTMLElement has limited styling support.
We will need a different View that injects a more complex tree of
HTMLElements into the DOM. Flat and MDL proved we can do such a thing,
but we don't need to do what MDL or Flat did. We can do whatever we want,
and call that a "new component set".
This "new component set" will be a collection of components like Panel,
and probably not Card. It will probably be implemented by establishing a
different set of default views for Basic components, or maybe it will need
its own base class. We won't know until we see what kinds of things we
need to support in Carlos's step #2. I don't think we can get too far on
#3 until we know what is involved in #2.
But if we don't create a new component set with those different default
views, then skinning may not appear first-class. The Basic ASDoc won't
mention skinning as it is in the views. Nor will the code-hinting. So
having a new component set gives us a place to hang ASDoc and code hinting
and the user doesn't have to do as much configuring: they just use the
new component set.
Of course, I could be wrong...
-Alex
On 10/16/17, 12:53 PM, "carlos.rovira@gmail.com on behalf of Carlos
Rovira" <carlos.rovira@gmail.com on behalf of
carlos.rovira@codeoscopic.com> wrote:
>@Alex, it would be great to create a theme feature that does not depends
>on
>Basic or Express but I think some rules would be needed in the end and a
>theme should "style" a concrete set of components (TextInput, CheckBox,
>Button, Panel,... and so on). The problem with external sets is that while
>MDL has a "Card", CreateJS doesn't have one...the controls that intersect
>are of course Button, TextInput, CheckBox.... but Panel is something Flex
>related, and you'll find nothing in MDL or CreateJS, for that reason, I
>think a theme feature should be something only for Royale UI sets, since
>we
>can do nothing more for the rest since we don't have control con MDL
>implementation.
>
>What is clear for me is that something like theme customization is
>something that we need for 1.0 since people need some grade of style in
>their applications build with Royale
>
>@Piotr, that's very good, I think we'll need to join forces to get this
>one, I'm ok with Alex approach, I think there's many starting points:
>
>1.- Look for the best implementation path (SVG? Bitmap? ...)
>2.- Create some designs that puts the rules to code (here we could use
>Illustrator, but If I'll some design for this I think I'll use Sketch App
>since is a tool very handy for UX/UI work. Here's where I think we could
>build a list of possible controls (Button, TextInput, Panel...) and create
>at least two starter designs (Wireframe and a complex one), that starter
>designs will be the basis of other Royale themes that people could make
>themselves.
>3.- Design the Arquitecture of themes considering PAYG, Strand/Beads, and
>how to make it pluggable while maintain a low weight.
>....
>
>So If I go with point 2, others could pick 1 or 3 (or other points if
>finaly we need more things to consider)
>
>@Om, I think it could be great to make some new thread and talk about we
>we
>thing we need for 1.0. I have a clear idea of what is needed at least
>IMHO,
>but I'm sure others will has their own vision and maybe It would be great
>to have some discussion about it
>
>
>
>
>
>2017-10-16 20:54 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
>
>> I too have more time for Royale going forward. At this point, I am not
>> sure what exactly needs to be done.
>> I want to start on a Charting library integration. I was hoping that
>>the
>> VS Code issue can be solved before I start. If anyone can take a look
>>at
>> that, it would be great.
>>
>> Thanks,
>> Om
>>
>> On Mon, Oct 16, 2017 at 11:51 AM, Piotr Zarzycki <
>> piotrzarzycki21@gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > I have lately more time for Royale, so I would be happy to help. It
>>will
>> be
>> > awesome if someone could share some resources website, articles etc.
>> which
>> > can help in some play with CSS3 and SVG.
>> >
>> > Alex,
>> >
>> > Do you saying that we should rather have another module which provides
>> > theme and that module in your thoughts should utilize Basic or
>>Express ?
>> >
>> > Cause for me it would be a bit too much build new set of components,
>>we
>> > already have such and I believe that we should stick to that. Work on
>>new
>> > theme as new module allow also reveal bugs and improve that
>>components.
>> > Justin raise several issues in our repo to only one component - How
>>many
>> of
>> > them are so much broken as DateChooser ?
>> >
>> > Carlos,
>> >
>> > I would be happy to get touch with you once you finish website and set
>> some
>> > plan. I agree with Alex that we should first build something in pure
>> HTML.
>> >
>> > Thanks,
>> > Piotr
>> >
>> >
>> >
>> > 2017-10-16 19:52 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
>> >
>> > > The biggest problem with FXG is that there are no editors that
>>support
>> > it.
>> > >
>> > > I kept using Illustrator CS5 for creating all my assets. While I
>>don't
>> > > have a problem with that or a need to upgrade to the latest
>>version, it
>> > > will be hard to ask users to use that version for their
>>FlexJS/Royale
>> > > skinning needs. Adobe makes it very hard for people to find and
>> download
>> > > those versions as well.
>> > >
>> > > Going forward, CSS3 and SVG would be a very good alternative for us.
>> It
>> > is
>> > > widely supported and easy for our users to incorporate in their
>> workflow.
>> > >
>> > > Thanks,
>> > > Om
>> > >
>> > > On Oct 16, 2017 9:05 AM, "Alex Harui" <ah...@adobe.com.invalid>
>> wrote:
>> > >
>> > > > IIRC, Om was working on this to some degree. One plan was to
>>convert
>> > FXG
>> > > > to SVG.
>> > > >
>> > > > AIUI, a SkinnableContainer wouldn't be that hard. Container
>>already
>> > has
>> > > > an inner div to hold the children, so a different view could have
>>the
>> > > > outer div display SVG behind the children. I think there were
>>more
>> > > > questions about SkinnableComponent because not every component is
>> > already
>> > > > implemented to support a skin by default, and SVG as a
>> backgroundImage
>> > > for
>> > > > some HTMLElements don't work well in all browsers.
>> > > >
>> > > > Flex Skinning was pretty expensive because it added a UIComponent
>> child
>> > > to
>> > > > every component. Because we are PAYG, we don't want to force
>>that on
>> > > > everyone, and as the MDL work showed, CSS Themes may be just as
>>good
>> at
>> > > > creating nice visual experiences and more standard/common. But as
>> > Yishay
>> > > > said, in theory, a new set of views could add that extra DIV
>>behind
>> > each
>> > > > component if that's what it takes to implement SVG "skins". And
>>we
>> > also
>> > > > know from MDL and Flat that we can also just re-factor components
>> into
>> > > > enough pieces that they can have a different look.
>> > > >
>> > > > Of course, I could be wrong...
>> > > > -Alex
>> > > >
>> > > > On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>> > > >
>> > > > >We need to have a "skinning story" - something about alternate
>> views,
>> > > CSS,
>> > > > >that sort of thing. Adding to my list.
>> > > > >‹peter
>> > > > >
>> > > > >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
>> > > > >
>> > > > >>I like it.
>> > > > >>
>> > > > >>
>> > > > >>> There is no direct equivalent of SkinnableContainer in Royale
>>(at
>> > > this
>> > > > >>> time). A reasonable alternative is the Container.
>> > > > >>
>> > > > >>Maybe we could mention that Royale components typically have
>>views
>> > > which
>> > > > >>can
>> > > > >>be used to control appearance without changing behavior. To me,
>> spark
>> > > > >>skins
>> > > > >>sort of played the same role.
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >>--
>> > > > >>Sent from:
>> > > > >>https://na01.safelinks.protection.outlook.com/?url=
>> > > > http%3A%2F%2Fapache-ro
>> > > > >>y
>> > > > >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
>> > > > 7C1f660ab8e3b74b1c
>> > > > >>a
>> > > > >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
>> > > > cee1%7C0%7C0%7C636437321952
>> > > > >>4
>> > > > >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&
>> > > reserved=0
>> > > > >
>> > > >
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > mobile: +48 880 859 557
>> > skype: zarzycki10
>> >
>> > LinkedIn:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linke
>>din.com%2Fpiotrzarzycki&data=02%7C01%7C%7Ca1f08c0c98234c6737b308d514cf99c
>>1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636437804230257724&sdata=V
>>zZBLWTLJ01c%2Bl9Ap8p4GqdI%2FcUnRPL9pq7GVT202VM%3D&reserved=0
>> >
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpl.link
>>edin.com%2Fin%2Fpiotr-zarzycki-92a53552&data=02%7C01%7C%7Ca1f08c0c98234c6
>>737b308d514cf99c1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364378042
>>30257724&sdata=q3Il3jzqiI3YsNLUdYV%2FmZ%2F0ZN7QNee4i6Twl%2B8g1eo%3D&reser
>>ved=0>
>> >
>> > GitHub:
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fpiotrzarzycki21&data=02%7C01%7C%7Ca1f08c0c98234c6737b308d514cf99c1%7
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636437804230257724&sdata=ltDp
>>wSz0tudeKPxXUUc20RmoNBh967tPM1FrX9ZGcso%3D&reserved=0
>> >
>>
>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Ca1f08c0c98234c6737b308d514cf99c1%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636437804230257724&sdata=Arlxbj7ZUzwePntR
>DGCwDA6EjMZzoJMnm8fuzl9xP7U%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7Ca1f08c0c98234c6737b308d514cf99c1%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636437804230257724&sdata=Arlxbj7ZUzwePntRD
>GCwDA6EjMZzoJMnm8fuzl9xP7U%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Ca1f08c0c98234c6737b308d514cf99c1%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636437804230257724&sdata=baaH0nONGzX2t%
>2FpzI0dXIxbUhU1pLF4kxZiizJP2svU%3D&reserved=0>
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: Flex2Royale
Posted by Carlos Rovira <ca...@codeoscopic.com>.
@Alex, it would be great to create a theme feature that does not depends on
Basic or Express but I think some rules would be needed in the end and a
theme should "style" a concrete set of components (TextInput, CheckBox,
Button, Panel,... and so on). The problem with external sets is that while
MDL has a "Card", CreateJS doesn't have one...the controls that intersect
are of course Button, TextInput, CheckBox.... but Panel is something Flex
related, and you'll find nothing in MDL or CreateJS, for that reason, I
think a theme feature should be something only for Royale UI sets, since we
can do nothing more for the rest since we don't have control con MDL
implementation.
What is clear for me is that something like theme customization is
something that we need for 1.0 since people need some grade of style in
their applications build with Royale
@Piotr, that's very good, I think we'll need to join forces to get this
one, I'm ok with Alex approach, I think there's many starting points:
1.- Look for the best implementation path (SVG? Bitmap? ...)
2.- Create some designs that puts the rules to code (here we could use
Illustrator, but If I'll some design for this I think I'll use Sketch App
since is a tool very handy for UX/UI work. Here's where I think we could
build a list of possible controls (Button, TextInput, Panel...) and create
at least two starter designs (Wireframe and a complex one), that starter
designs will be the basis of other Royale themes that people could make
themselves.
3.- Design the Arquitecture of themes considering PAYG, Strand/Beads, and
how to make it pluggable while maintain a low weight.
....
So If I go with point 2, others could pick 1 or 3 (or other points if
finaly we need more things to consider)
@Om, I think it could be great to make some new thread and talk about we we
thing we need for 1.0. I have a clear idea of what is needed at least IMHO,
but I'm sure others will has their own vision and maybe It would be great
to have some discussion about it
2017-10-16 20:54 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
> I too have more time for Royale going forward. At this point, I am not
> sure what exactly needs to be done.
> I want to start on a Charting library integration. I was hoping that the
> VS Code issue can be solved before I start. If anyone can take a look at
> that, it would be great.
>
> Thanks,
> Om
>
> On Mon, Oct 16, 2017 at 11:51 AM, Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have lately more time for Royale, so I would be happy to help. It will
> be
> > awesome if someone could share some resources website, articles etc.
> which
> > can help in some play with CSS3 and SVG.
> >
> > Alex,
> >
> > Do you saying that we should rather have another module which provides
> > theme and that module in your thoughts should utilize Basic or Express ?
> >
> > Cause for me it would be a bit too much build new set of components, we
> > already have such and I believe that we should stick to that. Work on new
> > theme as new module allow also reveal bugs and improve that components.
> > Justin raise several issues in our repo to only one component - How many
> of
> > them are so much broken as DateChooser ?
> >
> > Carlos,
> >
> > I would be happy to get touch with you once you finish website and set
> some
> > plan. I agree with Alex that we should first build something in pure
> HTML.
> >
> > Thanks,
> > Piotr
> >
> >
> >
> > 2017-10-16 19:52 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
> >
> > > The biggest problem with FXG is that there are no editors that support
> > it.
> > >
> > > I kept using Illustrator CS5 for creating all my assets. While I don't
> > > have a problem with that or a need to upgrade to the latest version, it
> > > will be hard to ask users to use that version for their FlexJS/Royale
> > > skinning needs. Adobe makes it very hard for people to find and
> download
> > > those versions as well.
> > >
> > > Going forward, CSS3 and SVG would be a very good alternative for us.
> It
> > is
> > > widely supported and easy for our users to incorporate in their
> workflow.
> > >
> > > Thanks,
> > > Om
> > >
> > > On Oct 16, 2017 9:05 AM, "Alex Harui" <ah...@adobe.com.invalid>
> wrote:
> > >
> > > > IIRC, Om was working on this to some degree. One plan was to convert
> > FXG
> > > > to SVG.
> > > >
> > > > AIUI, a SkinnableContainer wouldn't be that hard. Container already
> > has
> > > > an inner div to hold the children, so a different view could have the
> > > > outer div display SVG behind the children. I think there were more
> > > > questions about SkinnableComponent because not every component is
> > already
> > > > implemented to support a skin by default, and SVG as a
> backgroundImage
> > > for
> > > > some HTMLElements don't work well in all browsers.
> > > >
> > > > Flex Skinning was pretty expensive because it added a UIComponent
> child
> > > to
> > > > every component. Because we are PAYG, we don't want to force that on
> > > > everyone, and as the MDL work showed, CSS Themes may be just as good
> at
> > > > creating nice visual experiences and more standard/common. But as
> > Yishay
> > > > said, in theory, a new set of views could add that extra DIV behind
> > each
> > > > component if that's what it takes to implement SVG "skins". And we
> > also
> > > > know from MDL and Flat that we can also just re-factor components
> into
> > > > enough pieces that they can have a different look.
> > > >
> > > > Of course, I could be wrong...
> > > > -Alex
> > > >
> > > > On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
> > > >
> > > > >We need to have a "skinning story" - something about alternate
> views,
> > > CSS,
> > > > >that sort of thing. Adding to my list.
> > > > >‹peter
> > > > >
> > > > >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
> > > > >
> > > > >>I like it.
> > > > >>
> > > > >>
> > > > >>> There is no direct equivalent of SkinnableContainer in Royale (at
> > > this
> > > > >>> time). A reasonable alternative is the Container.
> > > > >>
> > > > >>Maybe we could mention that Royale components typically have views
> > > which
> > > > >>can
> > > > >>be used to control appearance without changing behavior. To me,
> spark
> > > > >>skins
> > > > >>sort of played the same role.
> > > > >>
> > > > >>
> > > > >>
> > > > >>--
> > > > >>Sent from:
> > > > >>https://na01.safelinks.protection.outlook.com/?url=
> > > > http%3A%2F%2Fapache-ro
> > > > >>y
> > > > >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
> > > > 7C1f660ab8e3b74b1c
> > > > >>a
> > > > >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
> > > > cee1%7C0%7C0%7C636437321952
> > > > >>4
> > > > >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&
> > > reserved=0
> > > > >
> > > >
> > > >
> > >
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > mobile: +48 880 859 557
> > skype: zarzycki10
> >
> > LinkedIn: http://www.linkedin.com/piotrzarzycki
> > <https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
> >
> > GitHub: https://github.com/piotrzarzycki21
> >
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: Flex2Royale
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I too have more time for Royale going forward. At this point, I am not
sure what exactly needs to be done.
I want to start on a Charting library integration. I was hoping that the
VS Code issue can be solved before I start. If anyone can take a look at
that, it would be great.
Thanks,
Om
On Mon, Oct 16, 2017 at 11:51 AM, Piotr Zarzycki <pi...@gmail.com>
wrote:
> Hi,
>
> I have lately more time for Royale, so I would be happy to help. It will be
> awesome if someone could share some resources website, articles etc. which
> can help in some play with CSS3 and SVG.
>
> Alex,
>
> Do you saying that we should rather have another module which provides
> theme and that module in your thoughts should utilize Basic or Express ?
>
> Cause for me it would be a bit too much build new set of components, we
> already have such and I believe that we should stick to that. Work on new
> theme as new module allow also reveal bugs and improve that components.
> Justin raise several issues in our repo to only one component - How many of
> them are so much broken as DateChooser ?
>
> Carlos,
>
> I would be happy to get touch with you once you finish website and set some
> plan. I agree with Alex that we should first build something in pure HTML.
>
> Thanks,
> Piotr
>
>
>
> 2017-10-16 19:52 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
>
> > The biggest problem with FXG is that there are no editors that support
> it.
> >
> > I kept using Illustrator CS5 for creating all my assets. While I don't
> > have a problem with that or a need to upgrade to the latest version, it
> > will be hard to ask users to use that version for their FlexJS/Royale
> > skinning needs. Adobe makes it very hard for people to find and download
> > those versions as well.
> >
> > Going forward, CSS3 and SVG would be a very good alternative for us. It
> is
> > widely supported and easy for our users to incorporate in their workflow.
> >
> > Thanks,
> > Om
> >
> > On Oct 16, 2017 9:05 AM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
> >
> > > IIRC, Om was working on this to some degree. One plan was to convert
> FXG
> > > to SVG.
> > >
> > > AIUI, a SkinnableContainer wouldn't be that hard. Container already
> has
> > > an inner div to hold the children, so a different view could have the
> > > outer div display SVG behind the children. I think there were more
> > > questions about SkinnableComponent because not every component is
> already
> > > implemented to support a skin by default, and SVG as a backgroundImage
> > for
> > > some HTMLElements don't work well in all browsers.
> > >
> > > Flex Skinning was pretty expensive because it added a UIComponent child
> > to
> > > every component. Because we are PAYG, we don't want to force that on
> > > everyone, and as the MDL work showed, CSS Themes may be just as good at
> > > creating nice visual experiences and more standard/common. But as
> Yishay
> > > said, in theory, a new set of views could add that extra DIV behind
> each
> > > component if that's what it takes to implement SVG "skins". And we
> also
> > > know from MDL and Flat that we can also just re-factor components into
> > > enough pieces that they can have a different look.
> > >
> > > Of course, I could be wrong...
> > > -Alex
> > >
> > > On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
> > >
> > > >We need to have a "skinning story" - something about alternate views,
> > CSS,
> > > >that sort of thing. Adding to my list.
> > > >‹peter
> > > >
> > > >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
> > > >
> > > >>I like it.
> > > >>
> > > >>
> > > >>> There is no direct equivalent of SkinnableContainer in Royale (at
> > this
> > > >>> time). A reasonable alternative is the Container.
> > > >>
> > > >>Maybe we could mention that Royale components typically have views
> > which
> > > >>can
> > > >>be used to control appearance without changing behavior. To me, spark
> > > >>skins
> > > >>sort of played the same role.
> > > >>
> > > >>
> > > >>
> > > >>--
> > > >>Sent from:
> > > >>https://na01.safelinks.protection.outlook.com/?url=
> > > http%3A%2F%2Fapache-ro
> > > >>y
> > > >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
> > > 7C1f660ab8e3b74b1c
> > > >>a
> > > >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
> > > cee1%7C0%7C0%7C636437321952
> > > >>4
> > > >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&
> > reserved=0
> > > >
> > >
> > >
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
>
> GitHub: https://github.com/piotrzarzycki21
>
Re: Flex2Royale
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi,
I have lately more time for Royale, so I would be happy to help. It will be
awesome if someone could share some resources website, articles etc. which
can help in some play with CSS3 and SVG.
Alex,
Do you saying that we should rather have another module which provides
theme and that module in your thoughts should utilize Basic or Express ?
Cause for me it would be a bit too much build new set of components, we
already have such and I believe that we should stick to that. Work on new
theme as new module allow also reveal bugs and improve that components.
Justin raise several issues in our repo to only one component - How many of
them are so much broken as DateChooser ?
Carlos,
I would be happy to get touch with you once you finish website and set some
plan. I agree with Alex that we should first build something in pure HTML.
Thanks,
Piotr
2017-10-16 19:52 GMT+02:00 OmPrakash Muppirala <bi...@gmail.com>:
> The biggest problem with FXG is that there are no editors that support it.
>
> I kept using Illustrator CS5 for creating all my assets. While I don't
> have a problem with that or a need to upgrade to the latest version, it
> will be hard to ask users to use that version for their FlexJS/Royale
> skinning needs. Adobe makes it very hard for people to find and download
> those versions as well.
>
> Going forward, CSS3 and SVG would be a very good alternative for us. It is
> widely supported and easy for our users to incorporate in their workflow.
>
> Thanks,
> Om
>
> On Oct 16, 2017 9:05 AM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
>
> > IIRC, Om was working on this to some degree. One plan was to convert FXG
> > to SVG.
> >
> > AIUI, a SkinnableContainer wouldn't be that hard. Container already has
> > an inner div to hold the children, so a different view could have the
> > outer div display SVG behind the children. I think there were more
> > questions about SkinnableComponent because not every component is already
> > implemented to support a skin by default, and SVG as a backgroundImage
> for
> > some HTMLElements don't work well in all browsers.
> >
> > Flex Skinning was pretty expensive because it added a UIComponent child
> to
> > every component. Because we are PAYG, we don't want to force that on
> > everyone, and as the MDL work showed, CSS Themes may be just as good at
> > creating nice visual experiences and more standard/common. But as Yishay
> > said, in theory, a new set of views could add that extra DIV behind each
> > component if that's what it takes to implement SVG "skins". And we also
> > know from MDL and Flat that we can also just re-factor components into
> > enough pieces that they can have a different look.
> >
> > Of course, I could be wrong...
> > -Alex
> >
> > On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
> >
> > >We need to have a "skinning story" - something about alternate views,
> CSS,
> > >that sort of thing. Adding to my list.
> > >‹peter
> > >
> > >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
> > >
> > >>I like it.
> > >>
> > >>
> > >>> There is no direct equivalent of SkinnableContainer in Royale (at
> this
> > >>> time). A reasonable alternative is the Container.
> > >>
> > >>Maybe we could mention that Royale components typically have views
> which
> > >>can
> > >>be used to control appearance without changing behavior. To me, spark
> > >>skins
> > >>sort of played the same role.
> > >>
> > >>
> > >>
> > >>--
> > >>Sent from:
> > >>https://na01.safelinks.protection.outlook.com/?url=
> > http%3A%2F%2Fapache-ro
> > >>y
> > >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
> > 7C1f660ab8e3b74b1c
> > >>a
> > >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
> > cee1%7C0%7C0%7C636437321952
> > >>4
> > >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&
> reserved=0
> > >
> >
> >
>
--
Piotr Zarzycki
mobile: +48 880 859 557
skype: zarzycki10
LinkedIn: http://www.linkedin.com/piotrzarzycki
<https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
GitHub: https://github.com/piotrzarzycki21
Re: Flex2Royale
Posted by OmPrakash Muppirala <bi...@gmail.com>.
The biggest problem with FXG is that there are no editors that support it.
I kept using Illustrator CS5 for creating all my assets. While I don't
have a problem with that or a need to upgrade to the latest version, it
will be hard to ask users to use that version for their FlexJS/Royale
skinning needs. Adobe makes it very hard for people to find and download
those versions as well.
Going forward, CSS3 and SVG would be a very good alternative for us. It is
widely supported and easy for our users to incorporate in their workflow.
Thanks,
Om
On Oct 16, 2017 9:05 AM, "Alex Harui" <ah...@adobe.com.invalid> wrote:
> IIRC, Om was working on this to some degree. One plan was to convert FXG
> to SVG.
>
> AIUI, a SkinnableContainer wouldn't be that hard. Container already has
> an inner div to hold the children, so a different view could have the
> outer div display SVG behind the children. I think there were more
> questions about SkinnableComponent because not every component is already
> implemented to support a skin by default, and SVG as a backgroundImage for
> some HTMLElements don't work well in all browsers.
>
> Flex Skinning was pretty expensive because it added a UIComponent child to
> every component. Because we are PAYG, we don't want to force that on
> everyone, and as the MDL work showed, CSS Themes may be just as good at
> creating nice visual experiences and more standard/common. But as Yishay
> said, in theory, a new set of views could add that extra DIV behind each
> component if that's what it takes to implement SVG "skins". And we also
> know from MDL and Flat that we can also just re-factor components into
> enough pieces that they can have a different look.
>
> Of course, I could be wrong...
> -Alex
>
> On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
> >We need to have a "skinning story" - something about alternate views, CSS,
> >that sort of thing. Adding to my list.
> >‹peter
> >
> >On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
> >
> >>I like it.
> >>
> >>
> >>> There is no direct equivalent of SkinnableContainer in Royale (at this
> >>> time). A reasonable alternative is the Container.
> >>
> >>Maybe we could mention that Royale components typically have views which
> >>can
> >>be used to control appearance without changing behavior. To me, spark
> >>skins
> >>sort of played the same role.
> >>
> >>
> >>
> >>--
> >>Sent from:
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-ro
> >>y
> >>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%
> 7C1f660ab8e3b74b1c
> >>a
> >>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636437321952
> >>4
> >>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&reserved=0
> >
>
>
Re: Flex2Royale
Posted by Alex Harui <ah...@adobe.com.INVALID>.
IIRC, Om was working on this to some degree. One plan was to convert FXG
to SVG.
AIUI, a SkinnableContainer wouldn't be that hard. Container already has
an inner div to hold the children, so a different view could have the
outer div display SVG behind the children. I think there were more
questions about SkinnableComponent because not every component is already
implemented to support a skin by default, and SVG as a backgroundImage for
some HTMLElements don't work well in all browsers.
Flex Skinning was pretty expensive because it added a UIComponent child to
every component. Because we are PAYG, we don't want to force that on
everyone, and as the MDL work showed, CSS Themes may be just as good at
creating nice visual experiences and more standard/common. But as Yishay
said, in theory, a new set of views could add that extra DIV behind each
component if that's what it takes to implement SVG "skins". And we also
know from MDL and Flat that we can also just re-factor components into
enough pieces that they can have a different look.
Of course, I could be wrong...
-Alex
On 10/16/17, 6:50 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>We need to have a "skinning story" - something about alternate views, CSS,
>that sort of thing. Adding to my list.
>‹peter
>
>On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
>
>>I like it.
>>
>>
>>> There is no direct equivalent of SkinnableContainer in Royale (at this
>>> time). A reasonable alternative is the Container.
>>
>>Maybe we could mention that Royale components typically have views which
>>can
>>be used to control appearance without changing behavior. To me, spark
>>skins
>>sort of played the same role.
>>
>>
>>
>>--
>>Sent from:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro
>>y
>>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%7C1f660ab8e3b74b1c
>>a
>>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636437321952
>>4
>>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&reserved=0
>
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com.INVALID>.
We need to have a "skinning story" - something about alternate views, CSS,
that sort of thing. Adding to my list.
‹peter
On 10/16/17, 2:29 AM, "yishayw" <yi...@hotmail.com> wrote:
>I like it.
>
>
>> There is no direct equivalent of SkinnableContainer in Royale (at this
>> time). A reasonable alternative is the Container.
>
>Maybe we could mention that Royale components typically have views which
>can
>be used to control appearance without changing behavior. To me, spark
>skins
>sort of played the same role.
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-roy
>ale-development.20373.n8.nabble.com%2F&data=02%7C01%7C%7C1f660ab8e3b74b1ca
>0b108d5145f4fd8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364373219524
>70504&sdata=ueXDGjTEy4hq0kzF9w1P3utRy%2B805PEm54F7P9ZceZ8%3D&reserved=0
Re: Flex2Royale
Posted by yishayw <yi...@hotmail.com>.
I like it.
> There is no direct equivalent of SkinnableContainer in Royale (at this
> time). A reasonable alternative is the Container.
Maybe we could mention that Royale components typically have views which can
be used to control appearance without changing behavior. To me, spark skins
sort of played the same role.
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com.INVALID>.
Thanks,
At least putting the comments into the source will allow anyone to change
or add to them over time. With this (eventually) being a buildable
example, when someone downloads the Royale kits they can run this example
and get some guidance. I will supply, somewhere/somehow, a preamble and
mission statement.
—peter
On 10/12/17, 2:57 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>Hi Peter,
>
>In my opinion, this is going in the right direction.
>
>I suggest that the Flex class could link directly to the SDK reference
>and that the "corresponding" Royale component could link directly to the
>Royale SDK reference.
>
>It is very helpful to have the short comment in the Royale Express column
>(column 2) explaining which is the underlying (basic) components and the
>convenience beads. Furthermore, it helps in understanding the distinction
>between strands and beads.
>
>The "notes" column is also very helpful.
>
>Great work !
>
>Nicolas Granon
>
>
>
>> -----Message d'origine-----
>> De : Peter Ent [mailto:pent@adobe.com.INVALID]
>> Envoyé : mercredi 11 octobre 2017 22:55
>> À : dev@royale.apache.org; users@royale.apache.org
>> Objet : Re: Flex2Royale
>>
>> I have a new version of the Flex to Royale comparison table. You can
>> find it here:
>>
>>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache
>>.org%2F~pent%2FFlex2RoyaleApp%2F&data=02%7C01%7C%7C0e2287948e1647ef613208
>>d5113e9983%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63643388292031369
>>8&sdata=r216C6cxxhLoxyXdeKRcqSCQ%2B9ZBgkuoQ9TeEbSxL%2FI%3D&reserved=0
>>
>> This table is built from the JSON output from the compiler has it scans
>> the ASDoc tags. I've included some new tags to document the comparison.
>> I still have some work to, including modifying the compiler to generate
>> a driver file (right now it uses a driver file I created). I had to
>> modify the html/P component and I added an html/PRE component. I'm
>> waiting for the rename to be finished before committing my changes
>> (plus I'll probably have a couple more).
>>
>> Let me know if you think this table would be helpful to people
>> migrating from Flex and what else you would like to see in it (besides
>> more components).
>>
>> —peter
>>
>> On 10/10/17, 10:47 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>>
>> >Its finally uploaded. You can find this new table here:
>> >
>> >https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apa
>> che.
>> >org%2F~pent%2FFlex2RoyaleApp&data=02%7C01%7C%7C483f4807c1584cabbfb508d
>> 5
>> >0fe
>> >dd374%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&
>> s
>> >dat
>> >a=zOAszJYRSMzxMaJSdC%2FAHiA66uINDUP7Uq8Y7Sz03Mc%3D&reserved=0
>> >
>> >I need to do some work on a couple Royale components to get this to
>> >look better, but that's the idea. I took the raw JSON and added a
>> "commentary"
>> >element to a couple in Express. Again, this is driven from a config
>> >file to limit the number of JSON files it needs to open.
>> >
>> >Compare with previous version at:
>> >
>> >https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apa
>> che.
>> >org%2F~pent%2FFlex2Royale&data=02%7C01%7C%7C483f4807c1584cabbfb508d50f
>> e
>> >dd3
>> >74%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sda
>> t
>> >a=D
>> >reDdizkpvEEYca4WgzRYY0DCjxbhhawlwWP2FxM59s%3D&reserved=0
>> >
>> >—peter
>> >
>> >On 10/10/17, 9:46 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>> >
>> >>I figured put -r would not work. So this morning I've been trying to
>> >>upload it. I didn't bother yesterday because I figured this would
>> happen.
>> >>The put -r keeps timing out. For some reason a single file is fine,
>> >>but a mass of files keeps failing. Probably my internet connection. I
>> >>will keep doing it piecemeal throughout the day; that should work.
>> >>
>> >>‹peter
>> >>
>> >>On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>> >>
>> >>>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to
>> >>>make the destination folder on the server before using put.
>> >>>
>> >>>HTH,
>> >>>-Alex
>> >>>
>> >>>[1]
>> >>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsta
>> c
>> >>>kov
>> >>>e
>> >>>r
>> >>>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-
>> fol&data
>> >>>=02
>> >>>%
>> >>>7
>> >>>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c1
>> 7
>> >>>8de
>> >>>c
>> >>>e
>> >>>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLu
>> W
>> >>>Puz
>> >>>W
>> >>>i
>> >>>1QIV4S1m%2B5c%3D&reserved=0
>> >>>der-that-contains-other-folders-using-sftp-on-li
>> >>>
>> >>>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>> >>>
>> >>>>I've built a little app that produces a table that looks through
>> the
>> >>>>ASDoc JSON files. This app is driven by a config file that contains
>> >>>>a map from Flex components to Royale Express components. For each
>> >>>>Royale component listed in the config file, the corresponding ASDoc
>> >>>>JSON file is loaded and if it has a new ASDoc tag, @commentary, it
>> >>>>shows that in the last column.
>> >>>>
>> >>>>I would like to show this to you, but I cannot figure out how to
>> >>>>post the site (about 6 MB, its js-debug) to my home.apache.org
>> >>>>account. I can transfer the file there as a .tar but it looks like
>> >>>>ssh is prevented on home.apache.org at this point.
>> >>>>
>> >>>>Using ASDoc + a driver file is one way to do this. Another way is
>> to
>> >>>>just scan all of the ASDoc JSON files looking for some clues about
>> >>>>which classes could be compared to Flex components. I would say
>> this
>> >>>>would mean adding some more ASDoc tags (e.g., @flexcomponent,
>> >>>>@flexdocurl) and it may take longer to scan through all the JSON
>> >>>>files and build the table.
>> >>>>
>> >>>>I need to sync up with changes to the repos and then I'll publish
>> my
>> >>>>example in the royale-as/examples directory so you can build it for
>> >>>>yourselves and take a look.
>> >>>>
>> >>>>‹peter
>> >>>
>> >>
>> >
>
>
RE: Flex2Royale
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Hi Peter,
In my opinion, this is going in the right direction.
I suggest that the Flex class could link directly to the SDK reference and that the "corresponding" Royale component could link directly to the Royale SDK reference.
It is very helpful to have the short comment in the Royale Express column (column 2) explaining which is the underlying (basic) components and the convenience beads. Furthermore, it helps in understanding the distinction between strands and beads.
The "notes" column is also very helpful.
Great work !
Nicolas Granon
> -----Message d'origine-----
> De : Peter Ent [mailto:pent@adobe.com.INVALID]
> Envoyé : mercredi 11 octobre 2017 22:55
> À : dev@royale.apache.org; users@royale.apache.org
> Objet : Re: Flex2Royale
>
> I have a new version of the Flex to Royale comparison table. You can
> find it here:
> http://home.apache.org/~pent/Flex2RoyaleApp/
>
> This table is built from the JSON output from the compiler has it scans
> the ASDoc tags. I've included some new tags to document the comparison.
> I still have some work to, including modifying the compiler to generate
> a driver file (right now it uses a driver file I created). I had to
> modify the html/P component and I added an html/PRE component. I'm
> waiting for the rename to be finished before committing my changes
> (plus I'll probably have a couple more).
>
> Let me know if you think this table would be helpful to people
> migrating from Flex and what else you would like to see in it (besides
> more components).
>
> —peter
>
> On 10/10/17, 10:47 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
> >Its finally uploaded. You can find this new table here:
> >
> >https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apa
> che.
> >org%2F~pent%2FFlex2RoyaleApp&data=02%7C01%7C%7C483f4807c1584cabbfb508d
> 5
> >0fe
> >dd374%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&
> s
> >dat
> >a=zOAszJYRSMzxMaJSdC%2FAHiA66uINDUP7Uq8Y7Sz03Mc%3D&reserved=0
> >
> >I need to do some work on a couple Royale components to get this to
> >look better, but that's the idea. I took the raw JSON and added a
> "commentary"
> >element to a couple in Express. Again, this is driven from a config
> >file to limit the number of JSON files it needs to open.
> >
> >Compare with previous version at:
> >
> >https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apa
> che.
> >org%2F~pent%2FFlex2Royale&data=02%7C01%7C%7C483f4807c1584cabbfb508d50f
> e
> >dd3
> >74%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sda
> t
> >a=D
> >reDdizkpvEEYca4WgzRYY0DCjxbhhawlwWP2FxM59s%3D&reserved=0
> >
> >—peter
> >
> >On 10/10/17, 9:46 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
> >
> >>I figured put -r would not work. So this morning I've been trying to
> >>upload it. I didn't bother yesterday because I figured this would
> happen.
> >>The put -r keeps timing out. For some reason a single file is fine,
> >>but a mass of files keeps failing. Probably my internet connection. I
> >>will keep doing it piecemeal throughout the day; that should work.
> >>
> >>‹peter
> >>
> >>On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >>
> >>>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to
> >>>make the destination folder on the server before using put.
> >>>
> >>>HTH,
> >>>-Alex
> >>>
> >>>[1]
> >>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsta
> c
> >>>kov
> >>>e
> >>>r
> >>>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-
> fol&data
> >>>=02
> >>>%
> >>>7
> >>>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c1
> 7
> >>>8de
> >>>c
> >>>e
> >>>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLu
> W
> >>>Puz
> >>>W
> >>>i
> >>>1QIV4S1m%2B5c%3D&reserved=0
> >>>der-that-contains-other-folders-using-sftp-on-li
> >>>
> >>>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
> >>>
> >>>>I've built a little app that produces a table that looks through
> the
> >>>>ASDoc JSON files. This app is driven by a config file that contains
> >>>>a map from Flex components to Royale Express components. For each
> >>>>Royale component listed in the config file, the corresponding ASDoc
> >>>>JSON file is loaded and if it has a new ASDoc tag, @commentary, it
> >>>>shows that in the last column.
> >>>>
> >>>>I would like to show this to you, but I cannot figure out how to
> >>>>post the site (about 6 MB, its js-debug) to my home.apache.org
> >>>>account. I can transfer the file there as a .tar but it looks like
> >>>>ssh is prevented on home.apache.org at this point.
> >>>>
> >>>>Using ASDoc + a driver file is one way to do this. Another way is
> to
> >>>>just scan all of the ASDoc JSON files looking for some clues about
> >>>>which classes could be compared to Flex components. I would say
> this
> >>>>would mean adding some more ASDoc tags (e.g., @flexcomponent,
> >>>>@flexdocurl) and it may take longer to scan through all the JSON
> >>>>files and build the table.
> >>>>
> >>>>I need to sync up with changes to the repos and then I'll publish
> my
> >>>>example in the royale-as/examples directory so you can build it for
> >>>>yourselves and take a look.
> >>>>
> >>>>‹peter
> >>>
> >>
> >
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com.INVALID>.
I have a new version of the Flex to Royale comparison table. You can find
it here:
http://home.apache.org/~pent/Flex2RoyaleApp/
This table is built from the JSON output from the compiler has it scans
the ASDoc tags. I've included some new tags to document the comparison. I
still have some work to, including modifying the compiler to generate a
driver file (right now it uses a driver file I created). I had to modify
the html/P component and I added an html/PRE component. I'm waiting for
the rename to be finished before committing my changes (plus I'll probably
have a couple more).
Let me know if you think this table would be helpful to people migrating
from Flex and what else you would like to see in it (besides more
components).
—peter
On 10/10/17, 10:47 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>Its finally uploaded. You can find this new table here:
>
>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.
>org%2F~pent%2FFlex2RoyaleApp&data=02%7C01%7C%7C483f4807c1584cabbfb508d50fe
>dd374%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sdat
>a=zOAszJYRSMzxMaJSdC%2FAHiA66uINDUP7Uq8Y7Sz03Mc%3D&reserved=0
>
>I need to do some work on a couple Royale components to get this to look
>better, but that's the idea. I took the raw JSON and added a "commentary"
>element to a couple in Express. Again, this is driven from a config file
>to limit the number of JSON files it needs to open.
>
>Compare with previous version at:
>
>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.
>org%2F~pent%2FFlex2Royale&data=02%7C01%7C%7C483f4807c1584cabbfb508d50fedd3
>74%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sdata=D
>reDdizkpvEEYca4WgzRYY0DCjxbhhawlwWP2FxM59s%3D&reserved=0
>
>—peter
>
>On 10/10/17, 9:46 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
>>I figured put -r would not work. So this morning I've been trying to
>>upload it. I didn't bother yesterday because I figured this would happen.
>>The put -r keeps timing out. For some reason a single file is fine, but a
>>mass of files keeps failing. Probably my internet connection. I will keep
>>doing it piecemeal throughout the day; that should work.
>>
>>‹peter
>>
>>On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>>
>>>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to
>>>make
>>>the destination folder on the server before using put.
>>>
>>>HTH,
>>>-Alex
>>>
>>>[1]
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov
>>>e
>>>r
>>>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-fol&data=02
>>>%
>>>7
>>>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c178de
>>>c
>>>e
>>>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLuWPuz
>>>W
>>>i
>>>1QIV4S1m%2B5c%3D&reserved=0
>>>der-that-contains-other-folders-using-sftp-on-li
>>>
>>>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>>>
>>>>I've built a little app that produces a table that looks through the
>>>>ASDoc JSON files. This app is driven by a config file that contains a
>>>>map
>>>>from Flex components to Royale Express components. For each Royale
>>>>component listed in the config file, the corresponding ASDoc JSON file
>>>>is
>>>>loaded and if it has a new ASDoc tag, @commentary, it shows that in the
>>>>last column.
>>>>
>>>>I would like to show this to you, but I cannot figure out how to post
>>>>the
>>>>site (about 6 MB, its js-debug) to my home.apache.org account. I can
>>>>transfer the file there as a .tar but it looks like ssh is prevented on
>>>>home.apache.org at this point.
>>>>
>>>>Using ASDoc + a driver file is one way to do this. Another way is to
>>>>just
>>>>scan all of the ASDoc JSON files looking for some clues about which
>>>>classes could be compared to Flex components. I would say this would
>>>>mean
>>>>adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it
>>>>may take longer to scan through all the JSON files and build the table.
>>>>
>>>>I need to sync up with changes to the repos and then I'll publish my
>>>>example in the royale-as/examples directory so you can build it for
>>>>yourselves and take a look.
>>>>
>>>>‹peter
>>>
>>
>
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com>.
I have a new version of the Flex to Royale comparison table. You can find
it here:
http://home.apache.org/~pent/Flex2RoyaleApp/
This table is built from the JSON output from the compiler has it scans
the ASDoc tags. I've included some new tags to document the comparison. I
still have some work to, including modifying the compiler to generate a
driver file (right now it uses a driver file I created). I had to modify
the html/P component and I added an html/PRE component. I'm waiting for
the rename to be finished before committing my changes (plus I'll probably
have a couple more).
Let me know if you think this table would be helpful to people migrating
from Flex and what else you would like to see in it (besides more
components).
—peter
On 10/10/17, 10:47 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>Its finally uploaded. You can find this new table here:
>
>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.
>org%2F~pent%2FFlex2RoyaleApp&data=02%7C01%7C%7C483f4807c1584cabbfb508d50fe
>dd374%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sdat
>a=zOAszJYRSMzxMaJSdC%2FAHiA66uINDUP7Uq8Y7Sz03Mc%3D&reserved=0
>
>I need to do some work on a couple Royale components to get this to look
>better, but that's the idea. I took the raw JSON and added a "commentary"
>element to a couple in Express. Again, this is driven from a config file
>to limit the number of JSON files it needs to open.
>
>Compare with previous version at:
>
>https://na01.safelinks.protection.outlook.com/?url=http:%2F%2Fhome.apache.
>org%2F~pent%2FFlex2Royale&data=02%7C01%7C%7C483f4807c1584cabbfb508d50fedd3
>74%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636432436504771677&sdata=D
>reDdizkpvEEYca4WgzRYY0DCjxbhhawlwWP2FxM59s%3D&reserved=0
>
>—peter
>
>On 10/10/17, 9:46 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
>>I figured put -r would not work. So this morning I've been trying to
>>upload it. I didn't bother yesterday because I figured this would happen.
>>The put -r keeps timing out. For some reason a single file is fine, but a
>>mass of files keeps failing. Probably my internet connection. I will keep
>>doing it piecemeal throughout the day; that should work.
>>
>>‹peter
>>
>>On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>>
>>>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to
>>>make
>>>the destination folder on the server before using put.
>>>
>>>HTH,
>>>-Alex
>>>
>>>[1]
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackov
>>>e
>>>r
>>>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-fol&data=02
>>>%
>>>7
>>>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c178de
>>>c
>>>e
>>>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLuWPuz
>>>W
>>>i
>>>1QIV4S1m%2B5c%3D&reserved=0
>>>der-that-contains-other-folders-using-sftp-on-li
>>>
>>>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>>>
>>>>I've built a little app that produces a table that looks through the
>>>>ASDoc JSON files. This app is driven by a config file that contains a
>>>>map
>>>>from Flex components to Royale Express components. For each Royale
>>>>component listed in the config file, the corresponding ASDoc JSON file
>>>>is
>>>>loaded and if it has a new ASDoc tag, @commentary, it shows that in the
>>>>last column.
>>>>
>>>>I would like to show this to you, but I cannot figure out how to post
>>>>the
>>>>site (about 6 MB, its js-debug) to my home.apache.org account. I can
>>>>transfer the file there as a .tar but it looks like ssh is prevented on
>>>>home.apache.org at this point.
>>>>
>>>>Using ASDoc + a driver file is one way to do this. Another way is to
>>>>just
>>>>scan all of the ASDoc JSON files looking for some clues about which
>>>>classes could be compared to Flex components. I would say this would
>>>>mean
>>>>adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it
>>>>may take longer to scan through all the JSON files and build the table.
>>>>
>>>>I need to sync up with changes to the repos and then I'll publish my
>>>>example in the royale-as/examples directory so you can build it for
>>>>yourselves and take a look.
>>>>
>>>>‹peter
>>>
>>
>
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com.INVALID>.
Its finally uploaded. You can find this new table here:
http://home.apache.org/~pent/Flex2RoyaleApp
I need to do some work on a couple Royale components to get this to look
better, but that's the idea. I took the raw JSON and added a "commentary"
element to a couple in Express. Again, this is driven from a config file
to limit the number of JSON files it needs to open.
Compare with previous version at:
http://home.apache.org/~pent/Flex2Royale
—peter
On 10/10/17, 9:46 AM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>I figured put -r would not work. So this morning I've been trying to
>upload it. I didn't bother yesterday because I figured this would happen.
>The put -r keeps timing out. For some reason a single file is fine, but a
>mass of files keeps failing. Probably my internet connection. I will keep
>doing it piecemeal throughout the day; that should work.
>
>‹peter
>
>On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
>>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to make
>>the destination folder on the server before using put.
>>
>>HTH,
>>-Alex
>>
>>[1]
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackove
>>r
>>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-fol&data=02%
>>7
>>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c178dec
>>e
>>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLuWPuzW
>>i
>>1QIV4S1m%2B5c%3D&reserved=0
>>der-that-contains-other-folders-using-sftp-on-li
>>
>>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>>
>>>I've built a little app that produces a table that looks through the
>>>ASDoc JSON files. This app is driven by a config file that contains a
>>>map
>>>from Flex components to Royale Express components. For each Royale
>>>component listed in the config file, the corresponding ASDoc JSON file
>>>is
>>>loaded and if it has a new ASDoc tag, @commentary, it shows that in the
>>>last column.
>>>
>>>I would like to show this to you, but I cannot figure out how to post
>>>the
>>>site (about 6 MB, its js-debug) to my home.apache.org account. I can
>>>transfer the file there as a .tar but it looks like ssh is prevented on
>>>home.apache.org at this point.
>>>
>>>Using ASDoc + a driver file is one way to do this. Another way is to
>>>just
>>>scan all of the ASDoc JSON files looking for some clues about which
>>>classes could be compared to Flex components. I would say this would
>>>mean
>>>adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it
>>>may take longer to scan through all the JSON files and build the table.
>>>
>>>I need to sync up with changes to the repos and then I'll publish my
>>>example in the royale-as/examples directory so you can build it for
>>>yourselves and take a look.
>>>
>>>‹peter
>>
>
Re: Flex2Royale
Posted by Peter Ent <pe...@adobe.com.INVALID>.
I figured put -r would not work. So this morning I've been trying to
upload it. I didn't bother yesterday because I figured this would happen.
The put -r keeps timing out. For some reason a single file is fine, but a
mass of files keeps failing. Probably my internet connection. I will keep
doing it piecemeal throughout the day; that should work.
‹peter
On 10/10/17, 12:28 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>Doesn't "put -r" work? See [1]. I think the key is to use mkdir to make
>the destination folder on the server before using put.
>
>HTH,
>-Alex
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackover
>flow.com%2Fquestions%2F10084941%2Fhow-can-i-upload-an-entire-fol&data=02%7
>C01%7C%7Ce14c075efb57450f7bde08d50f9770f3%7Cfa7b1b5a7b34438794aed2c178dece
>e1%7C0%7C0%7C636432065483689350&sdata=VKFE3jSG5bSlfwo%2Bcg7%2FgiZoLuWPuzWi
>1QIV4S1m%2B5c%3D&reserved=0
>der-that-contains-other-folders-using-sftp-on-li
>
>On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>
>>I've built a little app that produces a table that looks through the
>>ASDoc JSON files. This app is driven by a config file that contains a map
>>from Flex components to Royale Express components. For each Royale
>>component listed in the config file, the corresponding ASDoc JSON file is
>>loaded and if it has a new ASDoc tag, @commentary, it shows that in the
>>last column.
>>
>>I would like to show this to you, but I cannot figure out how to post the
>>site (about 6 MB, its js-debug) to my home.apache.org account. I can
>>transfer the file there as a .tar but it looks like ssh is prevented on
>>home.apache.org at this point.
>>
>>Using ASDoc + a driver file is one way to do this. Another way is to just
>>scan all of the ASDoc JSON files looking for some clues about which
>>classes could be compared to Flex components. I would say this would mean
>>adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it
>>may take longer to scan through all the JSON files and build the table.
>>
>>I need to sync up with changes to the repos and then I'll publish my
>>example in the royale-as/examples directory so you can build it for
>>yourselves and take a look.
>>
>>‹peter
>
Re: Flex2Royale
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Doesn't "put -r" work? See [1]. I think the key is to use mkdir to make
the destination folder on the server before using put.
HTH,
-Alex
[1]
https://stackoverflow.com/questions/10084941/how-can-i-upload-an-entire-fol
der-that-contains-other-folders-using-sftp-on-li
On 10/9/17, 1:55 PM, "Peter Ent" <pe...@adobe.com.INVALID> wrote:
>I've built a little app that produces a table that looks through the
>ASDoc JSON files. This app is driven by a config file that contains a map
>from Flex components to Royale Express components. For each Royale
>component listed in the config file, the corresponding ASDoc JSON file is
>loaded and if it has a new ASDoc tag, @commentary, it shows that in the
>last column.
>
>I would like to show this to you, but I cannot figure out how to post the
>site (about 6 MB, its js-debug) to my home.apache.org account. I can
>transfer the file there as a .tar but it looks like ssh is prevented on
>home.apache.org at this point.
>
>Using ASDoc + a driver file is one way to do this. Another way is to just
>scan all of the ASDoc JSON files looking for some clues about which
>classes could be compared to Flex components. I would say this would mean
>adding some more ASDoc tags (e.g., @flexcomponent, @flexdocurl) and it
>may take longer to scan through all the JSON files and build the table.
>
>I need to sync up with changes to the repos and then I'll publish my
>example in the royale-as/examples directory so you can build it for
>yourselves and take a look.
>
>—peter