Re: [FlexJS] Working on a MDL branch

[Alex Harui]

If you want to make an example in flex-asjs repo in examples/flexjs that
would be helpful.

-Alex

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

>Ok, just pushed to branch /feature/mdl
>
>my example project is out the examples. Do you think I should create an
>examples/mdlexample project and upload it to the branch as well?
>
>Thanks
>
>2016-10-14 20:42 GMT+02:00 Carlos Rovira :
>
>> Hi Alex,
>>
>> I tried the both add and
>>
>> 
>> add
>>   
>>
>> but didn't worked.
>>
>> I'll be uploading the branch, since I'm equally worried about the low
>> level code not working
>>
>> Thanks!
>>
>>
>>
>>
>>
>>
>>
>> 2016-10-14 20:19 GMT+02:00 Alex Harui :
>>
>>>
>>>
>>> On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>> Rovira" 
>>> wrote:
>>>
>>> >Hi,
>>> >
>>> >I'm trying to setup a MDL library to start making some components with
>>> >that
>>> >look and feel.
>>> >I'm following the Flat library project indications, and right now I'm
>>> >building it ok with maven (didn't test Ant, but as a copy/paste from
>>> Flat,
>>> >I think it should work as well).
>>> >
>>> >Then I tried in a sample project. Again, new dependencies set and mdl
>>> >declarations are working, but result is not looking as I expect, maybe
>>> due
>>> >to some low level constructions that I still doesn't dominate (mainly
>>>the
>>> >internals in the "createElement():WrappedHTMLElement" overload, that I
>>> >want
>>> >to try to give some love today as I get a bit more time.
>>> >
>>> >Ok, from here,...I'm still trying to understand more things... for
>>> >example:
>>> >
>>> >1.- MDL requires some CSS files to be linked. I'm using it with
>>> >-html-template tag in the example project, but, maybe this should be
>>> >provided by the MDL.swc ? if so, why could we do this?
>>>
>>> Use the  directive.  See CreateJS.swc's Application class.
>>>
>>> >
>>> >2.- To start implementing components, maybe it'd be better that
>>>someone
>>> >review what I'm doing (to avoid work in things that not conform to
>>> >standards setup here). Maybe I should upload the branch for people
>>>(Maybe
>>> >Alex, Peter,...) to take a look?
>>>
>>> Sure, feel free to share the branch.
>>>
>>> >
>>> >3.- I started trying to make a simple Colored Fab MDL button... (as
>>> >described here
>>>https://getmdl.io/components/index.html#buttons-section)
>>> >
>>> >and find that using a simple mxml declaration almost worked (it's not
>>> >right, only an approximation, since I can't write "low level" HTML in
>>> MXML
>>> >like an  with HTMLElement). So, this:
>>> >
>>> >
>>> >
>>>
>>> Did you try:
>>>
>>> 
>>>   add
>>> 
>>>
>>> And/or:
>>>
>>>
>>> 
>>>   
>>> add
>>>   
>>> 
>>>
>>> If neither of those worked, I will take a look.
>>>
>>>
>>> >
>>> >Shows a pink circle button, without icon.
>>> >
>>> >My MDL button has the following createElement code:
>>> >
>>> >/**
>>> > * @flexjsignorecoercion
>>>org.apache.flex.core.WrappedHTMLElement
>>> > * @flexjsignorecoercion HTMLButtonElement
>>> > */
>>> >override protected function createElement():WrappedHTMLElement
>>> >{
>>> >element = button = document.createElement('button') as
>>> >HTMLButtonElement;
>>> >button.className = 'mdl-button mdl-js-button
>>>mdl-button--fab
>>> >mdl-button--colored';
>>> >
>>> >positioner = element;
>>> >positioner.style.position = 'relative';
>>> >(button as WrappedHTMLElement).flexjs_wrapper = this;
>>> >element.flexjs_wrapper = this;
>>> >
>>> >return element;
>>> >}
>>> >
>>> >and I'm using at my example project : 
>>> >
>>> >But instead to throw the pink empty circle button as the MXML
>>>example, it
>>> >shows a normal button as if my declaration was  (the same
>>> >indeed)
>>> >
>>> >someone knows where I could be failing ?
>>>
>>> I don't see any obvious problems.  I would examine the DOM in the
>>>browser
>>> debugger and make sure the CSS got loaded and the className is properly
>>> set on the HTMLButtonElement.  I'm wondering if the className gets
>>>reset
>>> by the framework somehow.  Although note that setting the className on
>>>the
>>> outer button class that wraps the HTMLButtonElement should set the
>>> className on the button element.
>>>
>>> HTH,
>>> -Alex
>>>
>>>
>>
>>
>> --
>>
>> 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), 

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] Working on a MDL branch

[Carlos Rovira]

Hi Alex,

just committed the MDLExample project in examples folder with minimal code,
just a js:Button with styles that works and a mdl:Button that should have
that styles and doesn't work. I configure to build with maven, but not  ant.

thanks

Carlos



2016-10-14 22:27 GMT+02:00 Alex Harui :

> If you want to make an example in flex-asjs repo in examples/flexjs that
> would be helpful.
>
> -Alex
>
> On 10/14/16, 11:54 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"  carlos.rov...@codeoscopic.com> wrote:
>
> >Ok, just pushed to branch /feature/mdl
> >
> >my example project is out the examples. Do you think I should create an
> >examples/mdlexample project and upload it to the branch as well?
> >
> >Thanks
> >
> >2016-10-14 20:42 GMT+02:00 Carlos Rovira :
> >
> >> Hi Alex,
> >>
> >> I tried the both add and
> >>
> >> 
> >> add
> >>   
> >>
> >> but didn't worked.
> >>
> >> I'll be uploading the branch, since I'm equally worried about the low
> >> level code not working
> >>
> >> Thanks!
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> 2016-10-14 20:19 GMT+02:00 Alex Harui :
> >>
> >>>
> >>>
> >>> On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >>> Rovira" 
> >>> wrote:
> >>>
> >>> >Hi,
> >>> >
> >>> >I'm trying to setup a MDL library to start making some components with
> >>> >that
> >>> >look and feel.
> >>> >I'm following the Flat library project indications, and right now I'm
> >>> >building it ok with maven (didn't test Ant, but as a copy/paste from
> >>> Flat,
> >>> >I think it should work as well).
> >>> >
> >>> >Then I tried in a sample project. Again, new dependencies set and mdl
> >>> >declarations are working, but result is not looking as I expect, maybe
> >>> due
> >>> >to some low level constructions that I still doesn't dominate (mainly
> >>>the
> >>> >internals in the "createElement():WrappedHTMLElement" overload, that
> I
> >>> >want
> >>> >to try to give some love today as I get a bit more time.
> >>> >
> >>> >Ok, from here,...I'm still trying to understand more things... for
> >>> >example:
> >>> >
> >>> >1.- MDL requires some CSS files to be linked. I'm using it with
> >>> >-html-template tag in the example project, but, maybe this should be
> >>> >provided by the MDL.swc ? if so, why could we do this?
> >>>
> >>> Use the  directive.  See CreateJS.swc's Application class.
> >>>
> >>> >
> >>> >2.- To start implementing components, maybe it'd be better that
> >>>someone
> >>> >review what I'm doing (to avoid work in things that not conform to
> >>> >standards setup here). Maybe I should upload the branch for people
> >>>(Maybe
> >>> >Alex, Peter,...) to take a look?
> >>>
> >>> Sure, feel free to share the branch.
> >>>
> >>> >
> >>> >3.- I started trying to make a simple Colored Fab MDL button... (as
> >>> >described here
> >>>https://getmdl.io/components/index.html#buttons-section)
> >>> >
> >>> >and find that using a simple mxml declaration almost worked (it's not
> >>> >right, only an approximation, since I can't write "low level" HTML in
> >>> MXML
> >>> >like an  with HTMLElement). So, this:
> >>> >
> >>> >
> >>> >
> >>>
> >>> Did you try:
> >>>
> >>> 
> >>>   add
> >>> 
> >>>
> >>> And/or:
> >>>
> >>>
> >>> 
> >>>   
> >>> add
> >>>   
> >>> 
> >>>
> >>> If neither of those worked, I will take a look.
> >>>
> >>>
> >>> >
> >>> >Shows a pink circle button, without icon.
> >>> >
> >>> >My MDL button has the following createElement code:
> >>> >
> >>> >/**
> >>> > * @flexjsignorecoercion
> >>>org.apache.flex.core.WrappedHTMLElement
> >>> > * @flexjsignorecoercion HTMLButtonElement
> >>> > */
> >>> >override protected function createElement():
> WrappedHTMLElement
> >>> >{
> >>> >element = button = document.createElement('button') as
> >>> >HTMLButtonElement;
> >>> >button.className = 'mdl-button mdl-js-button
> >>>mdl-button--fab
> >>> >mdl-button--colored';
> >>> >
> >>> >positioner = element;
> >>> >positioner.style.position = 'relative';
> >>> >(button as WrappedHTMLElement).flexjs_wrapper = this;
> >>> >element.flexjs_wrapper = this;
> >>> >
> >>> >return element;
> >>> >}
> >>> >
> >>> >and I'm using at my example project : 
> >>> >
> >>> >But instead to throw the pink empty circle button as the MXML
> >>>example, it
> >>> >shows a normal button as if my declaration was  (the same
> >>> >indeed)
> >>> >
> >>> >someone knows where I could be failing ?
> >>>
> >>> I don't see any obvious problems.  I would examine the DOM in the
> >>>browser
> >>> debugger and make sure the CSS got loaded and the className is properly
> >>> set on the HTMLButtonElement.  I'm wondering if the className gets
> >>>reset
> >>> by the framework somehow.  Although note that 

Re: Moonshine IDE 1.2.1 Windows release

[Justin Mclean]

HI,

I took a look at the page and it looks good [1], but it would be nice it was 
more in line with Apache trademark policy. [2][3]

For instance:
- The project name is “Apache Flex” and “Apache Flex JS” not “Flex” or “Flex JS”
- A link back to the home page of our project would be nice
- Having an attribution of the Apache trademarks in the footer of the page

If you have any questions on the policy or what needs to change just ask and 
we’ll help.

Thanks,
Justin

1. http://moonshine-ide.com
2. http://www.apache.org/foundation/marks/#guidelines
3. http://www.apache.org/foundation/marks/faq/

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

AW: [Website] Progress on the Website-Generation topic

[Christofer Dutz]

If someone knows bootstrap good enough to eventually help me with the position 
of the navigation bar? Currently it's stuck to the top no matter where you 
scroll to. I would prefer it to have the Flex and Apache logo above (like in 
the current version) but as soon as you scroll down and the header hit's the 
top of the browser window, it stays there and remains visible. I know I have 
seen this behavior but I simply don't know the CSS magic I would have to apply 
here ;-)


