Re: New Flex SDK release

Hi, > There will be still a community Version... Is this also incompatible with > Apache? The 4.7 community version is under a variety of license of which the code and font are under a compatible license [1]. Their documentation isn’t under a compatible license. Hopefully this will be the sa

Icon fonts (was Re: New Flex SDK release)

In morre general terms: While we obviously cannot include content with incompatible licenses, I do think we should make it easy for users who want to use such content with FlexJS. For example, if a user has a license to Font Awesome Pro, it should be easy to do something to their config and jus

Re: Icon fonts (was Re: New Flex SDK release)

Hi guys, Material icons (https://material.io/icons/) is available under Apache License. It can be a serious alternative to Font Awesome. Hope it helps. Regards, Fabrice Montfort 2016-11-03 11:08 GMT+04:00 Harbs : > In morre general terms: > > While we obviously cannot include content with inc

Re: New Flex SDK release

Justin Mclean wrote > I assume we are only using the font files? I think we use the .otf font [1] and variables.less [2]. But latter only as template to create the AS3 constants file [3]. I understand that 4.7 font and code is compatible with Apache so we're probably fine but just out of curiosity

Re: FlexSDK license issue

Dammit ... I which I could build this with Maven ... ;-) Chris Am 03.11.16, 07:37 schrieb "Justin Mclean" : Hi, Turns out it was only used inside tests for Texen in velocity which as far as I can tell is not being used. Velocity and SDK still compile without it and can compile sam

Re: New Flex SDK release

Hi, > Should we also take care of license issues cause we grab [2] and create a > new file of it [3]? [2] is MIT licensed so IMO it wouldn’t hurt it add a pointer of that MIT to our LICENSE file. That way all bases are covered. There is an issue here (similar with certain other 3rd parties) in

Re: New Flex SDK release

One thing I would really be dleighted about, would be, if we could get rid of the patched libraries used in the sdk. However I don’t have any idea what sideeffects this would have. Chris Am 03.11.16, 08:53 schrieb "Justin Mclean" : Hi, > Should we also take care of license issues

Re: New Flex SDK release

