Re: [FlexJS] Translation from framework to JS

[Carlos Rovira]

Ok, I'll be experimenting and seeing where things goes, and by the time I
get something useful we could see what MDL things are implied and how
licenses should be applied.

Thanks Justin and Om for taking the time to see this, in the end is equally
important as to get the tech done.

Carlos



2016-10-15 3:37 GMT+02:00 Justin Mclean :

> Hi,
>
> > The wording in the license is very clear.  Which part of the highlighted
> > text do you have concerns with?
>
> I have no major concerns with the text, I do have concerns with CC
> licensed code in a release and just pointing that out. If a release
> contains no CC code and we’re 100% sure of that then all is good.
>
> I raised a github issue asking for clarification, after looking at a
> couple of licensing issues they have had before I believe their intent was
> to license the documentation under CC, not all .css and .html files, so the
> license text may actually be a little misleading.
>
> > You can double check with Legal if you want, but this is definitely not a
> > blocker issue for Carlos experimenting with MDL-FlexJS integration.
>
> Is certainly isn’t, Carlos is free to experiment away, but the issues
> should be resolved before the next release is made.
>
> Thanks,
> Justin




-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es


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: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

> The wording in the license is very clear.  Which part of the highlighted
> text do you have concerns with?

I have no major concerns with the text, I do have concerns with CC licensed 
code in a release and just pointing that out. If a release contains no CC code 
and we’re 100% sure of that then all is good.

I raised a github issue asking for clarification, after looking at a couple of 
licensing issues they have had before I believe their intent was to license the 
documentation under CC, not all .css and .html files, so the license text may 
actually be a little misleading.

> You can double check with Legal if you want, but this is definitely not a
> blocker issue for Carlos experimenting with MDL-FlexJS integration.

Is certainly isn’t, Carlos is free to experiment away, but the issues should be 
resolved before the next release is made.

Thanks,
Justin

Re: [FlexJS] Translation from framework to JS

[OmPrakash Muppirala]

The wording in the license is very clear.  Which part of the highlighted
text do you have concerns with?

You can double check with Legal if you want, but this is definitely not a
blocker issue for Carlos experimenting with MDL-FlexJS integration.

Thanks,
Om

On Oct 14, 2016 4:40 PM, "Justin Mclean"  wrote:

> Hi,
>
> > Justin, please see my earlier response.  We dont need to worry about the
> > license if we are using scss to generate the css.
>
> I would prefer that that be confirmed, this is not a minor issue like a
> header being missing. If we accidentally include CC source in our release
> it alters the terms of the Apache license, see point 2 in [1]. Legal JIRAs
> here [2] is the most relevant (but there are several others). This thread
> is where it was discussed [3] in particular [4][5].
>
> We do still need to worry about the missing NOTICE and the missing MIT
> license (if we include that file) as that has nothing to do with using
> css/scss files.
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/resolved.html#criteria
> 2. https://issues.apache.org/jira/browse/LEGAL-167
> 3. http://mail-archives.apache.org/mod_mbox/www-legal-
> discuss/201507.mbox/%3cCAPqz87pYe5c7-7cUpKQ5uZTbmFhYPosJ9PWL78qU+
> zt-lap...@mail.gmail.com%3e
> 4. http://mail-archives.apache.org/mod_mbox/www-legal-
> discuss/201507.mbox/%3cCAFG6u8EJEYUswGw6o8RZazVaRFO
> zzwvmgG3R1ZT_eYjQ7=l...@mail.gmail.com%3e
> 5. http://mail-archives.apache.org/mod_mbox/www-legal-
> discuss/201507.mbox/%3cf7a0b868-df13-432e-9b50-8c11eeff8...@jagunet.com%3e

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

Also this [1] from JimJag.

Thanks,
Justin

1. 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201507.mbox/%3c9b052e9f-e7a1-4b00-a5bf-86333bc47...@jagunet.com%3e

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

> Justin, please see my earlier response.  We dont need to worry about the
> license if we are using scss to generate the css.

I would prefer that that be confirmed, this is not a minor issue like a header 
being missing. If we accidentally include CC source in our release it alters 
the terms of the Apache license, see point 2 in [1]. Legal JIRAs here [2] is 
the most relevant (but there are several others). This thread is where it was 
discussed [3] in particular [4][5].

