If you want to make an example in flex-asjs repo in examples/flexjs that
would be helpful.
On 10/14/16, 11:54 AM, "carlos.rov...@gmail.com on behalf of Carlos
>Ok, just pushed to branch /feature/mdl
> 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
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.
2016-10-14 22:27 GMT+02:00 Alex Harui
I took a look at the page and it looks good , but it would be nice it was
more in line with Apache trademark policy. 
- 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
> 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 . CC-A is "category B” license  which means
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
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:
On Fri, Oct 14, 2016 at 4:02 PM, 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
Jenkins is on https:// and scripts are
> 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
> 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
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
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:
>> I'm in the process of trying to see how
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:
The link is lower down in this thread:
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
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
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.
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
On Fri, Oct 14, 2016 at 12:59 AM, Christofer Dutz wrote:
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.
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
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
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
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
> 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
"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
How would you implement async / await and
The MIT license text in question can be found here 
Justin, please see my earlier response. We dont need to worry about the
license if we are using scss to generate the css.
On Fri, Oct 14, 2016 at 3:33 PM, Justin Mclean
> The MIT license text in question can be found here 
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
> Hi Maxim,
> I initially setup the fluido skin, but
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
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
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
On 10/13/16, 9:39 PM, "Pan Li" wrote:
>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
On 10/13/16, 11:55 PM, "Justin Mclean" wrote:
>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
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
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.
On Oct 14, 2016 4:40 PM, "Justin
Depend on how MDL is going to be used there's a couple of minor issues that
- repo is missing a NOTICE file
- this file is MIT licensed  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
Also this  from JimJag.
> 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
So I contacted both parties with pull requests a week ago and have received no
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
On Fri, Oct 14, 2016 at 10:25 AM, Carlos Rovira
> 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
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
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
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
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
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
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?
2016-10-14 9:40 GMT+02:00 Justin Mclean :
> > I'm in the process of
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?
2016-10-14 20:42 GMT+02:00 Carlos Rovira :
> Hi Alex,
> I tried the both add
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:
but again the result is better using the js:Button with className than my
low level MDL
I tried the both add and
but didn't worked.
I'll be uploading the branch, since I'm equally worried about the low level
code not working
2016-10-14 20:19 GMT+02:00 Alex Harui :
> On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on
On 10/14/16, 10:25 AM, "carlos.rov...@gmail.com on behalf of Carlos
>I'm trying to setup a MDL library to start making some components with
>look and feel.
>I'm following the Flat library project
Mail list logo