Hi Jeffry,
Hopefully this gets added to the list in the right way as I'm cutting and
pasting from reading the search archives.
Incidentally, we should include instructions on how to search the archives
on the home page for the project, it's very difficult to locate
instructions, in the end I had
I guess I'll have to chime in here then :)
Right now I think having AOP as a framework feature is the most realistic,
once Falcon fully drops
we might start to see compile-time weaving, but for run-time dynamic
proxies it might be an idea to
make it a framework feature.
I am the author of as3common
>>AOP is probably a language thing, which we do not have control of.
Fair point Alex, AOP probably would better be a language feature rather
than a framework feature. Though we might see something sooner if we
implement it as a framework feature.
Having said that if enough f the micro-architecture
On 1/9/12 12:15 PM, "Doug McCune" wrote:
>
> Alex, does the Apache style of individual user contributions lend itself
> better to flushing this out? This is clearly something you've been working
> on at Adobe, but does the fact that Flex is now an Apache project and you
> are acting as an ind
>
> My current thoughts are to create a framework that is very granular and
> uses
> lots of composition. I have prototypes where HelloWorld is a 28K swf.
Alex, does the Apache style of individual user contributions lend itself
better to flushing this out? This is clearly something you've been w
On 1/9/12 10:31 AM, "Michael Schmalle" wrote:
> Alex, can you say what your framework classes are based on? Is this
> something where mobile and multi-touch can be used/composed but the
> framework not dependent on them?
My current thoughts are to create a framework that is very granular and
Quoting Alex Harui :
On 1/9/12 8:15 AM, "Carlos Rovira" wrote:
* Dinamic View States
...We need the capability to create states on the fly and let
other parts handle this dinamic view states (transitions,...). Without
this, view states are a bit limited.
Adobe has some work in this area
On 1/9/12 8:45 AM, "Jonathan Campos" wrote:
> I agree that "dynamic view states" isn't exactly clear to me.
This is probably just MXML/AS equivalence. Can you do everything in AS that
you can do in MXML. It is not quite possible or very hard for states and
transitions today.
> I could see
On 1/9/12 8:15 AM, "Carlos Rovira" wrote:
> * Dinamic View States
>
> ...We need the capability to create states on the fly and let
> other parts handle this dinamic view states (transitions,...). Without
> this, view states are a bit limited.
>
Adobe has some work in this area that will lik
+1 to the AOP idea
On 9 January 2012 17:06, Jonathan Campos wrote:
> On Mon, Jan 9, 2012 at 10:50 AM, Michael Schmalle >wrote:
>
> > I agree to, something that would deprecate the;
>
>
> It will probably be something I will focus on. So I can get ride of:
>
>
>
>
>
> . . .
>
> And all the o
On Mon, Jan 9, 2012 at 10:50 AM, Michael Schmalle wrote:
> I agree to, something that would deprecate the;
It will probably be something I will focus on. So I can get ride of:
. . .
And all the other code required to make that work.
--
Jonathan Campos
Quoting Jonathan Campos :
On Mon, Jan 9, 2012 at 10:42 AM, Jeffry Houser wrote:
Do you have a use case for dynamic view states? I can honestly say I've
never been limited by the current implementation.
I agree that "dynamic view states" isn't exactly clear to me. I could see a
need to off
On Mon, Jan 9, 2012 at 10:42 AM, Jeffry Houser wrote:
> Do you have a use case for dynamic view states? I can honestly say I've
> never been limited by the current implementation.
I agree that "dynamic view states" isn't exactly clear to me. I could see a
need to official support for "multi-di
Sorry, in my last email I deleted accidentally the first part:
On 09-01-2012 16:37, Nick Collins wrote:
Out of curiosity, what Maven support are you looking for that Flex-Mojos
doesn't provide, other than being natively integrated into the compiler,
perhaps?
- public repositories for the SDK
Do you have a use case for dynamic view states? I can honestly say
I've never been limited by the current implementation.
In the Flex 3 era you could define states on the fly; but it could be
a pain. I have never dug into the underpinnings of the Spark State
system, though.
On 1/9/2012
- public repositories for the SDK and other components
- plugin to generate flash builder / flashdevelop / FDT / etc project files
- Marvin Froeder subscribed here on the Flex mailing list :o)
João Saleiro
Out of curiosity, what Maven support are you looking for that Flex-Mojos
doesn't provide, other than being natively integrated into the compiler,
perhaps?
Nick Collins
On Mon, Jan 9, 2012 at 10:15 AM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:
> Hi,
>
> I would want to share my though
Hi,
I would want to share my thoughts about what changes would like to see in
forthcoming Apache Flex releases (far beyond 4.6.1 that would bring nothing
new AFAIK and will be only serve to put the project in the new Apache
rails). I'm referring to Apache Flex 4.7, 4.8, 4.9...and so on.
This is o
18 matches
Mail list logo