We do still need to worry about the missing NOTICE and the missing MIT license 
(if we include that file) as that has nothing to do with using css/scss files.

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#criteria
2. https://issues.apache.org/jira/browse/LEGAL-167
3. 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201507.mbox/%3ccapqz87pye5c7-7cupkq5uztbmfhyposj9pwl78qu+zt-lap...@mail.gmail.com%3e
4. 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201507.mbox/%3cCAFG6u8EJEYUswGw6o8RZazVaRFOzzwvmgG3R1ZT_eYjQ7=l...@mail.gmail.com%3e
5. 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201507.mbox/%3cf7a0b868-df13-432e-9b50-8c11eeff8...@jagunet.com%3e

Re: [FlexJS] Translation from framework to JS

[OmPrakash Muppirala]

Justin, please see my earlier response.  We dont need to worry about the
license if we are using scss to generate the css.

Thanks,
Om

On Fri, Oct 14, 2016 at 3:33 PM, Justin Mclean 
wrote:

> Hi,
>
> The MIT license text in question can be found here [1]
>
> Thanks,
> Justin
>
> 1. https://github.com/darius/requestAnimationFrame/blob/master/LICENSE
>

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

The MIT license text in question can be found here [1]

Thanks,
Justin

1. https://github.com/darius/requestAnimationFrame/blob/master/LICENSE

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

Depend on how MDL is going to be used there's a couple of minor issues that 
need addressing:
 - repo is missing a NOTICE file
 - this file is MIT licensed [1] and the repo is missing the MIT license text 
(as a header or in the LICENSE).

Can someone please raise a PR for NOTICE file as per recent discussion on legal 
discuss. For the missing MIT license it will only need to be addressed if we 
bundle that file.

The repo also contains a number of stock images that it would be doubtful that 
we would have permission to distribute, but I assuming that we wouldn’t be 
bundling those so it's not an issue.

Thanks,
Justin

1.   
https://github.com/google/material-design-lite/blob/mdl-1.x/src/third_party/rAF.js

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

> I think I don't need to include MDL libraríes, I think just a link to them
> should be ok, so the library "uses" it directly from the source link.

Probably not, as you can only depend on something if it’s licensed Category A 
or Category B in binary form even if it not in the release bundle. It may be OK 
see the bit “For small amounts of source.. ” [1] for that it would be best to 
ask on legal discuss.

IMO it would be best to contact them and get it clarified / ask to have it 
relicensed as the first step.

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#category-b

Re: [FlexJS] Translation from framework to JS

[Carlos Rovira]

Thanks Justin,

I think I don't need to include MDL libraríes, I think just a link to them
should be ok, so the library "uses" it directly from the source link. That
would be ok right?

Thanks


2016-10-14 9:40 GMT+02:00 Justin Mclean :

> Hi,
>
> > I'm in the process of trying to see how integrate a CSS library (like
> MDL).
>
> If (and I don’t know if this is your intention) you want to bundle MDL
> into FlexJS it may not be possible as the css and html files within are
> licensed under CC-A [1]. CC-A is "category B” license [2] which means it
> can’t be included in source form or modified.
>
> Thanks,
> Justin
>
> 1.https://github.com/google/material-design-lite/blob/mdl-1.x/LICENSE (at
> the very bottom)
> 2. https://www.apache.org/legal/resolved.html#category-b




-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es


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: [FlexJS] Translation from framework to JS

[Harbs]

Good point.

That’s probably the best plan.

AIUI, the HTML files there are basically just illustrating how to use the 
framework, so they don’t seem needed either.

On Oct 14, 2016, at 11:13 AM, OmPrakash Muppirala  wrote:

> Here is the relevant part from the license:
> ===
> 
> All code in any directories or sub-directories that end with *.html or
>   *.css is licensed under the Creative Commons Attribution International
>   4.0 License, which full text can be found here:
>   https://creativecommons.org/licenses/by/4.0/legalcode.
> 
> As an exception to this license, all html or css that is generated by
>   the software at the direction of the user is copyright the user. The
>   user has full ownership and control over such content, including
> whether and how they wish to license it.
> 
> ===
> 
> We can simply use the .scss files to generate the .css files we need.  We
> should be good in that case.
> 
> Thanks,
> Om
> 
> On Fri, Oct 14, 2016 at 1:09 AM, Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>>> Something is odd there.
>>> 
>>> Every css file I could find in that repo had an Apache header in it.
>>> 
>>> I wonder if someone forgot to update the license file at some point.
>> 
>> Or perhaps they use a tool that added a header (incorrectly) to all files?
>> 
>> It would be best to contact them and ask for clarification. Is anyone
>> willing to do that?
>> 
>> Thanks,
>> Justin

Re: [FlexJS] Translation from framework to JS

[OmPrakash Muppirala]

Here is the relevant part from the license:
===

All code in any directories or sub-directories that end with *.html or
   *.css is licensed under the Creative Commons Attribution International
   4.0 License, which full text can be found here:
   https://creativecommons.org/licenses/by/4.0/legalcode.

As an exception to this license, all html or css that is generated by
   the software at the direction of the user is copyright the user. The
   user has full ownership and control over such content, including
 whether and how they wish to license it.

===

We can simply use the .scss files to generate the .css files we need.  We
should be good in that case.

Thanks,
Om

On Fri, Oct 14, 2016 at 1:09 AM, Justin Mclean 
wrote:

> Hi,
>
> > Something is odd there.
> >
> > Every css file I could find in that repo had an Apache header in it.
> >
> > I wonder if someone forgot to update the license file at some point.
>
> Or perhaps they use a tool that added a header (incorrectly) to all files?
>
> It would be best to contact them and ask for clarification. Is anyone
> willing to do that?
>
> Thanks,
> Justin

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

> Something is odd there.
> 
> Every css file I could find in that repo had an Apache header in it.
> 
> I wonder if someone forgot to update the license file at some point.

Or perhaps they use a tool that added a header (incorrectly) to all files?

It would be best to contact them and ask for clarification. Is anyone willing 
to do that?

Thanks,
Justin

Re: [FlexJS] Translation from framework to JS

[Harbs]

Something is odd there.

Every css file I could find in that repo had an Apache header in it.

I wonder if someone forgot to update the license file at some point.

On Oct 14, 2016, at 10:40 AM, Justin Mclean  wrote:

> Hi,
> 
>> I'm in the process of trying to see how integrate a CSS library (like MDL).
> 
> If (and I don’t know if this is your intention) you want to bundle MDL into 
> FlexJS it may not be possible as the css and html files within are licensed 
> under CC-A [1]. CC-A is "category B” license [2] which means it can’t be 
> included in source form or modified.
> 
> Thanks,
> Justin
> 
> 1.https://github.com/google/material-design-lite/blob/mdl-1.x/LICENSE (at the 
> very bottom)
> 2. https://www.apache.org/legal/resolved.html#category-b

Re: [FlexJS] Translation from framework to JS

[Justin Mclean]

Hi,

> I'm in the process of trying to see how integrate a CSS library (like MDL).

If (and I don’t know if this is your intention) you want to bundle MDL into 
FlexJS it may not be possible as the css and html files within are licensed 
under CC-A [1]. CC-A is "category B” license [2] which means it can’t be 
included in source form or modified.

Thanks,
Justin

1.https://github.com/google/material-design-lite/blob/mdl-1.x/LICENSE (at the 
very bottom)
2. https://www.apache.org/legal/resolved.html#category-b

Re: [FlexJS] Translation from framework to JS

[Alex Harui]

On 10/11/16, 4:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Thanks Alex,
>
>thanks for the explanation, just to understand what's behind I
>remember
>that initially the way some components translates to JS was using a js
>file
>as a templete (so some code was transpired and some other not). AFAIR this
>was removed and now all is converted to JS, and now is inside of code. For
>example in js:Container line 89: element = document.createElement('div')
>as
>WrappedHTMLElement;

That's correct.  We don't write any JavaScript any more!  All of our .js
is transpiled from AS.  And it has been a huge savings by doing so.  There
are conditional compile flags for JS and SWF-specific code paths in most
lower-level components.

