RE: [URL Verdict: Neutral][Non-DoD Source] Re: Retiring the project
The problem may also be that the people who are using the Flex may not be subscribed to the mailing lists. We found there were people coming out of the woodwork when flash was going away, but that only happened because of the cliff that was looming for people targeting flash player. To include the discussion of who might have changed to Air. Are there are libraries / frameworks that rely on Flex as a base? Side note: we do not use Flex anymore we migrated all of our Flex applications to our custom library on Royale. -Mark K -Original Message- From: Olaf Krüger Sent: Thursday, June 9, 2022 02:19 To: dev@flex.apache.org Subject: [URL Verdict: Neutral][Non-DoD Source] Re: Retiring the project Hi, > That document is for podlings — not for TLPs. Thanks for the hint, maybe this is the right resource, not sure: https://attic.apache.org/ I found this from the Apache PMC overview, see [1]: "In summary, the only reason for a project to move to the Attic is lack of oversight due to an insufficient number of active PMC members. Note that going to the Attic is not necessarily a bad thing: it's merely a reflection that there isn't currently an active community to manage the project. It's also a clear way to set the right expectations for users of the project's code." However, it looks like the project is still more relevant than it seems and as Harbs said, if we are still enough PMCs, we could leave everything as it is. So, can we really guarantee to have at least 3 active PMC members? Please reply if you're still commited to be an active Flex PMC member! I didn't write any Flex/AS3 code for more than 2 or 3 years so please do not rely on me for another couple of years ;-) As long as we're still enough PMCs I think everything is fine. We should add a note to the board report that the project is silent but enough PMCs take care of if. Thanks, Olaf [1] https://www.apache.org/dev/pmc.html#move-to-attic On 2022/06/08 06:35:10 Harbs wrote: > That document is for podlings — not for TLPs. > > There’s nothing wrong with a project being in maintenance mode as long as > there’s enough of a PMC active. > > I think we still have enough of a PMC to maintain the project and I think > people are still using Flex. > > Harbs > > > On Jun 8, 2022, at 8:26 AM, Olaf Krüger wrote: > > > > Hi guys, > > > > we should thinking about retiring the project. > > This seems to be the guideline to retire a project at Apache [1] > > > > It looks like we need a community vote and some volunteers who helps with > > the process of retiring a project. > > > > What do you think? > > > > Thanks, > > Olaf > > > > [1] https://incubator.apache.org/guides/retirement.html > > > >
RE: Flash Player end of life
Justin, Our experience shows Chrome asking to activate flash by right clicking to load the application, but that is not much of a deterrence. In our case we have a standard html file embedding the swf app and not loading the swf directly. It might have something to do with how prominent or given size dedicated to the swf. I think the majority of support will drop in January, mostly based on receiving a new update to your browsers. However, Microsoft will have a bit longer term support [1] mostly directed at enterprise users. [1] https://blogs.windows.com/msedgedev/2020/09/04/update-adobe-flash-end-support/ -Mark K -Original Message- From: Justin Mclean Sent: Thursday, December 3, 2020 00:40 To: dev@flex.apache.org Subject: [Non-DoD Source] Flash Player end of life Hi, I notice on [1] it states this: In December, Chrome 55 will make HTML5 the default experience, except for sites which only support Flash Which I assume means a URL ending .swf? And on [2] it states: Since Adobe is no longer supporting Flash Player after the EOL Date, Adobe will block Flash content from running in Flash Player beginning January 12, 2021 to help secure users’ systems. If this is correct? If so that give a very limited window for "sites which only support Flash” to work. Does anyone know anything different? Thanks, Justin 1. https://blog.google/products/chrome/flash-and-chrome/ 2. https://www.adobe.com/products/flashplayer/end-of-life.html
RE: [Vote] Release flex-dk-converter-maven-extension
+1 -Mark K -Original Message- From: Carlos Rovira Sent: Wednesday, November 13, 2019 4:02 AM To: dev@flex.apache.org Subject: [Non-DoD Source] [Vote] Release flex-dk-converter-maven-extension Hi, This thread is to vote about the release of "flex-dk-converter-maven-extension" piece of code in Apache Flex to simplify Flex and Royale builds. Thanks -- Carlos Rovira http://about.me/carlosrovira
RE: [Non-DoD Source] Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
+1 Especially those old Adobe issues that were imported. To me they are mostly clutter because of the quantity, age, and missing attachments. I would much rather have a clean start. But brining in any new (from a given time range x number of months) wouldn't be a bonus, unless that's an entirely manual process. -Mark K -Original Message- From: Carlos Rovira [mailto:carlosrov...@apache.org] Sent: Wednesday, January 9, 2019 4:32 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Enabling GitHub "Issues" and "Wiki" for flex repositories Hi Olaf, I like your idea. I think going to GitHub is like when we migrate from SVN to GIT, we must go with the times. Is like FlexJS vs Royale wiki. We started a new one with newer info in Royale, but still have useful content from FlexJS that we should not remove and migrate as we can. So for me is ok to star clean on Github and lock JIRA, (or just be able to close or update JIRA content, but be unable to create new ones on JIRA. People working in Flex should now that as part of the things they need to know. If want to create a new ticket, first check JIRA, but create from scratch or recreate in Github. This will be an improvement for Flex in the end just my 2... Carlos El mar., 8 ene. 2019 a las 23:18, Olaf Krueger () escribió: > > Are we going to say that we won't fix any of the bugs currently open in > JIRA?... > > My concern is having two active bug bases... > > We maybe could set or treat or freeze JIRA as read-only and could link to > the entire Flex-JIRA from GitHub in order to not losing the history. > If somebody is going to fix one of those existing JIRA issues we could > simply recreate it manually as a GitHub issue. > If somebody will file a new GitHub issue we may want to check if there's a > JIRA duplicate in order to link it from the GitHub issue. > But on the other hand, I don't believe when somebody creates a new JIRA > that > somebody checks if there's already a JIRA duplicate. > > Thoughts? > > Olaf > > > > -- > Sent from: http://apache-flex-development.247.n4.nabble.com/ > -- Carlos Rovira http://about.me/carlosrovira
RE: [Non-DoD Source] Royale Logo
Definitely on the right track. Looks good already. Lower left is clean and just needs some color. Lower right the gradients are a bit off, like you already said you are still working them. -Mark K -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Sunday, September 24, 2017 4:51 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Royale Logo Hi, I've been working this week end on a logo for Royale and want to share my work in progress. Please try the following link: http://royale.codeoscopic.com/wp-content/uploads/2017/09/royale_logo.png The concept is a modern icon logo build with simplicity in mind and with lines and circles that could have multiple uses (black over white, white over black, colored, outlined, special finish...). The example only shows some work at the current state. In need more work to be finished. The logo has various meanings. It's a crown to give the user the main concept of Royale, something magnificent, superb, best in its class...but as well tries to give you some key points of the main composition architecture in Royale, the Strand-Beads concept with a base line (the strand) that conects circles (beads). So my intention is give the possibility of various meanings in one logo while try to keep it simple. The fonts used are "Aclonica" google fonts. The last example is not finished (gradients are not perfectly done yet and other things needs more polish) and is only a possible finish but it's really to show how could it be, but I'm sure I'll be redoing it from scratch, but I must left it for today. Although it's still a work in progress I think is worth it to share it with the community and see reactions and if you think if it will be a good logo or try another concept. So please share your thoughts! Thanks -- Carlos Rovira http://about.me/carlosrovira
RE: [Non-DoD Source] Re: Royale website and domain registration
Same thing now even with an E Royalesdk.com [1] or many others. [1] https://domains.google.com/registrar?s=royalesdk.com -Original Message- From: Andrew Wetmore [mailto:cottag...@gmail.com] Sent: Friday, September 22, 2017 1:10 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Royale website and domain registration Check for RoyaleSDK, with the "e"
RE: Royale website and domain registration
RoyalSDK sounds good. [1] can even get a .Com [1] https://domains.google.com/registrar?s=royalsdk&hl=en -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Friday, September 22, 2017 11:36 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Royale website and domain registration AIUI, royale.io is owned by a squatter and the price STARTS at $199. I haven't tried to buy a domain from a squatter, but I wouldn't be surprised if the price suddenly goes up. And then beyond that, I think you may have to still pay some other place to register the domain. Yes, royale.as can be associated with "royal pain in the ass" but the "as" was good enough for spoon.as back in the day. Royale.web would be fine with me. And we could grab other TLDs too, we don't have to choose one. My question is, is it worth it? Is royale.io going to pay off in some way $100 better than royale.as which would pay off $88 better than say, royaleapps.org or royalesdk.org? Thanks, -Alex On 9/22/17, 3:26 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Thanks Dany, > >if you guys see ok ni make a pool to get the .io domain that's fine with >me, I'll be donating as well few bucks >Maybe we should know first what's the final price and see open a thread >for >it asking the community for some little donation. Of course I suppose that >the rest of years will be down to a normal price of 5 to 10€ or something >like that. > >The other (more easy option) is to go with .app or .web if people like it >as you. > > >2017-09-22 11:35 GMT+02:00 Dany Dhondt : > >> Why not royale.web? Sounds cool to me… >> if royale.io or something else is chosen, I’d gladly donate some money. >> It’s the least we can do for all the work you folks did last year! >> >> Dany >> >> >> >> >> >> > Op 22 sep. 2017, om 11:23 heeft Piotr Zarzycki < >> piotrzarzyck...@gmail.com> het volgende geschreven: >> > >> > Let's wait what do others think about donating something. >> > >> > I'm not good in case of domain registration, but royale.io is >> registered by >> > someone else and we still can register it for us ? I checked in my >>domain >> > operator and I see price about 30$. >> > >> > Piotr >> > >> > 2017-09-22 11:08 GMT+02:00 Erik de Bruin : >> > >> >> or, slightly better, royale.rocks, again for $12 >> >> >> >> EdB >> >> >> >> >> >> >> >> On Fri, Sep 22, 2017 at 10:56 AM, Erik de Bruin >> >> wrote: >> >> >> >>> We can also be '4chan cool' and get roy4le.com for only $12, which >> I'll >> >>> gladly donate :-) >> >>> >> >>> EdB >> >>> >> >>> >> >>> >> >>> On Fri, Sep 22, 2017 at 10:53 AM, Piotr Zarzycki < >> >>> piotrzarzyck...@gmail.com> wrote: >> >>> >> If more people would like to give some we may have that royale.io. >>:) >> >> 2017-09-22 10:50 GMT+02:00 Erik de Bruin : >> >> > 'royale.as' is available here: >> > >> > >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nic. >>as%2F&data=02%7C01%7C%7C5ee0196900bd485a503808d501a47029%7Cfa7b1b5a7b3443 >>8794aed2c178decee1%7C0%7C0%7C636416728125097204&sdata=4J%2B8Xvu15SZvqQ6FZ >>zk3bxK%2BhUSP1LDw3Lv0Ph97Tc8%3D&reserved=0 >> > >> > But it is $100 for 2 years, payable up front. That will require >>some >> > crowdfunding as well. And if we go that route, we might as well go >> for >> the >> > .io which is way cooler ;-) >> > >> > EdB >> > >> > >> > >> > On Fri, Sep 22, 2017 at 10:42 AM, Piotr Zarzycki < >> > piotrzarzyck...@gmail.com> >> > wrote: >> > >> >> Carlos, >> >> >> >> I can give couple of dollars for royale.io :) Later for extension >> >> for >> >> another year it could cost same ? >> >> >> >> +1 for royale.as - In Polish there is no connection to anything >>bad >> :) I >> >> like it. >> >> >> >> Thanks, >> >> Piotr >> >> >> >> >> >> 2017-09-22 10:39 GMT+02:00 Carlos Rovira < >> carlos.rov...@codeoscopic.com >> >> : >> >> >> >>> Hi Erik, >> >>> >> >>> This is my order of preference: >> >>> >> >>> - royale.io is the best option, but as you said is expensive, so >> >> we >> > must >> >>> give up with that :( >> >>> >> >>> - royale.as: we should check if it comes with some negative >> meaning. I >> >>> don't see nothing, but maybe you guys that are more native in >> English >> >>> language could see some problems. Aside from that could be >> problematic >> > to >> >>> have a domain that is supposed to be designated to a country? >> >> (Samoa >> >>> Americana) >> >>> >> >>> Other top level options available (before going with more >>complex >> > names) >> >>> that could fit our purposes: >> >>> >> >>> * royale.app<-- ok we are not an App, but with Royale people >> will >> >> build >> >>> Apps ;) >> >>> * royale.web <-- pretty generic, isn't it? >> >>> * royale.dev<--
RE: [Non-DoD Source] Re: Royale website and domain registration
Royale.IT? -Mark K
Re: [DISCUSS] Name of the FlexJS Fork
Apache Bob... -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Tuesday, September 19, 2017 2:20 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork Ick… Why do these things have to be so complicated? ;-) Harbs > On Sep 19, 2017, at 8:58 PM, Dave Fisher wrote: > > There are any number of meanings for boja in many languages with and without > diacritics. > > https://en.m.wiktionary.org/wiki/boja > > Sent from my iPhone > >> On Sep 19, 2017, at 1:45 PM, Andrew Wetmore wrote: >> >> I can think of three ways* to pronounce "bo-ja" without even resorting to a >> South African "click" language. This makes it a challenge to refer to the >> product to anyone who does not already use it. >> >> *bodja, booya, boha. >> >> On Tue, Sep 19, 2017 at 2:42 PM, Piotr Zarzycki >> wrote: >> >>> Om, >>> >>> No offend :) That is why it is so hard to choose ;) I think "bo-ja" is the >>> closes to how I pronounce it. :) >>> >>> Piotr >>> >>> 2017-09-19 19:31 GMT+02:00 OmPrakash Muppirala : >>> >>>> Boja is one name I really dislike. Sorry Piotr😕 >>>> >>>> Also I dont know how to pronounce it. Is it Bo-ha, or boo-ha or bo-ja, >>> etc? >>>> >>>> On Sep 19, 2017 10:09 AM, "Piotr Zarzycki" >>>> wrote: >>>> >>>>> Reading Alex in VOTE thread and how many times we are mentioning Boja >>> - I >>>>> will change my VOTE. Limbr is a bit dangerous having Dave's finding. >>>>> >>>>> Piotr >>>>> >>>>> 2017-09-19 18:41 GMT+02:00 Harbs : >>>>> >>>>>> FWIW, I think Limbr is another good spelling. >>>>>> >>>>>>> On Sep 19, 2017, at 7:34 PM, Alex Harui >>>>>> wrote: >>>>>>> >>>>>>> We don't have time for another vote thread. We need to close down >>>> the >>>>>>> vote tonight or early tomorrow morning. So, if you are ok with >>>> Limber >>>>>>> (still not clear it will win, please state objections to using >>> Limbyr >>>>> as >>>>>>> the spelling. It is true a unique spelling stand out from search >>>>>> results, >>>>>>> but first, you have to remember how to spell it, and my spell >>> checker >>>>> is >>>>>>> constantly changing. >>>>>>> >>>>>>> -Alex >>>>>>> >>>>>>> On 9/19/17, 5:05 AM, "Kessler CTR Mark J" < >>> mark.kessler@usmc.mil >>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> If limber wins, a simple discussion thread should resolve letter >>>>> changes >>>>>>>> to the name. >>>>>>>> >>>>>>>> >>>>>>>> -Mark K >>>>>>>> >>>>>>>> -Original Message- >>>>>>>> From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] >>>>>>>> Sent: Tuesday, September 19, 2017 4:52 AM >>>>>>>> To: dev@flex.apache.org >>>>>>>> Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> It has advantage of having the name which do not exist on github. >>>> Let >>>>>> say >>>>>>>> that Limber with win in the voting - We probably have to open >>>> another >>>>>> VOTE >>>>>>>> to have "Limbyr" - Which I like personally. >>>>>>>> >>>>>>>> Is it enough that PMCs agreed here with changing Limber to Limbyr >>>>> here ? >>>>>>>> >>>>>>>> Thanks, Piotr >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Piotr Zarzycki >>>>> >>>>> mobile: +48 880 859 557 <+48%20880%20859%20557> >>>>> skype: zarzycki10 >>>>> >>>>> LinkedIn: http://www.linkedin.com/piotrzarzycki >>>>> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552> >>>>> >>>> >>> >>> >>> >>> -- >>> >>> Piotr Zarzycki >>> >>> mobile: +48 880 859 557 >>> skype: zarzycki10 >>> >>> LinkedIn: http://www.linkedin.com/piotrzarzycki >>> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552> >>> >> >> >> >> -- >> Andrew Wetmore >> >> http://cottage14.blogspot.com/
RE: Re: [DISCUSS] Name of the FlexJS Fork
If limber wins, a simple discussion thread should resolve letter changes to the name. -Mark K -Original Message- From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] Sent: Tuesday, September 19, 2017 4:52 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork Hi, It has advantage of having the name which do not exist on github. Let say that Limber with win in the voting - We probably have to open another VOTE to have "Limbyr" - Which I like personally. Is it enough that PMCs agreed here with changing Limber to Limbyr here ? Thanks, Piotr
RE: [VOTE] What should be the new Project Name for Proposed fork of FlexJS?
1. Arise 2. Boja 3. Limber (Binding) -Mark K -Original Message- From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] Sent: Sunday, September 17, 2017 3:19 PM To: dev@flex.apache.org Subject: [Non-DoD Source] [VOTE] What should be the new Project Name for Proposed fork of FlexJS? Hi, In this thread I've gathered list of names proposition for fork of FlexJS project. LIST: Royale Boja Strand Bead Limber Boinga Braid Arise HOW DO WE VOTE: 1) Pick up 3 names from the list and order them from the most favorite 2) We will give points for each items in the list which you have choose 3) In your list you can propose your own name - others can follow it in their lists EXAMPLE: 1) Name1 - 3 points 2) Name2 - 2 points 3) Name3 - 1 point WINNER: We will pickup winner based on gathered points by one of the name. The vote will be open until Tuesday September 19, 23:00 UTC Thanks, Piotr
RE: [Non-DoD Source] Re
You need to send an email to [1] to unsubscribe. All mailing list information can be found at [2]. [1] dev-unsubscr...@flex.apache.org [2] http://flex.apache.org/community-mailinglists.html Mark K -Original Message- From: Asimov [mailto:asim...@gmail.com] Sent: Monday, September 18, 2017 3:20 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re unsubscribe
RE: [DISCUSS] Name of the FlexJS Fork
/s DNF SDK - Definitely Not Flash SDK YAAS SDK - Yet Another ActionScript SDK :P -Mark K -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Friday, September 15, 2017 1:31 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork Dave says, and I agree, that if there is more than one candidate, we might need to use a more complicated voting system like STeVe. What other suggestions do you think have been popular enough to make a second candidate? I think FlexJS has been rejected as the project name. If anyone wants to push for a name other than Royale, please reply to this post with that name. Then we can decide whether we need to use STeVe or not. Thanks, -Alex On 9/15/17, 9:49 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala" wrote: >On Fri, Sep 15, 2017 at 9:45 AM, Piotr Zarzycki > >wrote: > >> Definitely the were the most support for Royale. +1 for starting vote >> YES/NO. We could express in the VOTE thread that anyone can shot his own >> name idea and others can give him +1. >> > >There were several suggestions, some of which we could consider. We >should >probably let the FlexJS yes/no settle down before we start another thread. >All this feels a bit rushed, I am having a bit of a hard time following >discussions/decisions. > >Thanks, >Om > > >> >> Piotr >> >> On Fri, Sep 15, 2017, 18:39 Piotr Zarzycki >> wrote: >> >> > As Alex said I also didn't answer for any single email from someone >>who >> > would like to start from scratch app or even would be new Flex world. >> > >> > We may get such people in the future, but we need to go with path >>where >> > first target will be ports the old one applications. >> > >> > As for the bad press - 4 years ago I have started work in a company >>as an >> > Flex Developer. This company grows on Flex development. Currently they >> > change the direction as many others, but I have to say that anyone >>from >> > initial 20 people said anything wrong about Flex. Just the opposite >>there >> > were very good press out there in the company as in outside in Cracow. >> > >> > I'm all for having product FlexJS. We cannot abandon such tremendous >> > opportunity. Look in the message from Rui in the VOTE thread - This is >> what >> > we need to provide in order to read next time. I've choose FlexJS for >>the >> > port, cause it provides me what I need. >> > >> > Thanks, >> > Piotr >> > >> > On Fri, Sep 15, 2017, 18:09 Erik de Bruin wrote: >> > >> >> > >> >> > have a problem if someone created a runtime we wanted to target >>called >> >> > "Dover". >> >> > >> >> >> >> Are you testing the non-native speakers? >> >> >> >> I spilt some of my coffee over that one ;-) >> >> >> >> EdB >> >> >> >> >> >> >> >> -- >> >> Ix Multimedia Software >> >> >> >> Jan Luykenstraat 27 >> >> 3521 VB Utrecht >> >> >> >> T. 06-51952295 >> >> I. >>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data >>=02%7C01%7C%7C4127f1b06d7f43f4310808d4fc59ca2f%7Cfa7b1b5a7b34438794aed2c1 >>78decee1%7C0%7C0%7C636410909953528643&sdata=BTLJuY5ffdBpl7z%2B%2FPa%2FHfu >>ogqLc38DybDD2qL8oF78%3D&reserved=0 >> >> >> > >>
RE: Re: [DISCUSS] Name of the FlexJS Fork
I wanted to throw in a couple words / names to see if they "spark" anything. Arise Dawn Raise / Rise Dimension Facet Morph Poly Strand Derive Drive Quest Journey Fortune Prospect Trend -Mark K
RE: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?
No (binding) The project name should not contain Flex or JS. The flex change because it’s separating the name and the JS because we do more than JS. -Mark K -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Thursday, September 14, 2017 11:37 AM To: dev@flex.apache.org Subject: [VOTE] Should the Project Name of the Proposed Fork be FlexJS? VOTE Should the Project Name of the Proposed Fork be FlexJS? [ ] Yes - The forked project should be Apache FlexJS. [ ] No - The forked project should have another name which will be discussed. [ ] Abstain - Don’t care what the forked project is called. The vote will be open for 72 hours until Sunday September 17, 16:00 UT.
RE: Re: [DISCUSS] Name of the FlexJS Fork
I actually spilt some coffee on this one. Lol -Mark K -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Thursday, September 14, 2017 1:26 PM To: dev@flex.apache.org Subject: Re: [DISCUSS] Name of the FlexJS Fork BendForward... (just kidding!) EdB
RE: [DISCUSS] Name of the FlexJS Fork
Royale sounds too much like Pulp Fiction... I do like the idea of the project and frameworks have similar names. Although I don't mind either way. If it's like having a make and a model, I would consider Apache more of the Make field and the Model being the SDK/framework which skips our project name all together. In our environment they hear the framework name, but do not know what it means, they simply just see the end result of the products we produce. We are judged on what our target application looks, feels, and functions like. Once we get rid of the Flash dependency, the only negative perception will go away. So the ultimate framework just needs to have professional name and website. Selling the concept of the framework is rated for us in three main aspects. 1. Longevity; knowing it will be around a long time. 2. Consistency that the structure, classes, and properties that we end up using won't be constantly changing (adding to is fine). 3. Activity on the project showing its alive and well. -Mark K
Re: [DISCUSS] Name of the FlexJS Fork
Probably could vote on the name change. But if that passes, it would need a discussion thread for the new name. -Mark K -Original Message- From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] Sent: Wednesday, September 13, 2017 6:06 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork Agreed with Mark completely! Especially in case of IDEs. I will summarize discussion tomorrow for the notice to the board that we have consensus or not. If there will not be more voices for change than for staying with current one do we still need start a Vote - Something like: Change name or not ? Dave what do you think about that ? Thanks, Piotr
Re: [DISCUSS] Name of the FlexJS Fork
One thing we need to do is stick with whatever name we come up with. There is a lot of time and money involved in renaming stuff. Not only internally for our own repo's, sites, JIRA, wikies... but also for things like the IDE makes or people building 3rd libraries from it. -Mark K
RE: [VOTE] Fork FlexJS from Apache Flex
+1 (binding) -Mark K -Original Message- From: Alex Harui [mailto:aha...@adobe.com.INVALID] Sent: Friday, September 01, 2017 2:28 AM To: dev@flex.apache.org Subject: [Non-DoD Source] [VOTE] Fork FlexJS from Apache Flex Hi folks, Here is the vote thread. Please vote on whether to submit the proposal below to the board. Please use +1 for yes, -1 for no, and if you want, any number in-between per [1]. Only PMC member votes will be used to determine the results, but we are more than happy to hear from non-PMC members as well. [1] https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fr actions Thanks, -Alex
RE: Re: [DISCUSS} Fork FlexJS from Apache Flex
It is good to point this out. There are other targets that can be compiled into other than flash. Such as Air and it's captive runtimes for desktop and mobile. My understanding is Adobe has a vested interesting alternatives to the Flash Player as targets. They are not getting rid of ActionScript or Air, so it's mostly going to receive support for all things AS related. There will still be quite a few PMC members on the Flex SDK side. Some will be on both SDK and JS sides. -Original Message- From: Olaf Krueger [mailto:okrue...@apache.org] Sent: Tuesday, August 29, 2017 7:14 AM To: dev@flex.apache.org Subject: Re: [DISCUSS} Fork FlexJS from Apache Flex I've already replied via nabble a few hours ago but it seems that it is not synced with the list for whatever reason... so sorry for annoying you: Hi Alex, thanks for this summary, I think this is the right way to go! +1 But for me, it sounds a little bit, that Apache Flex is labeled as discontinued. We should take care to not scare off or unsettle Apache Flex users. Even if FlashPlayer is dead, Flex with AIR is still an awesome platform! Maybe the usage of AIR could save some Flex apps a for while or give users some more time to migrate to FlexJS. > Most FlexJS PMC members are planning to remain on the Apache Flex PMC I think it would be good to also list the Apache Flex PMC members >I will be stepping down as Apache Flex chair Probably I've overlooked something but who will be the chair of Apache Flex? >It isn't clear how much longer Adobe will pay Peter and I to work on Flex and/or FlexJS. I would like to use the opportunity to mention that my company is only willing to invest time in FlexJS if Adobe will continue its support. So I hope that there will be a commitment by Adobe. The fork would be a good opportunity for Adobe to express oneself. Thanks, Olaf
RE: [DISCUSS} Fork FlexJS from Apache Flex
+1 to Split to FlexJS -Mark K
RE: [DISCUSS] Release Apache Flex SDK 4.16 RC2
I'll take a look at this tonight. Just got back from a business trip. -MArk -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Saturday, February 11, 2017 6:05 PM To: dev@flex.apache.org Subject: [DISCUSS] Release Apache Flex SDK 4.16 RC2 Hi, Please discuss the release candidate here and not in the vote thread. Thanks, Justin
RE: [FlexJS] Wanted: UX/UI Design Proposals
Side question on the fonts. Is it being taken into consideration for browsers that block downloading additional fonts? -Mark
RE: [FlexJS] Some things still missing ni FlexJS
1. Luckily we are not under any deadline at this time, but we did get a zing from a code review we had. They recommended we should migrate at some point. However our branch is always behind the industry curve for certain things. For instance we have a large population of Win7 users still. 2. It would be based on perspective, luckily we use most of the common components and charts. 90% could be acceptable for conversion. This is of course removing any customization to components from the equation. Those will always require a change. 3. I might here and there, but I've received a few new people that are consuming additional time getting them up to speed. Causing me to catch up on work. I like the idea of your comparison list. It would be a large table, but very functional. Could we have a new namespace of AS components that are stripped down that are 100% compatible to the FlexJS side? People could start converting over existing apps slowly while still being able to deploy to their current targets. Could also allow a bit more decoupling from the core player AS. I would find this more interesting of an avenue. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, January 17, 2017 4:29 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [FlexJS] Some things still missing ni FlexJS On 1/17/17, 3:43 AM, "Kessler CTR Mark J" wrote: >I do not use AMF for enterprise level applications. AMF falls short >of our requirements. But the bottom line for us for converting to FlexJS >would be seamless operation(look / feel / interaction) in all major >browsers (excluding IE) and the ability to compile it using our existing >spark based projects without having to having to create hundreds of JS >beads / customizations. Understandably heavier, but compatibility is >more important. > >The only selling point to me for converting to FlexJS would be that I >could cross compile Adobe Air apps and FlexJS. If not, then it would be >creating everything from scratch again. If that's the case I would have >to consider all the available SDK's out there before making a decision. Thanks for posting this. Some questions: 1) Are you under any deadline to migrate off of Flash? 2) If it turned out that 80% or 90% of your code would cross-compile would you still consider a full port to other SDKs? I doubt we'll ever get to 100%. 3) Would you have time to help get us to 80% or 90% or 99.5%? This got me thinking about whether Falcon could easily be tweaked to output a list of all APIs used by a code base. Then we could see how much of the Flex SDK and Flash APIs and other third-party APIs someone was using. It turns out that Spark Button has about 120 public APIs! It will be awhile if ever before FlexJS reproduces all 120. But my bet is that most of you only use about 12 APIs. While we have the Express set, and I've shown that porting most of Spark and MX on top of UIBase is "possible", in between there is the possibility of a "Spark-ish" set that builds on top of Basic like Express did and only supports the 12 popular Spark APIs for Button, etc, eventually adds a few more, but never promises to do all 120. Thoughts? -Alex
RE: [FlexJS] Some things still missing ni FlexJS
I do not use AMF for enterprise level applications. AMF falls short of our requirements. But the bottom line for us for converting to FlexJS would be seamless operation(look / feel / interaction) in all major browsers (excluding IE) and the ability to compile it using our existing spark based projects without having to having to create hundreds of JS beads / customizations. Understandably heavier, but compatibility is more important. The only selling point to me for converting to FlexJS would be that I could cross compile Adobe Air apps and FlexJS. If not, then it would be creating everything from scratch again. If that's the case I would have to consider all the available SDK's out there before making a decision. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Friday, January 13, 2017 1:11 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [FlexJS] Some things still missing ni FlexJS On 1/13/17, 12:44 AM, "Christofer Dutz" wrote: >Well from my point of view it was the whole “write once run everywhere” >thing. >I was totally annoyed of having to write UI things once and then patch >and bugfix things for all the other Browsers. I would say that fits under the "Developer Productivity" umbrella. > >But in general I think you (Alex) and I have one great difference in our >assumption of who will probably be our generation 1 users. > >You assume it’s mainly the people wanting to create new applications. >That’s why you see 1.0 the way you do it. That is an incorrect assumption. IMO, there are at least some existing Flex apps that don't use AMF. Now it may turn out that we will have AMF shortly, but until it is done, those who don't need it can start migrating their apps today. Some folks are already migrating. I will believe that AMF is used by the vast majority of Flex apps, but as I said upthread, we simply need to attract more committers/contributors to really get FlexJS off the ground. Some folks believe that declaring something as 1.0 will invite more folks to try it and thus get involved. I don't have a strong opinion, but that sounds like a reasonable approach, and better than telling folks not to try FlexJS for another year or two and wait for the few of us who are active committers to reproduce all of these killer features that a much larger team of full-timers did at Adobe over many more years. Flex 4 had many more features than Flex 3, which had more features than Flex 2 which had more features than Flex 1.0. FlexJS 1.0 may only allow a small percentage of Flex customers to migrate, but again, if that brings in new contributors we can handle more Flex customers with FlexJS 2.0 and so on. There may also be a way to get traction with new customers and new apps as well by trying to get attention from Cordova developers, CreateJS developers, etc. I don't care who gets to production first, whether it is a new app or migrated app, but mainly, I think a testimonial is what we really need since we don't have a budget for marketing. So when folks show up with a need in order to get to production, I will try to help them out. -Alex
RE: [FlexJS] Tour de FlexJS
+1 -Mark -Original Message- From: Peter Ent [mailto:p...@adobe.com] Sent: Tuesday, January 10, 2017 1:33 PM To: dev@flex.apache.org Subject: [Non-DoD Source] [FlexJS] Tour de FlexJS Hi, Regarding the notation of a "Tour de FlexJS" in the spirit of the "Tour de Flex", I thought I might start a repository to hold it. We have a lot of material now and people could begin contributing to it. Perhaps the repo could be "flex-tourjs" or something similar. I think keeping the project separate from the FlexJS SDK would allow it to be released on its own schedule and not tie up the FlexJS release with more issues. Let me know what you think. Alex has suggested using the ASDoc example as the starting point. Regards, Peter Ent Adobe Systems/Apache Flex Project
Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release
You can send an email to [1] and it will remove you from this mailing list. If you want to know more about the rest of the mailing lists / options check out [2]. [1] dev-unsubscr...@flex.apache.org [2] http://flex.apache.org/community-mailinglists.html -Mark -Original Message- From: darrin [mailto:dar...@bijousoftware.com] Sent: Tuesday, January 10, 2017 4:11 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Apache Flex SDK 4.16 RC1 release I would like to come off this email list but I can't, I have tried to cancel using the process but my email address doesn't exist, can anyone help? RegardsDarrin TennisOutlaws.com
RE: [Non-DoD Source] Re: Starting fresh / new developers
So far it looks like two items have emerged. We should give FlexJS its own pages and fanfare. Maybe we should move the Tour de Flex to the Development tab. It does have a good amount of examples in it. However it seems to have each example compiled separately. Which makes everything take longer to load when you click between examples. Side question for the FlexJS. Would it be beneficial to have a new AS namespace / set of components that match the new style used in the FlexJS... this to allow ability to target both flash and flexjs without creating so many FlexJS only beads? -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Tuesday, December 27, 2016 8:23 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Starting fresh / new developers flexjs.apache.org would be great, but maybe even something like flexjs.com or apacheflexjs.com or something like that... would it be possible (although internaly it will be as well flex.apache.org/flexjs, but just a main domain pointing to a subdomain or page inside a subdomain that will give some relevance and entity...a huge point in marketing the technology) 2016-12-27 21:53 GMT+01:00 OmPrakash Muppirala : > On Tue, Dec 27, 2016 at 12:01 PM, Christofer Dutz < > christofer.d...@c-ware.de > > wrote: > > > Hi, > > > > First of all I would favor a FlexJS site written in FlexJS. I can > > definitely provide the parts we need to add in order to have this auto > > published, as I just recently fought this fight. Especially based on the > > MDL example (which looks amazing). > > > > I think in Apache all projects have their own sub-domain, but not more > > than one. So I think in our case we are stuck to “flex.apache.org” but > > could continue with an URL like http://flex.apache.org/flexjs > > Keeping things inside the “flex” domain sort of underlines that this is > > part of the flex project and not a separate flexjs project. > > > > > Good idea. I'm all for it. > > I think we can still ask for flexjs.apache.org even though FlexJS is part > of Apache Flex. Can someone with more knowledge please confirm? > > Thanks, > Om > > > > Chris > > > > > > Am 27.12.16, 11:28 schrieb "carlos.rov...@gmail.com im Auftrag von > Carlos > > Rovira" > carlos.rov...@codeoscopic.com>: > > > > Hi, > > > > I think FlexJS web is a must, something that points directly to > FlexJS > > and > > market all the thing (no mentions to old Flex SDK). > > And I think this should have its own domain and a great modern look > and > > feel with accurate marketing reading and images. > > > > As well we could have a section with the easy start examples Josh did > > in > > the wiki (maybe this time with runtime companions), an many other > > stuff. > > > > I think the right tool for this is a Wordpress website so we could > make > > things fast, easy and good looking, I can help with that in that > > format, in > > other systems I'm not fluent. > > > > my 2ctns > > > > Carlos > > > > > > > > > > > > > > > > > > > > 2016-12-26 21:55 GMT+01:00 Josh Tynjala : > > > > > 1. I think FlexJS would benefit from its own dedicated page on the > > main > > > website that describes its benefits in a more polished, bite-sized > > form. > > > Basically, more of a marketing page that keeps the architecture > > discussion > > > limited to high-level bullet points. If someone really wants to > dive > > in to > > > the nitty gritty details, we have multiple pages in the wiki that > go > > more > > > in-depth on the architecture. > > > > > > 2. The Flex SDK Installer is still working well, in my opinion. > > We've been > > > able to successfully tweak the install scripts when we release new > > SDK > > > updates, as necessary, and there hasn't been a need to push updates > > to the > > > installer app. For instance, Adobe recently changed AIR SDK for Mac > > to be a > > > DMG file, and the upcoming Flex 4.16 will support this different > > format. > > > Older SDKs won't work with AIR 24 and newer, though, and if we > > wanted to > > > support that, we'd need to release small updates to each of them. > > > > > > The manual install instructions should still be accurate. Users > > simply need > > > to pass the installer.xml file to Ant (and, optionally, versions > for > > > Flash/AIR stuff) and the rest is automated. > > > > > > In both cases, the SDK will work in IDEs. Ultimately, the same > > install > > > script is run. A FlexJS project may require extra tweaks in certain > > IDEs > > > because they don't know about FlexJS and we're tricking them into > > thinking > > > this is the classic Flex SDK. > > > > > > 3. I think that Tour de Flex provides a ton of good examples for > > getting > > > started the Flex SDK. I see that it's under "About Flex" in the > main > > > we
RE: Attached document
Please don't open random documents sent as email attachments. Especially ones marked macro enabled. -Mark
RE: [Bindable] and private setters (was Re: [Falcon])
+1 for leaving the setter private. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, November 22, 2016 1:01 PM To: dev@flex.apache.org Subject: Re: [Bindable] and private setters (was Re: [Falcon]) On 11/22/16, 9:26 AM, "Josh Tynjala" wrote: >If they make the getter public and the setter private, it's probably on >purpose. If the compiler then forces the setter to be public for >[Bindable], it should at least tell them that something probably >unexpected >is happening. I think a warning makes sense. I don't think that [Bindable] has to force the setter to be public. IMO, the right answer is to leave the setter as private and you'll get the same errors as if you didn't use [Bindable] which is an error about read-only if you don't use the private:: prefix. That isn't completely obvious, but at least is consistent. Thoughts? -Alex
RE: Re: [FalconJX] Generating ASDoc
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: 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: Current FlexJS license/notice issues
IMHO if their project is licensed and their individual files are not licensed it's a non-issue at least as that is concerned. If what was said was true about just using a snippet and I'm understanding this thread correctly, then let's give them a attribution / reference back to the source and call it good. My vote would be that Justin can go off on his own and communicate with them without the general consensus of the PMC. If we would like to put it to an official vote we can so this can be put to rest. Until then I'm expressing a -1 for convoluting another project. -Mark
Re: Official naming for the "standard" Flex SDK
It really would be considered more of a suite in that example. But they are not separate products at this time. The targeted output is what's changing. Most people would just say I develop with Flex and I make apps for Mobile / Browser / Desktop. The only different one is the FlexJS which has some customization / minimization that doesn't exist in the standard SDK. That one reason it gets mentioned separately is because of its differences. -Mark -Original Message- From: OK [mailto:p...@olafkrueger.net] Sent: Wednesday, September 07, 2016 6:56 AM To: dev@flex.apache.org Subject: RE: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK Kessler CTR Mark J wrote > Should not use flash in the name. The main SDK can target flash player, > air, and native apps (with captive runtime). Hmm, I thought that all these runtimes are under the same hood wich is called "Flash platform" by Adobe. Seems that the Adobe naming confused me also ;-) Kessler CTR Mark J wrote > Then there is FlexJS which is divergent from the main SDK. So I think > Apache Flex as a title would do just fine. Ok, but that means that both SDKs exists side by side: ->Apache Flex ->Apache FlexJS But my understanding is that FlexJS is under the hood of Apache Flex: ->Apache Flex -->FlexJS -->Previous Flex So if you'd like to make sure that there will be no confusion if you talk or write just about "Apache Flex" you have to mention that you mean the "AIR, Flash,... whatever SDK". Probably at the end this discussion is useless but maybe a unique name would avoid confusion, especially if FlexJS gets more and more popular and moves into the focus of non-Flex developers. Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54911.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK
Should not use flash in the name. The main SDK can target flash player, air, and native apps (with captive runtime). Then there is FlexJS which is divergent from the main SDK. So I think Apache Flex as a title would do just fine. -Mark -Original Message- From: OK [mailto:p...@olafkrueger.net] Sent: Wednesday, September 07, 2016 3:39 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Official naming for the "standard" Flex SDK Forgot to mention my proposal: FlexJS -> Flex JavaScript FlexFP -> Flex Flash Platform Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Official-naming-for-the-standard-Flex-SDK-tp54897p54898.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Welcome Greg Dove as Apache Flex Committer
Gratz and welcome Greg. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, September 07, 2016 12:49 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Welcome Greg Dove as Apache Flex Committer Hi folks, The Apache Flex PMC is excited to welcome Greg Dove as our newest committer! Greg has recently contributed improvements for FlexJS binary data handling, and test cases and bug fixes for data binding on FlexJS which earned him the merit to become a committer (yes, you can become a committer the same way). Please join us in welcoming him as a committer to the Apache Flex project. Welcome Greg! -Alex
RE: FlexJS stopImmediatePropagation
I agree for the most part of grain of salt, but Microsoft stated they will only update the latest version of IE now[1]. That's the only real reason I brought it up. "Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical supports and security updates. Internet Explorer 11 is the last version of Internet Explorer, and will continue to receive security updates, compatibility fixes, and technical support on Windows 7, Windows 8.1, and Windows 10." [1] https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, August 09, 2016 12:22 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: FlexJS stopImmediatePropagation Historically, market share reports like this have not been accurate for large enterprises and schools which often standardize on something one or two versions back. So, I tend to be conservative about what versions we need to support. -Alex
RE: FlexJS stopImmediatePropagation
Just a thought, I think at this point if we are still worrying about IE we should only worry about IE11[2] since even IE9 [1] is in heavy decline. [1] https://www.netmarketshare.com/report.aspx?qprid=3&qpaf=&qpcustom=Microsoft+Internet+Explorer+9.0&qpcustomb=0 [2] https://www.netmarketshare.com/report.aspx?qprid=3&qpaf=&qpcustom=Microsoft+Internet+Explorer+11.0&qpcustomb=0 -Mark
RE: [Non-DoD Source] Welcome Yishay Weiss as Apache Flex Committer
Grats and Welcome. -Mark -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Sunday, July 24, 2016 11:19 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Welcome Yishay Weiss as Apache Flex Committer Hi folks, The Apache Flex PMC is excited to welcome Yishay Weiss as our newest committer! Yishay has recently been contributing with bug reports, pull requests on FlexJS, and sharing helpful info on the mailing lists, all of which earned him the merit to become a committer (yes, you can become a committer the same way). Please join us in welcoming him as a committer to the Apache Flex project. Welcome Yishay! -Harbs
RE: [Non-DoD Source] RE: flexjs init the int =0
Forgot about that. I'm just used to always initializing my ints/numbers to 0 or -1. -Original Message- From: Josh Tynjala [mailto:joshtynj...@gmail.com] Sent: Tuesday, July 05, 2016 8:10 AM To: dev@flex.apache.org Subject: [Non-DoD Source] RE: flexjs init the int =0 A Number initializes to NaN in the Flash runtimes, if you don't set it to anything else. - Josh On Jul 5, 2016 3:07 AM, "Kessler CTR Mark J" wrote:
RE: flexjs init the int =0
Number? -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Friday, July 01, 2016 7:46 PM To: dev@flex.apache.org Subject: Re: flexjs init the int =0 Yep. Looking into it. Are there any other types other than int and uint that will need initialization? -Alex On 7/1/16, 1:38 PM, "jude" wrote: >in as3 > >var i:int; // i equals 0 > >in JavaScript i is undefined because we don't know what type it is > >var i; // null, undefined or NaN > >therefore we need to initialize every integer as zero when it's defined. >On Jun 30, 2016 10:35 PM, "lizhi" wrote: > >> and i++ in as i=1 >> but js i= NaN >> >> >> >> -- >> View this message in context: >> >>http://apache-flex-development.247.n4.nabble.com/flexjs-init-the-int- >>0-tp53569p53570.html >> Sent from the Apache Flex Development mailing list archive at >>Nabble.com. >> smime.p7s Description: S/MIME cryptographic signature
RE: Package keyword and import class
I'll give it a shot tonight. -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, June 01, 2016 10:11 AM To: Kessler CTR Mark J; dev@flex.apache.org Subject: [Non-DoD Source] Re: Package keyword and import class Can you try with falcon? Sent from my LG G3, an AT&T 4G LTE smartphone -- Original message-- From: Kessler CTR Mark J Date: Wed, Jun 1, 2016 4:38 AM To: 'dev@flex.apache.org'; Subject:Package keyword and import class Bumped into a path for a project that has a folder with "package" in the name and it causes a syntax error[1]. Shouldn't the import pathing be able to handle any folder name without keywords interfering with it? At this time, just renaming the folder works to correct it. Doesn't work: import mypath.package.myview; Works: import mypath.packages.myview; [1] Error: Syntax error: expecting identifier before package. -Mark
Package keyword and import class
Bumped into a path for a project that has a folder with "package" in the name and it causes a syntax error[1]. Shouldn't the import pathing be able to handle any folder name without keywords interfering with it? At this time, just renaming the folder works to correct it. Doesn't work: import mypath.package.myview; Works: import mypath.packages.myview; [1] Error: Syntax error: expecting identifier before package. -Mark
RE: Welcome Olaf Krüger as Apache Flex Committer
Welcome aboard! :) -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, May 12, 2016 2:51 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Welcome Olaf Krüger as Apache Flex Committer Hi folks, The Apache Flex PMC is excited to welcome Olaf Krüger as our newest committer! Olaf has recently been contributing with bug reports, some custom skins, and helping out on the mailing list, all of which earned him the merit to become a committer (yes, you can become a committer the same way). Please join us in welcoming him as a committer to the Apache Flex project. Welcome Olaf! -Alex
Re: subscribe to dev@flex.apache.org
No worries, all good now. -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Monday, May 09, 2016 6:11 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: subscribe to dev@flex.apache.org Ack! Feel free to forward it... On May 9, 2016, at 1:08 PM, Kessler CTR Mark J wrote: > Di you send it to him or the list :P ? > > -Mark > > -Original Message- > From: Harbs [mailto:harbs.li...@gmail.com] > Sent: Monday, May 09, 2016 2:47 AM > To: dev@flex.apache.org > Subject: Re: subscribe to dev@flex.apache.org > > Send an email to: dev-subscr...@flex.apache.org[1] > > Harbs > > [1]http://flex.apache.org/community-mailinglists.html > > On May 9, 2016, at 8:52 AM, saicharan.see...@ebix.com wrote: > >> >> Hi , >> >> I would like to get notifications on FlexJs by subscribing to dev list of it >> . >> >> >> Thanks, >> Charan >> >> The information contained in this message may be CONFIDENTIAL and is for the >> intended addressee only. Any unauthorized use, dissemination of the >> information, or copying of this message is prohibited. If you are not the >> intended addressee, please notify the sender immediately and delete this >> message. >
RE: Re: subscribe to dev@flex.apache.org
Di you send it to him or the list :P ? -Mark -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Monday, May 09, 2016 2:47 AM To: dev@flex.apache.org Subject: Re: subscribe to dev@flex.apache.org Send an email to: dev-subscr...@flex.apache.org[1] Harbs [1]http://flex.apache.org/community-mailinglists.html On May 9, 2016, at 8:52 AM, saicharan.see...@ebix.com wrote: > > Hi , > > I would like to get notifications on FlexJs by subscribing to dev list of it . > > > Thanks, > Charan > > The information contained in this message may be CONFIDENTIAL and is for the > intended addressee only. Any unauthorized use, dissemination of the > information, or copying of this message is prohibited. If you are not the > intended addressee, please notify the sender immediately and delete this > message.
RE: Re: AW: [FALCON] Code analysis stats for Falcon
Just adding some two cents on the other side. We do not use Maven for our internal production. We have exclusively private intranets for our development environments that do not have internet access. We have our own build mechanisms in place internally which function better than kludging an online tool to work exclusively offline. Don't get me wrong, I think having Maven for the people who want and support it would be great, but it cannot be the only option. I do agree Ant can be a PITA sometimes just like any other scripted build / language. So keep maven for one option. Could we create an Air app that would be able to manage the other options? -Mark
RE: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept integer values
I use the issue "Name-#" then a colon [1]. Seems to pick it up well. I use this when I'm writing out the commit message. I'm not sure if it can grab it anywhere in the message or if it can grab multiple issues in one. So when I did that last one, I used [2]. [1] FLEX-12345: My commit message [2] FLEX-35082: Changed the way regex was being used to compare the given pattern for dataProvider objects in the findRowIndex / findRowIndices methods. -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Friday, April 29, 2016 11:41 AM To: dev@flex.apache.org Cc: Mark Kessler Subject: [Non-DoD Source] RE: Re: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept integer values On Apr 29, 2016 4:16 AM, "Kessler CTR Mark J" wrote: > > I don't agree. When the you format your commit messages it adds it to the issue automatically. I'm not going to post a duplicate message for it. Fair enough. Do you know how to format the commit message so it appears in the JIRA ticket automatically? I could use that trick myself Thanks, Om > > > -Mark > > -Original Message- > From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala > Sent: Thursday, April 28, 2016 7:51 PM > To: dev@flex.apache.org; Mark Kessler > Subject: Re: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept integer values > > The general practice is to add the commit sha as a comment when closing a > ticket. It will make things easier to track. > > Thanks, > Om > > On Thu, Apr 28, 2016 at 4:39 PM, Mark Kessler (JIRA) > wrote: > > > > > [ > > https://issues.apache.org/jira/browse/FLEX-35082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > Mark Kessler resolved FLEX-35082. > > - > >Resolution: Fixed > > Fix Version/s: Apache Flex 4.16.0 > > > > > moveIndexFindRow doesn't accept integer values > > > -- > > > > > > Key: FLEX-35082 > > > URL: https://issues.apache.org/jira/browse/FLEX-35082 > > > Project: Apache Flex > > > Issue Type: Bug > > > Components: Spark: List > > >Affects Versions: Apache Flex 4.14.1 > > >Reporter: Dany Dhondt > > >Assignee: Mark Kessler > > >Priority: Minor > > > Fix For: Apache Flex 4.16.0 > > > > > > Attachments: Main.mxml > > > > > > > > > This method has the following signature: > > > public function moveIndexFindRow(field:String, value:String, > > startingIndex:int = 0, patternType:String = RegExPatterns.EXACT):Boolean > > > When a dataProvider object with key 'field' has a 'value' of other than > > String, the method fails > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332) > >
RE: Re: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept integer values
I don't agree. When the you format your commit messages it adds it to the issue automatically. I'm not going to post a duplicate message for it. -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Thursday, April 28, 2016 7:51 PM To: dev@flex.apache.org; Mark Kessler Subject: Re: [jira] [Resolved] (FLEX-35082) moveIndexFindRow doesn't accept integer values The general practice is to add the commit sha as a comment when closing a ticket. It will make things easier to track. Thanks, Om On Thu, Apr 28, 2016 at 4:39 PM, Mark Kessler (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/FLEX-35082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Mark Kessler resolved FLEX-35082. > - >Resolution: Fixed > Fix Version/s: Apache Flex 4.16.0 > > > moveIndexFindRow doesn't accept integer values > > -- > > > > Key: FLEX-35082 > > URL: https://issues.apache.org/jira/browse/FLEX-35082 > > Project: Apache Flex > > Issue Type: Bug > > Components: Spark: List > >Affects Versions: Apache Flex 4.14.1 > >Reporter: Dany Dhondt > >Assignee: Mark Kessler > >Priority: Minor > > Fix For: Apache Flex 4.16.0 > > > > Attachments: Main.mxml > > > > > > This method has the following signature: > > public function moveIndexFindRow(field:String, value:String, > startingIndex:int = 0, patternType:String = RegExPatterns.EXACT):Boolean > > When a dataProvider object with key 'field' has a 'value' of other than > String, the method fails > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
RE: [Non-DoD Source] moveIndexFindRow
Dany ,
Would you please create an issue in our JIRA[1] system with a small test
application and I'll take a look at it.
[1] https://issues.apache.org/jira/browse/FLEX
-Mark
-Original Message-
From: Dany Dhondt [mailto:archeme...@mac.com]
Sent: Wednesday, April 27, 2016 2:01 PM
To: dev@flex.apache.org
Subject: [Non-DoD Source] moveIndexFindRow
Hello,
I used the moveIndexFindRow method in the listBase class.
The signature is this:
public function moveIndexFindRow(field:String, value:String, startingIndex:int
= 0, patternType:String = RegExPatterns.EXACT):Boolean
the value attribute has String as type.
It is very common to have a dataProvider with objects like
{myProp: myIntegerValue, ...}
calling moveIndexFindRow(“myProp”, String(myIntegerValue) wouldn’t work in this
case.
Why is value restricted to String?
-Dany
RE: AW: FlexJS identity crisis. was: [Discuss]Accept donation of drawing APIs
Sounds like that ASP 5... wait I mean ASP Core v1.0. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, April 20, 2016 12:47 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: AW: FlexJS identity crisis. was: [Discuss]Accept donation of drawing APIs Possible, but IMO, Flex 5 implies more backward-compatibility than FlexJS can currently deliver.
RE: [Non-DoD Source] Re: [Discuss]Accept donation of drawing APIs
We should never just accept anything automatically. Apache is a business that has to meet legal requirements. The PMC for each project are entrusted to help protect the organization while looking out for the best interest for their project. While in a perfect world we could just absorb everything in/on/around what we work on and sift through it later. However that brings up several issues, which is why we start out with a discussion. All these things take time. Things like the following should be a general way of looking at things. 1. Is there a benefit to adding item X to the project? 2. Does the project / community show an actual interest in using item X? 3. What type of license does item X have and is it compatible with our own licenses? 4. Are there any developers / committers that need to sign an ICLA before donation can happen? 5. In what repository will it go and where in its structure? 6. Who will volunteer to scrub / make it compliant with Apache rules and licenses.? -Mark
RE: [Non-DoD Source] Re: Easy way to convert a property to a style
Sidebar... What's your opinion of embedding assets in styles and assigning them? -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Friday, April 15, 2016 1:09 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: Easy way to convert a property to a style On Apr 15, 2016 9:35 AM, "Alex Harui" wrote: > > > > On 4/15/16, 12:56 AM, "jude" wrote: > > >thanks, I was concerned if there was anything special or if it was about > >the metadata. > > There might be some metadata involved, but I don't think so. > > > > >I might add patches for these and maybe a visibleInLayout property that > >sets both the visible and includeInLayout at the same time. > > FWIW, overuse of visible and includeInLayout together has been one of the > most common performance killer I've seen in large applications. But sure, > why not? What would be the best way to hide the object and not let it take up space in the layout? > > -Alex >
RE: [Non-DoD Source] [FlexJS][XML]first milestone
That's awesome. As for your test cases, I have two common uses. I receive my server data back in e4x format. So I need to make sure I can separate out different XML sets from one call and also be able to do inline filtering later. A third case would be for the filterfunctions and sorting. Forgive any issues with the following, I'm free typing this in email. 1. One call, two sets. var xmlSource:XML = 2015 2016 2017 2015 2016 2017 ; var xmllcSet1:XMLListCollection = new XMLListCollection(); var xmllcSet2:XMLListCollection = new XMLListCollection(); xmllcSet1.source = xmlSource.Set1.child; xmllcSet2.source = xmlSource.Set2.child; 2. And inline filtering using the same xmlSource. var xmllcFiltered: XMLListCollection = new XMLListCollection(); xmllcFiltered.source = xmlSource. Set1.child.(year == "2015"); -Mark -Original Message- From: Harbs [mailto:harbs.li...@gmail.com] Sent: Sunday, April 10, 2016 9:03 AM To: dev@flex.apache.org Subject: [Non-DoD Source] [FlexJS][XML]first milestone I reached a milestone today with E4X. I have the first working test which reads an XML literal, writes it back out to a string and writes the value of an attribute using E4X notation in Javascript! Over the next couple of weeks I expect to be fixing a lot of issues related to XML and the better the test-case coverage we have, the better the quality will be. I'd like to put out a call for snippets of E4X code that people are using in the wild so we can incorporate tests for as many use cases as we can get. If you have code snippets to contribute, please respond! Thanks, Harbs (P.S. There is currently a compiler issue with two of the XML methods, so the XML.js file needs a bit of editing before it can be used. Hopefully this issue will be fixed soon.)
RE: Re: [VOTE] Release Apache FlexJS 0.6.0 RC3
+1 Binding -Mark
RE: LAST CALL] Release FlexJS/FalconJX 0.6.0
I haven't gotten around to checking it. I'll look it over tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, March 22, 2016 2:50 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: LAST CALL] Release FlexJS/FalconJX 0.6.0 I think I'm done fixing bugs. We should cut an RC soon in case there are complications. Has everyone who plans to vote reviewed the nightly packages? Anybody have anything else they want to cram in this release? Thanks, -Alex On 3/14/16, 10:41 PM, "Alex Harui" wrote: > >I did a pass through the packages and made some changes that should now be >reflected in the nightly builds. It would be helpful if others also >examined the packages before we start cutting release candidates. > >FlexJS: >http://apacheflexbuild.cloudapp.net:8080/job/flex-asjs/lastSuccessfulBuild >/ >artifact/out/ >FalconJX: >http://apacheflexbuild.cloudapp.net:8080/job/flex-falcon/lastSuccessfulBui >l >d/artifact/out/ >For FalconJX, we are only interested in the apache-flex-falconjx packages, >not the apache-flex-falcon packages. > >-Alex >
RE: LAST CALL] Release FlexJS/FalconJX 0.6.0
+1 Would have a positive impact and show continuous progress. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, March 09, 2016 1:41 PM To: dev@flex.apache.org Subject: [Non-DoD Source] LAST CALL] Release FlexJS/FalconJX 0.6.0 Hi, Should we try to cut a release before the SF event? I don't think the big things under development (Maven integration, Spark-like component set, XML) will land in time for the SF event, but we've fixed some bugs, added some features like Tree, Storage, Proxy, Reflection, and eliminated all hand-written JS files. Thoughts? -Alex
RE: [Non-DoD Source] Re: HTTPService breakage in Flex SDK 4.15?
Our HTTPService is working under the 4.15 SDK for https. This was testing with our web front ends (HTTPS) and returning XML responses. Hope this narrows it down a smidge. -Mark
RE: unsubscribe
You can unsubscribe by sending an email to [1] and there are other mailing list options at [2]. The commits mailing list is a bit rough if you're not expecting that volume of emails. [1] commits-unsubscr...@flex.apache.org [2] http://flex.apache.org/community-mailinglists.html -Mark -Original Message- From: Sumudu Chinthaka [mailto:csum...@gmail.com] Sent: Sunday, February 07, 2016 8:33 PM To: comm...@flex.apache.org Subject: unsubscribe
RE: [Non-DoD Source] Re: AW: AW: [ApacheCon NA] Whose going and what topics?
> In other words, AS3 is always in "use strict" mode! And that's a good thing ! :P -Mark smime.p7s Description: S/MIME cryptographic signature
RE: Re: Updating the Website with the new ASF logo?
Didn't notice that... however it's an awesome reference. Especially if you consider the other ones mentioned too. -Original Message- From: Nicholas Kwiatkowski [mailto:nicholaskwiatkow...@gmail.com] Sent: Wednesday, January 27, 2016 4:22 PM To: dev@flex.apache.org Subject: Re: Updating the Website with the new ASF logo? But speaking of the new logo -- did anybody notice that Flex was specifically called out in the press-release as "best in class software project"? https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86 On Wed, Jan 27, 2016 at 9:28 AM, Christofer Dutz wrote: > Hi, > > as it's now official ... how about changing the Logo on our website? > I would do it, but I guess there are enough people here that actually know > how to do it ;-) > > Chris >
RE: [Non-DoD Source] NativeProcess is not exiting
If you are windows you could include a command line option for a taskkill [1] if you have any scripts running. [1] taskkill /F /IM java.exe -Mark -Original Message- From: dhwanishah85 [mailto:dhwanisha...@gmail.com] Sent: Thursday, January 07, 2016 7:02 AM To: dev@flex.apache.org Subject: [Non-DoD Source] NativeProcess is not exiting Hi, I am working on Developing an IDE for flex named "Moonshine". In order to make FDB work, I need to start 3 nativeprocesses. FDB itself is java process and thus it starts java.exe in system processes. When I build-debug my small flex application with intentionally changed AIR version number to wrong number and this will make runtime fail and throwing - "error while loading initial content". Thus we catch this error and step by step making nativeprocess exit. But I can not able to make java.exe exit. And this causes issues when i run application again after correcting the version number in app.xml file. In next run of the application i am getting message from fdb that "(fdb) Another Flash debugger is probably running; please close it. Details: 'Unrecognized Windows Sockets error: 0: JVM_Bind'." Please suggest how to make java.exe exit. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/NativeProcess-is-not-exiting-tp51079.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [LAST CALL] Release Apache Flex 4.15
+1 All seemed to check out for me. I used the 4.15 branch to check since I cannot access the apacheflexbuild.cloudapp.net on port 8080 from here. Our proxies do not like it. -Mark -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Monday, December 28, 2015 12:03 AM To: dev@flex.apache.org Subject: [LAST CALL] Release Apache Flex 4.15 Hi, There only a couple of outstanding questions/minor README changes before we’re ready to make a release candidate for Apache Flex SDK 4.15. Can people please check the current CI build [1] and check that everything is in working order. In particular can you check that: - README and RELEASE_NOTES are up to date - LICENSE and NOTICE are correct - You can compile from source - The new SDK (either compile or binary) can be used in an IDE and can be used to compile existing projects Thanks, Justin 1.http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/lastSuccessfulBuild/artifact/out/
RE: [FalconJX] Is it time to delete the FalconJS code?
Might as well make an archive folder that's generic and we can put anything else we want to keep but don't want in the main source areas. -Mark
RE: [FlexJS] No more JS!
Awesome news. A great milestone. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, December 17, 2015 3:09 AM To: dev@flex.apache.org Subject: [FlexJS] No more JS! Hi, I am happy to announce that we've completed the "back port" of the FlexJS JavaScript files to ActionScript. There are no longer any JavaScript source files in the FlexJS framework code base. All JS-specific code is now written in ActionScript and cross-compiled to JavaScript. This is a significant accomplishment because it proves that ActionScript is a viable object-oriented language for writing JavaScript, similar to how TypeScript is used. And it proves that our tool chain and workflow can be used to create large code bases that utilize 3rd-party libraries. Thanks go to all of those who were involved in this effort. I expect that, going forward, our productivity in developing FlexJS will be higher because we won't have to deal with as many mistakes in our JS code. The tool chain catches lots of issues long before you run anything. I'm sure there will be bugs to fix from the back port, and plenty of bugs in JIRA already, but now we can get back to bug fixes and features and making FlexJS the new way of creating applications. Short-term, I'm hoping we'll get the regular Flex 4.15.0 SDK released soon, then I hope to release all of this back-ported code as a FlexJS 0.6.0. Thanks, -Alex
RE: mustella for charts
Wow, so based on your link [1] we can get get FTE on MX components. Just
change its textFieldClass and set an embedded font with CFF enabled. I may
give this a shot later on some reports.
Can be changed in the mxml by:
Or in CSS by:
mx|Label
{
textFieldClass:ClassReference("mx.core.UIFTETextField");
}
[1]
http://help.adobe.com/en_US/flex/using/WSda78ed3a750d6b8f-26a13bbf123c441239d-8000.html
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, December 14, 2015 1:16 AM
To: dev@flex.apache.org
Subject: Re: mustella for charts
So, I did some digging and found that:
1) Before the change to default to mx:Label, the Mustella chart tests were
using Spark Label with embedded fonts.
2) There was already plumbing to better support Spark Label in Charts. I
didn't know about it, but it appears that you are supposed to use the
MXFTEText.css theme [2]. I tried it on the sample in FLEX-34909 [1] and
it seemed to work there. It would be great if someone would confirm.
FWIW, I found that in [2] I had to use the actual path to MXFTEText.css, I
couldn't just start with "frameworks/projects..."
So, I think we should revert back to defaulting to using Spark Label and
then these tests should start passing again.
Thoughts?
-Alex
[1] https://issues.apache.org/jira/browse/FLEX-34909
[2]
http://help.adobe.com/en_US/flex/using/WSda78ed3a750d6b8f-26a13bbf123c44123
9d-8000.html
On 12/11/15, 11:32 AM, "Alex Harui" wrote:
>I don't see any obvious degradation, but I know folks much better eyes
>than I do. I think you are seeing the difference in rendering between
>device and embedded fonts and maybe also TextLine vs TextField.
>
>There have been complaints in the past about embedded fonts looking more
>fuzzy or blurry compared to device fonts. I think it has to do with the
>glyph renderer getting too confident that it can render stems on
>half-pixels instead of messing with kerning to try to put stems on pixels.
>
>-Alex
>
>From: Mark Kessler
>mailto:kesslerconsult...@gmail.com>>
>Reply-To: "dev@flex.apache.org"
>mailto:dev@flex.apache.org>>
>Date: Friday, December 11, 2015 at 11:21 AM
>To: "dev@flex.apache.org"
>mailto:dev@flex.apache.org>>
>Subject: Re: mustella for charts
>
>Original baseline image: http://tinypic.com/r/245y5xe/9
>Current Bad image: http://tinypic.com/r/f0nnd0/9
>
>
>
>On Fri, Dec 11, 2015 at 2:02 PM, Mark Kessler
>mailto:kesslerconsult...@gmail.com>> wrote:
>I'll hold off then for now. But I can tell you the current fonts being
>shown in the baseline have a higher clarity than what the new baselines
>would show. I'll see if this example goes through. First is current,
>second is the new one.
>
>
>[Inline image 3][Inline image 4]
>-Mark
>
>On Fri, Dec 11, 2015 at 1:04 PM, Alex Harui
>mailto:aha...@adobe.com>> wrote:
>
>
>On 12/11/15, 9:57 AM, "omup...@gmail.com on
>behalf of OmPrakash Muppirala"
>mailto:omup...@gmail.com> on behalf of
>bigosma...@gmail.com> wrote:
>
>>Do you know if Spark labels ever worked with Charts? I dont think so.
>
>I was wondering that myself. Somehow, the current chart baseline images
>are showing text, so one thing I was going to do was dig into it to see
>whether it was using TextLine or TextField. Maybe it is using TextLine
>with device fonts. Certainly, your changes caused subtle rendering
>differences and it might be useful to truly understand what the impact
>will be. If someone could use right-to-left text with TextLine and device
>fonts in Charts today, then replacing TextLine with TextField will break
>them.
>
>-Alex
>
>
>
RE: Mustella fixing (was Re: Next Flex SDK release)
Well remember it's not just about rotating axis labels, but rotating the entire display to print out landscape easily. We try to use only spark components where we can. But things like charts and PrintDataGrids help knock out some decent reports. However they are mx only. For the embedded fonts, we have 4 declarations in our css. With / without CFF for both the regular font and bold font. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, December 08, 2015 11:11 AM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK release) Ah yes, axis label rotation forces you to embed the fonts. I'm wondering how many folks take advantage of rotated axis labels? In your apps with Charts, are they using Spark controls in the rest of the UI? Many people have to embed both a normal and bold font, the thing is, with the current code in the repo, if you had embedded those fonts with embedAsCFF=true to use in Spark controls, you would have to now also embed the font with embedAsCFF=false, and if you use bold labels on the Charts, you would need to embed both the normal and bold font with embedAsCFF=false. -Alex
RE: Re: AW: [DISCUSS] Adopting AS3Commons
We are talking about adopting the source. It makes sense to bring over ActionScript utilities that people still actively use. Even when they stop being supported in their current site. It helps keep the echo system a little stronger. -Mark -Original Message- From: lizhi [mailto:s...@qq.com] Sent: Tuesday, December 08, 2015 2:15 AM To: dev@flex.apache.org Subject: Re: AW: [DISCUSS] Adopting AS3Commons i thinks it is just a lib.it in the github is good.why put it to flex? the flex should clear. if the flex can not use the lib from github,should fixed,it is a bug. why put some lib in flex? -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Adopting-AS3Commons-tp50473p50546.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: Mustella fixing (was Re: Next Flex SDK release)
If I remember correctly one of the main reasons we started embedding fonts was to be able to rotate text on reports. The other being a consistent font no matter the platform/browser. We had to embed a normal font and a bold one. To make a smidge smaller, we used the "unicode-range" in the CSS. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 07, 2015 12:41 PM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK release) On 12/7/15, 9:07 AM, "Kessler CTR Mark J" wrote: > >To me it makes to have mx labels in the MX charts. If we create >some spark charts, using spark labels would make sense. However you >would have to embed the fonts again. The downside to not embedding the >fonts and just using what your default font is, the tests would show >bitmap compare issues more frequently. Right now it looks like the >majority of the failures are bitmap comparisons. Right, the failures are bitmap failures because there are slight differences in the way TextField vs TextLine render text. I don't know if that matters to anyone or not. If we decide not to support embedded fonts for Spark Label, then someone can just cut new baselines and the bitmaps will compare again. More background: Back in the Adobe days, there wasn't enough time on the schedule to create a whole new set of Spark Charts, plus I believe that the thinking was that because Charts already provided a consistent approach to customization of every aspect of the visuals, there wasn't much to be gained by trying to create a whole new set of components on top of SkinnableComponent. IOW, the actual chart component itself (PieChart, BarChart, etc) doesn't have anything to be skinned, and it wasn't clear that was much to be gained by having the things like the Axis and lines and bars and wedges and other pieces be SkinnableComponents. So, a bunch of code was added so that, if there is a Spark Label linked into the SWF, the Charts would default to using that, otherwise in a pure MX project, they use MX Label. I think that was done so you could use Charts in Mobile projects which are supposed to be Spark-Only (and other Spark-only desktop and web projects). Maybe the better question is: Do any of you actually create Spark-only apps? I don't know what the cost of embedding a font twice is for the larger unicode fonts, but I thought that folks building out Mobile apps were trying to make them Spark-only. But maybe you don't embed fonts in Mobile apps or the additional size isn't a problem? And as I mentioned earlier, I don't know if right-to-left text actually would work in Charts with Spark Labels and whether there are other things you can do with embedded CFF fonts that folks won't be able to use in Charts that matter either. So from a capabilities standpoint, I think we should support Spark Label and embedded CFF fonts, but from a practical standpoint, I'm unclear whether it is worth it. -Alex
RE: Mustella fixing (was Re: Next Flex SDK release)
To me it makes to have mx labels in the MX charts. If we create some spark charts, using spark labels would make sense. However you would have to embed the fonts again. The downside to not embedding the fonts and just using what your default font is, the tests would show bitmap compare issues more frequently. Right now it looks like the majority of the failures are bitmap comparisons. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, December 07, 2015 11:24 AM To: dev@flex.apache.org Subject: Re: Mustella fixing (was Re: Next Flex SDK release) On 12/7/15, 5:33 AM, "Tom Chiverton" wrote: >On 24/11/15 19:00, OmPrakash Muppirala wrote: >> And do you think I can close this issue as fixed for now? > >The Mustella tests are still failing... My understanding of the situation is: 1) I'm still not sure we have the right solution in the repo. AIUI, there still isn't a way to use embedded fonts with Spark Label in Charts. You have to use device fonts, or embed both CFF and non-CFF and use MX Label. Nobody spoke up for or against having such a limitation so maybe it doesn't matter. If folks had spoken up that they wanted to use embedded fonts with Spark Label then I would volunteer to try to figure out how to get that to work. 2) Mihai fixed a bunch of tests then ran out of time. Hopefully he'll be able to find more time soon. I don't know if were in a big hurry to get this release out, so I've been focusing on trying to finish up the FlexJS back port, which Peter and I hope to finish this week. Then I might be able to help out here if these are the only remaining issues. -Alex
RE: [DISCUSS] Adopting AS3Commons
Well if we are moving some of the stuff around, but want to allow people to still find it... Should we make the utils and AS3commons its own namespace / library to make it an easier transition for people? Then they would just have to add a new header property to access the previous components / methods. xmlns:u="library://ns.apache.org/flex/utils" -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Sunday, December 06, 2015 12:25 AM To: dev@flex.apache.org Subject: Re: [DISCUSS] Adopting AS3Commons I'm not a fan of changing the package names. Already this week we heard folks wanting AMF because they don't want to change their backend, and I've heard several folks wanting a more Spark-like API surface for FlexJS. My new mantra for 2016 is to try to not make more work for folks who are migrating their code. What do we really gain by changing package names and making folks alter their code? Would we also switch out mx and spark for org.apache.flex? I suppose we could bundle AS3Commons with the SDK, but keep in mind that I think we want to make as much of AS3Commons work for FlexJS as well. @Chris and/or Christophe, what other libraries is AS3Commons dependent on that we need to be concerned about? Thanks, -Alex
RE: [DISCUSS] Adopting AS3Commons
Good point, we should keep it the same then. However if we do have to reorganize it in the future, we can go over options then. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Friday, December 04, 2015 10:52 AM To: dev@flex.apache.org Subject: Re: [DISCUSS] Adopting AS3Commons I'd either leave it as is: org.as3commons Or add apache: org.apache.as3commons Or add apache.flex: org.apache.flex.as3commons Or hint at Apache Commons: org.apache.commons.as3 There is backward compatibility to be considered, so if we rename the packages folks would have to change their source code to use it, so I'd probably lean towards leaving it as is. -Alex
RE: Adopting Swiz
+1 r/s -Mark Kessler Senior Program Analyst MCICOM G4 Phone: (571) 256-7089 Email: mark.kessler@usmc.mil -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Thursday, December 03, 2015 12:46 PM To: dev@flex.apache.org Subject: Adopting Swiz Hi, As I mentioned in the "Adopting AS3Commons" discussion, the Software Grant process is not always required to accept a code base under the Apache License. Over two years ago, we voted to accept the "donation" of the Swiz framework. The donation was never completed because the donor never completed the Software Grant process, probably because it was too difficult to track down every past contributor and get their signature. The same sort of email we will be sending to the past AS3Commons contributors if we vote to adopt AS3Commons I am planning to send to the past Swiz contributors and see if we can take in the Swiz code if we get positive responses from the major contributors and no objections. But I wanted to let everyone here know first in case there are objections. Thoughts? -Alex smime.p7s Description: S/MIME cryptographic signature
RE: Re: [DISCUSS] Adopting AS3Commons
+1 Would we store it under something like "org.apache.flex.utils"? -Mark
RE: APACHE FLEX 4.14 WITH FLASHDEVELOP
Pretty much as Alex said. Just add the SDK path in first [1] globally. Then create a new Flex 4 project. Copy the source into the src folder. Right click on the main source file in the project tree view and click on the "Set Document Class". Should be a good start. [1] https://cwiki.apache.org/confluence/display/FLEX/2.3+FlashDevelop -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, December 02, 2015 12:57 PM To: dev@flex.apache.org Subject: Re: APACHE FLEX 4.14 WITH FLASHDEVELOP I haven't used FlashDevelop, so I don't know if there is a better way, but I would imagine you could create an empty project and copy source files. -Alex
RE: AW: [FALCONJX] Java Versions
Security wise, I think we should be allowing the latest Java's to be used. -Mark
RE: do-while-false
Let me see if I can reformat into all the examples so we can have a real sample
for people. Below shows the original, what was committed. Then shows the last
few examples. Hopefully this won't get word wrapped to badly or have font
issues.
The original was changed to better group the sets of conditions and added
brackets to be able to see the "do something" separated from the conditions
better. My input for it would be; what you choose will be based on the current
code and will vary with each case.
Original:
if (prompt != null && prompt != "" && skin && skin.currentState &&
(skin.currentState.indexOf("WithPrompt") != -1 && text.length != 0 ||
skin.currentState.indexOf("WithPrompt") == -1 && text.length == 0))
invalidateSkinState();
Commited:
if (prompt != null && prompt != "" && skin && skin.currentState)
{
if (skin.currentState.indexOf("WithPrompt") != -1 && text.length != 0 ||
skin.currentState.indexOf("WithPrompt") == -1 && text.length == 0)
{
invalidateSkinState();
}
}
example 1:
if (prompt != null)
{
if (prompt != "")
{
if (skin)
{
if (skin.currentState)
{
if (skin.currentState.indexOf("WithPrompt") != -1 &&
text.length != 0 ||
skin.currentState.indexOf("WithPrompt") == -1 &&
text.length == 0)
{
invalidateSkinState();
}
}
}
}
}
example 2:
do
{
if(prompt == null){break};
if(prompt == ""){break};
if(!skin){break};
if(!skin.currentState){break};
if(skin.currentState.indexOf("WithPrompt") == -1 && text.length != 0 ||
skin.currentState.indexOf("WithPrompt") != -1 && text.length ==
0){break};
invalidateSkinState()
break;
} while(false);
-Mark
-Original Message-
From: Harbs [mailto:harbs.li...@gmail.com]
Sent: Thursday, November 19, 2015 3:16 AM
To: dev@flex.apache.org
Subject: do-while-false
There’s a coding pattern that I like to use which I picked up from the InDesign
SDK. When there’s some code which needs a lot of conditions to be executed,
it’s hard to write the conditions in a way that’s easily human readable.
You can either do:
if(conditiona && conditionb && conditionc &&conditiond(
{
//do something
}
or:
if(conditiona){
if(conditionb){
if(conditionc){
if(conditiond){
// do something
}
}
}
}
Both of these are kind of hard on the eyes and make fixes error-prone.
The do-while-false solution is much more ledgible than both of these and it
goes like this:
do{
if(!conditiona){break};
if(!conditionb){break};
if(!conditionc){break};
if(!conditiond){break};
//do something
}while(false);
The reason it works is that do-while-false executes exactly once, and break
leaves the “loop”.
The pattern reverses the logic and instead of checking when you *should*
execute the code, it checks when you should bail out. The reason I like this
pattern is because it makes for much flatter code and each condition stands on
its own. That makes it easy to read and fix conditions at a later point.
How do folks feel about trying to use this pattern?
What prompted this post is commit b29975c which attempts to make a mess of
conditions for invalidateSkinState() a bit clearer.
Thoughts?
Harbs
RE: Next Flex SDK release
I meant to go back and look at that one a while ago, guess it fell off my radar. I'll have a look at it tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, November 18, 2015 12:53 AM To: dev@flex.apache.org Subject: Re: Next Flex SDK release 1) Deferred setFocus https://issues.apache.org/jira/browse/FLEX-34954 This was caused by commit d5c329722cd60568c53210973024b591b912b486 to fix https://issues.apache.org/jira/browse/FLEX-33537 I’d like to get Mark’s thoughts on reverting that commit. It did fix the issue in FLEX-33537, but did cause a lot of other issues. I honestly don’t have my mind made up on what to do. Thanks, -Alex
RE: Those @#*$^ Environment Variables
It was just based on someone else's comment about cleaning up and restructuring some. I'm sure it only really affects those of us who using synching. Having a few thousand less files per sdk to check/synch can make a speed difference. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, November 16, 2015 1:45 PM To: dev@flex.apache.org Subject: Re: Those @#*$^ Environment Variables On 11/16/15, 9:36 AM, "Kessler CTR Mark J" wrote: >Well for one of my dev machines, we've removed all the source, build >files, property files, samples, and templates out of the folders. >Multiple SDK's stored in a shared parent folder. The sdk folders are >labeled things like "Flex 4.14.1" / "Flex 4.13.0" / "Flex 4.6.0". I have >them setup in FD so if I need to change the SDK used in a project I can >simply select it out of a drop down in the project properties. I think I’m still lost. Is there a benefit to removing those files other than saving disk space? The Installer can install individual Flex versions to a shared parent folder if you want, and at least in FB, I can install each SDK version and switch between them. -Alex
RE: Those @#*$^ Environment Variables
Well for one of my dev machines, we've removed all the source, build files, property files, samples, and templates out of the folders. Multiple SDK's stored in a shared parent folder. The sdk folders are labeled things like "Flex 4.14.1" / "Flex 4.13.0" / "Flex 4.6.0". I have them setup in FD so if I need to change the SDK used in a project I can simply select it out of a drop down in the project properties. If I need to debug the SDK, I would grab the latest SDK source from development and have it as a project separately. If the problem doesn't exist there, it may be time to update to the latest SDK. If it still exists, then add a patch to the develop branch and put a workaround / monkey patch the current project. It's harder for us to just recompile the current sdk with changes, since that would change the RSLs and also affect our shared modules in use. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, November 16, 2015 11:14 AM To: dev@flex.apache.org Subject: Re: Those @#*$^ Environment Variables On 11/16/15, 5:23 AM, "Kessler CTR Mark J" wrote: > >One my ideas for improvement would be to change the way we do binary >packages. The strip out everything from the binary package except the >bare bones of what is required. So just keep it the libraries, asdocs, >licenses, notices and such. Keeping the source 100% separate since the >binaries are not official anyways. This would allow us to have a >smaller, less cluttered structure. Would make it easier to have folders >with multiple version of the SDK binaries available as well. Can you provide another level of detail as to what you mean? What would you kick out of the binary package? We’ve always shipped the AS source for the SWCs so they can be used in debugging. -Alex
RE: Those @#*$^ Environment Variables
I use the environmental variables. Especially when I synch sdk/air/global files between development machines. My main work development machine is on a private network. Each of my machines are setup with different paths and have slightly different environments. Using scripts to setup the environmental variables is easy to do for windows at least (setx var value)[1]. Not to mention doesn't clutter up my c drive / root areas.We should always allow for choices of paths without having to change config files on every machine. I am however not opposed to restructuring however. One my ideas for improvement would be to change the way we do binary packages. The strip out everything from the binary package except the bare bones of what is required. So just keep it the libraries, asdocs, licenses, notices and such. Keeping the source 100% separate since the binaries are not official anyways. This would allow us to have a smaller, less cluttered structure. Would make it easier to have folders with multiple version of the SDK binaries available as well. [1] https://technet.microsoft.com/en-us/library/cc755104.aspx -Mark smime.p7s Description: S/MIME cryptographic signature
RE: Re: [FlexJS] Back port
Well not to mention the inline filtering which is part of the ease of use for the e4x, but harder to recreate. mySVG.parent.(somefield=="criteria") -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Monday, November 09, 2015 2:09 PM To: dev@flex.apache.org Subject: Re: [FlexJS] Back port On Mon, Nov 9, 2015 at 11:00 AM, Harbs wrote: > I’m not 100% clear on the status of the back-ports or the best way to go > about it. I figured I’d wait until we’re done with the release and then > coordinate with you and Peter. > > In the meantime, I started work on some XML classes. I pretty much decided > on departing a bit from classic E4X for two reasons: 1. It’s just about > impossibly to reproduce the E4X behavior. 2. E4X was always awkward to use. > I’m going to more or less copy the public API of XML, but my version of > XMLList is going to work differently. Both XML and XMLList (I’m calling > them XMLNode and XMLNodeList) will have filter functions which work similar > to Array filter functions. The only E4X expression I have used over and over is the ability to get an array of child nodes using the double-dot expression. For example: var mySVG:XML = ; We could write: var paths:XMLList = mySVG..path; I think if we can add support to just this (maybe a few more based on popular usage), we should be able to get existing Flex apps easily ported. Although, I am not sure how hard something like this would be to implement. Thoughts? Thanks, Om > This should allow getting chunks of XML in a more sane method than using > hard-to-read E4X expressions. > > I’m hoping to have something commit-able on that front by the end of the > week. > > I’ll try to follow what you are doing with DragDrop and Effects so I get a > better feel of how it’s done. > > On Nov 9, 2015, at 7:36 PM, Alex Harui wrote: > > > Harbs, > > > > Thanks for the commits for the back port. Let us know if you actually > > start work on porting an existing SWC. I’m going to wait another day > > before cutting the FalconJX RC2 in case Justin has more feedback on the > > LICENSE. So I am going to try to port dragdrop and effects. > > > > -Alex > > > > On 11/9/15, 12:12 AM, "Alex Harui" wrote: > > > >> > >> > >> On 11/8/15, 11:55 PM, "Harbs" wrote: > >>> > Meanwhile, Peter and I are back porting the SWCs one-by-one in the > core_js_to_as branch of flex-asjs. We haven’t written a how-to or > anything, but you can look at Binding, Core, Collections and HTML as > examples. > >>> > >>> Color me confused, but I still see all 3 source folders after switching > >>> to the back port branch. It looks like you’re doing the back-port in > the > >>> as folder? The folder clean-up will happen after the port is complete? > >> > >> The asjs folders should be empty (more or less) in Binding, Core, and > >> other completed SWCs. We move all .as files to the as/src folder and > fix > >> up the compile-asjs-config.xml files. We are keeping the js/src folders > >> for now, then we’ll delete them once we feel good we’ve ported them > >> correctly. > >>> > I think Peter is working on Charts and Mobile. Graphics builds > cleanly > but Peter needs to verify it. So, if you want, let us know what SWC > you > want to try and see if you can see the patterns from the other > projects > and change logs. > >>> > >>> I’ll spend some time studying this today. I just added compiler > arguments > >>> to the Flash Builder project files so AFB does not choke on the > compiler > >>> arguments. I’ll commit those changes shortly. FWIW, the only real error > >>> I'm getting is in HTML IScrollingLayoutParent that ILayoutParent is not > >>> found. > >> > >> I have to stop for the night, but I don’t think IScrollingLayoutParent > >> should be there anymore. Check the logs in the develop branch to > verify. > >> > >> Thanks for helping. > >> -Alex > >> > > > >
RE: vector error
Send an email to dev-unsubscr...@flex.apache.org [1] http://flex.apache.org/community-mailinglists.html -Mark -Original Message- From: Jack Freudenheim [mailto:j...@sounder.com] Sent: Tuesday, November 03, 2015 9:19 AM To: dev@flex.apache.org Subject: Re: vector error unsubscribe On 11/3/15 2:28 AM, Alex Harui wrote: > What output are you getting and what error occurs? > > -Alex > > On 11/2/15, 10:39 PM, "lizhi" wrote: > >> in as3. >> new Vector.<*>([1,1,1]); >> not the same Vector.<*>([1,1,1]); >> >> pls try >> >> >> >> -- >> View this message in context: >> http://apache-flex-development.247.n4.nabble.com/vector-error-tp49772p >> 49783.html >> Sent from the Apache Flex Development mailing list archive at Nabble.com.
RE: [Non-DoD Source] Re: [DISCUSS] Discuss Release Apache FlexJS 0.5.0 RC1
For the FlexUnit? I already had it in for the Falcon test folders. -Mark -Original Message- From: Justin Mclean [mailto:justinmcl...@me.com] Sent: Tuesday, November 03, 2015 9:39 PM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Discuss Release Apache FlexJS 0.5.0 RC1 Hi, > D:\PortableDev\FlexJS\frameworks\projects\Core\as\tests\build.xml:150: > java.util > .concurrent.ExecutionException: Socket timeout waiting for flexunit report >at java.util.concurrent.FutureTask.report(FutureTask.java:122) >at java.util.concurrent.FutureTask.get(FutureTask.java:192) >at org.flexunit.ant.tasks.TestRun.run(Unknown Source) >at org.flexunit.ant.tasks.FlexUnitTask.execute(Unknown Source) >at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) >at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces You need to add the swf directory to be trusted in the Global Security Settings panel. (Right click on the blank player window to bring it up). Thanks, Justin
RE: [Non-DoD Source] Re: [DISCUSS] Discuss Release Apache FlexJS 0.5.0 RC1
When I set the FALCON_HOME and the FALCONJX_HOME I added the path up to the LIB folder, but did not include the LIB folder to get that to work. So if I had a path... C:\FALCON\releasefolders\lib I would add FALCON_HOME = C:\FALCON\releasefolders -Mark -Original Message- From: Justin Mclean [mailto:justinmcl...@me.com] Sent: Wednesday, November 04, 2015 3:32 AM To: dev@flex.apache.org Subject: [Non-DoD Source] Re: [DISCUSS] Discuss Release Apache FlexJS 0.5.0 RC1 Hi, > That part of the build is building the AS SWC using Falcon not FalconJX. > So check FALCON_HOME/lib for compc and falcon-flexTasks.jar FALCON_HOME only has falcon-compc.jar and falcon-flexTasks.jar. There’s no compc.jar in there. ls $FALCON_HOME/lib compiler.jarfalcon-compc.jarfalcon-optimizer.jar externalfalcon-flexTasks.jarfalcon-swfdump.jar falcon-asc.jar falcon-mxmlc.jar > I noticed your FALCON_HOME and FALCONJX_HOME environment variables have > trailing “/“. Made no difference. Thanks, Justin
RE: [FlexJS] Framework using externs (was: Setup Error)
I'll take a look at it tonight. -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Sunday, October 18, 2015 10:35 AM To: dev@flex.apache.org Subject: Re: [FlexJS] Framework using externs (was: Setup Error) On 10/18/15, 12:39 AM, "Harbs" wrote: >What do I need to do to help with this? Well, my understanding of the release process is that folks who intend to vote on the release should examine the nightly build as if it were a release candidate. I’ve posted in the discuss threads a link to scripts that take you through the examination steps. Once we get enough feedback that the nightly looks ok, we can open a vote thread. Thanks, -Alex
RE: [ENQUIRY] Some general feedback on our build system
1. Yes 2. Setting it up from scratch is a trial by fire. Much easier after you've done it once. 3. I'm sure it would change the way people contribute if their stopping block was just setting things up. 4. Yes, if people want to test/use the possibly unstable versions. This could however allow them to gain a new feature or bug fix before our next release. -Mark -Original Message- From: Christofer Dutz [mailto:christofer.d...@c-ware.de] Sent: Friday, October 02, 2015 8:23 AM To: 'dev@flex.apache.org'; us...@flex.apache.org Subject: [ENQUIRY] Some general feedback on our build system Hi, I would like to take the opportunity to ask the people registered to our mailing lists regarding their experience with the builds of our projects. Q1: Have you ever built flex-sdk, flex-falcon, flex-asjs, ...? Q2: Did you have any problems with this? Q3: If you were having problems, would making this easier make you contribute (more)? Q4: Do you think it is important to have the latest development version available as binaries (via Installer and Maven)? I would greatly appreciate if the one or the other on our lists could take the time to answer at least some of these questions. Chris
RE: Mustella server stuck?
Sounds good, thank you. -Mark -Original Message- From: Erik de Bruin [mailto:e...@ixsoftware.nl] Sent: Thursday, August 20, 2015 8:57 AM To: dev@flex.apache.org Subject: Re: Mustella server stuck? That'd be me ;-) I'm AFK until Monday, then I'll do a hard reboot and update some stuff as well. OK? EdB
RE: Mustella server stuck?
If you don't mind me being slow on it, I'll help clean up the SDK ones. It looks like they are mostly bitmap compare issues. So mostly looking at the bad ones and seeing something has changed like a skin / layout. -Mark -Original Message- From: Tom Chiverton [mailto:t...@extravision.com] Sent: Monday, August 17, 2015 7:05 AM To: dev@flex.apache.org Subject: Re: Mustella server stuck? I killed a long running job this morning, so it's catching up. flex-sdk_mustella needs some love at some point. Sadly my hotel last week had no wifi :-/ Tom On 17/08/15 10:56, Kessler CTR Mark J wrote: > Is the Mustella server stuck on the mobile tests from 11 days ago? > > [1] http://flex-mustella.cloudapp.net/ > > -Mark > > __ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > __ >
Mustella server stuck?
Is the Mustella server stuck on the mobile tests from 11 days ago? [1] http://flex-mustella.cloudapp.net/ -Mark
RE: [FLEXJS] Layout
The HTML resetting basically baselines all the browsers to roughly the same
default state. We have used it in the past to give a better starting point.
Here is a sample block of it that shows it resetting quite a few tags defaults.
The concept is to run the reset.css file before you set up anything else. So
instead of putting it in flex JS, just put in the inline css load to the
generated html doc.
html, body, div, span, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
abbr, address, cite, code,
del, dfn, em, img, ins, kbd, q, samp,
small, strong, sub, sup, var,
b, i,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, figcaption, figure,
footer, header, hgroup, menu, nav, section, summary,
time, mark, audio, video {
margin:0;
padding:0;
border:0;
outline:0;
font-size:100%;
vertical-align:baseline;
background:transparent;
}
[1] (older one, but one of the originals)
http://meyerweb.com/eric/tools/css/reset/
[2] http://html5reset.org/
[3] http://html5doctor.com/html-5-reset-stylesheet/
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, August 10, 2015 9:13 AM
To: dev@flex.apache.org
Subject: Re: [FLEXJS] Layout
On 8/10/15, 5:57 AM, "Kessler CTR Mark J"
wrote:
>Just a side bar question. Does FlexJS use any type of html5/css reset
>files for setting up default formatting?
I had to lookup what that is. There isn’t such a thing now, but it can
certainly be added to the html5 library. I think it would be equivalent
to a theme. If you look at at the flat.swc I added recently, it has a
different implementation of controls and its own defaults.css.
Remember, there is lots of stuff missing in FlexJS right now, but the
basic principle is that any patterns you use often should be encapsulated,
abstracted, and then plugged into the workflow somehow.
HTH,
-Alex
RE: [FLEXJS] Layout
Just a side bar question. Does FlexJS use any type of html5/css reset files for setting up default formatting? r/s -Mark Kessler Senior Program Analyst MCICOM G4 Phone: (571) 256-7089 Email: mark.kessler@usmc.mil -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Saturday, August 08, 2015 12:50 AM To: dev@flex.apache.org Subject: [FLEXJS] Layout One of my goals for FlexJS is to leverage as much code in the browser as possible. That’s why there are button components that thinly wrap the HTML button element. You can pay-as-you-go and select heavier buttons that allow more complex skinning and/or styling. I thought we’d be able to leverage the browser’s layout code for vertical and horizontal layout. The current version sets the children to display:block or display:inline-block. That’s much less code than running a loop on the children, figuring out margins, left/right constraints, etc, and therefore less code to write, debug and maintain. But these days, I’m starting to wonder if one of the benefits of FlexJS will be in the availability of layouts that pretty much use position:absolute to control everything. There are lots of funky rules and workarounds for how browsers deal with display:inline-block, for example. Anyway, I’m wondering if there is anything, besides performance, we might give up by giving up on display:inline-block and writing our own horizontal layout. Thoughts? -Alex
RE: [FlexJS] FlexJS installation - bundle Google Closure Library?
So we have two schools of thought on it. Option 1. Keep downloading it so we can have the most up-to-date version (for better or worse). Option 2. Keep the current working copy and not having another upgrade until we release a new version. -Mark -Original Message- From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of Carlos Rovira Sent: Thursday, July 30, 2015 10:43 AM To: dev@flex.apache.org Subject: Re: [FlexJS] FlexJS installation - bundle Google Closure Library? +1 2015-07-30 15:09 GMT+02:00 Alex Harui : > If someone wants to make these changes, I won’t object, but IMO, Google > Closure Library changes often, usually for the better. Bundling will tie > a FlexJS release to a particular version of GCL and that may not always be > desirable at this point. I believe we have the option of changing the > installer so it downloads GCL without asking for license approval as well. > > -Alex > > On 7/30/15, 4:26 AM, "Kessler CTR Mark J" > wrote: > > >+1 > > > >-Mark > > > >-Original Message- > >From: Justin Mclean [mailto:jus...@classsoftware.com] > >Sent: Wednesday, July 29, 2015 8:40 PM > >To: dev@flex.apache.org > >Subject: Re: [FlexJS] FlexJS installation - bundle Google Closure Library? > > > >Hi, > > > >> Since Google Closure Library is also Apache licensed, can we package it > >> with the binary release instead of having the Installer download it > >> separately? > > > >+1 and also any other MIT or BSD licensed stuff. Mean will have to make > >some minor mods to NOTICE/LICENSE but it's straight forward. > > > >Justin > > -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Tres Creus, nº 104, 2-1, 08202 de Sabadell (Barcelona) con la documentación necesaria.
RE: [FlexJS] FlexJS installation - bundle Google Closure Library?
+1 -Mark -Original Message- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Wednesday, July 29, 2015 8:40 PM To: dev@flex.apache.org Subject: Re: [FlexJS] FlexJS installation - bundle Google Closure Library? Hi, > Since Google Closure Library is also Apache licensed, can we package it > with the binary release instead of having the Installer download it > separately? +1 and also any other MIT or BSD licensed stuff. Mean will have to make some minor mods to NOTICE/LICENSE but it's straight forward. Justin
RE: Screenshare in AIR
Well adobe has their Connect [1] application. It runs in flash and can share a desktop [2], so I know something exists. Although I think people are changing over to Java for screen sharing these days since it's installed in most places already. [1] http://www.adobe.com/products/adobeconnect.html [2] https://community.apan.org/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-40-40/5672.Adobe-Connect-room.png -Mark
RE: [VOTE] Release Apache Flex SDK Installer 3.2 RC2
+0 I forgot to commit the README update last night . After that happens I'm good. (or if anyone else wants to update it) OS: Win 7 64bit English -Successfully built from source (after changing path). -Successfully installed. -Successfully downloaded sdk using installer. -Mark
RE: [DISCUSS] Discuss Release Apache Flex SDK Installer 3.2 RC2
I will be able to review this rc2 tonight (which is half a day away at this time). -Mark
RE: [FlexJS] FlexJS vs. AngularJS 2.0
On a side note, I remember fiddling with angular a while back. I bumped into this free training for it [1] that gave a good start up understanding of how some of the things work in it. [1] http://campus.codeschool.com/courses/shaping-up-with-angular-js/intro -Mark -Original Message- From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash Muppirala Sent: Monday, June 15, 2015 4:06 PM To: dev@flex.apache.org Subject: [FlexJS] FlexJS vs. AngularJS 2.0 Here is a rundown of how to do things with AngularJS 2.0: http://angular-tips.com/blog/2015/06/why-will-angular-2-rock/ As I walk through the details, I see the twists and turns they are going through to do seemingly simple things. The single biggest reason for that is that there is no MXML like malleable way to declaratively create the UI and to wire things up. I am interested in seeing a step by step comparison of doing things the FlexJS way vs. AngularJS2.0 way. Here are a few things we can concentrate on: 1. Module loading 2. Classes 4. Components 5. Design Patterns 6. Events 7. Calling webservices 8. Skinning ... Anyone wants to volunteer to help write this document? This would involve understanding and writing FlexJS code samples. This would also involve understanding AngularJS2.0 as well. Which is a benefit on its own. Volunteers? Thanks, Om
RE: [GENERA-ASK] Start using paste.apache.org :)
Depends if they keep the data for as long as we keep mail archives. Otherwise it makes the mail archives less valuable. Can always do both though :) -Mark -Original Message- From: piotrz [mailto:piotrzarzyck...@gmail.com] Sent: Thursday, June 11, 2015 1:46 AM To: dev@flex.apache.org Subject: [GENERA-ASK] Start using paste.apache.org :) Hi Team, I'm struggling a lot with the problem of reading post on this dev list which is mixed with code or stack traces. I have polite ask to all commiters and PMCs please start using [1]. It will increase a lot readabiliti of our posts. :) [1] https://paste.apache.org Thank you, Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/GENERA-ASK-Start-using-paste-apache-org-tp47621.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
