Hi Alex and FlexJS community,
I have been following this thread:
Re: Will we have a new release out the door till 8th of September?
I wanted to provide a brief update:
We have been working hard on getting a new version of the Moonshine IDE
ready and released through the Apple App Store. We ran into an incredible
series of delays and problems with restrictions placed upon the App Store
release, so we had to add a 'helper' application to (hopefully) get around
the problems Peter Ent reported months ago on recent Mac OS X releases
including El Capitan.
Now that we are done with it, we hope this approach will get approved by
Apple. Even without the App Store release, we will post the direct
download version on the site in the next few days, and Santanu will make a
post here announcing it.
Given that 0.70 of FlexJS is nearing release, I would like to revive a
request I made in April for a roadmap of what is left before we can call it
1.0.
I think this is important to gather widespread attention. It also needs
to be paired with an easy on-boarding experience for new users and a
functional set of demo applications and learning tools. You may notice we
integrated Tour de Flex with the Moonshine IDE for this reason, and we also
intend to add in the FlexJS docs soon.
It would be really helpful to our cause if we can articulate the major
bullet points for why someone interested in cross platform development
should go with FlexJS / AIR vs. Xamarin. I think it is important for us as
a community to clearly state the benefits beyond just not being a solution
backed by Microsoft and subject to their whims.
I have also asked Dhwani and Kinjal to make sure they contribute back the
Tabbed component to FlexJS that they recently got working. And we have
built in a new feature to turn Balsamiq mockups into FlexJS applications
that we are working on polishing.
Finally, we really need help getting code completion put into Moonshine.
I'd appreciate hearing from anyone who is skilled in building Abstract
Syntax Trees and parsing them in real time who could contribute this.
Thank you,
Justin Hill
My Apache Flex community contribution is working on the open source
Moonshine-IDE.com for FlexJS.
----- Message from "Justin M. Hill" <jus...@prominic.net> on Fri, 1 Apr
2016 02:52:26 -0500 -----
To: dev@flex.apache.org
Subject: FlexJS - roadmap to 1.0 release with code bounties and
conversion analyzer
Hi Alex,
Would it be possible to start making more extensive use of JIRA on FlexJS?
There appears to be a very basic list of issues outstanding for FlexJS 1.0
Release Candidate. I'm sure there is a lot more on a roadmap somewhere...
and it would be nice to have it articulated in JIRA.
https://issues.apache.org/jira/browse/FLEX/fixforversion/12324435/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel
I reviewed your PowerPoint presentation draft for the FlexJS meeting on
Monday.
Slides 30 through and 36 detail "how much can you reuse" and has
information on scanning for "imports flash.*" and "embed".
I think we should write an analyzer to help estimate code conversion for
existing Flash / Flex Builder projects and add that to Moonshine IDE. We
could then present an estimate of the amount of code that will "just work"
on a FlexJS build from the project.
If you can correlate the skill set necessary to tackle each of the major
issues, I think FlexJS is at a point where we could start to recruit
individuals or companies to assist with the remaining issues to reach 1.0
level so their Flex apps will be ported to JavaScript/HTML.
Surely there are enough corporations out there with an investment in Flex
application modernization needs that financially it would make sense to
sponsor a portion of the remaining development work on FlexJS 1.0 so that
their application port to no longer be dependent upon the Flash player will
be accelerated.
Thank you,
Justin Hill
My Apache Flex community contribution is working on the open source
Moonshine-IDE.com for FlexJS.