>And js:Container is not in "Core" and is in "HTML" since is dependent of
>the what you want to output, (as it's a version in CreateJS and others).
>Is this right?

org.apache.flex.html.Container maps to js:Container and wraps a DIV on the
JS side.  CreateJS is not involved at all in the basic components.  The
basic component set tries to use thinly-wrapped HTMLElements.  There is a
separate CreateJS.swc that has its own component set that leverages
CreateJS.

HTH,
-Alex

Re: [FlexJS] Translation from framework to JS

[Harbs]

Container is basically a div. Hence it’s in the HTML package.

There’s an svg GraphicContainer in the Graphics package which uses an svg 
namespace and I expect there to eventually be a canvas one as well.

Harbs

On Oct 11, 2016, at 2:52 PM, Carlos Rovira  
wrote:

> And js:Container is not in "Core" and is in "HTML" since is dependent of
> the what you want to output, (as it's a version in CreateJS and others).
> Is this right?

Re: [FlexJS] Translation from framework to JS

[OK]

Carlos Rovira wrote
> regarding Flat.swc you mentioned, I was not aware of it. I check the
> library, but don't know if there's some project using it as an example. Is
> there some of it?

Source:
https://github.com/apache/flex-asjs/tree/develop/frameworks/projects/Flat

Example:
https://github.com/apache/flex-asjs/tree/develop/examples/flexjs/DataBindingExample_Flat

HTH,
Olaf




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Translation-from-framework-to-JS-tp55687p55696.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Translation from framework to JS

[Carlos Rovira]

Thanks Alex,

thanks for the explanation, just to understand what's behind I remember
that initially the way some components translates to JS was using a js file
as a templete (so some code was transpired and some other not). AFAIR this
was removed and now all is converted to JS, and now is inside of code. For
example in js:Container line 89: element = document.createElement('div') as
WrappedHTMLElement;
And js:Container is not in "Core" and is in "HTML" since is dependent of
the what you want to output, (as it's a version in CreateJS and others).
Is this right?

regarding Flat.swc you mentioned, I was not aware of it. I check the
library, but don't know if there's some project using it as an example. Is
there some of it?

Thanks

Carlos


2016-10-11 8:01 GMT+02:00 Alex Harui :

>
>
> On 10/10/16, 2:43 PM, "Alex Harui"  wrote:
>
> >
> >IMO, there are at least two valid approaches.  I honestly don't favor one
> >over the other.
>
> I thought of a third, that may or may not work for MDL depending on how
> much, if at all, MDL requires configuration via CSS.  There will someday
> be a skinnable component set for FlexJS.  It won't be as lightweight as
> the basic set, but that is PAYG.  Then, MDL is implemented more or less
> like other Flex themes.  Vectors and code (and maybe some CSS) describe
> the visuals.  AIUI, FXG would be used on the SWF side and converted to SVG
> on the JS side.
>
> -Alex
>
> >
> >1) Custom Component Set.  This is sort of what we tried in Flat.swc.  We
> >created subclasses of existing components and customized some CSS (based
> >on the FlatUI css files) to get the look and feel we wanted.  In doing so,
> >for now at least, we "dumbed-down" the CSS to what FlexJS is currently
> >capable of (simple class and id selectors).  There are no advanced
> >selectors.  Anything requiring advanced selectors was skipped, or was
> >re-engineered via subclassing and the extensible type selector model I
> >mentioned above.  The important takeaway is that by doing "more work", you
> >can probably create any look and feel you want today in FlexJS
> >2) CSS as Theme.  At some point in time, I think we want to allow someone
> >to build out their UI in MXML, set className and id properties, and then
> >drop in an existing third-party CSS file and it would "just work" just
> >like if you switched the css file out on an equivalent .html file.  Or
> >maybe you'd have to thinly-wrap the third-party code, I don't know.  The
> >JS side is probably mostly ready to do this, but it would require a lot of
> >work on the SWF side to handle a CSS lookup that is essentially
> >standards-compliant.  The SWF side code would have to handle all advanced
> >CSS selectors and directives since in my brief tour of Flat and BootStrap,
> >they leverage a lot of fancy CSS.
> >
> >In sum, if you've got time, we could probably fashion a set of components
> >that look like they follow MDL.  But the dream is that we would thinly
> >wrap an existing 3rd-party library and it would "just work".  That is
> >currently more work today, but someday, that might be the preferred path.
>
>


-- 

Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es


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: [FlexJS] Translation from framework to JS

[Alex Harui]

On 10/10/16, 2:43 PM, "Alex Harui"  wrote:

>
>IMO, there are at least two valid approaches.  I honestly don't favor one
>over the other.

I thought of a third, that may or may not work for MDL depending on how
much, if at all, MDL requires configuration via CSS.  There will someday
be a skinnable component set for FlexJS.  It won't be as lightweight as
the basic set, but that is PAYG.  Then, MDL is implemented more or less
like other Flex themes.  Vectors and code (and maybe some CSS) describe
the visuals.  AIUI, FXG would be used on the SWF side and converted to SVG
on the JS side.

-Alex

>
>1) Custom Component Set.  This is sort of what we tried in Flat.swc.  We
>created subclasses of existing components and customized some CSS (based
>on the FlatUI css files) to get the look and feel we wanted.  In doing so,
>for now at least, we "dumbed-down" the CSS to what FlexJS is currently
>capable of (simple class and id selectors).  There are no advanced
>selectors.  Anything requiring advanced selectors was skipped, or was
>re-engineered via subclassing and the extensible type selector model I
>mentioned above.  The important takeaway is that by doing "more work", you
>can probably create any look and feel you want today in FlexJS
>2) CSS as Theme.  At some point in time, I think we want to allow someone
>to build out their UI in MXML, set className and id properties, and then
>drop in an existing third-party CSS file and it would "just work" just
>like if you switched the css file out on an equivalent .html file.  Or
>maybe you'd have to thinly-wrap the third-party code, I don't know.  The
>JS side is probably mostly ready to do this, but it would require a lot of
>work on the SWF side to handle a CSS lookup that is essentially
>standards-compliant.  The SWF side code would have to handle all advanced
>CSS selectors and directives since in my brief tour of Flat and BootStrap,
>they leverage a lot of fancy CSS.
>
>In sum, if you've got time, we could probably fashion a set of components
>that look like they follow MDL.  But the dream is that we would thinly
>wrap an existing 3rd-party library and it would "just work".  That is
>currently more work today, but someday, that might be the preferred path.