So if anyone here knows this stuff, please come forward and help me get this 
site a little more into shape :-)


Chris


Von: Justin Mclean 
Gesendet: Freitag, 14. Oktober 2016 09:44:27
An: dev@flex.apache.org
Betreff: Re: [Website] Progress on the Website-Generation topic

Hi,

> So has anyone else had a look at the newly generated documentation in the 
> flex-site.git "maven-site" branch? As I mentioned, if you checkout the 
> "asf-site" branch you can see the generated output.

Just taking look now. It been a couple of busy weeks with conferences and other 
work (yesterday I assembled, programmed and tested 40 prototype devices) and 
I’m just catching up on a few things.

Thanks,
Justin

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: [Website] Progress on the Website-Generation topic

[Maxim Solodovnik]

On Fri, Oct 14, 2016 at 4:02 PM, Christofer Dutz 
wrote:

> Hi Om,
>
>
> I think that approach is probably the best ... I did encounter problems
> when running the website from the working directory of Jenkins. Don't know
> why.
>
>
Jenkins is on https:// and scripts are being loaded from CDN via http://
Things like this need to be fixed in final version :(

For our project we are generating site using
https://maven.apache.org/skins/maven-fluido-skin/
Works for us :)


> The template is configured in the site.xml document, as this configures
> the the reflow themes built-in template. You can see all the options here:
>
> http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html
>
>
> The toc component seems to have this sort of option (offsetTopnav), but
> not the topNav element responsible for the top navigation. I hope this is
> customizable without having to adjust the reflow template itself.
>
>
> But I just stumbled over the bottomNav column feature ... will add that
> right away :-)
>
>
> Another option would be to overwrite the css style by adding the
> declarations to "site.css" but as I said ... I'm no web-developer and I
> sort of feel like wasting days on stuff like that ... so if you know what
> to do, just give it a try.
>
>
> With a simple:
>
>
> mvn clean site
>
>
> you can re-generate the site and have a look at the result in the
> "target/site" directory.
>
>
>
> Chris
>
> 
> Von: omup...@gmail.com  im Auftrag von OmPrakash
> Muppirala 
> Gesendet: Freitag, 14. Oktober 2016 10:33:28
> An: dev@flex.apache.org
> Betreff: Re: [Website] Progress on the Website-Generation topic
>
> Never mind, I checked out the flex-site.
>
> The proper fix would be to
> 1.  Remove the class "navbar-fixed-top" on the navbar div in all pages.
> 2.  Set padding-top = 0 for body in bootswatch.css
>
> (2) is straightforward.  But it looks like we need to make the change for
> (1) in every page.  Is there a html template that drives all the pages?
>
> Thanks,
> Om
>
> On Fri, Oct 14, 2016 at 1:28 AM, Harbs  wrote:
>
> > The link is lower down in this thread:
> > https://builds.apache.org/view/E-G/view/Flex/job/Flex-
> > Site%20(Maven)/ws/target/site/index.html
> >
> > On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala 
> > wrote:
> >
> > > Where can I find this site?
> > >
> > > It sounds like the nav bar has CSS setting position: sticky;
> > > Either that, or the position of the nav bar is being translated in an
> > > onScroll event handler in javascript.
> > >
> > > Thanks,
> > > Om
> > >
> > > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz <
> > christofer.d...@c-ware.de
> > >> wrote:
> > >
> > >> If someone knows bootstrap good enough to eventually help me with the
> > >> position of the navigation bar? Currently it's stuck to the top no
> > matter
> > >> where you scroll to. I would prefer it to have the Flex and Apache
> logo
> > >> above (like in the current version) but as soon as you scroll down and
> > the
> > >> header hit's the top of the browser window, it stays there and remains
> > >> visible. I know I have seen this behavior but I simply don't know the
> > CSS
> > >> magic I would have to apply here ;-)
> > >>
> > >>
> > >> So if anyone here knows this stuff, please come forward and help me
> get
> > >> this site a little more into shape :-)
> > >>
> > >>
> > >> Chris
> > >>
> > >> 
> > >> Von: Justin Mclean 
> > >> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> > >> An: dev@flex.apache.org
> > >> Betreff: Re: [Website] Progress on the Website-Generation topic
> > >>
> > >> Hi,
> > >>
> > >>> So has anyone else had a look at the newly generated documentation in
> > >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout
> > the
> > >> "asf-site" branch you can see the generated output.
> > >>
> > >> Just taking look now. It been a couple of busy weeks with conferences
> > and
> > >> other work (yesterday I assembled, programmed and tested 40 prototype
> > >> devices) and I’m just catching up on a few things.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> >
> >
>



-- 
WBR
Maxim aka solomax

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: [Website] Progress on the Website-Generation topic

[Justin Mclean]

Hi,

> So has anyone else had a look at the newly generated documentation in the 
> flex-site.git "maven-site" branch? As I mentioned, if you checkout the 
> "asf-site" branch you can see the generated output.

Just taking look now. It been a couple of busy weeks with conferences and other 
work (yesterday I assembled, programmed and tested 40 prototype devices) and 
I’m just catching up on a few things.

Thanks,
Justin

Re: [Discuss] What's keeping the others from participating?

[Justin Mclean]

Hi,

While I’m still precipitating and not exactly silent - it’s not as much as I 
once was contributing.

Reasons in no particular order.
- I’m mentoring and involved in a number of other Apache projects and need to 
split my limited volunteer time between them
- I’m no longer working on Flex work full time
- It’s unlikely I would be able to get paid work using FLexJS in the near future
- FlexJS was very hard to compile (until recently)
- There is little FlexJS documentation (but improving)
- It’s hard to keep up with changes
- FLexJS release notes don’t describe changes between versions
- Some other communities (Apache and elsewhere) are more welcoming
- Issues that should be easily fixed aren't. If this wasn’t the case I would 
have time to commit more.

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

[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: [Website] Progress on the Website-Generation topic

[Harbs]

The link is lower down in this thread:
https://builds.apache.org/view/E-G/view/Flex/job/Flex-Site%20(Maven)/ws/target/site/index.html

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

> Where can I find this site?
> 
> It sounds like the nav bar has CSS setting position: sticky;
> Either that, or the position of the nav bar is being translated in an
> onScroll event handler in javascript.
> 
> Thanks,
> Om
> 
> On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz > wrote:
> 
>> If someone knows bootstrap good enough to eventually help me with the
>> position of the navigation bar? Currently it's stuck to the top no matter
>> where you scroll to. I would prefer it to have the Flex and Apache logo
>> above (like in the current version) but as soon as you scroll down and the
>> header hit's the top of the browser window, it stays there and remains
>> visible. I know I have seen this behavior but I simply don't know the CSS
>> magic I would have to apply here ;-)
>> 
>> 
>> So if anyone here knows this stuff, please come forward and help me get
>> this site a little more into shape :-)
>> 
>> 
>> Chris
>> 
>> 
>> Von: Justin Mclean 
>> Gesendet: Freitag, 14. Oktober 2016 09:44:27
>> An: dev@flex.apache.org
>> Betreff: Re: [Website] Progress on the Website-Generation topic
>> 
>> Hi,
>> 
>>> So has anyone else had a look at the newly generated documentation in
>> the flex-site.git "maven-site" branch? As I mentioned, if you checkout the
>> "asf-site" branch you can see the generated output.
>> 
>> Just taking look now. It been a couple of busy weeks with conferences and
>> other work (yesterday I assembled, programmed and tested 40 prototype
>> devices) and I’m just catching up on a few things.
>> 
>> Thanks,
>> Justin
>> 

AW: [Website] Progress on the Website-Generation topic

[Christofer Dutz]

Hi Om,


I think that approach is probably the best ... I did encounter problems when 
running the website from the working directory of Jenkins. Don't know why.


The template is configured in the site.xml document, as this configures the the 
reflow themes built-in template. You can see all the options here:

http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html


The toc component seems to have this sort of option (offsetTopnav), but not the 
topNav element responsible for the top navigation. I hope this is customizable 
without having to adjust the reflow template itself.


But I just stumbled over the bottomNav column feature ... will add that right 
away :-)


Another option would be to overwrite the css style by adding the declarations 
to "site.css" but as I said ... I'm no web-developer and I sort of feel like 
wasting days on stuff like that ... so if you know what to do, just give it a 
try.


With a simple:


mvn clean site


you can re-generate the site and have a look at the result in the "target/site" 
directory.



Chris


Von: omup...@gmail.com  im Auftrag von OmPrakash Muppirala 

Gesendet: Freitag, 14. Oktober 2016 10:33:28
An: dev@flex.apache.org
Betreff: Re: [Website] Progress on the Website-Generation topic

Never mind, I checked out the flex-site.

The proper fix would be to
1.  Remove the class "navbar-fixed-top" on the navbar div in all pages.
2.  Set padding-top = 0 for body in bootswatch.css

(2) is straightforward.  But it looks like we need to make the change for
(1) in every page.  Is there a html template that drives all the pages?

Thanks,
Om

On Fri, Oct 14, 2016 at 1:28 AM, Harbs  wrote:

> The link is lower down in this thread:
> https://builds.apache.org/view/E-G/view/Flex/job/Flex-
> Site%20(Maven)/ws/target/site/index.html
>
> On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala 
> wrote:
>
> > Where can I find this site?
> >
> > It sounds like the nav bar has CSS setting position: sticky;
> > Either that, or the position of the nav bar is being translated in an
> > onScroll event handler in javascript.
> >
> > Thanks,
> > Om
> >
> > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz <
> christofer.d...@c-ware.de
> >> wrote:
> >
> >> If someone knows bootstrap good enough to eventually help me with the
> >> position of the navigation bar? Currently it's stuck to the top no
> matter
> >> where you scroll to. I would prefer it to have the Flex and Apache logo
> >> above (like in the current version) but as soon as you scroll down and
> the
> >> header hit's the top of the browser window, it stays there and remains
> >> visible. I know I have seen this behavior but I simply don't know the
> CSS
> >> magic I would have to apply here ;-)
> >>
> >>
> >> So if anyone here knows this stuff, please come forward and help me get
> >> this site a little more into shape :-)
> >>
> >>
> >> Chris
> >>
> >> 
> >> Von: Justin Mclean 
> >> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> >> An: dev@flex.apache.org
> >> Betreff: Re: [Website] Progress on the Website-Generation topic
> >>
> >> Hi,
> >>
> >>> So has anyone else had a look at the newly generated documentation in
> >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout
> the
> >> "asf-site" branch you can see the generated output.
> >>
> >> Just taking look now. It been a couple of busy weeks with conferences
> and
> >> other work (yesterday I assembled, programmed and tested 40 prototype
> >> devices) and I’m just catching up on a few things.
> >>
> >> Thanks,
> >> Justin
> >>
>
>

RE: Re: [FalconJX] Generating ASDoc

[Kessler CTR Mark J]

> flex.apache.org/docs/flexjs/com.example.SomeComponent/
> flex.apache.org/docs/flexsdk/com.example.SomeComponent/

This would be great for be a great format for IDE's to be able to load 
documentation specific to the component you have selected.



-Mark

Re: [Website] Progress on the Website-Generation topic

[OmPrakash Muppirala]

Where can I find this site?

It sounds like the nav bar has CSS setting position: sticky;
Either that, or the position of the nav bar is being translated in an
onScroll event handler in javascript.

Thanks,
Om

On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz  wrote:

> If someone knows bootstrap good enough to eventually help me with the
> position of the navigation bar? Currently it's stuck to the top no matter
> where you scroll to. I would prefer it to have the Flex and Apache logo
> above (like in the current version) but as soon as you scroll down and the
> header hit's the top of the browser window, it stays there and remains
> visible. I know I have seen this behavior but I simply don't know the CSS
> magic I would have to apply here ;-)
>
>
> So if anyone here knows this stuff, please come forward and help me get
> this site a little more into shape :-)
>
>
> Chris
>
> 
> Von: Justin Mclean 
> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> An: dev@flex.apache.org
> Betreff: Re: [Website] Progress on the Website-Generation topic
>
> Hi,
>
> > So has anyone else had a look at the newly generated documentation in
> the flex-site.git "maven-site" branch? As I mentioned, if you checkout the
> "asf-site" branch you can see the generated output.
>
> Just taking look now. It been a couple of busy weeks with conferences and
> other work (yesterday I assembled, programmed and tested 40 prototype
> devices) and I’m just catching up on a few things.
>
> Thanks,
> Justin
>

AW: AW: AW: AW: [Website] Progress on the Website-Generation topic

[Christofer Dutz]

Ok ... pinging this thread again ...


So has anyone else had a look at the newly generated documentation in the 
flex-site.git "maven-site" branch? As I mentioned, if you checkout the 
"asf-site" branch you can see the generated output.


Chris


Von: Christofer Dutz 
Gesendet: Donnerstag, 13. Oktober 2016 07:49:01
An: dev@flex.apache.org
Betreff: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic

Hi Alex,


Well you do need buildbot ... nothing else is allowed to commit. But nothing 
else than buildbot.


I was talking about the user workflow. These three steps are the steps you 
need, if you want to change something and I guess you can't get any simpler 
than that. Especially with the ability to test your changes locally before 
committing. Buildbot kicks in as soon as you commit and does the rest.


But needing buildbot isn't a change as we currently need buildbot for the 
current version too (https://ci.apache.org/builders/flex-site-staging). So in 
this case we would simply replace on buildbot job with another.


So if we are comparing the new three-step user workflow:

1. Do changes

2. Test them locally with a "mvn clean site"

3. Commit changes


to the current user workflow, which is:

1. Do changes

2. Commit changes

3. Wait for buildbot to stage the changes

4. Check if the output is what we want in the staging area

5. Go to the Web-Ui and release all changes at once (Could be a problem that 
you release stuff someone else is currently working on, but I guess that's a 
more theoretical problem)


I think the new workflow is a great improvement. And especially if it's just 
the fixing of typos, it boils down to a two step Workflow:

1. Do changes

2. Commit changes


And another thing I noticed is that the new page performs a lot better on small 
resolutions like on tablets or mobile phones (If you decrease the width of the 
browser window the site adjusts like in the old version, but the 
mobile-menu-version of the new version looks a lot nicer than that of the 
current version)


And I just wanted to put straight that this workflow is not more complicated 
than anything we have right now. I know 99% of people on this list just read 
and don't let their voice be heard and I just think if they read your email 
containing a completely incorrect "How I understood it" summary from you, it 
would manipulate them in thinking the whole thing is too complicated - which it 
is not.


Chris




Von: Alex Harui 
Gesendet: Donnerstag, 13. Oktober 2016 06:40:35
An: dev@flex.apache.org
Betreff: Re: AW: AW: AW: [Website] Progress on the Website-Generation topic

Well, maybe I'm just being dense, but in the most recent two threads you
started on this topic, you mention buildbot, and I saw a lot of buildbot
traffic come into my mailbox.  So apologies if I haven't followed your
emails in detail, but I did not see any prior mention of not needing
buildbot and could not find your 3-step workflow in previous emails.

On 10/12/16, 12:54 PM, "Christofer Dutz"  wrote:

>Well I think I wrote down the entire workflow as well as the when's and
>why's so many times that I'm not going to repeat them again.
>
>You don't need the build at builds.a.o at all. I just set that up in the
>beginning because in the beginning I thought I would have to trigger
>buildbot from there and didn't delete it after finishing, because I
>simply forgot it's there.
>
>What you get is:
>- A website in git and not svn.
>- The code is generally a lot cleaner.
>- You don't have to commit changes to test them in the staging area.
>- You don't have to use that stupid web interface to release staged stuff
>to production.
>
>I currently don't have asciidoctor in there at all, so please stop
>describing this approach as complicated and simply read my emails.

I've been trying to figure out the advantage of using builds.a.o vs
buildbot.  It sounds like the key point is that we can publish without
having to go through the web interface.  That sounds like a good deal to
me.  Let's see what others think.

>
>Workflow is:
>
>1. Do changes in the "maven-site" branch
>2. Test them locally by running "mvn clean site"
>3. Commit and push them
>
>That's it. Nothing more to it.

So assuming others are in favor, what are the remaining steps?  Do we want
to exactly reproduce the existing site?  Do we need to be concerned about
the "insecure content" errors/warnings?  Nick K was working on a revamp of
our website.  I wonder how that work will be impacted.

Thanks,
-Alex

Major benefits of FlexJS over other approaches

[Christofer Dutz]

Hi,


as we were having a discussion in the "what's keeping the others ..." thread.

I agree that from the feature-set I too am a little jealous. I too see Generics 
and Lambdas as a really cool feature of TypeScript. Most of the others however 
I see more as "Yeah you need that if you don't know how to code correctly" ;-)


In my talk at solutions.hamburg and the talks after that talk I noticed that 
the biggest advantages of our current path are:

- Migration of existing codebases while keeping the general logic and most 
changes applying to the UI only

- The huge number of well established existing third party libraries for all 
sorts of use-cases (Most of the non-ui-related frameworks should be reusable in 
JS applications)

- TypeScript is really new and therefore most existing libraries are max one 
year old and are lacking the maturity the well riped Flex libraries have

- What ActionScript is missing in features, we can extend (and I think we 
already started discussing adding generics support to ActionScript)

- You never know what the big companies do, you can't predict which path 
Microsoft will be going with TypeScript. If they decide they need to change 
something, you have to live with that.


At least these features are the ones I noticed people getting big ears most.


Chris

Re: [Website] Progress on the Website-Generation topic

[OmPrakash Muppirala]

Never mind, I checked out the flex-site.

The proper fix would be to
1.  Remove the class "navbar-fixed-top" on the navbar div in all pages.
2.  Set padding-top = 0 for body in bootswatch.css

(2) is straightforward.  But it looks like we need to make the change for
(1) in every page.  Is there a html template that drives all the pages?

Thanks,
Om

On Fri, Oct 14, 2016 at 1:28 AM, Harbs  wrote:

> The link is lower down in this thread:
> https://builds.apache.org/view/E-G/view/Flex/job/Flex-
> Site%20(Maven)/ws/target/site/index.html
>
> On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala 
> wrote:
>
> > Where can I find this site?
> >
> > It sounds like the nav bar has CSS setting position: sticky;
> > Either that, or the position of the nav bar is being translated in an
> > onScroll event handler in javascript.
> >
> > Thanks,
> > Om
> >
> > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz <
> christofer.d...@c-ware.de
> >> wrote:
> >
> >> If someone knows bootstrap good enough to eventually help me with the
> >> position of the navigation bar? Currently it's stuck to the top no
> matter
> >> where you scroll to. I would prefer it to have the Flex and Apache logo
> >> above (like in the current version) but as soon as you scroll down and
> the
> >> header hit's the top of the browser window, it stays there and remains
> >> visible. I know I have seen this behavior but I simply don't know the
> CSS
> >> magic I would have to apply here ;-)
> >>
> >>
> >> So if anyone here knows this stuff, please come forward and help me get
> >> this site a little more into shape :-)
> >>
> >>
> >> Chris
> >>
> >> 
> >> Von: Justin Mclean 
> >> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> >> An: dev@flex.apache.org
> >> Betreff: Re: [Website] Progress on the Website-Generation topic
> >>
> >> Hi,
> >>
> >>> So has anyone else had a look at the newly generated documentation in
> >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout
> the
> >> "asf-site" branch you can see the generated output.
> >>
> >> Just taking look now. It been a couple of busy weeks with conferences
> and
> >> other work (yesterday I assembled, programmed and tested 40 prototype
> >> devices) and I’m just catching up on a few things.
> >>
> >> Thanks,
> >> Justin
> >>
>
>

