flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From OmPrakash Muppirala <bigosma...@gmail.com>
Subject Re: [DISCUSS] Release Apache FlexJS 0.5.0
Date Fri, 06 Nov 2015 20:36:17 GMT
>
>   I hope Chris will
> stick around to do it and that others can help them.  I will try to help
> with refactoring needed to make Maven work better.  Those changes usually
> help make sure we have the loose-coupling we need between modules.



I think that is a good start.


>   I’m
> not that interested in refactoring the Flex SDK.   I am interested in the
> notion of slicing off any Flex SDK dependencies in the Falcon code base so
> we can Mavenize FlexJS without dealing with the Flex SDK first.  And I’m
> actually looking forward to seeing the Mavenizing of FlexJS.  Maybe I’ll
> learn more about Maven by watching those commits.
>

I am hoping to do the same.


>
> I’m sure in the early days of FlexJS and Falcon, going away for a while
> and coming back probably didn’t work.  But is that still true?  And if so,
> can you just blow away your repos and re-grab flex-asjs and run “ant all”
> and get back up and running?
>

It is an option.  But, I have several partially done cool things that were
stopped due to personal time issues, build issues, etc.  I would hate to
lose all that.  But I will probably just end up doing what you suggested.


>
> And for folks reading this who are in the silent faction:  Please speak
> up.  Or write me off-list if there is something you have to say that you
> don’t want to say on these lists.  And tell me/us why you have been
> silent.  Is there something we are doing or should be doing to make it
> easier for you to speak up?
>

I don't think the silent faction are paying attention, to this thread, or
even to this forum.  Ideally, we should make things easy to build, do a
couple of simple tutorials and invite folks to try it out.  That would be a
better approach to make them speak up.


>
> So, my takeaway is that we should fork off two actionable threads.  One
> about eliminating environment variables for Flash/AIR, and the other about
> folder restructuring in flex-asjs to make Mavenizing easier?  Did I miss
> anything?
>

As I understand things, I think that is pretty much it.  And oh, the work
needed from Adobe to mavenize the Flash runtime artifacts.

Thanks,
Om


>
> Meanwhile, I am trying to upgrade the build scripts to fix issues found in
> the FalconJX packages so that we can get releases out faster in the future
> by catching issues sooner.
>
> If you are still having problems with this FlexJS release candidate,
> please provide more detail.
>
> Thanks,
> -Alex
>
> On 11/6/15, 1:08 AM, "Justin Mclean" <justinmclean@me.com> wrote:
>
> >HI,
> >
> >> Nobody is saying simpler builds wouldn’t help.  But how much?
> >
> >A lot I think. Developer are unable to contribute if they can’t compile
> >and test their changes.
> >
> >>  More than a more functional DataGrid?  Or a more Spark and/or MX-like
> >>component set
> >> that reduces migration time for your app?  Or being able to write your
> >>JS
> >> using AS?
> >
> >IMO you would more likely get people contribution things like that if it
> >was simpler to build.
> >
> >> To folks reading this who are interested in
> >> FlexJS: what is the most important two or three things we should be
> >> working on?
> >
> >IMO:
> >1. Simpler builds
> >2. More frequent releases (say every 3 or 4 months).
> >3. Compiling MXML
> >4. Working documented examples / how to port existing applications
> >
> >> The build script was improved in this release such that if you have a
> >> couple of known sets of circumstances, like not having any of the repos,
> >> that running “ant all” will get all the repos and build them in the
> >>right
> >> order.
> >
> >I meant to ask before does that use well known versions or does it just
> >grab the latest out of the develop (or another) branch?
> >
> >Thanks,
> >Justin
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message