Re: [FlexJS] Translation from framework to JS

[Alex Harui]

On 10/10/16, 12:05 PM, "carlos.rov...@gmail.com on behalf of Carlos
Rovira" 
wrote:

>Hi,
>
>I'm in the process of trying to see how integrate a CSS library (like
>MDL).
>In order to get it, I need to know more about the process of converting a
>FlexJS component to JS.
>For example, a js:Container, should translate to a  or something like
>that, is that right?
>(I see js:ContainerBase but not js:Container, where's that class?)
>or a js:Button is finaly a button tag?

js:Container is org.apache.flex.html.Container, in the HTML.swc and wraps
a 
js:Button is a 

>
>If is that...I see using className work to assign some MDL css classes
>Do you know if there's more points of integration that I should know in
>order to get a successful integration.

The way it works now is that the JS version of any component should be
able to have its className and id property set, which will set the same
properties on the HTMLElement, which should, in theory, allow lots of CSS
to "just work".  The SWF version is supposed to emulate what CSS will do.
It works ok, but I'm sure it needs fine tuning.

In addition, because Flex allowed for custom type selectors, which AFAICT,
CSS does not allow, you can specify in the FlexJS CSS non-standard type
selectors like TextInput, Container, DataGrid, etc.  On the SWF side,
these get factored into the CSS lookup much like it did in regular Flex.
On the JS side, we want each component to specify a "typeName" property
which is appended to the className via framework code.  The FlexJS
compiler "translates" TextInput to .TextInput thus making the lookup work
the same.  This allows an extensible type selector model to specify
default styles for various components without collisions from the class
selector "className" property.

>
>As I get more knowledge on this, I think w could discuss, if we could get
>a
>MDL library to expose MDL look'n feel directly on FlexJS
>Or I you think there's a better approach.

IMO, there are at least two valid approaches.  I honestly don't favor one
over the other.

1) Custom Component Set.  This is sort of what we tried in Flat.swc.  We
created subclasses of existing components and customized some CSS (based
on the FlatUI css files) to get the look and feel we wanted.  In doing so,
for now at least, we "dumbed-down" the CSS to what FlexJS is currently
capable of (simple class and id selectors).  There are no advanced
selectors.  Anything requiring advanced selectors was skipped, or was
re-engineered via subclassing and the extensible type selector model I
mentioned above.  The important takeaway is that by doing "more work", you
can probably create any look and feel you want today in FlexJS
2) CSS as Theme.  At some point in time, I think we want to allow someone
to build out their UI in MXML, set className and id properties, and then
drop in an existing third-party CSS file and it would "just work" just
like if you switched the css file out on an equivalent .html file.  Or
maybe you'd have to thinly-wrap the third-party code, I don't know.  The
JS side is probably mostly ready to do this, but it would require a lot of
work on the SWF side to handle a CSS lookup that is essentially
standards-compliant.  The SWF side code would have to handle all advanced
CSS selectors and directives since in my brief tour of Flat and BootStrap,
they leverage a lot of fancy CSS.