Hi, And it turns out this is a know outstanding issue (for a while) and other people have the same issue :-( [1] Justin 1. https://github.com/FortAwesome/Font-Awesome/issues/5281

Re: New Flex SDK release

Hi, > One thing I would really be dleighted about, would be, if we could get rid of > the patched libraries used in the sdk. > However I don’t have any idea what sideeffects this would have. Way back I did look into doing so but was going to be a lot of work for Bartik as Adobe made a large nu

Re: New Flex SDK release

I'm also not a layer and I don't want to trigger another license disucssion here but is it not enough to just add the MIT license text as additional header to the affected files including the required copyright info? MIT license: "The above copyright notice and this permission notice shall be incl

Re: New Flex SDK release

Hi, > I'm also not a layer and I don't want to trigger another license disucssion > here but is it not enough to just add the MIT license text as additional > header to the affected files including the required copyright info? Yes that an option (and given as one on legal discuss). Given the git

Re: New Flex SDK release

>Yes that an option (and given as one on legal discuss). Great! One last question: Should I replace the Apache license header by the MIT one or should I add the MIT header under the Apache license header? Thanks! Olaf -- View this message in context: http://apache-flex-development.247.n4

Re: New Flex SDK release

Hi, > Should I replace the Apache license header by the MIT one or should I add > the MIT header under the Apache license header? Generally the changes have to be extensive to change the header on a file, translation from one language to another generaly doesn’t count. I’m not a lawyer but look

Re: New Flex SDK release

Justin Mclean wrote > I’m not a lawyer but looking at the file I’d use the MIT header only. This is the modified AwesomeUtils.as [1] which includes the update to FontAwesome 4.7 and the MIT licence header that replaces the Apache license header. If this is ok I'll commit it to the origin Flex repo

Re: New Flex SDK release

Hi Justin, Guess I would opt to work on that path, but I’m not going to put up with the build. So probably the path would be to migrate the FlexSDK to be buildable with maven and as soon as I have a stable system with good test coverage, to start cleaning this up. But at the moment I don’t know

Re: New Flex SDK release

Hi, > This is the modified AwesomeUtils.as [1] which includes the update to > FontAwesome 4.7 and the MIT licence header that replaces the Apache license > header. Looks good to me. > Should I commit it to the 4.16.0 branch? Yep when ever you have time to do so that would be great. Thanks, Jus

Re: New Flex SDK release

On 11/3/16, 1:12 AM, "Justin Mclean" wrote: >Hi, > >> One thing I would really be dleighted about, would be, if we could get >>rid of the patched libraries used in the sdk. >> However I don’t have any idea what sideeffects this would have. > >Way back I did look into doing so but was going to b

Installer.xml changes needed (was Re: New Flex SDK release)

Hi, The Adobe AIR SDK 24 is available in beta form at [1] and is incompatible with our installers (both for regular Flex as well as FlexJS). So, our users currently will not be able to use the Installer or Ant to set up with Adobe AIR 24 or later. I have created JIRA issues FLEX-35166 and FLEX-3

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I can take this work up. Depending on how much work this would take and amy available bandwidth, this could take a while. Do you know what exactly needs to be done here? Thanks, Om On Nov 3, 2016 8:54 AM, "Alex Harui" wrote: > Hi, > > The Adobe AIR SDK 24 is available in beta form at [1] and

Re: Installer.xml changes needed (was Re: New Flex SDK release)

On 11/3/16, 9:35 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >I can take this work up. Depending on how much work this would take and >amy available bandwidth, this could take a while. > >Do you know what exactly needs to be done here? Don't know for sure. My guess would

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I still see the zip file available here https://fpdownload.macromedia.com/pub/labs/flashruntimes/air/AdobeAIRSDK.zip On Nov 3, 2016 9:54 AM, "Alex Harui" wrote: > > > On 11/3/16, 9:35 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" > wrote: > > >I can take this work up. Depending on

Re: Installer.xml changes needed (was Re: New Flex SDK release)

And I still see the adl.exe inside the zip file: https://snag.gy/uSrbL5.jpg On Thu, Nov 3, 2016 at 10:10 AM, OmPrakash Muppirala wrote: > I still see the zip file available here > > https://fpdownload.macromedia.com/pub/labs/flashruntimes/ > air/AdobeAIRSDK.zip > > On Nov 3, 2016 9:54 AM, "Alex

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I see links for dmg and exe from here http://labs.adobe.com/downloads/air.html I believe the zip and tar will go away or may not be the latest. Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Thu, Nov 3, 2016 10:10 AM To: dev@flex.apach

[FlexJS] How to change a node at runtime

Hi, I'm implementing a component that could be implemented with different HTML elements. Depending of what we want we could start with "a", "span" or "div". So I would need to replace the node at runtime so users could change the structure maybe with a "type" propoerty. I'm trying to make this wo

Re: Installer.xml changes needed (was Re: New Flex SDK release)

Hmm, I see a dmg for mac and a zip for windows (in the Flex Developers section) Was there any announcement about this change? On Thu, Nov 3, 2016 at 11:11 AM, Alex Harui wrote: > I see links for dmg and exe from here http://labs.adobe.com/ > downloads/air.html > > I believe the zip and tar will

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I also see a ZIP for the Windows SDKs on that page. The only EXE that I see is for the Windows AIR runtime, which isn't what the installer downloads. - Josh On Thu, Nov 3, 2016 at 11:13 AM, OmPrakash Muppirala wrote: > Hmm, I see a dmg for mac and a zip for windows (in the Flex Developers > sec

Re: Installer.xml changes needed (was Re: New Flex SDK release)

Interestingly, I was able to simply unzip the .dmg file and inspect its contents. It simply has a folder called AIR SDK: https://snag.gy/i8gNmu.jpg Also of interest is the fact that I have been using only the .zip files in the NPM FlexJS installer. That seems to work fine with Macs as well. I t

Re: Installer.xml changes needed (was Re: New Flex SDK release)

I thought there were symlinks for Mac. Maybe it doesn't matter for what we use it for. Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: OmPrakash Muppirala Date: Thu, Nov 3, 2016 11:31 AM To: dev@flex.apache.org; Subject:Re: Installer.xml changes needed (was Re:

Re: [FlexJS] How to change a node at runtime

Ok, I get it with something like this: var link:HTMLElement = document.createElement('a') as HTMLElement; element.parentNode.replaceChild(link, element); but after that component gets a bit crazy. I finaly use: positioner = element; positioner.style.position = 'relative'; element.flexjs_wrapper

Re: [FlexJS] How to change a node at runtime

forgot to mention that I use element = link as WrappedHTMLElement; between both code blocks 2016-11-03 20:08 GMT+01:00 Carlos Rovira : > Ok, I get it with something like this: > > var link:HTMLElement = document.createElement('a') as HTMLElement; > element.parentNode.replaceChild(link, element)

Re: New Flex SDK release

> If there are any issues you want to see fixed in this release please add them > to this subtask [2] in the release JIRA. I'd like to get FLEX-34880 done for this release. If I work on it in the weekend, would it be too late, you think?

Maybe a bug with external CSS not linking

Hi, I'm trying to assign a CSS file without luck. The same rules in a CSS file in framework component library works, but not in the project example I saw that no other example project is using an external CSS file. I used in pom.xml something like this in configuration

Re: Installer.xml changes needed (was Re: New Flex SDK release)

OK, my sources say that ZIP format will be around for a while. But don't we have to switch to using DMG for Mac? I don't know if the ZIP has Mac versions of ADL and ADT in it. And if we do just end up launching the DMG, we might want to create a path for launching an EXE in case there is an issu

Re: Maybe a bug with external CSS not linking

Hi Carlos, is only for COMPC building libraries. For applications, I think we want the following to work: It appears to work for FlexJSStore example. Or are you looking for some other configuration? Thanks, -Alex On 11/3/16, 12:33 PM, "carlos.rov...@gmail.com on behalf of Carlos Ro

Re: Installer.xml changes needed (was Re: New Flex SDK release)

Even in the case of the .dmg, I think we should just unzip it and extract the AIR SDK. I don't think we want to launch it. On Thu, Nov 3, 2016 at 1:28 PM, Alex Harui wrote: > OK, my sources say that ZIP format will be around for a while. But don't > we have to switch to using DMG for Mac? I d

Re: New Flex SDK release

Hi, > I'd like to get FLEX-34880 done for this release. If I work on it in > the weekend, would it be too late, you think? That will be fine, it will be a little while before we make a release candidate and vote on it. Thanks, Justin

Re: Maybe a bug with external CSS not linking

Hi Alex, perfect, that works. No other config is needed (at least by me), thanks. btw, don't know if url works ok, I have to set: since this doesn't work: is this right? Thanks 2016-11-03 21:22 GMT+01:00 Alex Harui : > Hi Carlos, > > is only for COMPC building libraries. > > For appl

Re: Installer.xml changes needed (was Re: New Flex SDK release)

Fine with me as long as that properly allows the executables to run later. I'm not on the latest Mac OS, so I won't be able to test it. -Alex From: "omup...@gmail.com" mailto:omup...@gmail.com>> on behalf of OmPrakash Muppirala mailto:bigosma...@gmail.com>> Date: Thu

[FlexJS][Maven] Missing assets in target folder

Hi Chris, I'm trying to test a simple in MDLExample without luck, something like: is not working. I think the problem is maven is not copying the image asset to to target folder. I get it working with something like this: (reaching it from outside target and from the source project) Mayb

[FlexJS] HTML headings h1 to h6

I was wondering what to do with text heading (h1 to h6) do we have some component for this? If not, should we have a "Heading" component? What do you think? -- Carlos Rovira http://about.me/carlosrovira

Re: Maybe a bug with external CSS not linking

On 11/3/16, 2:52 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Alex, > >perfect, that works. No other config is needed (at least by me), thanks. > >btw, don't know if url works ok, I have to set: > > > >since this doesn't work: > > > >is this right? > >Thanks I think that

Re: [FlexJS][Maven] Missing assets in target folder

On 11/3/16, 3:10 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi Chris, > >I'm trying to test a simple in MDLExample without luck, >something like: > > > >is not working. > >I think the problem is maven is not copying the image asset to to target >folder. > >I get it workin

Re: [FlexJS] HTML headings h1 to h6

On 11/3/16, 3:26 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >I was wondering what to do with text heading (h1 to h6) >do we have some component for this? If not, should we have a "Heading" >component? >What do you think? IMO, we should have six components that thinly wrap

Re: [FlexJS][Maven] Missing assets in target folder

Could the -html-template be expanded to support more than a single file? More like the Flex SDK? That would be a good way to include images, CSS, and other stuff. - Josh On Thu, Nov 3, 2016 at 3:34 PM, Alex Harui wrote: > > > On 11/3/16, 3:10 PM, "carlos.rov...@gmail.com on behalf of Carlos Rov

Re: [FlexJS] Optimizing the maven build ... success ...

Hi Chris, I'm using the "closure-classpath-sources" branch, taking into account the fast it makes me build, I was wondering what's the problem to merge it to develop. Hope it was a matter of tiny things and could be integrated soon. Thanks Carlos 2016-10-31 16:40 GMT+01:00 Alex Harui : > > > O

[FlexJS] Apply style to component

Hi, could I have some style in a .css like this: demo-card-wide.mdl-card { width: 512px; } .demo-card-wide > .mdl-card__title { color: #fff; height: 176px; background: url('../../../../src/main/resources/Unknown.jpeg') center / cover; } .demo-card-wide > .mdl-card__menu { color: #fff; }

Re: [FlexJS][Maven] Missing assets in target folder

On 11/3/16, 3:54 PM, "Josh Tynjala" wrote: >Could the -html-template be expanded to support more than a single file? >More like the Flex SDK? That would be a good way to include images, CSS, >and other stuff. Does the regular Flex SDK have some way to copy "other stuff"? I thought the IDEs ha

Re: [FlexJS] Apply style to component

I'd have to really think through this, but at a quick glance, isn't demo-card-wide.mdl-card an advanced selector that is looking for a className mdl-card inside a className demo-card-wide? Also, I think our default container wraps the children in another div in order to manage complex c

Re: [FlexJS][Maven] Missing assets in target folder

You're probably right. It may not be the compiler. Regardless, I'm pretty sure that whatever it is that handles templates for Flex SDK apps supports a directory of files. I think that would be very useful for HTML apps so that the index.html file can optionally come with supporting files like CSS a

[FlexJS] Container.numElements is not working

platform: Mac OS 10.4; FlexJS 0.7 numElements of the UI element Container doesn't work, it can be reproduced by this code snippet: Run it in FlexJS0.7 in javascript or awf mode, it will

Re: [FlexJS] Container.numElements is not working

Thanks. Please try the nightly 0.8.0 build. It should be fixed already. -Alex On 11/3/16, 7:55 PM, "Pan Li" wrote: > > >platform: Mac OS 10.4; FlexJS 0.7 > >numElements of the UI element Container doesn't work, it can be reproduced >by this code snippet: > > > > >

Re: [FlexJS] How to change a node at runtime

Hi Carlos, We've been working under the assumption that the element doesn't change in run-time, just like you wouldn't change Element.tagName in JS. Why do you need that option? In which scenario would it not be better to just replace the component with a different one with a different element?

Re: MDL Tweet

Thanks Chris, Carlos and Josh! I will try VS Code and get back to you with the results. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/MDL-Tweet-tp56042p56234.html Sent from the Apache Flex Development

Re: [FlexJS] Optimizing the maven build ... success ...

Hi Carlos, I didn’t want to merge it back without getting confirmation, that it doesn’t break things for all non-maven builds. I think there still is an issue, which I will have to figgure out as soon as I can find the time (Unfortunatlely I currently have a paid-project which I actually have t