Re: [Discuss] What's keeping the others from participating?

[Tom Chiverton]

For me, FlexJS is 'rocket science' - I'm not an expert in compilers, or 
even the build tools involved - I've written a few simple maven scripts 
here and there.


I also have less time - my employeer has a single Flex application now, 
and one in AIR. New work is in Ember, Angular or some other 'JS native' 
framework.


I was looking to help with the change the website CMS but I've been well 
beaten to it :-)


I do not see a problem in "living with it".

Tom


On 13/10/16 07:08, Christofer Dutz wrote:

Hi guys,


I just wanted to take the opportunity to ask you what's keeping you from 
participating in any discussions here on the list and on contributing anything 
else.


Apache Flex currently has the 10th largest committer base in the ASF, but 
currently it feels like there is only 4-5 people still active on this project. 
Having this in-diversity in discussions is starting to get more and more 
tiresome as I almost know the responses which are going to come if I post 
something. I think most of the time I could start writing the reply for the 
expected response right away so I don't have to do it later.


Are we doing something wrong?


What's keeping all of you stay silent?


Is is:

- lack of interest?

- lack of time?

- that you think this is too much rocket-science? / It's too complicated to 
contribute

- a consumer attitude that you just want to know what others are doing for you?


Apache is all about community, but for me this doesn't feel much like a community 
anymore. Sometimes I think we could rename dev@flex.apache.org to a...@flex.apache.org as 
he is definitely the most active poster. Discussing stuff with the project sort of feels 
more and more like "If I want to change something, I'll take it to the list and 
discuss it with Alex first". It shouldn't be that way.


Is is just us 4-5 people and we simply have to live with it, or can we do 
anything to get you guys back on board?


For the last more-than-a-year I have been working exclusively on trying to 
lower the complexity to contribute in order to get more people on board. It 
seems that effort was a waste of time. Please prove me wrong.


@Alex: I would like to kindly ask you to please refrain from responding right away and 
let at least a hand full of others respond first. I would like to see if this eventually 
prevents the "someone else is taking care of it for me" effect.


Chris


__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__

Re: [Discuss] What's keeping the others from participating?

[Maxim Solodovnik]

I currently have no time at all :(
I'm trying to move forward my "main" Apache project
And need to do day time work :((
Hopefully will find some time and will try to contribute something :)

On Fri, Oct 14, 2016 at 4:12 PM, Tom Chiverton  wrote:

> For me, FlexJS is 'rocket science' - I'm not an expert in compilers, or
> even the build tools involved - I've written a few simple maven scripts
> here and there.
>
> I also have less time - my employeer has a single Flex application now,
> and one in AIR. New work is in Ember, Angular or some other 'JS native'
> framework.
>
> I was looking to help with the change the website CMS but I've been well
> beaten to it :-)
>
> I do not see a problem in "living with it".
>
> Tom
>
>
> On 13/10/16 07:08, Christofer Dutz wrote:
>
>> Hi guys,
>>
>>
>> I just wanted to take the opportunity to ask you what's keeping you from
>> participating in any discussions here on the list and on contributing
>> anything else.
>>
>>
>> Apache Flex currently has the 10th largest committer base in the ASF, but
>> currently it feels like there is only 4-5 people still active on this
>> project. Having this in-diversity in discussions is starting to get more
>> and more tiresome as I almost know the responses which are going to come if
>> I post something. I think most of the time I could start writing the reply
>> for the expected response right away so I don't have to do it later.
>>
>>
>> Are we doing something wrong?
>>
>>
>> What's keeping all of you stay silent?
>>
>>
>> Is is:
>>
>> - lack of interest?
>>
>> - lack of time?
>>
>> - that you think this is too much rocket-science? / It's too complicated
>> to contribute
>>
>> - a consumer attitude that you just want to know what others are doing
>> for you?
>>
>>
>> Apache is all about community, but for me this doesn't feel much like a
>> community anymore. Sometimes I think we could rename dev@flex.apache.org
>> to a...@flex.apache.org as he is definitely the most active poster.
>> Discussing stuff with the project sort of feels more and more like "If I
>> want to change something, I'll take it to the list and discuss it with Alex
>> first". It shouldn't be that way.
>>
>>
>> Is is just us 4-5 people and we simply have to live with it, or can we do
>> anything to get you guys back on board?
>>
>>
>> For the last more-than-a-year I have been working exclusively on trying
>> to lower the complexity to contribute in order to get more people on board.
>> It seems that effort was a waste of time. Please prove me wrong.
>>
>>
>> @Alex: I would like to kindly ask you to please refrain from responding
>> right away and let at least a hand full of others respond first. I would
>> like to see if this eventually prevents the "someone else is taking care of
>> it for me" effect.
>>
>>
>> Chris
>>
>>
>> __
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.com
>> __
>>
>
>


-- 
WBR
Maxim aka solomax

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: [Discuss] What's keeping the others from participating?

[Jason Taylor]

"TypeScript and Dart for JS all run on top of JS, so my understanding is that 
any new language constructs they offer can be implemented on top of Flash as 
well, although you might give up runtime type-checking for those new language 
features."  

How would you implement async / await and parallel programming features on top 
of flash when the flash runtime in no way supports those types of constructs.  
Again Alex you continue to dismiss these features, while those of us that 
program in these features daily will dismiss FlexJS in time if the future 
roadmap dosen't include this.  It's way way way more important than you seem to 
believe.

~ JT


-Original Message-
From: Alex Harui [mailto:aha...@adobe.com] 
Sent: Thursday, October 13, 2016 3:37 PM
To: dev@flex.apache.org
Subject: Re: [Discuss] What's keeping the others from participating?



On 10/13/16, 3:20 PM, "Jason Taylor"  wrote:

>Hi Harbs, I honestly don't see how the language can move forward when 
>the goal of FlexJS is to be able to compile to swf.  As long as we are 
>stuck with that baggage implementing async / await and other parallel 
>processing operations won't be possible without breaking the swf 
>compatibility and fracturing FlexJS.  That's where the crux of my 
>disagreement with the team is.  I don't believe compiling to swf is 
>important in the long term, and by binding ourselves to that we are 
>limiting out future drastically.  In a few years I don't think an 
>application developer will be willing to switch framework platform 
>without async / await, generics, or lamda's.  I am excited about 
>FlexJS, but honestly I hope it's ported over to a better language system like
>typescript or dart.   The world needs a great rapid application
>development framework with a declarative UI language, but the world 
>dosen't need SWF's in the future.
>

Compiling to SWF isn't a requirement for FlexJS.  I still think it is a good 
thing so all our current SWCs can run as SWF.  Having runtime type-checking is 
important as applications grow in complexity and are developed by remote 
development teams.

But even if it was a requirement, TypeScript and Dart for JS all run on top of 
JS, so my understanding is that any new language constructs they offer can be 
implemented on top of Flash as well, although you might give up runtime 
type-checking for those new language features.

And there is nothing stopping anyone from building a version of the compiler 
that handles TS or Dart instead of AS.  Its all open-source.
 
Thanks,
-Alex

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

[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: [Website] Progress on the Website-Generation topic

[Maxim Solodovnik]

It is sad Maven has no references to this skin :(
Not sure if I will have time, but maybe I'll invest some time to
refactoring the site one more time :)))


On Fri, Oct 14, 2016 at 6:26 PM, Christofer Dutz 
wrote:

> Hi Maxim,
>
>
> I initially setup the fluido skin, but that is more a skin for the normal
> maven-style pages. Generating our website with that would look sort of 90s
> or max early 2000s ;-)
>
>
> The cool thing with the reflow-skin is that it's a reactive version that
> adjusts to mobile devices nicely and allows us to auto-generate something
> looking very similar to our current Website.
>
>
> Chris
>
> 
> Von: Maxim Solodovnik 
> Gesendet: Freitag, 14. Oktober 2016 11:54:40
> An: dev@flex.apache.org
> Betreff: Re: [Website] Progress on the Website-Generation topic
>
> On Fri, Oct 14, 2016 at 4:02 PM, Christofer Dutz <
> christofer.d...@c-ware.de>
> wrote:
>
> > Hi Om,
> >
> >
> > I think that approach is probably the best ... I did encounter problems
> > when running the website from the working directory of Jenkins. Don't
> know
> > why.
> >
> >
> Jenkins is on https:// and scripts are being loaded from CDN via http://
> Things like this need to be fixed in final version :(
>
> For our project we are generating site using
> https://maven.apache.org/skins/maven-fluido-skin/
> Works for us :)
>
>
> > The template is configured in the site.xml document, as this configures
> > the the reflow themes built-in template. You can see all the options
> here:
> >
> > http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html
> >
> >
> > The toc component seems to have this sort of option (offsetTopnav), but
> > not the topNav element responsible for the top navigation. I hope this is
> > customizable without having to adjust the reflow template itself.
> >
> >
> > But I just stumbled over the bottomNav column feature ... will add that
> > right away :-)
> >
> >
> > Another option would be to overwrite the css style by adding the
> > declarations to "site.css" but as I said ... I'm no web-developer and I
> > sort of feel like wasting days on stuff like that ... so if you know what
> > to do, just give it a try.
> >
> >
> > With a simple:
> >
> >
> > mvn clean site
> >
> >
> > you can re-generate the site and have a look at the result in the
> > "target/site" directory.
> >
> >
> >
> > Chris
> >
> > 
> > Von: omup...@gmail.com  im Auftrag von OmPrakash
> > Muppirala 
> > Gesendet: Freitag, 14. Oktober 2016 10:33:28
> > An: dev@flex.apache.org
> > Betreff: Re: [Website] Progress on the Website-Generation topic
> >
> > Never mind, I checked out the flex-site.
> >
> > The proper fix would be to
> > 1.  Remove the class "navbar-fixed-top" on the navbar div in all pages.
> > 2.  Set padding-top = 0 for body in bootswatch.css
> >
> > (2) is straightforward.  But it looks like we need to make the change for
> > (1) in every page.  Is there a html template that drives all the pages?
> >
> > Thanks,
> > Om
> >
> > On Fri, Oct 14, 2016 at 1:28 AM, Harbs  wrote:
> >
> > > The link is lower down in this thread:
> > > https://builds.apache.org/view/E-G/view/Flex/job/Flex-
> > > Site%20(Maven)/ws/target/site/index.html
> > >
> > > On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala <
> bigosma...@gmail.com>
> > > wrote:
> > >
> > > > Where can I find this site?
> > > >
> > > > It sounds like the nav bar has CSS setting position: sticky;
> > > > Either that, or the position of the nav bar is being translated in an
> > > > onScroll event handler in javascript.
> > > >
> > > > Thanks,
> > > > Om
> > > >
> > > > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz <
> > > christofer.d...@c-ware.de
> > > >> wrote:
> > > >
> > > >> If someone knows bootstrap good enough to eventually help me with
> the
> > > >> position of the navigation bar? Currently it's stuck to the top no
> > > matter
> > > >> where you scroll to. I would prefer it to have the Flex and Apache
> > logo
> > > >> above (like in the current version) but as soon as you scroll down
> and
> > > the
> > > >> header hit's the top of the browser window, it stays there and
> remains
> > > >> visible. I know I have seen this behavior but I simply don't know
> the
> > > CSS
> > > >> magic I would have to apply here ;-)
> > > >>
> > > >>
> > > >> So if anyone here knows this stuff, please come forward and help me
> > get
> > > >> this site a little more into shape :-)
> > > >>
> > > >>
> > > >> Chris
> > > >>
> > > >> 
> > > >> Von: Justin Mclean 
> > > >> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> > > >> An: dev@flex.apache.org
> > > >> Betreff: Re: [Website] Progress on the Website-Generation topic
> > > >>
> > > >> Hi,
> > > >>
> > > >>> So has anyone else had a look at the newly generated documentation
> in
> > > >> 