In sum, if you've got time, we could probably fashion a set of components
that look like they follow MDL.  But the dream is that we would thinly
wrap an existing 3rd-party library and it would "just work".  That is
currently more work today, but someday, that might be the preferred path.

>
>I think this is one of the main things we need, to start spreading the
>word
>of FlexJS in a more engaging way, since visuals is what people first look
>to choose us
>(then comes the technology behind, but if and amazing technology doesn't
>look at first glance attractiveis difficult to bring people on board)

For sure, better look and feel of our examples would certainly help.
Peter is polishing up a new "Mobile Stocks" demo and it would be nice to
have help making it really look good.  I can even imagine trying to
publish it to the app stores.  More on that when Peter declares he is done
with the first phase, hopefully in a few days.

-Alex

Re: [FlexJS] Translation from framework to JS

[OmPrakash Muppirala]

I have this on my to do list as well.  Will jump in as soon as I get some
time.

Thanks,
Om

On Oct 10, 2016 1:08 PM, "OK"  wrote:

> Carlos Rovira-3 wrote
> > As I get more knowledge on this, I think w could discuss, if we could get
> > a
> > MDL library to expose MDL look'n feel directly on FlexJS
> > Or I you think there's a better approach.
> > I think this is one of the main things we need, to start spreading the
> > word
> > of FlexJS in a more engaging way, since visuals is what people first look
> > to choose us
> > (then comes the technology behind, but if and amazing technology doesn't
> > look at first glance attractiveis difficult to bring people on board)
>
> Hi Carlos,
> I'm also still pretty sure that the need of a modern look and feel is
> crucial for FlexJS.
> I saw that Peter already done a great job with introducing the flat
> component set.
> I'm hopefully getting more and more familar with FlexJS while porting a
> little PureMVC demo to FlexJS.
> As soon as I'm finished this first FlexJS journey I'm willing to help with
> completing existing component sets and adding a MDL component set.
> But I'm also pretty sure that I'll have to take some more hurdles to get
> familar with asjs...
>
> Olaf
>
>
>
>
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-Translation-from-
> framework-to-JS-tp55687p55689.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS] Translation from framework to JS

[OK]

Carlos Rovira-3 wrote
> As I get more knowledge on this, I think w could discuss, if we could get
> a
> MDL library to expose MDL look'n feel directly on FlexJS
> Or I you think there's a better approach.
> I think this is one of the main things we need, to start spreading the
> word
> of FlexJS in a more engaging way, since visuals is what people first look
> to choose us
> (then comes the technology behind, but if and amazing technology doesn't
> look at first glance attractiveis difficult to bring people on board)

Hi Carlos,
I'm also still pretty sure that the need of a modern look and feel is
crucial for FlexJS.
I saw that Peter already done a great job with introducing the flat
component set.
I'm hopefully getting more and more familar with FlexJS while porting a
little PureMVC demo to FlexJS.
As soon as I'm finished this first FlexJS journey I'm willing to help with
completing existing component sets and adding a MDL component set.
But I'm also pretty sure that I'll have to take some more hurdles to get
familar with asjs...

Olaf




--
View this message in context: 
http://apache-flex-development.247.n4.nabble.com/FlexJS-Translation-from-framework-to-JS-tp55687p55689.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.