Board report for October 2022 has been submitted
## Description: The mission of the Apache Flex project is to create and maintain software related to the development of expressive web applications that deploy to all major browsers, desktops and devices (including smartphones, tablets and tv) ## Issues: ## Membership Data: Apache Flex was founded 2012-12-19 (10 years ago) There are currently 68 committers and 45 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Olaf Krüger on 2017-08-28. - No new committers. Last addition was Greg Dove on 2016-09-07. ## Project Activity: No changes have been made to the Flex framework for a long time. ## Community Health: There is nearly no mailing list activity at the Flex lists. Some Flex related discussions are held at the Apache Royale lists. The project is searching for a new chair.
Board report for September 2021 has been submitted
Hi guys, since there's nothing new to report and in order to ease things I directly submitted the due September board report without letting you proofread it... hope that's ok for you! The report is available at our wiki [1] Thanks, Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/September+2021
Re: Board report time (June 2021)
...it's submitted now. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (June 2021)
Hi guys, it's board report time, this is the draft: https://cwiki.apache.org/confluence/display/FLEX/June++2021 It's nearly a copy of the previous one. Please review it and feel free to add or remove whatever makes sense! The report has to be sent at the very latest until Wed Jun 9th. Thanks! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time March 2021
The report has been submitted. -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time March 2021
Hi Andrew, > No changes have been made Done, thanks!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time March 2021
Hi guys, it's board report time, this is the draft: https://cwiki.apache.org/confluence/display/FLEX/March++2021 Please review it and feel free to add or remove whatever makes sense! The report has to be sent at the very latest until Wed Mar 10th. Thanks! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: AIR app (Captive runtime) is blocked by anti-virus scanner
I accidently posted it on dev, moved to users: http://apache-flex-users.246.n4.nabble.com/AIR-app-Captive-runtime-is-blocked-by-anti-virus-scanner-td18485.html -- Sent from: http://apache-flex-development.247.n4.nabble.com/
AIR app (Captive runtime) is blocked by anti-virus scanner
Hi, since we moved some remaining Flex apps to AIR (Using captive runtime), some of users reports that the app is being blocked by their anti-virus-scanner. Because in some cases, the responsable IT-departments don't like to whitelist additional apps, we run into trouble. We are not yet using a "real" certificate at compile time. Could this be the problem? Or could there be anything else in the Flex / AIR apps that is causing the virus scanner to block it? Thanks in advance! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2020)
I just submitted the report, thanks! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2020)
It's fixed, thank you Andrew! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (December 2020)
Hi guys, it's board report time! The report has to be sent at the very latest until Wed Dec 9th. This is the draft [1]. It would be great if somebody could review it. Feel free to add or remove whatever makes sense! Thanks! Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/December+2020 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Flex Website -- next steps
+1 Thank you for working on this!! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report submitted (September 2020)
Hi guys, I am sorry, but I had some trouble with my incoming emails and totally overlooked the due board report reminder for September. So, I just prepared it quickly and pushed it without asking you guys to review it. You can find the submitted report here [1]. Hope that's ok for anybody, sorry again! Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/September+2020 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: the Flex website
This is, what Apache says: "When should a project move to the Attic? Projects whose PMC are unable to muster 3 votes for a release, who have no active committers or are unable to fulfill their reporting duties to the board are all good candidates for the Attic." [1] Olaf [1]https://attic.apache.org/ -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: the Flex website
Hi Andrew, not sure, but it looks like we're currently using the Apache CMS. This is from the Flex Wiki [1]: "It is currently running on the Apache CMS, which is loosely built on a combination of an mdtext compiler and Svnpubsub." IIRIC, Nicholas Kwiatkowski built the page originally. I took a look into your migration guide and it sounds like that we have to rewrite the entire page by using other technologies, e.g. one of the static site generators. Is that right? Thanks, Olaf [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=30754191 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2020)
The report has been sent, thanks to all for your help! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2020)
Thanks Leo! I just updated the report and will send it now! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2020)
Sounds good, thanks Leo! I'll mention this within the report. Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2020)
Thanks! >with the exception of the unanswered question about Harman. I thought you could say something about Harman ;-) However, if nobody has any news about it I'll just remove this section ;-) Thanks again, Andrew! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2020)
Hi Andrew, thanks for taking a look! I tried to share this document with you, not sure if that has any impact on the permissions. Are you basically able to login to the Confluence wiki? Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (June 2020)
Hi guys, it's board report time! The report has to be sent at the very latest until Wed June 10th. This is the draft [1]. It would be great if somebody could review it. Feel free to add or remove whatever makes sense! Thanks! Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/June+2020 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (March 2020)
Hi guys, it's board report time! [1] The report has to be sent at the very latest until Wed Mar 11th. I'll create a draft ASAP. Until then, if someone has something that needs to be mentioned, please leave a comment here! Thanks! Olaf [1] This email was sent on behalf of the ASF Board. It is an initial reminder to give you plenty of time to prepare the report. According to board records, you are listed as the chair of a committee that is due to submit a report this month. [1] [2] The meeting is scheduled for Wed, 18 Mar 2020 at 10:30 PDT and the deadline for submitting your report is 1 full week prior to that (Wed Mar 11th)! Meeting times in other time zones: https://timeanddate.com/s/4298 Please submit your report with sufficient time to allow the board members to review and digest. Again, the latest you should submit your report is 1 full week (7days) prior to the board meeting (Wed Mar 11th). If you feel that an error has been made, please consult [1] and if there is still an issue then contact the board directly. As always, PMC chairs are welcome to attend the board meeting. Thanks, The ASF Board [1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt [2] - https://svn.apache.org/repos/private/committers/board/calendar.txt [3] - https://svn.apache.org/repos/private/committers/board/templates [4] - https://reporter.apache.org/ -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
I've just posted the report. Thanks for the help! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
>https://github.com/apache/royale-asjs/wiki/Board-Report-2019-12 This is the Royale report ;-) However, I'll push the Flex version as it is now! Thanks! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
> I edited the board report that I saw in GitHub Not sure which board you mean. Could it be that you refer to the Royale report? If not so, please provide me a link ;-) Thanks for the help! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
> So...the simpler fix would be for every Royale committer to also be a Flex committer. I guess there's no way doing so since we have separated projects. Are you still plan to make some changes? You could post it here as Piotr mentioned. Otherwise, I would push it as it is. (I am travelling and not always have a proper connection) Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
>I could log in, but do not have sufficient permissions I just took a look at the document permissions. For me it looks like there're are no special restrictions defined, any logged-in user should be able to edit it. However, whatever way you find to edit it, thanks for the help!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
> Oops. Confluence says I am not permitted to access the document. Just the document or are you not able to login to the Confluence Wiki at all? Not sure if we I have to set special permissions to the particular document... -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (December 2019)
> I added a bit more info. Cool, thanks Carlos! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (December 2019)
Hi guys, it's board report time! I've created the December 2019 report here [1]. Please take a look at it and add or change things if needed! The report has to be sent until Wed Dec 11th. @Carlos Would be great if you could review/change the "#Project Activity" section in relation to the latest changes regarding Maven. Thanks! Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/December+2019 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Launch of the 2020 ASF Community Survey
Hello everyone, If you have an apache.org email, you should have received an email with an invitation to take the 2020 ASF Community Survey. Please take 15 minutes to complete it. If you do not have an apache.org email address or you didn’t receive a link, please follow this link to the survey: https://communitysurvey.limequery.org/454363 This survey is important because it will provide us with scientific information about our community, and shed some light on how we can collaborate better and become more diverse. Our last survey of this kind was implemented in 2016, which means that our existing data about Apache communities is outdated. The deadline to complete the survey is January 4th, 2020. You can find information about privacy on the survey’s Confluence page [1]. Your participation is paramount to the success of this project! Please consider filling out the survey, and share this news with your fellow Apache contributors. As individuals form the Apache community, your opinion matters: we want to hear your voice. If you have any questions about the survey or otherwise, please reach out to us! Kindly, ASF Diversity & Inclusion https://diversity.apache.org/ [1] https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discussion] About release flex-dk-converter-maven-extension
Seems that Piotr was faster and I overlooked his post ;-) -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discussion] About release flex-dk-converter-maven-extension
Hi, >I am registered in Apache Royale Users but i cant reply or create any new post Just to register is probably not enough, you have to subscribe to the list. See [1][2] or [3]. Hope this helps, Olaf [1] http://apache-royale-users.20374.n8.nabble.com/mailing_list/MailingListOptions.jtp?forum=1 [2] https://royale.apache.org/mailing-lists/ [3] https://apache.org/foundation/mailinglists.html -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (September 2019)
Hi, because we're in a hurry, I just submitted the report. Thanks, Carlos (at users) and Piotr for reviewing! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2019)
The June report is submitted! Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (June 2019)
I've just applied your changes. Thanks, Andrew! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (June 2019)
Hi guys, it's board report time! I've created the June 2019 report here [1]. Please take a look at it and add or change things if needed! The report has to be sent until Mon June 10th. Thanks, Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/June+2019 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (March 2019)
I've just submitted the report, thanks for the help!! -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (March 2019)
>I'm thinking whether it's important to mention that some PMC resigned in last three months. Thank you for this hint Piotr! AFAIK Dave and Carol resigned during this period (January to March 2019)? Carol still needs to be removed. Is that right? Scott resigned in the previous board report period of time. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Board report time (March 2019)
>I made some edits to the text for grammar and word use, not to the substance. Great, many thanks for your help, Andrew!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Board report time (March 2019)
Hi guys, it's board report time! I've created the March 2019 report here [1]. Please take a look at it and add or change things when needed! The report has to be sent until Wed Mar 13th. Thanks, Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/March++2019 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
[RESULT][VOTE] Moving JIRA issues and Confluence Wiki to GitHub
Failed. Result: [0]: 4 votes [+1]: 2 votes So we leave anything as it is. Thanks for voting! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Vote] Moving JIRA issues and Confluence Wiki to GitHub
+1 In 2018, 15 issues were created by using JIRA. So I don't expect too many duplicates for the future. If it is possible, we would set JIRA and the Conflucence Wiki read-only. -- Sent from: http://apache-flex-development.247.n4.nabble.com/
[Vote] Moving JIRA issues and Confluence Wiki to GitHub
Hi, this is the official vote thread to approve the move from JIRA issues to GitHub issues and to move the Confluence Wiki to the Github Wiki. As discussed here [1], the idea is to don't migrate the JIRA issues to GitHub. Instead, we want a clean restart at GitHub issues. The JIRA issues will be treated as an archive. We may will move some Wiki articles to GitHub. Vote [ ] +1 Agree [ ] -1 Veto (please provide specific comments) The vote passes if there is: - At least 3 +1 votes from the PMC - More positive votes than negative votes This vote will be open for at least 72 hours. [1] http://apache-flex-development.247.n4.nabble.com/Enabling-GitHub-quot-Issues-quot-and-quot-Wiki-quot-for-flex-repositories-td65601.html -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
@Justin > i’m that sure that it is. JIRA has a number of significant benefits over > GitHub issues including better searching and querying. (Yes I use both). Just to make sure that I got it right: Does that mean that you basically support the idea of moving from JIRA to GitHub issues or do you see some significant drawbacks? @All In order to get an "official" result, I propose to start a vote about it. Will do this soon... Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
> 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/
Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
> Do we know if it possible it import all historical JIRA issues ... I don't know it this is possible. > JIRA has a number of significant benefits over GitHub issues including > better searching and querying JIRA is probably more powerful but I guess the simplicity of GitHub is the greater advantage here. I think if we would go with GitHub issues it would be a good opportunity for a "clean restart". That doesn't mean that the existing JIRA issues are useless, these should remain there. Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Enabling GitHub "Issues" and "Wiki" for flex repositories
I was thinking more like a cut of the old Wiki and JIRA than a migration of the existing stuff. I think it would be easier and more transparent for folks to handle future development (if it will happen) by using GitHub. We may migrate some wiki stuff someday, don't know. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [LAZY] Mandatory migration of git repositories to gitbox.apache.org
> It looks like they have started doing something Yes, seems to be done ;-) -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Enabling GitHub "Issues" and "Wiki" for flex repositories
Hi, I would like to create an INFRA Jira in order to ask them to enable GitHub "Issues" and the "Wiki" for following repositories: - flex-tlf.git - flex-utilities.git - flex-flexunit.git - flex-site.git - flex-external.git - flex-sdk.git - flex-blazeds.git - flex-radii8.git We will maybe use these GitHub features mainly for the flex-sdk repo, but maybe it makes sense to just enable it for all flex repos? Any objections? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Clean-Up after migration to GitBox
Hi, the repositories are moved to GitBox [1]. Daniel from INFRA commented this: "Repositories have been moved. You'll have to sort out the mess with your two web site repos yourself, one is an svn clone, one is, I presume, a repo for a next gen site? Both were called the same thing, which caused some internal confusion. the ng repo has been called flex-site-ng.git now." So, we have two website repos now, flex-site [2] and flex-site-ng [3]. flex-site is the one which is life. Does anybody know what's about flex-site-ng? Can we leave it as it is or is there any need to do anything with it? @Piotr You offered to fix some things, what would you like to fix? Thanks, Olaf [1] https://issues.apache.org/jira/browse/INFRA-17574 [2] https://github.com/apache/flex-site [3] https://github.com/apache/flex-site-ng -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [LAZY] Mandatory migration of git repositories to gitbox.apache.org
Since nobody has objections I've created the Jira for INFRA: https://issues.apache.org/jira/browse/INFRA-17574 Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Hi Carlos, yes, the migration is mandatory. They will do the migration after February 7th without any warnings. But my understanding is, that they asked the communities to do it before this deadline orderly in order to avoid as much trouble as possible. Without any feedback from the communities, they won't migrate before February 7th. Of course, we could wait until February 7th, but the danger is that INFRA could be very busy then with fixing whatever other issues from other communities. If we want to let them do the migration earlier, we need to get a consensus about this and we need to inform INFRA. To get a consensus I thought a simple vote is a proper way. Makes sense? ...of course, I could be wrong ;-) Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Thanks for the explanation, Alex! > We should oblige and agree that they can move early... Just to make sure that we all are on the same path: Even if we expect some minor issues we want to let them do the migration ASAP. Each upcoming issue will be fixed after the migration is done. If that's right, I guess we should start a vote and when it's done I would file an INFRA JIRA which includes a link to the vote to let them know that they can migrate, right? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Hi, > -update any Flex jobs on builds.a.o. What is builds.a.o? > FWIW, I turned off my CI server for Flex several weeks ago Ok, for what was it used for? Do we need it for making a release? Is the installer affected by the migration? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Just an example of how the Hadoop community has handled the migration: https://issues.apache.org/jira/browse/INFRA-17448 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org
Hi guys, if I understand it correctly we have to vote for the migration and we optionally can specify a date for it. However, - Does anybody know if this migration will break anything? - Do we need to keep the FlexJS repositories (Maybe they can be deleted because they moved to Royale)? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Flex Roadmap 2019
Hi Leo, >I was wondering if there is anyone interested on updating / extending / >improving Flex SDK. Even if we're started using Royale we still heavily rely on Flex/AIR here and I guess we're not alone. > If so, we could discuss what might be good additions for > 2019 and make a roadmap. I think the problem with roadmaps is that enough resources are needed to process them. That said, we're at Apache here and the progress depends on anybody of us ;-) However, I think if we get some contributions we should try to bundle our forces in order to get another release out. I am curious about what others think about it. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Help required - Board report time
Hi Tom, I just copied the September report and added Piotr's text [1]. Maybe that helps? @Piotr Just a shoot in the dark: I always need some attempts to log in because I always forget that just the Apache ID is expected, not the email. Thanks, Olaf [1] https://cwiki.apache.org/confluence/display/FLEX/December+2018 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Question on Migrating from Flex to FlexJS
Hmm... just a test, I just replied and it seems my post didn't make it to the list. -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Question on Migrating from Flex to FlexJS
I noticed that rarely/sporadically some posts don't make it to the list for whatever reason. Maybe you just should give it another try...? Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: AMF for .NET Standard now available (.NET Core + olders runtimes)
Maybe this helps [1]. Regardless of the GPL, I understand it this way: If no license is used within a project, in theory, the project must not be used by anyone. So it's probably always a good idea to add a license which fits your needs. It also makes it easier for others to use your project. HTH, Olaf [1] https://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DRAFT] Apache Flex SDK Installer 3.3.2 Released!
Hi Piotr, thanks again for preparing the release! I just wonder if we should inform the users a bit more about what happens by using the current release. So, just a suggestion: Instead of this [1] maybe something like this?: The Apache Flex SDK Installer 3.3.2 is an update to the Apache Flex SDK Installer 3.3.1 which has an issue to handle large downloads because of its 32-bit version. In order to work around this issue, the 32-bit based installer runs a 64-bit version of the installer now. You'll be notified about this during the execution of the installer. Thanks, Olaf [1] Apache Flex SDK Installer 3.3.2 is an update to Apache Flex SDK Installer 3.3.1. It provides ability to run on Windows Apache Flex Installer as 64-bit app in order to handle large memory consumption during downloads. -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [VOTE] Apache Flex SDK Installer 3.3.2 RC2
+1 Windows7/64bit -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.2 RC2*
Hi, just a shoot in the dark: Did you make sure that the selected directory is empty? Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.2 RC1*
Hi Alex, thanks for the good explanation, got it now! Even if the NativeInstaller is more comfortable, maybe a CaptiveRuntime version which has to be downloaded is enough someday. However, thank you for making the installer work again!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.2 RC1*
Hi, it works for me on Windows7/64bit. Just my observations: - The first warning came up after starting the installer - After the SDK download has started the second warning came up and after confirming it the installer closed itself - After I manually restarted the installer I had to go through the initial steps again (without warnings) and from this point, it just works! As already mentioned it is not the best user experience but I think we can go with it as it is. I've not followed the entire discussions around the installer issues, so just for my understanding: Is the reason for this workaround only to get the Native Installer work in order to be able to start it from the webpage? And would work a "standalone captive runtime" version also? Thank you!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.2 RC1*
Just to give some more feedback for now: I've just downloaded and installed the installer on Windows7/64bit. After starting it I've got the first warning as mentioned. All works fine until this point. Because I am behind a proxy here I cannot continue testing, I'll try to continue with it tonight. Thanks for working on this! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Life after FlashPlayer, are you prepared?
Hello from the Apache Royale (FlexJS) team, even if Flex with AIR is still an awesome and outstanding technology, Flex in the browser ends with the end of FlashPlayer in 2020. To be clear: There will be no way to run your Flex apps in current browser versions around 2020! The Flex mailing lists are followed by a few hundred people and we assume that there are still a lot of Flex browser apps out there. So, we are really interested in what you are planning to do with your Flex apps, e.g. - Do you need to stick with the browser at all? - Do you plan to migrate your Flex apps to whatever other technology? - Did you already migrate your Flex apps to whatever other technology? - ... If you are reading this post and have a Flex app, please speak up about what your plans are! Thanks, The Apache Royale (FlexJS) team -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [VOTE] Apache Flex SDK Installer 3.3.1 RC3
+1 Tested on Windows 7 and Windows 10. I had some issues with the virus scanner on my Windows 7 business machine which exiles the *installer*.exe. Maybe others run into similar issues. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC3*
Just for the sake of completeness: Today, the installation was carried out to the end under Windows7, even if it still hangs a while while "Verifying Apache Flex SDK MD5 Signature". But after the installation was finished, our company virus scanner exiles the entire installer.exe for whatever reason. However, I guess the installer is ok ;-) On my private Windows10 machine it works like a charm! Thanks! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC3*
I'll give it another try tomorrow evening, also on Windows10. Thanks for working on this Piotr!!! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC3*
>How long did you wait ? Is this your first attempt ? About 20minutes, third attend... Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Discuss] Apache Flex SDK Installer 3.3.1 RC3*
Hi, the installer hangs here on my Windows7 machine while "Verifying Apache Flex SDK MD5 Signature". Is something broken or do I miss something? Thanks, Olaf [1] Installer version 3.3.1 (windows) Using Locale: en_GB Fetched the SDK download mirror URL from the CGI. SDK version Apache Flex SDK 4.16.1 AIR version 29.0 Flash Player version 29.0 Creating Apache Flex home Creating temporary directory Downloading Apache Flex SDK from: http://ftp.halifax.rwth-aachen.de/apache/flex/4.16.1/binaries/apache-flex-sdk-4.16.1-bin.zip Verifying Apache Flex SDK MD5 Signature -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Fontawesome 5
Hi, as soon I have time I'll try to make FontAwesome5 part of the SDK as its own project. For those who don't know how to use Font Awesome 5 with Flex: I've just created a little demo project and some explanation [1]. Hope this helps, Olaf [1] https://github.com/olafkrueger/FontAwesome5WithApacheFlex -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Fontawesome 5
FontAwesome4 is part of the flatspark project. I would like to propose to outsource FontAwesome5 into its own project. If I remember it correctly, such a project just needs the FontAwesome otf font files, a license file and an AS3 class that holds constants for each particular icon name. Thoughts? Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Fontawesome 5
Ahhh... I've just seen that you've already created the JIRA [1] Thanks, Olaf [1] https://issues.apache.org/jira/browse/FLEX-35380 -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: Fontawesome 5
Hi, if I understand it correctly, FontAwesome5 was rewritten from scratch and existing FontAwesome4 icons were replaced by new ones. So it seems to me that this update is not the same easy task which it was in the past. However, could you file a JIRA for this task? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [VOTE] What should be the new Project Name for Proposed fork of FlexJS?
1. Boja 2. Limber (Limbr) 3. Beads Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
[OT] Unsubscribed and offline for a few weeks
Hi, I'd just like to let you know that this my last day at work before I'll start a holiday trip over a few weeks. Hence I've been unsubscribed from the list. Probably I will be sporadically online. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
Could we try to summarize all name proposals in order to build a single post that contains all candidates (project names) before voting? I think it's not so easy to extract all naming ideas from the different threads/posts, I just remember a few. What do you think of just creating a list of previous proposals and new ones in reply to this post?: - Royale - Bend - ... Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
Another idea to get out the naming dilemma could be to find a name for the new project that still contains 'flex' but don't let you think of flex when you read it the first time, e.g.: ... Inflexion Flexor Flexure ... Just a Scrabble exercise... ;-) So people might be less confused if they find the word 'flex' in the codebase. Maybe current users and as well new users feel comfortable with such a name. Just a thought... Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
Hi, This was posted by Chris at the [VOTE] thread >and I know what getting rid of "flex" everywhere inside the project would mean regarding refactoring and >tool support. I thought that for now we just vote for a new project name in order to get rid of the word 'Flex' within the Apache project name. Hence I thought that there's no urgent need to replace the occurrence of the word 'flex' throughout the entire codebase. I think that there are a lot of projects out there which were renamed and still contains old names in their codebase. Do I misunderstand something? Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
>So same product but marketed with two different names? I think this is what we see in the real world all the time: Identical products are optimized (under different names) for local markets or special target groups to satisfy the needs of consumers. Sounds like a reasonable way to reach as many people as possible but it also means some more effort and there is a risk of confusing the people Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [VOTE] Should the Project Name of the Proposed Fork be FlexJS?
No (Binding) On 2017-09-14 08:37, Dave Fisher <[hidden email]> wrote: > 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. -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
Hi, I just would like to mention that it seems to me that there's an inner urge inside most of us to leave the beaten paths and to build a new identity for FlexJS which is more appropriate to this awesome technology in any respects. Moreover, it seems to me more and more that such a new shiny identity provides a fair chance to get more people involved. I just fear the effort. So thank you, Carlos, for your offer to help out with this!!! I like "bøje" which is the Danish translation for "bend" (I think this was already suggested by Harbs anywhere). I also like anagrams and words as names that don't exist yet, e.g.: Flex -> elfX However and whatever name, you got me! Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [FLEX JS] How to import mx.managers.PopUpManager?
m_awais wrote > I am trying to import mx.managers.PopUpManager in my flex JS project mxml > file. There's no way to use "s:" or "mx:" components with FlexJS! In general, you can't reuse anything that has a dependency to Flash or classic Flex! This is also true for e.g. the "mx.collections.ArrayCollection". HTH, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS] Name of the FlexJS Fork
I would stick with the name "FlexJS" for now. I do not think that people associate negative vibes with it. So many other JS frameworks are born every day, I think a new name may confuse people. But I agree that in future it could make sense to rename it, especially if there will be other targets than JS one day... who knows... Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [Flex JS] Adobe substitute
There's also a js:Panel [1]. And this is a working snippet [2] HTH, Olaf [1] https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/Basic/src/main/flex/org/apache/flex/html/Panel.as [2] -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [FlexJS][Installer] Future packaging of FlexJS releases
>If this sound good to folks.. This sounds really good, Alex!! I think it's an important thing to get rid of some dependencies and to ease the FlexJS setup. Thanks, Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [VOTE] Fork FlexJS from Apache Flex
+1 Olaf -- Sent from: http://apache-flex-development.247.n4.nabble.com/
Re: [DISCUSS} Fork FlexJS from Apache Flex
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 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 -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Fork-FlexJS-from-Apache-Flex-tp64007p64012.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
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: [Flex JS] Flex SDK Installer always get stuck at "Finish uncompressing"
Hmm... if we just would like to target JS, do we still need AIR and playerglobal.swc? If not, maybe we could provide a FlexJS "JS only" version? Maybe another approach could be to declare AIR as a prerequisite? Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-JS-Flex-SDK-Installer-always-get-stuck-at-Finish-uncompressing-tp63989p63994.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Flex JS] Flex SDK Installer always get stuck at "Finish uncompressing"
Hi, is there any chance to pre-build the various FlexJS releases including the nightly (maybe also for different platforms) at server side in order to just provide an URL to make it downloadable? So the question is, could we replace the installer by manual SDK downloads for FlexJS? And if not, is the show stopper a technical or legal issue? Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-JS-Flex-SDK-Installer-always-get-stuck-at-Finish-uncompressing-tp63989p63992.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Javascript functions
Piotr, whats about just creating some TypeDefs? Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Javascript-functions-tp63954p63956.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)
Thanks Alex, that helps! -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-FlexJS-External-dependencies-Adobe-Google-tp63945p63950.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [Flex/FlexJS] External dependencies (Adobe, Google, ...)
>What sort of commitment are you looking for? I was not sure about if there something is needed in the AIR source code to support Flex. But of course as you said it's all about AS3 and that should work... Thanks, Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-FlexJS-External-dependencies-Adobe-Google-tp63945p63949.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
[Flex/FlexJS] External dependencies (Adobe, Google, ...)
Hi, we have to do a decision in near future what we will do with our Flex apps. So I'd like to know if there are any external dependencies that could stop our Flex or FlexJS apps from working. Flex: Is there something needed to do at Adobes side to ensure that Flex apps will work with future AIR releases? And if so, is there any commitment by Adobe that they will support Flex in future? FlexJS: If we just speak about JS, are there any dependencies to Adobe left? Speaking about swf, what's about replacing FlashPlayer by AIR within FlexJS. Is this a realistic scenario? Are there any other crucial dependencies that could be a problem in future? (Closure compiler?) Thanks for help! Olaf -- View this message in context: http://apache-flex-development.247.n4.nabble.com/Flex-FlexJS-External-dependencies-Adobe-Google-tp63945.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
