Another couple pennies worth of input...
One of the things that isn't being considered is that even though you can
compile the Haxe language back down to many different bytecodes, it's still
not a way to directly remove the dependency on Adobe's runtime. So much of
the core of Flex is dependent on
atform.
On Fri, Nov 16, 2012 at 8:10 AM, Omar Gonzalez wrote:
> So I'm not that intimately familiar with how it compiles to JS, can you
> elaborate on your concern here?
>
> Also, why do you say haxe is obscure? It is entirely open source, what's
> obscure about that?
Not to add fuel to the fire, but is choosing another platform like Haxe as
a core dependency of our project really a good idea?
I like Haxe as a concept, but I'm not 100% sold on the way they implement
the multiple compile targets (especially JS/HTML) AND am certainly
concerned that the future of
It depends on the goals of the Flex project. If we are looking to create
something that is purpose built for the Flash runtime, then I don't believe
so.
However, if we are looking at Flex as a toolkit to build rich interfaces
and are willing to break from the SWF compile target being our core focu
I agree with Omar 100%.
Git is a bit better of a SCM, but the flexibility the use of GitHub affords
really lends itself to a more engaged community.
If we want an engaged community, and the challenges we face with Apache's
non-support of Git aren't too severe, Git is the only good choice for fu
Whatever branching model/scm we use, we need to provide a step-by-step guide
(or tool as Mark suggested) on how to checkout the code, make changes, and
submit a patch…
While I get the Apache Mentors' viewpoints on sticking with what works for
Apache projects, I fear we are missing a huge opport
#9 for sure (if my vote counted)
On Monday, August 13, 2012 at 4:19 PM, Alex Harui wrote:
> Hi,
>
> It is time to make a decision on branching and source control vendors. This
> vote will end at 2pm PDT Wednesday, August 15. Please vote for one of the
> following.
>
> 1. 3-Tier Branching Model
Well, looks like there is a clear winner ;-)
On Monday, May 28, 2012 at 5:00 PM, Jesus Macedo wrote:
> The first one :)
>
>
I second the idea of putting together a bit of a styleguide for people to
use when building applications... maybe a combination of best practices and
examples for what you can do with the framework.
I also would encourage us to employ some talented developer/designers to
create a new default spark
