Hii Gorgon,
> Are developers on this list still able to earn a living building new Flex
> apps, or are you maintaining old ones?
Yes. Doing a bit of both.
Justin
[
https://issues.apache.org/jira/browse/FLEX-33264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-33264:
Attachment: FLEX-33264.patch
> Fix Mustella files that contains a BOM in the middle of a file i
>
>> In the meantime, make sure you look at the slide deck from Michael
>> Labriola¹s 360Min presentation on how he is developing apps for HTML. I¹m
>> sure he¹ll reply with the link
>
> Is the slidedeck already pulished somewhere?
>
http://www.slideshare.net/michael.labriola/randori-design-go
On 11/16/12 6:23 PM, "jude" wrote:
> That is my point in staying with what we have. The Flex SDK has had some
> constraints on it that made it what it is today. I'm not against starting a
> new or full rewrite but I would say let's get this project going on the
> current code base first. Let's
On 11/16/2012 10:25 PM, Hordur Xtest2 Imap wrote:
Also, when Steve J started his crusade against Flash on the iPhone, part of the
argument was HTML5 is so good you can do anything with that, that you can do in
Flash. Fast forward a few years and the reality is almost all mobile apps are
native
Well I dont agree with this.
If we narrow down the discussion a bit and just talk about Flex apps in the
browser, then as far as I know there are only two usable ways of running apps
there, via Flash player or as HTML/JS. One way depends on Adobe technology and
the other on the implementation o
> I have been playing around with Falcon JS to help me form an opinion on what
> the next steps are, but I need some sign-offs from folks in Adobe before I
> can make it public
Looking forward to read your opinion.
> In the meantime, make sure you look at the slide deck from Michael
> Labriol
[
https://issues.apache.org/jira/browse/FLEX-33264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499333#comment-13499333
]
Cyrill Zadra commented on FLEX-33264:
-
Affected files:
frameworks/projects/advancedgr
Hi Gordon
I think so too.. I'll try to create a list with all the affected files
and if there aren't too much I'll replace them manually .. otherwise
there is maybe a way to do it by script.
cyrill
Am 16.11.2012 um 11:15 schrieb Gordon Smith :
> I believe a BOM is only a BOM if it's at the
Cyrill Zadra created FLEX-33264:
---
Summary: Fix Mustella files that contains a BOM in the middle of a
file instead the beginning.
Key: FLEX-33264
URL: https://issues.apache.org/jira/browse/FLEX-33264
Pro
On Fri, Nov 16, 2012 at 4:13 PM, Alex Harui wrote:
> Keep in mind that I'm the biggest proponent of the full re-write. We may
> still find a few performance mistakes in the current code (like the Chart
> styles init that just got fixed), but really, some very smart people have
> spent a lot of t
Bertrand's post is much better than the similar in substance one that I
composed but had not edited last night.
I can say from experience that [1] is well worth watching. I really like how
this community self-innoculates.
Regards,
Dave
On Nov 16, 2012, at 2:20 AM, Bertrand Delacretaz wrote:
>
We could discuss for hours about the technical aspects of the Flash Player
and how well Flex integrates with it, however there's one thing that is not
going to change:
- Customer Perception.
This very fact is key to decide the future of Flex because nobody wants to
use a technology that no one wan
Hi Frédéric,
many thanks for you link I will dig it and see your approach.
2012/11/16 Frédéric THOMAS
> I started something very basic at the beginning of the year but didn't
> have time to continue but I thought to go back on it at some point waitting
> as weel what Alex did and Mike Labriola
@Gordon
ActionScript 2.0 was introduced in 2004 and is still supported in Flash
Player.
As you say, AS3 / AVM2 will not disappear from one day to the other, and
Adobe, also, was clear on this point.
Maybe an average Flex application just doesn't need the new features that
will be introduced in AS4
I'm still doing some new development; however the question of "Why not
HTML5" is coming up more and more frequently
On 11/16/2012 5:09 PM, Gordon Smith wrote:
I think that developers can continue to build good apps with AS3 and V11, but
I'm assuming -- perhaps wrongly -- that the demand for
Hi Carlos,
I don't often post on this list, yet I consider myself a big supporter of
Flex. This discussion makes me change my silent policy because it targets
my growing main concern, which I assume is shared by many other developers:
Will I be able to make a living with Flex programming in future
Hi Gordon,
yes thats exactly my point of view regarding a new flex from scratch.
Regarding current Flex 4.x...evidently we are tied.
Coming from you, is very valuable comment, and should make think many of us
in this list.
2012/11/16 Gordon Smith
>
> My advice is to avoid tying Flex to any pr
What we do is calling Flash/Flex APis through a custom FABridge (That we
are planing to contribuate soon). So at the of the day it still a
Flash/Flex application but not written in ActionScript/MXML.
You can have a look at a demo here : http://flex4j.appspot.com/
For AIR we wrapped the AIR JS AP
I expect more momentum in the coming months due to developers realizing, or
marketeers realizing, what HTML5 in practice means...
Verstuurd vanaf mijn iPhone
Op 16-nov.-2012 om 23:23 heeft Om het volgende
geschreven:
> On Fri, Nov 16, 2012 at 2:09 PM, Gordon Smith wrote:
>
>> I think that d
On Fri, Nov 16, 2012 at 2:09 PM, Gordon Smith wrote:
> I think that developers can continue to build good apps with AS3 and V11,
> but I'm assuming -- perhaps wrongly -- that the demand for them is going to
> decrease because companies see that Adobe is no longer investing many
> resources in the
Did you use some HTML/JS implementation of native Flash/AIR APIs such as Sprite?
- Gordon
-Original Message-
From: Alain Ekambi [mailto:jazzmatad...@gmail.com]
Sent: Friday, November 16, 2012 2:43 PM
To: flex-dev@incubator.apache.org
Subject: Re: Flex 5 in haxe
We dont use ActionScript/
We dont use ActionScript/MXML at all.
ActionScript/MXML were not scaling for our customers(most of them use
J2EE) so we exported the Flash/AIR/Flex API to Java using GWT giving their
devs the ability to write Flex using the tools they are familiar with.
2012/11/16 Gordon Smith
> > we have
Hi all we do also have a slash of momentum building air and mobile apps for
our customers and more and more customers ask us to deliver in flex/air i
believe the framework does have its quirks but nontheless it's still the
best framework to work with and lets be fair HTML5 is not an option and i
ca
@Gordon, Alex,
We are also creating new apps as well as maintaining older ones. We
previously created web-only OR mobile-only apps. But lately we are
creating a library project which holds 95% of the code and 2 specific
projects for mobile and AIR versions of the app. Just today I presented a
sale
> we have a different approach to Flex development
Can you elaborate on that a little?
-Original Message-
From: Alain Ekambi [mailto:jazzmatad...@gmail.com]
Sent: Friday, November 16, 2012 2:22 PM
To: flex-dev@incubator.apache.org
Subject: Re: Flex 5 in haxe
@Gordon
We actually see an
@Gordon
We actually see an increasing interest in Flex/AIR coming for our customers.
With the small team that we have we actualy cant keep up with the requests.
But i have to say we have a different approach to Flex development tho.
2012/11/16 Alex Harui
>
>
>
> On 11/16/12 1:52 PM, "Fréderic
On 11/16/12 1:52 PM, "Fréderic Cox" wrote:
> I'm glad Alex is here because I believe he does not only have
> the experience but also great ideas where Flex should be headed. And he
> might have been blocked previously by business decisions but now can take
> Flex to a even higher level.
>
Kee
>You're probably right, but for the minority who did write separate business
>logic, I think this will be the path of least resistance. And for those who
>didn't, it still might be easier to refactor >their code to get separation
>than have to rewrite every line. Anyway, that's the angle I'm
I think that developers can continue to build good apps with AS3 and V11, but
I'm assuming -- perhaps wrongly -- that the demand for them is going to
decrease because companies see that Adobe is no longer investing many resources
in them. Hasn't demand already fallen off over the last year? Are
I understand what you mean here but isn't that always going to be the
case. AS4 will go into maintenance mode, then AS5 etc.. What I don't
understand is why AS3 is not good enough for a Flex 5 version or even Flex
6 which will export to multiple targets. Can you elaborate on that?
Output should be
I agree with Jude, we should use Flex 5 to show Adobe what they gave away.
I am still creating apps using Adobe AIR and Flex 4.6 and I'm able to
create feature-rich apps which run on mobile and desktop using the same
codebase. This is pure gold but Adobe doesn't realize it, or did but did
not have
On 11/16/12 12:27 PM, "Michael A. Labriola"
wrote:
>> Because I expect the major factor in deciding what to do with your existing
>> apps is about the cost of moving. For sure, if you completely abandon Flex
>> you will have to rewrite all of your >views and all of your business logic.
>> If
> We need the Flash Player and AIR. Adobe needs to continue to support us.
The continued support is that AS3 and V11 and AIR-for-V11 aren't going away.
But I think the idea is that they go into maintenance mode. They're not the
technology of the future. Do you want to develop for an old, aging p
Another penny... Adobe was not good at marketing Flex (or AIR). And I don't
think we're doing well at selling or marketing Flex either. How many people
or clients know it's the best solution out there for targeting multiple
platforms plus it's many other benefits? I can't speak for everyone but I
k
On 11/16/12 1:35 PM, "Gordon Smith" wrote:
> Note that I did not include AS3, because AS3 is no longer proprietary to
> Adobe. But I don't see how AS3 gets you onto every platform you want to run
> on. I'd like to hear more from Alex what his vision for iOS and Android is.
> For example, get t
Note that I did not include AS3, because AS3 is no longer proprietary to Adobe.
But I don't see how AS3 gets you onto every platform you want to run on. I'd
like to hear more from Alex what his vision for iOS and Android is. For
example, get to HTML/JS and then use Cordova?
- Gordon
-Origi
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
+1 to Nick's comments. Alex has stated that Adobe is looking at how the
Flex community responds to Apache Flex.
We need the Flash Player and AIR. Adobe needs to continue to support us.
Adobe cannot starve it's children anymore. This needs to change.
Flex is the greatest framework / toolchain I've
Personally I think we are looking at the wrong problem here. The changes
proposed seem quite drastic to me. I believe we can achieve great things
using the current codebase and target. Sure, we need to remove the
dependency from Flash at some time but we need to be realistic here ..
Porting too Hax
Folks,
I have sat out this whole day reading everything.
This statement of Gordon's is golden and should be taken seriously. I
have no idea what the answer is to the 100's of posts today but one
thing is clear, break the Adobe dependencies however possible and
don't count on them.
I was
Even if a high-quality open-source version of Flash Player were developed, it
wouldn't have anything like the ubiquity that Adobe's player has, so you'd have
distribution issues.
- Gordon
-Original Message-
From: Bruce Montague [mailto:bruce_monta...@symantec.com]
Sent: Friday, Novembe
If Haxe really produces fast-running and good-looking apps on all platforms of
interest (does it?), I think it should be a top contender since it is
open-source. You could throw away the ActionScript part of Falcon and make the
MXML part of Falcon produce Haxe source code. MXML script blocks, ev
Hi, I do not know that much about Flex, the history of Flex, or all the other
background relating to this thread, etc.. How realistic would it be for an open
source community to write an open source, portable, (likely vanilla C),
equivalent of Flash Player and the AVM? Maybe not including all o
> From what I previously read, I don't think we were getting an updated Falcon
> compiler that will generate AVM3 code.
> They were not planning on open-sourcing that (but correct me if I'm wrong in
> that aspect).
That's correct. Adobe has no plans to open-source its new AS4-for-V12 compiler.
>Because I expect the major factor in deciding what to do with your existing
>apps is about the cost of moving. For sure, if you completely abandon Flex
>you will have to rewrite all of your >views and all of your business logic.
>If I offered a solutions where you still had to rewrite your view
On Fri, Nov 16, 2012 at 3:08 PM, Stefan Horochovec <
stefan.horocho...@gmail.com> wrote:
[snip]
> The development of the new VM and AS4 specification is not reported or
> discussed with Apache Flex, knowing that we depend exclusively of Flash
> Player and AIR to execute applications. This in my
>I'm guessing that this is because the major companies who used to use Flex and
>swore that they had plenty of compiler engineers who would help finish Falcon
>have moved on to other >technologies.
Just to speak for all of those companies, much of this happened at the Flex
summit. When many of
Hi
Well, I'm sad to say it, but those doubts now arise from the fact that Flex
generates bytecode that runs on a VM that does not perterce to us, we are
required to use the features it comes, and not what would like to have.
Some features that were designed in the list (Generics, proposed by mysel
> Currently I see no compelling reason to move to the new VM when it comes out.
> Once we know more about it that may change but it sounds like it wont be
> compatible with AS3.
The new VM will not execute the old bytecode that any AS3 compiler currently
produces. Adobe is turning its new Falco
> Since Falcon has little support of MXML, I see we don't loose almost nothing.
Given that Falcon can compile MXML apps like Checkinapp, I don't think it's
accurate to characterize its level of MXML support as "little". My own
characterization would be "80% complete". But completing the other 20
I believe a BOM is only a BOM if it's at the beginning of the file. So I think
Falcon is correct to complain and the files should be fixed.
- Gordon
-Original Message-
From: Cyrill Zadra [mailto:cyrill.za...@gmail.com]
Sent: Friday, November 16, 2012 1:58 AM
To: flex-dev@incubator.apach
"it seems that moving Falcon to a direction where it can target other
runtimes is going to take much less time than a complete rewrite of the
framework"
Not sure at all. its hard to say, and maybe Gordon could try to answer.
Check my other thread: its not only a new target / new language issue
Hi,
it sounds quite like a short term vision to me.
yes i agree that flex is still good solution for TODAY running on Adobes
runtimes.
maybe for a few years also but its risky and totally Adobe dependant.
Of course theres better JS fraework for HTML5, because flex don't
support HTML5. Flex is
+1 to everything Nicholas Kwiatkowski stated.
AS3 is a matured language and if your objective is to target other runtimes
then you wouldn't convert to AS4 anyway.
I'm not an expert on compilers but it seems that moving Falcon to a
direction where it can target other runtimes is going to take much
On Fri, Nov 16, 2012 at 11:57 AM, Hordur Thordarson wrote:
>
> There are only two visible deployment options going forward, Adobe's VM or
> HTML. Both have plusses and minuses and my view is that HTML has many more
> minuses, at least currently, and I just don't see that changing in the near
> f
On 11/16/12 9:26 AM, "sébastien Paturel" wrote:
> Le 16/11/2012 17:53, Alex Harui a écrit :
>> I still remain
>> convinced that once you force folks to rewrite their business logic in
>> another language, then they are more likely to review all of the
>> possibilities out there, and there ar
Hello folks,
I would like to add my 2 cents to this interesing discussion.
First let me share my experience with the Flash platform.
We have been building Flash based solutions for many years now.
We have different set of products mostly based on GWT that cover all the
spectrum (Native mobile
We have the compiler -- why can't we just adapt the output to another
platform instead of the input. We are only limited to the input standards
we create outselves. Nothing in the compiler is forcing us to output to
SWF.
-Nick
On Fri, Nov 16, 2012 at 10:51 AM, Carlos Rovira <
carlos.rov...@code
On Fri, Nov 16, 2012 at 8:17 AM, Justin Mclean wrote:
>
> I only know a little about Haxe. Could you comment on what would be
> required (in terms of skills and effort) to port Flex to Haxe? I know it's
> ActionScript like but is missing a few features that Flex may be using?
> Other than compilin
>
> I can't wait to ear about what you have to propose for the #2 objective.
> Maybe thats why you are more confident about the "keep AS3" solution.
>
>
Same here!
Le 16/11/2012 17:53, Alex Harui a écrit :
I still remain
convinced that once you force folks to rewrite their business logic in
another language, then they are more likely to review all of the
possibilities out there, and there are currently many, like Sencha,
PhoneGap/Cordova, going native for
I started something very basic at the beginning of the year but didn't have
time to continue but I thought to go back on it at some point waitting as
weel what Alex did and Mike Labriola too on AOP, glance at it if you want
https://github.com/doublefx/UIComponentBehaviors
-Message d'origin
Hi Alex,
that would be great, since that is IMO the first stone to start the effort.
Thanks
2012/11/16 Alex Harui
>
>
>
> On 11/16/12 9:07 AM, "Carlos Rovira"
> wrote:
>
> > Hi,
> >
> > I'd want to ask here if some refactor/experiment about decoupling
> > UIComponent with composition over i
Hi Justin,
as someone with lots of apps and products written in current Flex, I would
want to continue with my products migration to new versions. But the
reality out there is that all ways points to a new rewrite. I'm sure there
are people here that wants maintain and evolutione the actual framew
On 11/16/12 9:07 AM, "Carlos Rovira" wrote:
> Hi,
>
> I'd want to ask here if some refactor/experiment about decoupling
> UIComponent with composition over inheritance could be shared. I'd want to
> start experimenting with haxe and that would be very helpful.
>
> Alex? others? Is something
On Fri, Nov 16, 2012 at 9:07 AM, Justin Mclean wrote:
> Hi,
>
> >> They could do a 180 on their views of AIR next November. Then what?
> IMO We'd still have some time to change course, as we could still use
> exiting versions of AIR and captive runtime.
>
> Justin
>
>
I'd rather be prepared for th
On Fri, Nov 16, 2012 at 9:07 AM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:
> Hi,
>
> I'd want to ask here if some refactor/experiment about decoupling
> UIComponent with composition over inheritance could be shared. I'd want to
> start experimenting with haxe and that would be very hel
It has been almost a year since we announced Flex would be donated to Apache.
We’ve spent all of this time preparing donations of the code. It has taken
much longer than I would have ever imagined, but we are almost done. The
FalconJS code passed legal review yesterday and just needs a few ot
On Fri, Nov 16, 2012 at 9:05 AM, Justin Mclean wrote:
> Hi,
>
> > a new flex 5 from scratch concept would not be trying to be compatible
> backwards.
> So it's not Flex then but a new framework. I'm sure that would be fun, but
> how would that serve the current users of the Flex framework? Would t
Hi,
I'd want to ask here if some refactor/experiment about decoupling
UIComponent with composition over inheritance could be shared. I'd want to
start experimenting with haxe and that would be very helpful.
Alex? others? Is something shared in some whiteboard? if yes, could you
share the link?
T
Hi,
>> They could do a 180 on their views of AIR next November. Then what?
IMO We'd still have some time to change course, as we could still use exiting
versions of AIR and captive runtime.
Justin
Hi,
> a new flex 5 from scratch concept would not be trying to be compatible
> backwards.
So it's not Flex then but a new framework. I'm sure that would be fun, but how
would that serve the current users of the Flex framework? Would there be a
clear migration path?
> If the task of write a ne
> They could do a 180 on their
> views of AIR next November. Then what?
Well, then I'd be buggered for sure, that's the risk :-)
> This view is a little narrow minded. I would say apps like Gmail are pretty
> data-rich, and it runs great
Unfortunately the resources required to write and maintain
On 16.11.2012, at 16:30, sébastien Paturel wrote:
> "I agree that the strategy should be maintain and enhance the current
> framework while planning/preparing for the future."
> Yes and talking about a complete rewrite has to be figured out quite early if
> we want to be ready when we need.
Sur
It was nice to hear that some of you are still creating new apps or
modifying existing apps and Flash/AIR runs in enough places to satisfy you.
I hadn't heard that in quite a while.
My "mandate", which will be a year old in mid-December and could require
updating, and doesn't have to apply to anyo
Of course, compile without depend on Air, will be great, also open new big
doors like Windows Phone or BlackBerry (not playbook), developing with the same
code for that platforms, wowww. Not is the same HTM5 and Native App, I thing
the Native APPs never will dead.
Adobe Air 5 will have the abil
+1
On Fri, Nov 16, 2012 at 8:05 AM, Miguel Martín-Forero Ruiz <
miguel.mar...@cycle-it.com> wrote:
> +1
>
>
i think we agree on this.
actually, my first definition don't describe which platforms it should
targets.
but yes flex definition includes the ability to target multple
platforms. And this goal will be greatly achived if it targets as much
playforms as possible.
But definition of flex should no
I am not entirely familiar either and I didn't mean to imply that I have
any strong complaints with the way Haxe does things. I did read some forum
posts about about others making a slew of suggestions regarding the way
it's implemented and the product of the compilation for JS. Since I haven't
inv
Hi Justin,
a new flex 5 from scratch concept would not be trying to be compatible
backwards. If the task of write a new Flex is huge...make it backwards
compatible will be totaly utopic IMHO. So as my last line in my propossal
says...we should try to start with something like an experiment, to sha
On Fri, Nov 16, 2012 at 8:10 AM, Hordur Thordarson wrote:
> Well, I got the feeling that some users on this list were advocating a
> total rewrite asap rather than maintaining and improving the current
> codebase. A new Flex framework, built in Haxe or some other language than
> AS3/MXML is a to
if i get it well, we'r not talking about converting the framework to
haxe, but to rewrite the framework from scratch on haxe. and using the
same (or almost) flex API.
It seems so far that trying to port an existing flex to HTML5 whether it
is with flex on haxe, or any other choice, will be quite
"I agree that the strategy should be maintain and enhance the current
framework while planning/preparing for the future."
Yes and talking about a complete rewrite has to be figured out quite
early if we want to be ready when we need.
"usable solution to that problem so I can easily deploy to an
>
> "so you're not actually describing something that is under Apache Flex
> control"
> it would be the case if in fact i put Adobe runtimes in my definition of
> flex, which i don't.
>
>
The thread has gotten too long with responses that are even longer for me
to get everything straight.
It sound
On 11/16/12 1:58 AM, "Cyrill Zadra" wrote:
> I may have found the problem. It looks like there are files where the
> BOM isn't at the beginning of a file and thats the case where falcon
> can run into problems.
Hah! The magic of PERL scripts that replace headers. OK, we will need to
clean t
On 11/16/12 2:08 AM, "Bertrand Delacretaz" wrote:
> Hi,
>
> On Thu, Nov 15, 2012 at 6:35 PM, Alex Harui wrote:
>> ...Is it ok to start the vote on graduation?...
>
> From the steps listed at
> http://incubator.apache.org/guides/graduation.html I see three things
> missing:
>
> 1) Update th
Hi,
> Some months ago my thoughts was very different, but right now that a full
> rewrite is required, my opinion is clear about what to choose, and for
> something new, I choose Haxe.
Can you outline what would be require to convert the existing Flex framework
for use with Haxe? MXML (and bindi
On 11/16/12 4:15 AM, "Martin Heidegger" wrote:
> It looks like I won't spend more time on Flex. Feel free to remove me.
IMO, you earned your way in, and even if you can't be active in the near
future, who knows what a more distant future will hold. Committer-hood,
once earned, does not expire
I don't see a problem here.
Its a fact that flex USE Adobe runtimes to target as much platforms as
it can.
Its because of history of flex. and because until recent time, it was a
very efficient tool to achieve that.
If FalconJS was a fully usable solution, it would run on something else
then Ad
Well, I got the feeling that some users on this list were advocating a total
rewrite asap rather than maintaining and improving the current codebase. A new
Flex framework, built in Haxe or some other language than AS3/MXML is a totally
new framework that will have no support for the current cod
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?
-omar
On Friday, November 16, 2012, Ben Dalton wrote:
> Not to add fuel to the fire, but is choosi
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
> But bad news - in this situation i think guys from Adobe doesn't help us
with new compiler.
This should not be the motivation to go one way or another. Adobe's
position is already shared and know: They want only gamming. They throw
flex away. Tools, AVMs and languages are updated and designed on
[
https://issues.apache.org/jira/browse/FLEX-33263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Frampton resolved FLEX-33263.
---
Resolution: Fixed
Fix Version/s: Apache Flex Next
Author: cframpton
Date: Fri Nov 16 1
Result: 37 +1 (binding 19, non-binding 18)
Binding (19 +1):
Bertrand Delacretaz
Carol Frampton
Dave Fisher
Erik de Bruin
Espen Skogen
Gordon Smith
Greg Reddin
Jeffrey Houser
Jonathan Campos
Jun Heider
Justin McAllen
Michael Labriola
Michael Schmalle
Nicholas Kwiatkowski
Omar Gonzalez
OmPrakash M
The problem with your definition, Sébastien, is that you target all of
those platforms via AIR, so you're not actually describing something that
is under Apache Flex control. Flex just happens to be able to take
advantage of that runtime to target different platforms.
Using haxe as a language woul
[
https://issues.apache.org/jira/browse/FLEX-33263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carol Frampton reassigned FLEX-33263:
-
Assignee: Carol Frampton
> FocusOut in datagrid causes RTE if target.parent is null
>
[
https://issues.apache.org/jira/browse/FLEX-33134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498843#comment-13498843
]
Erik de Bruin commented on FLEX-33134:
--
This is so cool! I have distilled the followi
Why you say its too generic?
Maybe the "many platforms" is too generic, and i could precise Desktop,
browsers, tablets and smartphones?
What other framework/language can achieve that today?
then you can find some Flex competitors which don't do the job with same
easiness and succes.
Bottomline
1 - 100 of 152 matches
Mail list logo