AW: Re: [FalconJX] Generating ASDoc

[Christofer Dutz]

Hi Mark,


I think the IDE shouldn't require HTTP access to a remote server to display 
content. In this case there would be no way in telling an IDE generically where 
for find the root of documentation for library X.


That's where the javadoc jars come in. At least for maven IDEs know that they 
simply have to load the jar {artifactId}-{version}-javadoc.jar if the class is 
in an artifact {artifactId}-{version}.{whatever}.


Currently the way I setup the JavaDoc for the flexjs compiler modules for being 
indexed by Google, they would produce:

flex.apache.org/docs/flexjs/compiler/latest-dev/com/example/SomeComponent/...

for the current dev-branch. And in case of a release of 0.8.0 they would add:

flex.apache.org/docs/flexjs/compiler/0.8.0/com/example/SomeComponent/

So you could reference the explicit version of an API for documentation.


But in both cases there should be a html file to back the documentation for a 
given class and the path to that file should reflect the package structure.


I guess we both agree on that :-)


Chris


Von: Kessler CTR Mark J 
Gesendet: Freitag, 14. Oktober 2016 12:34:10
An: dev@flex.apache.org
Betreff: RE: Re: [FalconJX] Generating ASDoc


> flex.apache.org/docs/flexjs/com.example.SomeComponent/
> flex.apache.org/docs/flexsdk/com.example.SomeComponent/

This would be great for be a great format for IDE's to be able to load 
documentation specific to the component you have selected.



-Mark

Re: AW: AW: AW: AW: [Website] Progress on the Website-Generation topic

[Alex Harui]

On 10/14/16, 12:42 AM, "Christofer Dutz"  wrote:

>
>So if we are comparing the new three-step user workflow:
>
>1. Do changes
>
>2. Test them locally with a "mvn clean site"
>
>3. Commit changes
>
>
>to the current user workflow, which is:
>
>1. Do changes
>
>2. Commit changes
>
>3. Wait for buildbot to stage the changes
>
>4. Check if the output is what we want in the staging area
>
>5. Go to the Web-Ui and release all changes at once (Could be a problem
>that you release stuff someone else is currently working on, but I guess
>that's a more theoretical problem)
>

I wouldn't mind getting rid of that step 5 in the current workflow, so if
there are enough volunteers to re-create our site in Git that's fine with
me.
Interestingly, I just saw on another list that a supposed advantage of the
current workflow is that non-committers can use ASF CMS and its web UI to
make changes.  Collecting doc changes from non-committers might be a good
thing.  Our wiki has a separate account system that allows us to do that
as well.  But would anyone in the community want to leverage that?  Maybe
using the Web UI is old-school and submitting pull requests is sufficient.

So, in sum, no objections from me but I doubt I'll be much help on
finishing the port.  I am, however, curious as to how this will impact
Nick.  I think he was in-progress on a web-site revamp.

Thanks,
-Alex

Is reflection supported? More general, how could I tell if one feature is supported?

[Pan Li]

Hi guys
We are working on one FlexJS application, it looks like the refection utils
in Flex are all missing in last FlexJS. We had switched to other approach
so we don't need it right now. but here are my questions:
1 The last api document doesn't have classes of refection utils, but some
other Flex classes are also not existing. Can I assume they are
unsupported? But the api document is also missing some top level classes.
Is there some rule to define which class should be included in api
document? It may be very obvious to advanced FlexJS users, but it is very
confusing to anyone new to FlexJS.

2 Is there plan to support reflection later?

3 More importantly, how could I know if one feature is fully support in
last FlexJS without writing test code? Is there some over all document of
what is supported? Again it should be very obvious to advanced FlexJS
users, but to us new to FlexJS, one simple feature list can literally save
weeks of work.


My Apache Flex community contribution is working on the open source
Moonshine-IDE.com for FlexJS.

Re: [FlexJS] 'new int()' causes problem in FlexJS 0.7

[Alex Harui]

On 10/13/16, 9:39 PM, "Pan Li"  wrote:

>
>
>Hi Alex
>there is no reason to use "new". I am asking this because we have old Flex
>code to migrate to FlexJS, and I noticed a difference

OK, well I made a change to the compiler to generate a call to
org.apache.flex.utils.Language._int().  Should be in the next nightly
build in about 3 hours from now.

Thanks,
-Alex

Re: Current FlexJS license/notice issues

[Alex Harui]

On 10/13/16, 11:55 PM, "Justin Mclean"  wrote:

>Hi,
>
>So I contacted both parties with pull requests a week ago and have
>received no reply.
>
>For FlatUI that's not so surprising as there was no reply to another
>licensing question asked by Alex way back in March and there very little
>activity on the project. The pull request contains a LICENSE file,
>headers and I also nicely asked them to confirm copyright belongs to them
>and not the contributors. Given there's no reply my plan is to go ahead
>as per per the discussion on legal discuss I'll add the header / license
>without the copyright line.
>
>For openfl I’ve also receive any reply and again as per the discussion on
>legal discuss I’ll go ahead and add the header.
>
>Are there any objections to the above? Or anything else people want to
>add?

I'd give them more than a week to respond.  IMO, no urgency here.
>
>Alex how is progress with the CreateJS licensing/header issue? Have you
>contacted CreateJS yet?

I have not contacted CreateJS, but have started the process of getting
approved by Adobe folks to contact them.  Not sure how long that will take.

-Alex

RE: [Discuss] What's keeping the others from participating?

[Josh Tynjala]

Don't these languages transpile their features down to ES5, where they
aren't supported natively either? Why can't we do the same for SWF output?
I think Alex was trying to suggest this, rather than dismissing you, but
maybe it wasn't clear enough.

Looking ahead, I personally see the Flash runtimes becoming less and less
important for FlexJS. For many developers, I don't see them building SWFs
ever, even for debugging (sorry Alex, but I don't think many will bother to
do that...). Most people will probably be deploying only the JS version to
production, and if we allow them to output modern JS, these features can
even be fully native.

Try not to feel too held back by Flash, Jason. We can either polyfill for
SWF or even make certain new language features JS-only.

- Josh

On Oct 14, 2016 4:50 PM, "Jason Taylor"  wrote:

> "TypeScript and Dart for JS all run on top of JS, so my understanding is
> that any new language constructs they offer can be implemented on top of
> Flash as well, although you might give up runtime type-checking for those
> new language features."
>
> How would you implement async / await and parallel programming features on
> top of flash when the flash runtime in no way supports those types of
> constructs.  Again Alex you continue to dismiss these features, while those
> of us that program in these features daily will dismiss FlexJS in time if
> the future roadmap dosen't include this.  It's way way way more important
> than you seem to believe.
>
> ~ JT
>
>
> -Original Message-
> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Thursday, October 13, 2016 3:37 PM
> To: dev@flex.apache.org
> Subject: Re: [Discuss] What's keeping the others from participating?
>
>
>
> On 10/13/16, 3:20 PM, "Jason Taylor"  wrote:
>
> >Hi Harbs, I honestly don't see how the language can move forward when
> >the goal of FlexJS is to be able to compile to swf.  As long as we are
> >stuck with that baggage implementing async / await and other parallel
> >processing operations won't be possible without breaking the swf
> >compatibility and fracturing FlexJS.  That's where the crux of my
> >disagreement with the team is.  I don't believe compiling to swf is
> >important in the long term, and by binding ourselves to that we are
> >limiting out future drastically.  In a few years I don't think an
> >application developer will be willing to switch framework platform
> >without async / await, generics, or lamda's.  I am excited about
> >FlexJS, but honestly I hope it's ported over to a better language system
> like
> >typescript or dart.   The world needs a great rapid application
> >development framework with a declarative UI language, but the world
> >dosen't need SWF's in the future.
> >
>
> Compiling to SWF isn't a requirement for FlexJS.  I still think it is a
> good thing so all our current SWCs can run as SWF.  Having runtime
> type-checking is important as applications grow in complexity and are
> developed by remote development teams.
>
> But even if it was a requirement, TypeScript and Dart for JS all run on
> top of JS, so my understanding is that any new language constructs they
> offer can be implemented on top of Flash as well, although you might give
> up runtime type-checking for those new language features.
>
> And there is nothing stopping anyone from building a version of the
> compiler that handles TS or Dart instead of AS.  Its all open-source.
>
> Thanks,
> -Alex
>
>

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,

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,

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,

> 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: Current FlexJS license/notice issues

[Justin Mclean]

Hi,

So I contacted both parties with pull requests a week ago and have received no 
reply.

For FlatUI that's not so surprising as there was no reply to another licensing 
question asked by Alex way back in March and there very little activity on the 
project. The pull request contains a LICENSE file, headers and I also nicely 
asked them to confirm copyright belongs to them and not the contributors. Given 
there's no reply my plan is to go ahead as per per the discussion on legal 
discuss I'll add the header / license without the copyright line.

For openfl I’ve also receive any reply and again as per the discussion on legal 
discuss I’ll go ahead and add the header.

Are there any objections to the above? Or anything else people want to add?

Alex how is progress with the CreateJS licensing/header issue? Have you 
contacted CreateJS yet?

Thanks,
Justin

Re: [FlexJS] Working on a MDL branch

[OmPrakash Muppirala]

On Fri, Oct 14, 2016 at 10:25 AM, Carlos Rovira 
wrote:

> Hi,
>
> I'm trying to setup a MDL library to start making some components with that
> look and feel.
> I'm following the Flat library project indications, and right now I'm
> building it ok with maven (didn't test Ant, but as a copy/paste from Flat,
> I think it should work as well).
>
> Then I tried in a sample project. Again, new dependencies set and mdl
> declarations are working, but result is not looking as I expect, maybe due
> to some low level constructions that I still doesn't dominate (mainly the
> internals in the "createElement():WrappedHTMLElement" overload, that I
> want
> to try to give some love today as I get a bit more time.
>
> Ok, from here,...I'm still trying to understand more things... for example:
>
> 1.- MDL requires some CSS files to be linked. I'm using it with
> -html-template tag in the example project, but, maybe this should be
> provided by the MDL.swc ? if so, why could we do this?
>
> 2.- To start implementing components, maybe it'd be better that someone
> review what I'm doing (to avoid work in things that not conform to
> standards setup here). Maybe I should upload the branch for people (Maybe
> Alex, Peter,...) to take a look?
>
> 3.- I started trying to make a simple Colored Fab MDL button... (as
> described here https://getmdl.io/components/index.html#buttons-section)
>
> and find that using a simple mxml declaration almost worked (it's not
> right, only an approximation, since I can't write "low level" HTML in MXML
> like an  with HTMLElement). So, this:
>
> 
> 
>
> Shows a pink circle button, without icon.
>

Sounds like a fantastic first step :-))


