## 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 found
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/Se
...it's submitted now.
Thanks,
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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!
The report has been submitted.
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
Hi Andrew,
> No changes have been made
Done, thanks!!
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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-fl
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/
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 "
I just submitted the report, thanks!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
It's fixed, thank you Andrew!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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+20
+1 Thank you for working on this!!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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
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.
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
The report has been sent, thanks to all for your help!
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
Thanks Leo!
I just updated the report and will send it now!
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
Sounds good, thanks Leo!
I'll mention this within the report.
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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/
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/
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+202
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 i
I've just posted the report.
Thanks for the help!
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
>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/
> 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/
> 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 n
>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
--
Se
> 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/
> I added a bit more info.
Cool, thanks Carlos!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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
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:
Seems that Piotr was faster and I overlooked his post ;-)
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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
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/
The June report is submitted!
Thanks,
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
I've just applied your changes.
Thanks, Andrew!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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://a
I've just submitted the report, thanks for the help!!
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
>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 perio
>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/
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://apach
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/
+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/
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 t
@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 s
> 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 f
> 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 advan
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
> It looks like they have started doing something
Yes, seems to be done ;-)
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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
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
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/
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, t
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 r
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-developme
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/
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,
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
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/displa
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/
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/
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.
HT
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
I
+1
Windows7/64bit
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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/
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.2
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 t
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
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 li
+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/
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 reas
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/
>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/
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.
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/FontAwesome5WithApac
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
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/
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: h
1. Boja
2. Limber (Limbr)
3. Beads
Thanks,
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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/
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 previou
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
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 na
>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
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
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 iden
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.ArrayCol
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 t
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]
>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/
+1
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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!
Ma
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
disc
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.233
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
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.
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.
>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.n
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 r
1 - 100 of 155 matches
Mail list logo
