The history you mentioned is of the Home file.
Take a look at this [1] to see the moonshine history.
Maybe we should move it all sooner to a docs dir and publish it via github
pages. We probably have better control of all the content then.
HTH,
Olaf
[1]
>By GitHub pages you mean as part of Apache ?
No. Github pages use Jekyll as static site generator under the hood and
Jekyll supports Markdown to generate the pages.
So the migration should not so much effort.
At the end, each particular article is represented by its particular file
then which
Ups, overlooked this Post...
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github-repo-tp63786p63846.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
>I’d like to be able to use MXML to mark up some HTML and just have the CSS
“work”.
+1
I think it is a good idea to provide an AS3 accessible counterpart for each
particular HTML component inside the html package.
>From a users perspective, this is probably what users expect to find inside
the
Nicholas Kwiatkowski-2 wrote
> The current site is actually managed by a static-site generator using
> markdown.
What do you think about creating a site that is dedicated to FlexJS?
@Piotr
I've started to put some docs together for the mdl:badge bead. [1]
It's not complete and only a first shot.
Great input from all of you, thanks!
Unfortunately, I'm pretty sure that I don't know most of the FlexJS stuff
myself so expect some traffic here on the list related to all the topics
next time.
I'd like to create a demo (source code and live demo) for each particular
topic and I think it makes
Hi Piotr,
>As for the examples maybe it's worth to put them into FlexJS Tour where
Peter start initial work [1].
Is this FlexJS Tour already hosted anywhere as a live demo?
>Anyone know whether we could take from Apache some new domain or how to put
it as subpage of our website?
Would be great
>To work around bugs in the compiler (which get fixed as they are
discovered), I have a separate CSS file >that I include with my app which
contains CSS that has trouble being compiled.
Just to make sure that I understand it right:
Does that mean, that it works if we just outsource the CSS that
This is an awesome tutorial, thanks Harbs!
Hope I'll have some time to follow these steps by myself.
However, if I'll get your permission I will definitely help to put in on the
github wiki.
Maybe we're also able to build a working example including a live demo...
Thanks,
Olaf
--
View this
Forget about this:
>The advantage of MXML is that we can declare both JS code and the CSS in
the same file.
I think you mean AS instead of JS?!
Thanks,
Olaf
--
View this message in context:
>Go for it! :-)
Done! [1]
Looking forward to following the steps by myself.
If I'll be successful I'll add a working FlexJS example to the wiki.
Olaf
[1]
https://github.com/ok-at-github/flexjs-docs/wiki/Adapting-HTML-CSS-JS-project
--
View this message in context:
This is also really helpful!!
I will try it out by myself and will add it to the docs!
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-more-problematic-CSS-tp63810p63814.html
Sent from the Apache Flex Development mailing list archive
Hi,
I'd like to write some docs about the browser compatibility of FlexJS and
wonder how this technically works.
Is there some magic implemented within the compiler or is an external lib
used or is there whatever mechanism to ensure that the transpiled code works
fine with most of the browsers?
But what mechanism takes care of the compatibility with the main browsers
like IE, Edge, Chrome, Firefox, Safari and all those particular versions?
Or is there no magic needed and it just works for whatever needed?
Thanks,
Olaf
--
View this message in context:
And if there's nothing already implemented to ensure browser compatibility
what could folks do if they have issues with some browsers?
Is there something like a conditional compiling for different browsers?
Thanks,
Olaf
--
View this message in context:
>There’s nothing really built in
Mhh... but I wonder if FlexJS can not guarantee consistency through
different browsers and different platforms, could we really speak about a
cross platform framework then?
Or do I miss something?
Thanks,
Olaf
--
View this message in context:
OmPrakash Muppirala wrote
> That said, if you plan to migrate it to the Apache Flex project at a
> future
> point, it will be easier if you add an Apache V2 license to your repo
> right
> away.
That was the first thing that I've done after creating the repo [1]
But cause you mention it I just
>I found one work-around for one scenario and I’m investigating another for a
different one.
What do you mean with work-around?
Is it the approach to find some code that works with all browsers or do
you're using browser sniffing (Class BrowserInfo as you mentioned above)?
Thanks,
Olaf
--
>I will try to do this as you were did, but it will not be to fast.
Thanks Piotr!
I don't know anything about the life time of a particular CodePen, but maybe
we could use it to publish some FlexJS live demos.
Olaf
--
View this message in context:
piotrz wrote
> I would rather explore TourJS and make there examples. Then publish links
> to each of them.
Could you provide me a link to a live demo of TourJS?
Thanks,
Olaf
--
View this message in context:
Hi,
I'm trying to create a CodePen for the MDL slider but it doesn't work as
expected.
I just tried to copy the transpiled HTML/JS/CSS to CodePen.
This is a CodePen example for the MDL slider [1].
It basically works but it's not the same result as the browser shows.
Do I miss something?
I've got it, thanks!
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Browser-compatibility-tp63828p63866.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
>Could you additionally post what you have in your FlexJS MDL project ?
https://gist.github.com/ok-at-github/2e7dd966423db0b3954dce3de89b430e
(This works fine in the browser)
I have to mention that I copy and paste the code from the FlexJS debug
target and also from the browser source while
Let's just focus on content for now... there's still a way to go ;-)
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github-repo-tp63786p63864.html
Sent from the Apache Flex Development mailing list archive
Hmm, whether TourJS or some other examples, I think we definitely need to get
some examples or live demos online.
FlexJS lives a bit in the dark cause all the useful content is hidden behind
the scene. Difficult to find and maybe also difficult to get it working.
Would be great if we could have
Thank you!
I've just installed it on Windows7 and it works!
Olaf
BTW:
Seems that your Moonshine web side is outdated? [1]
[1]
Moonshine is being developed using:
Apache Flex® SDK 4.15.0
Adobe AIR® SDK 22.0
Apache FlexJS® SDK 0.7.0
Apache Ant® 1.9.2
--
View this message in context:
>only with one workspace, other workspaces are fine
Do you've already tried to re-create the workspace?
I've other weird issues with FB from time to time and re-creating the
workspace helps most of the time.
HTH,
Olaf
--
View this message in context:
Great Josh, you should post it on the users list!
@All
Please don't forget that everybody can support this awesome guy by being a
patron [1]
Olaf
[1] https://www.patreon.com/josht
--
View this message in context:
>I don't see class SearchClass in the project
Maybe I'm wrong, but I'm also don't see a representation for "http://apache-flex-development.247.n4.nabble.com/FlexJS-question-about-porting-an-Adobe-Flex-3-project-to-HTML-JS-tp62698p63036.html
Sent from the Apache Flex Development mailing list
>Having a single code base which can target AIR and HTML in the browser will
probably fill a real lack.
That would be awesome!!
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-End-of-life-of-the-Flash-Player-tp63557p63561.html
Sent from the Apache
Hi,
I would like to ask if the FP EOL announcement has any effects on FlexJS?!
Do you think it is still worth to follow the conditional compiling approach
or is it maybe time to
abandon the swf side in order to concentrate on JS?
Thanks,
Olaf
--
View this message in context:
>Yeah. That’s probably the issue with AIR 25 being too big…
Would just like to confirm:
AIR 23 works, AIR 25 still fails probably cause of this known issue.
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Installer-Problems-tp62791p62802.html
Sent
It works, great job again Piotr!
Thank you,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Installer-Problems-tp62791p62828.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Great work, a big thank you to all of you to get out this important release!
BTW: I also can't see any [Announce] entry on the nabble.com users' list...
Thanks,
Olaf
--
View this message in context:
The installer is working now!
I've just installed 0.8.0 successfully :-)
Thank you,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Installer-Problems-tp62791p62799.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi,
I've just tried to install the 0.8.0 release using the installer on
Windows7/64bit but it doesn't work for me.
See that attached log [1].
Do I miss something?
There's no urgent from my side, I'd just like to give it a try.
Thanks,
Olaf
[1] Installer log:
Installer version 3.2.0 (windows)
For me, both links are working.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Installer-Problems-tp62791p62797.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I've overlooked the other "Installer Problems" thread, sorry.
The installer is dowloading now... seems that it works for whatever reason.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Installer-Unable-to-download-Apache-Flex-SDK-tp62793p62796.html
Nicholas Kwiatkowski-2 wrote
> - Re-creating Fontkit. Chris Dutz said he might be able to work on it,
> but I havent seen anything else to that affect.
At ApacheCon somebody found a lib that maybe contains a working FontKit
port.
Piotr created a JIRA that contains the link [1]
HTH,
Olaf
Hi guys,
it seems to me that since Adobe announced the EOL of FlashPlayer there's
some more interest in FlexJS.
And it also seems to me that is still not so easy to get in touch with
FlexJS for others.
One reason is probably the lack of the documentation.
My feeling is that some more
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
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:
Hi Alex,
great that you've heard the community voice and start working on this!
>...and loaded after application startup...
Does this mean that a FlexJS module is loaded from the server (same origin
as the main app?) by some magic or is it already bundled and delivered with
the FlexJS app and
Josh Tynjala wrote
> Did you delete your ./target/javascript directory before compiling with
> the
> new SDK?
I'm pretty sure that I've done that all the time without any success.
After I've changed the "output" option as you mentioned the first time
including deleting the target folder it works
>New capabilities in this release include:
- Maybe it is worth to mention that the layout system was revised... or was
this rather a bug fix?
>You can also use...
- I think it's definitely worth to mention Josh's vscode extension here as a
powerful IDE.
Thanks,
Olaf
--
View this message in
Hi,
>It sounds like enum may be one of those that JavaScript allows that
ActionScript currently doesn't.
I've checked it out and it turns out that for both (AS3 and JS, ECMAScript5)
'enum' is flagged as future reserved
keyword [1][2].
Does is makes sense to just add it to as3ReservedWords [3]?
Carlos Rovira wrote
> btw, I want to ask to you about the experience. could you post about it?
> how was it? how many people was attending? what was the overal feeling and
> thinking for the people coming?
> I could not read anything of this, so I think it could be great some words
> about it
Hi
Thanks to all those who made this awesome event possible and successful at
least!
And special thanks to Chris of course!
I'm pretty sure FlexJS will benefit from this Summit!
Olaf
--
View this message in context:
Hi,
I've stumbled over the issue that the compiler doesn't recognize the
reserved JS word 'enum'.
Instead, it just returns just a 'Parse error' without any hints that 'enum'
is a reserved JS keyword [1]
Is it a big deal to teach the compiler all the reserved JS keywords [2].
I found something
Hey Piotr,
the check-in procedure in Miami was done really quick, much faster than in
Germany.
So I've had some time to revive the work on my PureMVC EmployeeAdmin FlexJS
port ;-)
>How this failing fragment of code look like ? Could you post it on
https://paste.apache.org/ ?
In my case, it
Josh Tynjala wrote
> As I mentioned in my previous post, JavaScript started
> allowing reserved words in places where they couldn't be used before with
> ES5. Since AS3 is derived from ECMAScript, it's pretty safe for us to do
Hi Josh,
maybe I get something wrong once again or I miss something
>I guess the stream will definitely direct towards more people migrating to
JS so I think we shouldn’t >prohibit flash related reserver words in the js
world.
I'm confused.
Do you mean that we should allow using AS3 reserved words if they are
allowed in the JS world?
Wouldn't that mean that AS3
Maybe this also helps:
http://apache-flex-users.246.n4.nabble.com/FalconJX-How-To-Use-td14824.html#a14841
Summary:
You have to remove all flex/flash dependencies from your AS3 code and you
have to replace your mx/spark components by FlexJS components. Depending on
your code base that could be
>Our plan is to migrate from Adobe Flex to HTML/JS but it is not to convert
it to FlexJS.
FlexJS also places you in the position to use HTML with AS3 [1]
>Now, I am asking if any possiblity of converting the MXML to HTM
I think there's no way to convert MXML to HTML automatically.
Hope this
Hi guys,
>It seems to me there is some interest in the extended community to see a
release out
It's still hard for me to understand the technical details but it seems to
me that the discussion Maven over Ant has reached a new climax which is not
very helpful at least.
Maybe I got something
You find some approaches at docker Hub [1]
Olaf
[1] https://hub.docker.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Running-Flash-AIR-as-docker-container-tp62462p62463.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi,
after some weeks being technically offline at home, I'm hopefully back in
the game now;-)
I've just downloaded the nightly build using the installer and tried to
compile my little test app
with no success [1].
I noticed that the target folder contains just a weird javascript file.
I've
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
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
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
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 -
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
1. Boja
2. Limber (Limbr)
3. Beads
Thanks,
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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/
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
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
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.
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:
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
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
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!
+1
Olaf
--
Sent from: http://apache-flex-development.247.n4.nabble.com/
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
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
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:
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.
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,
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]
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/
+1
Windows7/64bit
--
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:
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
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
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
+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/
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
>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/
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/
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/
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/
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
+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 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]
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 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
> 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
> 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
1 - 100 of 154 matches
Mail list logo