>
> My MDL button has the following createElement code:
>
> /**
>  * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
>  * @flexjsignorecoercion HTMLButtonElement
>  */
> override protected function createElement():WrappedHTMLElement
> {
> element = button = document.createElement('button') as
> HTMLButtonElement;
> button.className = 'mdl-button mdl-js-button mdl-button--fab
> mdl-button--colored';
>
> positioner = element;
> positioner.style.position = 'relative';
> (button as WrappedHTMLElement).flexjs_wrapper = this;
> element.flexjs_wrapper = this;
>
> return element;
> }
>
> and I'm using at my example project : 
>
> But instead to throw the pink empty circle button as the MXML example, it
> shows a normal button as if my declaration was  (the same
> indeed)
>
> someone knows where I could be failing ?
>

Sounds like some manifest.xml file has not been updated.

I don't know the exact errors, but if I may suggest another option - just
create these new buttons, etc. as custom components in your FlexJS
project.  We can worry about making it a proper FlexJS library project
later.



>
> Thanks
>
> PD: I saw Justin posting about MDL license, I don't want to integrate MDL
> in the project, instead, I want to declare external links to use them, if
> this is not right I think there should be other methods to be license
> compliant...
>

I think you should be fine with this approach.

Thanks for taking this initiative.   Very exciting :-)

Regards,
Om


>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>

[FlexJS] Working on a MDL branch

[Carlos Rovira]

Hi,

I'm trying to setup a MDL library to start making some components with that
look and feel.
I'm following the Flat library project indications, and right now I'm
building it ok with maven (didn't test Ant, but as a copy/paste from Flat,
I think it should work as well).

Then I tried in a sample project. Again, new dependencies set and mdl
declarations are working, but result is not looking as I expect, maybe due
to some low level constructions that I still doesn't dominate (mainly the
internals in the "createElement():WrappedHTMLElement" overload, that I want
to try to give some love today as I get a bit more time.

Ok, from here,...I'm still trying to understand more things... for example:

1.- MDL requires some CSS files to be linked. I'm using it with
-html-template tag in the example project, but, maybe this should be
provided by the MDL.swc ? if so, why could we do this?

2.- To start implementing components, maybe it'd be better that someone
review what I'm doing (to avoid work in things that not conform to
standards setup here). Maybe I should upload the branch for people (Maybe
Alex, Peter,...) to take a look?

3.- I started trying to make a simple Colored Fab MDL button... (as
described here https://getmdl.io/components/index.html#buttons-section)

and find that using a simple mxml declaration almost worked (it's not
right, only an approximation, since I can't write "low level" HTML in MXML
like an  with HTMLElement). So, this:




Shows a pink circle button, without icon.

My MDL button has the following createElement code:

/**
 * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
 * @flexjsignorecoercion HTMLButtonElement
 */
override protected function createElement():WrappedHTMLElement
{
element = button = document.createElement('button') as
HTMLButtonElement;
button.className = 'mdl-button mdl-js-button mdl-button--fab
mdl-button--colored';

positioner = element;
positioner.style.position = 'relative';
(button as WrappedHTMLElement).flexjs_wrapper = this;
element.flexjs_wrapper = this;

return element;
}

and I'm using at my example project : 

But instead to throw the pink empty circle button as the MXML example, it
shows a normal button as if my declaration was  (the same
indeed)

someone knows where I could be failing ?

Thanks

PD: I saw Justin posting about MDL license, I don't want to integrate MDL
in the project, instead, I want to declare external links to use them, if
this is not right I think there should be other methods to be license
compliant...

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: AW: [Discuss] What's keeping the others from participating?

[Alex Harui]

On 10/13/16, 2:42 PM, "Christofer Dutz"  wrote:
>What do you think? (yes even Alex ... I guess you can come out now ;-)
>

I agree with Chris that is great to hear this feedback.

Roadmaps, schedules, priorities are just plain difficult in a
volunteer-driven project.  As you can see from several responses, folks
just run out of time.  IMO, the one thing I think will help us most is
getting some FlexJS apps into production.  That's why Harbs and Yishay
often get quicker responses from me.  If anybody else can get going on
trying to get a FlexJS app into production, they will also get priority on
my list.  Yes, it is a rough and bumpy road right now, but on the other
hand, you will hopefully get better response time from the other
committers on your issues, which is sort of like free engineering
resources.

It is true as Piotr pointed out that it is hard for me to see where the
holes are since I am under-the-hood so much.  I know there is agreement
that documentation is lacking, but I am still not clear on what words we
could write and where we could publish them that would make the biggest
difference.  There is no way we can quickly replace the entire body of
written information about Flex, so I think we need to find the highest
value information and figure out how best to publish it.  So I would
appreciate continued discussion on that.  For those of you who responded
on this thread and have time, it would help me if you can add the next
level of detail by filling in the template "such as , that would be
solved by .", or "such as , but when using the Flex SDK I get
unstuck by ."

In other words:  "I tried to do something advanced, such as ..., but got
stuck, and that would be solved by ..." or
"I tried to do something advanced, such as ..., but got stuck, but when
using the Flex SDK I get unstuck by  ..."


One more thing:  The community also could use at least one more
independent consultant who understand FlexJS.  I've been asked twice to
sit down with a company considering FlexJS and help them estimate what the
porting effort would be.  I can't do that without a lot of hassle due to
employee agreement restrictions.  Those companies have subsequently
decided not to go with FlexJS because there isn't someone they can bring
in to guide them through the process.

Thanks,
-Alex

Re: [FlexJS] How to output

[Carlos Rovira]

Hi Alex,

without doubt these are great ideas, since my understanding is that,
although FlexJS should in most cases hide in components the complexity os
HTML/JS internals, many times people would want to declare "low level" JS.
To create those components, I'm not ready enough. I'm still trying to
generate an MDL project, and I have something compiling but not working as
expected in a local branch generated by me.



2016-10-13 23:49 GMT+02:00 Alex Harui :

> Josh is right that you currently can't, but I'm not sure the reason is
> about MXML being a higher abstraction layer.
>
> IMO, the issue is about how FalconJX transpiles MXML.  It creates a simple
> data structure and the data interpreter just takes the classes mapped to
> the tag names and tries to instantiate them.  HTMLElement doesn't seem to
> allow direct instantiation.  It seems to want us to call
> document.createElement.  I suppose we could change the interpreter to
> check for HTMLElements and instantiate them differently.
>
> The FlexJS components that MXML currently supports all wrap HTMLElements.
> I would have not wrapped HTMLElement if HTMLElement supported
> instantiation via "new" and more importantly, supported subclassing via
> "new", since MXML essentially creates a subclass of the top tag in an MXML
> file.  If there is a way around these limitations, it would seriously
> change the way we write the FlexJS framework.
>
> So, right now, you could create FlexJS components that wrap each and every
> HTMLElement.  We just haven't bothered for the low-level text-oriented
> elements.  I still claim it will be faster to deal with them as innerHTML.
>  Otherwise a lot of wrapping code will run to establish the same DOM.
> Feel free to create those components if you want to.
>
> I haven't tried it, but hopefully the FlexJS components support
> defaultProperty properly.  Maybe the compiler needs additional smarts
> around defaultProperty so you can do:
>
> 
>   Some Header
>   This is some text.
> 
>
> And that would map the contents to the html property (it might map to the
> text property today, not sure).
>
> HTH,
> -Alex
>
>
>
> On 10/13/16, 2:22 PM, "Josh Tynjala"  wrote:
>
> >You can't. Think of MXML as being at a higher abstraction layer. It
> >doesn't
> >know anything about HTML or the Flash display list.
> >
> >- Josh
> >
> >On Thu, Oct 13, 2016 at 2:09 PM, Carlos Rovira <
> >carlos.rov...@codeoscopic.com> wrote:
> >
> >> Thanks for the various responses, many useful.
> >>
> >> One more thing: Can I use HTMLElement in MXML. I'm trying without luck:
> >>
> >> 
> >>
> >> Thanks
> >>
> >> 2016-10-13 22:25 GMT+02:00 Alex Harui :
> >>
> >> > I think we need more context to answer this question.
> >> >
> >> > From MXML, you should be able to put "simple" HTML as the value of
> >> > Label.html, Button.html, TextInput.html and hopefully any other FlexJS
> >> > framework component that displays text.  Essentially, we want all
> >>FlexJS
> >> > UI widgets to work with HTML as well as plain text Strings.  On the
> >>SWF
> >> > side, the HTML support is currently limited by flash.text.TextField.
> >>On
> >> > the JS side, the components should just be setting innerHTML.
> >> >
> >> > If you are writing AS to transpile to low-level JS, then as others
> >> > answered you can create HTMLxxxElements and work with them, or also
> >>just
> >> > set the innerHTML of some element.
> >> >
> >> > I still have dreams of a component set for FlexJS with components
> >>such as
> >> > "I" so you could essentially in-line HTML with the rest of your MXML,
> >>but
> >> > that will be a bunch of work on the SWF-side, and probably not nearly
> >>as
> >> > efficient as havin browser take raw HTML as innerHTML.
> >> >
> >> > HTH,
> >> > -Alex
> >> >
> >> > On 10/13/16, 11:55 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >> > Rovira"  >> > carlos.rov...@codeoscopic.com> wrote:
> >> >
> >> > >Hi,
> >> > >
> >> > >I'm trying to output  html tag, I think it should be something
> >>like
> >> > >HTMLIElement or something.
> >> > >Btw, Where I could find the HTMLInputElement, HTMLSpanElement and
> >> others?
> >> > >
> >> > >Thanks
> >> > >
> >> > >--
> >> > >
> >> > >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
> >> > 

AW: [Website] Progress on the Website-Generation topic

[Christofer Dutz]

Hi Maxim,


I initially setup the fluido skin, but that is more a skin for the normal 
maven-style pages. Generating our website with that would look sort of 90s or 
max early 2000s ;-)


