Hi Alex,
On the topic of a roadmap to FlexJS 1.0 --
I agree about needing a real-world application to consider FlexJS 1.0 being
a good point of reference, but I think we might be in a bit of a catch-22
situation.
If we call it 1.0, more people will give it a try. Even internally at
Prominic, people have at first been hesitant to think we could get anywhere
with FlexJS because it is not "1.0" yet. So there is something
psychological about that number to the world of software. On the one
hand, we don't want to just randomly call it 1.0, but we need to figure out
what minimum remaining features the group needs to get their own projects
working on it as a 1.0 probably. After all, I suspect most people pouring
resources into FlexJS are doing so as a means to breath life into their
existing Flex software investments.
So my question is: what does the rest of the group need to call it 1.0?
At Prominic, Bootstrap integration and data binding have been two notable
holdups. Prominic team, please speak up on what else we need.
I suggest on the "FlexJS - roadmap to 1.0 release" thread we ask everyone
who is active right now to submit on JIRA what their personal goal for a
1.0 release over the next 2 weeks. We need to get the group in the habit
of using JIRA to stay organized so priorities don't get buried in these
e-mail threads in my opinion.
Some people like us don't have JIRA rights AFAIK so maybe we can also ask
people to post JIRA addition requests in a specific way to the list so
someone else who does have rights can post them. Like a subject of "JIRA
addition for 1.0 target:"
After the 2 week time-frame of submissions, the group can then choose a
method to organize the JIRA tickets into those that actually the group
decides should be 1.0 vs. those that could wait until 1.1 release.
Regarding the competitive analysis of FlexJS to tools like Xamarin,
Prominic can try to write something, but we really could use feedback
(off-list is fine if it is against policy) from others more knowledgeable
than us. I really think this is important so new people can have the
information handed to them about why this is useful.
Thank you,
Justin Hill
My Apache Flex community contribution is working on the open source
Moonshine-IDE.com for FlexJS.
----- Message from Alex Harui <aha...@adobe.com> on Wed, 7 Sep 2016
05:13:39 +0000 -----
To: "dev@flex.apache.org" <dev@flex.apache.org>
cc: Santanu Karar <sant...@prominic.net>, "Dhwani K. Shah"
<dhw...@prominic.net>, "Kinjal J. Patel" <kin...@prominic.net>,
"Atin K. Gupta" <a...@prominic.net>, Pan Li <pa...@prominic.net>,
Bing Li <bin...@prominic.net>, "Walker L. Dalton"
<wal...@prominic.net>, "Efrain Salomon" <efr...@prominic.net>, "Joel
C. Anderson" <j...@prominic.net>
Subject: Re: FlexJS - roadmap to 1.0 release
Hi Justin,
Just today I was thinking of finally getting around to trying Moonshine on
my Windows computer. More below...
On 9/6/16, 9:42 PM, "Justin M. Hill" <jus...@prominic.net> wrote:
>
>Hi Alex and FlexJS community,
>
>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.
For me, I would like at least one public testimonial that someone was able
to use FlexJS and put an app into production. We have example apps, but I
want to know if FlexJS can do something a bit more complex. Other folks
may have different opinions and I could easily change my mind if folks
want to call the release after 0.7.0 our 1.0 release.
>
>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 haven't used Xamarin, plus I think as a member of Apache I'm not
supposed to do opinion-based competitive analysis. It is fine to state
hard facts though, but in many ways your choice of tools is subjective.
Mostly, I think we need folks who have been successful to articulate the
advantages.
>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.
Moonshine is an AIR app, correct? Porting Falcon's AST code to
ActionScript would be a serious project. I'm wondering if there is some
way to leverage Falcon, possibly as an ANE, or via some other
cross-process communication. Falcon is already set up to be a
code-completion engine for Flash Builder.
Thoughts?
-Alex