The cool thing with the reflow-skin is that it's a reactive version that 
adjusts to mobile devices nicely and allows us to auto-generate something 
looking very similar to our current Website.


Chris


Von: Maxim Solodovnik 
Gesendet: Freitag, 14. Oktober 2016 11:54:40
An: dev@flex.apache.org
Betreff: Re: [Website] Progress on the Website-Generation topic

On Fri, Oct 14, 2016 at 4:02 PM, Christofer Dutz 
wrote:

> Hi Om,
>
>
> I think that approach is probably the best ... I did encounter problems
> when running the website from the working directory of Jenkins. Don't know
> why.
>
>
Jenkins is on https:// and scripts are being loaded from CDN via http://
Things like this need to be fixed in final version :(

For our project we are generating site using
https://maven.apache.org/skins/maven-fluido-skin/
Works for us :)


> The template is configured in the site.xml document, as this configures
> the the reflow themes built-in template. You can see all the options here:
>
> http://andriusvelykis.github.io/reflow-maven-skin/skin/components.html
>
>
> The toc component seems to have this sort of option (offsetTopnav), but
> not the topNav element responsible for the top navigation. I hope this is
> customizable without having to adjust the reflow template itself.
>
>
> But I just stumbled over the bottomNav column feature ... will add that
> right away :-)
>
>
> Another option would be to overwrite the css style by adding the
> declarations to "site.css" but as I said ... I'm no web-developer and I
> sort of feel like wasting days on stuff like that ... so if you know what
> to do, just give it a try.
>
>
> With a simple:
>
>
> mvn clean site
>
>
> you can re-generate the site and have a look at the result in the
> "target/site" directory.
>
>
>
> Chris
>
> 
> Von: omup...@gmail.com  im Auftrag von OmPrakash
> Muppirala 
> Gesendet: Freitag, 14. Oktober 2016 10:33:28
> An: dev@flex.apache.org
> Betreff: Re: [Website] Progress on the Website-Generation topic
>
> Never mind, I checked out the flex-site.
>
> The proper fix would be to
> 1.  Remove the class "navbar-fixed-top" on the navbar div in all pages.
> 2.  Set padding-top = 0 for body in bootswatch.css
>
> (2) is straightforward.  But it looks like we need to make the change for
> (1) in every page.  Is there a html template that drives all the pages?
>
> Thanks,
> Om
>
> On Fri, Oct 14, 2016 at 1:28 AM, Harbs  wrote:
>
> > The link is lower down in this thread:
> > https://builds.apache.org/view/E-G/view/Flex/job/Flex-
> > Site%20(Maven)/ws/target/site/index.html
> >
> > On Oct 14, 2016, at 11:07 AM, OmPrakash Muppirala 
> > wrote:
> >
> > > Where can I find this site?
> > >
> > > It sounds like the nav bar has CSS setting position: sticky;
> > > Either that, or the position of the nav bar is being translated in an
> > > onScroll event handler in javascript.
> > >
> > > Thanks,
> > > Om
> > >
> > > On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz <
> > christofer.d...@c-ware.de
> > >> wrote:
> > >
> > >> If someone knows bootstrap good enough to eventually help me with the
> > >> position of the navigation bar? Currently it's stuck to the top no
> > matter
> > >> where you scroll to. I would prefer it to have the Flex and Apache
> logo
> > >> above (like in the current version) but as soon as you scroll down and
> > the
> > >> header hit's the top of the browser window, it stays there and remains
> > >> visible. I know I have seen this behavior but I simply don't know the
> > CSS
> > >> magic I would have to apply here ;-)
> > >>
> > >>
> > >> So if anyone here knows this stuff, please come forward and help me
> get
> > >> this site a little more into shape :-)
> > >>
> > >>
> > >> Chris
> > >>
> > >> 
> > >> Von: Justin Mclean 
> > >> Gesendet: Freitag, 14. Oktober 2016 09:44:27
> > >> An: dev@flex.apache.org
> > >> Betreff: Re: [Website] Progress on the Website-Generation topic
> > >>
> > >> Hi,
> > >>
> > >>> So has anyone else had a look at the newly generated documentation in
> > >> the flex-site.git "maven-site" branch? As I mentioned, if you checkout
> > the
> > >> "asf-site" branch you can see the generated output.
> > >>
> > >> Just taking look now. It been a couple of busy weeks with conferences
> > and
> > >> other work (yesterday I assembled, programmed and tested 40 prototype
> > >> devices) and I’m just catching up on a few things.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> >
> >
>



--
WBR
Maxim aka solomax

RE: Re: [FalconJX] Generating ASDoc

[Kessler CTR Mark J]

Oh another thing.  We have some split documentation for our Adobe SDK and 
Apache SDK ASDocs.  What did we come up with before for merging the two in some 
fashion?


-Mark

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] Working on a MDL branch

[Carlos Rovira]

Ok, just pushed to branch /feature/mdl

my example project is out the examples. Do you think I should create an
examples/mdlexample project and upload it to the branch as well?

Thanks

2016-10-14 20:42 GMT+02:00 Carlos Rovira :

> Hi Alex,
>
> I tried the both add and
>
> 
> add
>   
>
> but didn't worked.
>
> I'll be uploading the branch, since I'm equally worried about the low
> level code not working
>
> Thanks!
>
>
>
>
>
>
>
> 2016-10-14 20:19 GMT+02:00 Alex Harui :
>
>>
>>
>> On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira" 
>> wrote:
>>
>> >Hi,
>> >
>> >I'm trying to setup a MDL library to start making some components with
>> >that
>> >look and feel.
>> >I'm following the Flat library project indications, and right now I'm
>> >building it ok with maven (didn't test Ant, but as a copy/paste from
>> Flat,
>> >I think it should work as well).
>> >
>> >Then I tried in a sample project. Again, new dependencies set and mdl
>> >declarations are working, but result is not looking as I expect, maybe
>> due
>> >to some low level constructions that I still doesn't dominate (mainly the
>> >internals in the "createElement():WrappedHTMLElement" overload, that I
>> >want
>> >to try to give some love today as I get a bit more time.
>> >
>> >Ok, from here,...I'm still trying to understand more things... for
>> >example:
>> >
>> >1.- MDL requires some CSS files to be linked. I'm using it with
>> >-html-template tag in the example project, but, maybe this should be
>> >provided by the MDL.swc ? if so, why could we do this?
>>
>> Use the  directive.  See CreateJS.swc's Application class.
>>
>> >
>> >2.- To start implementing components, maybe it'd be better that someone
>> >review what I'm doing (to avoid work in things that not conform to
>> >standards setup here). Maybe I should upload the branch for people (Maybe
>> >Alex, Peter,...) to take a look?
>>
>> Sure, feel free to share the branch.
>>
>> >
>> >3.- I started trying to make a simple Colored Fab MDL button... (as
>> >described here https://getmdl.io/components/index.html#buttons-section)
>> >
>> >and find that using a simple mxml declaration almost worked (it's not
>> >right, only an approximation, since I can't write "low level" HTML in
>> MXML
>> >like an  with HTMLElement). So, this:
>> >
>> >
>> >
>>
>> Did you try:
>>
>> 
>>   add
>> 
>>
>> And/or:
>>
>>
>> 
>>   
>> add
>>   
>> 
>>
>> If neither of those worked, I will take a look.
>>
>>
>> >
>> >Shows a pink circle button, without icon.
>> >
>> >My MDL button has the following createElement code:
>> >
>> >/**
>> > * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
>> > * @flexjsignorecoercion HTMLButtonElement
>> > */
>> >override protected function createElement():WrappedHTMLElement
>> >{
>> >element = button = document.createElement('button') as
>> >HTMLButtonElement;
>> >button.className = 'mdl-button mdl-js-button mdl-button--fab
>> >mdl-button--colored';
>> >
>> >positioner = element;
>> >positioner.style.position = 'relative';
>> >(button as WrappedHTMLElement).flexjs_wrapper = this;
>> >element.flexjs_wrapper = this;
>> >
>> >return element;
>> >}
>> >
>> >and I'm using at my example project : 
>> >
>> >But instead to throw the pink empty circle button as the MXML example, it
>> >shows a normal button as if my declaration was  (the same
>> >indeed)
>> >
>> >someone knows where I could be failing ?
>>
>> I don't see any obvious problems.  I would examine the DOM in the browser
>> debugger and make sure the CSS got loaded and the className is properly
>> set on the HTMLButtonElement.  I'm wondering if the className gets reset
>> by the framework somehow.  Although note that setting the className on the
>> outer button class that wraps the HTMLButtonElement should set the
>> className on the button element.
>>
>> HTH,
>> -Alex
>>
>>
>
>
> --
>
> 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.
>
>


-- 

Carlos Rovira
Director General
M: +34 

Re: [FlexJS] Working on a MDL branch

[Carlos Rovira]

Hi Om,

just did what you propose and still shows the same:

1.- copy the class org.apache.flexjs.mdl to my test project
2.- removed old code
3.- instantiate using:

xmlns:mdl="org.apache.flex.mdl.*"

and



but again the result is better using the js:Button with className than my
low level MDL button that shows as a standard button.
It's like the .className is doing nothing...



2016-10-14 19:39 GMT+02:00 OmPrakash Muppirala :

> On Fri, Oct 14, 2016 at 10:25 AM, Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > I'm trying to setup a MDL library to start making some components with
> that
> > look and feel.
> > I'm following the Flat library project indications, and right now I'm
> > building it ok with maven (didn't test Ant, but as a copy/paste from
> Flat,
> > I think it should work as well).
> >
> > Then I tried in a sample project. Again, new dependencies set and mdl
> > declarations are working, but result is not looking as I expect, maybe
> due
> > to some low level constructions that I still doesn't dominate (mainly the
> > internals in the "createElement():WrappedHTMLElement" overload, that I
> > want
> > to try to give some love today as I get a bit more time.
> >
> > Ok, from here,...I'm still trying to understand more things... for
> example:
> >
> > 1.- MDL requires some CSS files to be linked. I'm using it with
> > -html-template tag in the example project, but, maybe this should be
> > provided by the MDL.swc ? if so, why could we do this?
> >
> > 2.- To start implementing components, maybe it'd be better that someone
> > review what I'm doing (to avoid work in things that not conform to
> > standards setup here). Maybe I should upload the branch for people (Maybe
> > Alex, Peter,...) to take a look?
> >
> > 3.- I started trying to make a simple Colored Fab MDL button... (as
> > described here https://getmdl.io/components/index.html#buttons-section)
> >
> > and find that using a simple mxml declaration almost worked (it's not
> > right, only an approximation, since I can't write "low level" HTML in
> MXML
> > like an  with HTMLElement). So, this:
> >
> > 
> > 
> >
> > Shows a pink circle button, without icon.
> >
>
> Sounds like a fantastic first step :-))
>
>
> >
> > My MDL button has the following createElement code:
> >
> > /**
> >  * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
> >  * @flexjsignorecoercion HTMLButtonElement
> >  */
> > override protected function createElement():WrappedHTMLElement
> > {
> > element = button = document.createElement('button') as
> > HTMLButtonElement;
> > button.className = 'mdl-button mdl-js-button mdl-button--fab
> > mdl-button--colored';
> >
> > positioner = element;
> > positioner.style.position = 'relative';
> > (button as WrappedHTMLElement).flexjs_wrapper = this;
> > element.flexjs_wrapper = this;
> >
> > return element;
> > }
> >
> > and I'm using at my example project : 
> >
> > But instead to throw the pink empty circle button as the MXML example, it
> > shows a normal button as if my declaration was  (the same
> > indeed)
> >
> > someone knows where I could be failing ?
> >
>
> Sounds like some manifest.xml file has not been updated.
>
> I don't know the exact errors, but if I may suggest another option - just
> create these new buttons, etc. as custom components in your FlexJS
> project.  We can worry about making it a proper FlexJS library project
> later.
>
>
>
> >
> > Thanks
> >
> > PD: I saw Justin posting about MDL license, I don't want to integrate MDL
> > in the project, instead, I want to declare external links to use them, if
> > this is not right I think there should be other methods to be license
> > compliant...
> >
>
> I think you should be fine with this approach.
>
> Thanks for taking this initiative.   Very exciting :-)
>
> Regards,
> Om
>
>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>



-- 

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] Working on a MDL branch

[Carlos Rovira]

Hi Alex,

I tried the both add and


add
  

but didn't worked.

I'll be uploading the branch, since I'm equally worried about the low level
code not working

Thanks!







2016-10-14 20:19 GMT+02:00 Alex Harui :

>
>
> On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira" 
> wrote:
>
> >Hi,
> >
> >I'm trying to setup a MDL library to start making some components with
> >that
> >look and feel.
> >I'm following the Flat library project indications, and right now I'm
> >building it ok with maven (didn't test Ant, but as a copy/paste from Flat,
> >I think it should work as well).
> >
> >Then I tried in a sample project. Again, new dependencies set and mdl
> >declarations are working, but result is not looking as I expect, maybe due
> >to some low level constructions that I still doesn't dominate (mainly the
> >internals in the "createElement():WrappedHTMLElement" overload, that I
> >want
> >to try to give some love today as I get a bit more time.
> >
> >Ok, from here,...I'm still trying to understand more things... for
> >example:
> >
> >1.- MDL requires some CSS files to be linked. I'm using it with
> >-html-template tag in the example project, but, maybe this should be
> >provided by the MDL.swc ? if so, why could we do this?
>
> Use the  directive.  See CreateJS.swc's Application class.
>
> >
> >2.- To start implementing components, maybe it'd be better that someone
> >review what I'm doing (to avoid work in things that not conform to
> >standards setup here). Maybe I should upload the branch for people (Maybe
> >Alex, Peter,...) to take a look?
>
> Sure, feel free to share the branch.
>
> >
> >3.- I started trying to make a simple Colored Fab MDL button... (as
> >described here https://getmdl.io/components/index.html#buttons-section)
> >
> >and find that using a simple mxml declaration almost worked (it's not
> >right, only an approximation, since I can't write "low level" HTML in MXML
> >like an  with HTMLElement). So, this:
> >
> >
> >
>
> Did you try:
>
> 
>   add
> 
>
> And/or:
>
>
> 
>   
> add
>   
> 
>
> If neither of those worked, I will take a look.
>
>
> >
> >Shows a pink circle button, without icon.
> >
> >My MDL button has the following createElement code:
> >
> >/**
> > * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
> > * @flexjsignorecoercion HTMLButtonElement
> > */
> >override protected function createElement():WrappedHTMLElement
> >{
> >element = button = document.createElement('button') as
> >HTMLButtonElement;
> >button.className = 'mdl-button mdl-js-button mdl-button--fab
> >mdl-button--colored';
> >
> >positioner = element;
> >positioner.style.position = 'relative';
> >(button as WrappedHTMLElement).flexjs_wrapper = this;
> >element.flexjs_wrapper = this;
> >
> >return element;
> >}
> >
> >and I'm using at my example project : 
> >
> >But instead to throw the pink empty circle button as the MXML example, it
> >shows a normal button as if my declaration was  (the same
> >indeed)
> >
> >someone knows where I could be failing ?
>
> I don't see any obvious problems.  I would examine the DOM in the browser
> debugger and make sure the CSS got loaded and the className is properly
> set on the HTMLButtonElement.  I'm wondering if the className gets reset
> by the framework somehow.  Although note that setting the className on the
> outer button class that wraps the HTMLButtonElement should set the
> className on the button element.
>
> HTH,
> -Alex
>
>


-- 

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] Working on a MDL branch

[Alex Harui]

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

>Hi,
>
>I'm trying to setup a MDL library to start making some components with
>that
>look and feel.
>I'm following the Flat library project indications, and right now I'm
>building it ok with maven (didn't test Ant, but as a copy/paste from Flat,
>I think it should work as well).
>
>Then I tried in a sample project. Again, new dependencies set and mdl
>declarations are working, but result is not looking as I expect, maybe due
>to some low level constructions that I still doesn't dominate (mainly the
>internals in the "createElement():WrappedHTMLElement" overload, that I
>want
>to try to give some love today as I get a bit more time.
>
>Ok, from here,...I'm still trying to understand more things... for
>example:
>
>1.- MDL requires some CSS files to be linked. I'm using it with
>-html-template tag in the example project, but, maybe this should be
>provided by the MDL.swc ? if so, why could we do this?

Use the  directive.  See CreateJS.swc's Application class.

>
>2.- To start implementing components, maybe it'd be better that someone
>review what I'm doing (to avoid work in things that not conform to
>standards setup here). Maybe I should upload the branch for people (Maybe
>Alex, Peter,...) to take a look?

Sure, feel free to share the branch.

>
>3.- I started trying to make a simple Colored Fab MDL button... (as
>described here https://getmdl.io/components/index.html#buttons-section)
>
>and find that using a simple mxml declaration almost worked (it's not
>right, only an approximation, since I can't write "low level" HTML in MXML
>like an  with HTMLElement). So, this:
>
>
>

Did you try:


  add


And/or:



  
add
  


If neither of those worked, I will take a look.


>
>Shows a pink circle button, without icon.
>
>My MDL button has the following createElement code:
>
>/**
> * @flexjsignorecoercion org.apache.flex.core.WrappedHTMLElement
> * @flexjsignorecoercion HTMLButtonElement
> */
>override protected function createElement():WrappedHTMLElement
>{
>element = button = document.createElement('button') as
>HTMLButtonElement;
>button.className = 'mdl-button mdl-js-button mdl-button--fab
>mdl-button--colored';
>
>positioner = element;
>positioner.style.position = 'relative';
>(button as WrappedHTMLElement).flexjs_wrapper = this;
>element.flexjs_wrapper = this;
>
>return element;
>}
>
>and I'm using at my example project : 
>
>But instead to throw the pink empty circle button as the MXML example, it
>shows a normal button as if my declaration was  (the same
>indeed)
>
>someone knows where I could be failing ?

I don't see any obvious problems.  I would examine the DOM in the browser
debugger and make sure the CSS got loaded and the className is properly
set on the HTMLButtonElement.  I'm wondering if the className gets reset
by the framework somehow.  Although note that setting the className on the
outer button class that wraps the HTMLButtonElement should set the
className on the button element.

HTH,
-Alex