As far as involving Git that should be up to each individual developer. Git
is very efficient at managing branches locally and contains workflows that
allow you to interface with an SVN repository while giving you the
branching freedom that a DCVS system like Git offers.
I also agree with Jeffry o
I'm with the rest of the people that hold this as really important to them.
It makes it easier to read. I understand that we are not all going to come
to an agreement on 100% of the formatting, but that's what teams do, they
come to a compromise and they all buy in and comply for the sake of the
te
Maybe the mentors will guide us here. I seem to have the impression that
the trunk should always be the release. It can never be in a state that
isn't a certified release. I think that may be because our "product" is
just source code, and folks shouldn't have to navigate through tags to get
the
Please create an @apache.org account for me. I'd like
the user id saravans.
--
* Gs*
I poked around the Apache projects and found this:
http://cxf.apache.org/javadoc/latest/
If you pick the class AegisDataBinding, you will see it inherits from
java.lang.object which is not in the package list but the links point to the
main javadoc at oracle. And there is a list of methods inheri
We might want to hold off on even placeholders until we hear back from
Adobe on branding.
On Wednesday, January 4, 2012, Randy Troppmann
wrote:
> Hi Dave,
>
> Try these urls:
>
> http://randytroppmann.com/flex/apache-flex-logo.png
> http://randytroppmann.com/flex/apache-flex-logo-69x80.png
>
> -
Hi Dave,
Try these urls:
http://randytroppmann.com/flex/apache-flex-logo.png
http://randytroppmann.com/flex/apache-flex-logo-69x80.png
- Randy
On Wed, Jan 4, 2012 at 10:56 PM, Dave Fisher wrote:
> Hi Randy,
>
> The list strips out attachments. If you will provide an alternative url or
> send
Hi Randy,
The list strips out attachments. If you will provide an alternative url or send
it to me directly that would be great.
Regards,
Dave
On Jan 4, 2012, at 6:46 PM, Randy Troppmann wrote:
> Here is a placeholder logo in a couple sizes.
>
>
>
> On Wed, Jan 4, 2012 at 7:09 PM, Dave Fish
As someone that has worked with an Apache like project before I can say
that the sandbox approach is very very help and would prefer to keep it.
Branches are meant to go back into the trunk eventually, however the
sandbox may never go into the trunk and have various crazy changes.
It's been helpf
I would have to agree with Jeffery. Almost all of the projects I've seen
that use SVN are organized in a Trunk/Branch/Tag method. I don't see any
reason for us not to mimic the same.
I also think that long-term 'projects' and short-term be given the same
treatment. Each gets its own branch, and
An other way, maybe clearer in term of dev and branching would maybe the use of
svn as master and git for branching, you can read more in the links bellow :
http://blogpro.toutantic.net/2012/01/02/another-git-branching-model/
http://wiki.apache.org/general/GitAtApache
Frédéric Thomas
> Date:
Here is a placeholder logo in a couple sizes.
On Wed, Jan 4, 2012 at 7:09 PM, Dave Fisher wrote:
>
> On Jan 4, 2012, at 1:52 PM, Dave Fisher wrote:
>
>>
>> On Jan 4, 2012, at 12:42 PM, Bertrand Delacretaz wrote:
>>
>>> Hi Dave,
>>>
>>> On Wed, Jan 4, 2012 at 6:35 PM, Dave Fisher wrote:
>>> ...
On Jan 4, 2012, at 1:52 PM, Dave Fisher wrote:
>
> On Jan 4, 2012, at 12:42 PM, Bertrand Delacretaz wrote:
>
>> Hi Dave,
>>
>> On Wed, Jan 4, 2012 at 6:35 PM, Dave Fisher wrote:
>> ...
>>> I have significant experience using the Apache CMS with the Apache
>>> OpenOffice podling.
>>>
>>> See
I can honestly say it's been a long time since I looked at the public
Flex SVN repo; so I'm not sure the extent of what is in there or how it
is organized.
Most projects I've worked on have used a "Trunk/Branch/Tag" approach.
To map:
* Released sounds kind of like tags; which is a full
As a short term project, how about bringing some of the new mobile components
to the Desktop/Web?
Arturo Alvarado
- Original Message -
From: "Alex Harui"
To: flex-dev@incubator.apache.org
Sent: Wednesday, January 4, 2012 7:13:36 PM
Subject: Re: So, what should we do first?
Still hop
At some point, most every Flex Component inherits from a Flash
component. In my own development, I Find it hugely beneficial to be
able to look at all the inherited methods and properties. I often find
properties and methods up in the hierarchy that I didn't know existed
just by reading t
Still hoping for end of week, but maybe Monday.
-Alex
On 1/4/12 4:54 PM, "Jeff Tapper" wrote:
> Any idea how long till adobe commits the code?
> On Jan 4, 2012 7:44 PM, "Alex Harui" wrote:
>
>> I¹m loving the ideas and energy on this list so far. And so, the subject
>> question needs to be
Any idea how long till adobe commits the code?
On Jan 4, 2012 7:44 PM, "Alex Harui" wrote:
> I’m loving the ideas and energy on this list so far. And so, the subject
> question needs to be answered: What should we (the committers in this
> project) do first?
>
> I recall from the summit that a
I’m loving the ideas and energy on this list so far. And so, the subject
question needs to be answered: What should we (the committers in this project)
do first?
I recall from the summit that a healthy Apache project releases at least every
4 to 6 months, and one of the things an incubator po
Hi,
just want to say hi to all members. I'm glad to see Apache Flex coming and
many known people here.
Hope as well to contribute as soon as I can, and this hope will be in few
month from now on.
Best and...
Go Apache Flex Go!
:)
--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:
Hi,
I'm an initial commiter to the Flex project. I'm listed in the Flex
Proposal under a different e-mail that I decided to change in order to
better separate interests.
If I was judging the future of Flex by the activity I've been seeing
today on this list, I'd say we're in for bright days
I didn't quite answer the use case question you had.
Two that are huge is as I said an ASDoc Editor, you have no idea how
much time this has saved me, just think of the typing, editing and
code completion for documentation.
The other is metadata. Allowing a DOM to access the compilers AST t
OK,
Then I stand corrected with the SWC option I guess I don't quite
understand how that works with the Flash Builder IDE at least.
Mike
Quoting Alex Harui :
Good question. We will have to first figure out whether we can/should. I
would imagine that there is JavaDoc for Java-based projec
Good question. We will have to first figure out whether we can/should. I
would imagine that there is JavaDoc for Java-based projects in Apache that
inherit from Java classes and the JavaDoc does not include packages not in
Apache project. Maybe the mentors can answer.
We might have to make it s
For clarity on my compiler hooks comment... imagine if you could send compiled
output through optimization utilities like Apparat (Joa has released it as open
source btw) or using byte-code as the base for a DSL. Lot's of possibilities...
Cheers,
Rick Winscot
On Wednesday, January 4, 2012 at
Hi Bertrand
I've now sent this in.
Tink
On 4 Jan 2012, at 10:23, Bertrand Delacretaz wrote:
Hi,
On Tue, Jan 3, 2012 at 9:08 PM, Tink wrote:
I am an initial committer for Flex (the email address used on that
list is
stephen.do...@tink.ws, please can that be amended to
f...@tink.ws). Pl
Why couldn't we load (Flash) SWC's that hold the asdoc comments like
Flash Builder does and extract them.
In a properly designed application framework, you would pull that
information into the DOM before the render.
I have alot of experience with this area so I would love more
conversatio
I'm probably worrying about this a bit too early and I know I've violated
this a bit also. I'm going to watch what I say.
On Wed, Jan 4, 2012 at 5:10 PM, Jonathan Campos wrote:
> And you did. I made sure to apologize early to you because it wasn't your
> comment, but just general comments of firs
And you did. I made sure to apologize early to you because it wasn't your
comment, but just general comments of first priorities and what is
important. My worry is that some of these discussions hinder someone that
may come in that doesn't feel like they can help rearchitect the framework,
but just
Quoting Rick Winscot :
web-links between classes,
easy
references to classes in the build paths
done
doc generation
done, I have written JASDoc using jasblocks that creates all my
components asdocs in html
What I'm saying is I already have an application that uses an AST DOM
in asblo
I'm curious if we'll be able to generate the full ASDocs, like what
are on the Adobe site without the source code for the Flash stuff. We
can only go so far up the inheritance tree.
On 1/4/2012 5:40 PM, Michael Schmalle wrote:
I do not have a lot of experience with the actual compiler and
No argument.
I'd like to think I was clearly expressing personal preference, not
dictating other people's actions.
On 1/4/2012 5:44 PM, Jonathan Campos wrote:
Just to be fair. If they want to make another set of Components that
is completely their choice. Sorry Jeff for responding with thi
Mike,
This sounds like an interesting idea. I've been all over MetaAS, PMD, and Code
Model... which is what it would take to make something like this happen. Why so
much depth? Mainly, because 'docs' aren't just 'text.' A good example would be
web-links between classes, references, etc. Code fo
I have a CMS which consists of 10-15 modules with dynamic skinning (3
skins based on rolloutID the style.swf for the relevant project will be
loaded at runtime) and there has been a lot of work done by inexperienced
developers (following code guidelines with good testing but focus was on
getting it
Keep in mind that Adobe hopes to contribute Falcon at some later point in
time which seems to have a much cleaner code base to work from. Although it
isn't available now. Also keep in mind that the compiler source may not be
in the first drop to Apache.
On 1/4/12 2:45 PM, "Jonathan Campos" wro
I've been fortunate to test out some of Michael's work on ASDoc tooling, I
can say they are well worth it :)
As for the compiler hooks, I guess we'll have to wait for Adobe to donate
the new Falcon compiler before we can start having fun with those ideas.
On 4 January 2012 23:45, Jonathan Campos
Go for it
On Wed, Jan 4, 2012 at 4:40 PM, Michael Schmalle wrote:
> Hi,
>
> I do not have a lot of experience with the actual compiler and asdoc tool
> but that has not stopped me from having fun with parsers and AST. :)
>
> I am wondering if there is any interest in creating some apis in the
> c
Just to be fair. If they want to make another set of Components that is
completely their choice. Sorry Jeff for responding with this to your post,
just see lots of people talking about what should and should not be done.
We all have to remember that some people's passions may be in a different
dir
On 1/4/2012 10:23 PM, Iwo Banaś wrote:
Many of performance issues can be addressed but to be sure that we are
addressing the right ones we'll need a good performance benchmarks.
Preferably a full enterprise applications. I'm aware that it's not
possible to release commercial application code as
Hi,
I do not have a lot of experience with the actual compiler and asdoc
tool but that has not stopped me from having fun with parsers and AST.
:)
I am wondering if there is any interest in creating some apis in the
compiler that jive with the asdoc tool(modifying the asdoc tool). I'm
g
Has open Laszlo stayed up to date? I hadn't heard of it in many years.
I--personally--would rather see efforts put towards optimizing
existing Flex Components or the component framework; not on creating a
3rd component framework within Flex.
On 1/4/2012 5:10 PM, Raju Bitter wrote:
It wo
The large CSS file issue should be resolved in 4.6. And Ryan will likely
submit another patch that makes it even better during state transitions.
It is important to profile your application to understanding why you are
having performance problems. Sure, UIComponent can be refactored and
become
If someone was so inclined they could create some intentionally complicated
application that allows you to view mailing list messages or some app to
that effect. Then with this shared (and possibly helpful) app we could beat
against it for performance.
Just a wild idea.
On Wed, Jan 4, 2012 at 4:2
>From what I understood about the DI features in the framework in Labriola's
talk at the flex summit, these would actually happen at compile-time, so
its not the same DI functionality we're used to when building applications
(like Parsley/Swiz/Spring/etc).
Interesting details by the way about the d
Using Flex to render HTML/CSS as been thought to be a ton of work, but could
definitely happen with community support. I have an old prototype on my
blog that I've been refactoring in my spare time.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
On 1/4/12 2:03 P
The Flex framework is a big beast but from my experience whichever
part you pick it can be optimized :-)
The biggest issue with StyleManager is scalability, it's fast for
small toy projects and simple examples but terribly slow for huge
applications.The problem is that styles processing times grow
Greg thank you - that was my problem.
Carol
-Original Message-
From: Greg Reddin
Reply-To: "flex-dev@incubator.apache.org"
Date: Wed, 4 Jan 2012 14:14:20 -0800
To: "flex-dev@incubator.apache.org"
Subject: Re: help please - not able to commit
>On Wed, Jan 4, 2012 at 4:10 PM, Carol Fram
Go for it.
On 1/4/12 2:13 PM, "Michael Schmalle" wrote:
> This is likely not an option due to lexical errors, a lot of
> formatters out there aren't perfect since they parse and re-emit code.
>
> If there was a formatter that was written that hooked into the flex
> compiler's AST, that is anot
On Wed, Jan 4, 2012 at 4:10 PM, Carol Frampton wrote:
>
> I am able to checkout the branch
> http://svn.apache.org/repos/asf/incubator/flex/trunk but I am not able to
> commit with either SmartSVN, which is what I usually use, or the command
> line.
Did you try https://svn.apache.org/repos/asf/in
This is likely not an option due to lexical errors, a lot of
formatters out there aren't perfect since they parse and re-emit code.
If there was a formatter that was written that hooked into the flex
compiler's AST, that is another animal.
I would love to work on that. :)
Mike
Quoting Ro
Adobe will not be caching RSLs from Apache so yes, we want to reduce the
need for caching RSLs in the future.
On 1/4/12 1:34 PM, "Roland Zwaga" wrote:
> Its kind of sad since the framework RSL's then won't be put in the player's
> trusted cache, but then again, if the SDK gets better modularize
I'm with you Alex. Definitely hear what you are saying and would like to
solve this issue.
On Wed, Jan 4, 2012 at 4:09 PM, Alex Harui wrote:
> Interfaces, modularity and DI are all good things. But, IMHO, the key
> thing
> to keep in mind is that we are working in a constrained environment. If
as a committer you have the ability to 0/-1 code for formatting. I would
think it would be considered "polite" to let them know that was the reason
was formatting so they can do a quick fix.
On Wed, Jan 4, 2012 at 4:08 PM, Rogelio Castillo Aqueveque <
roge...@rogeliocastillo.com> wrote:
> maybe a
It would make sense to build a light-weight component set for Flex,
which could be used for rendering Flex apps in HTML5 later on. The
approach could be based on the UI/component implementation OpenLaszlo
has (which provides cross-compilation features for ActionScript and
JavaScript, check this dem
I am able to checkout the branch
http://svn.apache.org/repos/asf/incubator/flex/trunk but I am not able to
commit with either SmartSVN, which is what I usually use, or the command
line.
I am able to use the username and password to log in to Apache Account
Utility so I think I have them right.
I
Interfaces, modularity and DI are all good things. But, IMHO, the key thing
to keep in mind is that we are working in a constrained environment. If you
are old enough to have tried to fit a DOS program in 640K, then that's a
good analogy to keep in mind. It will all come down to trade-offs. No
Fair enough. I hadn't considered other ide's. Maybe there are alternatives that
could be setup for other ide's with supporting documentation of code guidance,
rather than "standards". I agree we can't make everyone follow the same coding
conventions, but we can highly encourage them.
>From my e
maybe a pre-commit hook into svn client that run the formatter just before the
commit happens would work.
---
Rogelio Castillo Aqueveque
roge...@rogeliocastillo.com
On 4/01/2012, at 6:57 PM, Michael Schmalle wrote:
> This is kind of what I was getting at.
>
> The problem with the Flex Forma
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
This is exactly why I asked because I saw that, what 4 years ago? :)
Still committed code didn't follow it.
As committers, if we agree on a convention, to we have the right to
turn down code that does not follow it and tel
There will be numerous smaller things to tackle of course, I just wanted
this general topic started to get some feedback.
- I want UIComponent to be more lightweight
- I want to reduce the performance cost of using styles and style
selectors/descendants
- I don't want UI to get blocked because of
Please forgive if this is out of turn or place, it seems people are making
suggestions about the work they would like to see done on Flex and I would
like to contribute.
I've used Flex for about 5 years and always found text formatting to be
difficult and limited.
I would like to see as an alt
Exactly!
But here comes the interfaces gotcha: to benefit from interfaces you
can't just add a huge interface for every class,
you have to define minimal, simple and implementation independent
interfaces and ensure that different part of the framework are
communicating using these interfaces.
The
Carol, we talked about this previously. I am right there with you about
uniform code. Big deal to me.
On Wed, Jan 4, 2012 at 3:54 PM, Carol Frampton wrote:
> There is a coding standard but unfortunately not everyone chose to follow
> it, or only followed the parts they liked.
>
> http://opensour
On Wed, Jan 4, 2012 at 3:08 PM, Alex Harui wrote:
> Hi Greg,
>
> Regarding Spoon, are there things an Apache project typically does not do
> that Spoon or some other entity should be doing? Like promotion, education,
> training etc.?
Apache projects "can" do everything you mentioned. Also, Apach
This is kind of what I was getting at.
The problem with the Flex Formatter is it's an Eclipse plugin that
last time I looked. The dev might have abstracted it but I don't know.
The problem is Flash Builder is not the only ide in town.
Mike
Quoting Douglas Arthur :
I for one vote that we s
I agree with the sentiment, but I don't think that "performance" is an
actionable item. The Flex Framework is a big beast; what exactly do you
want to improve performance of?
If you were to say that "I want views in a mobile web app to change
quicker when using a viewChange effect" that w
+1 , if it can be done with FlexFormatter it would be even better
On 04/01/12 22:54, "Carol Frampton" wrote:
>There is a coding standard but unfortunately not everyone chose to follow
>it, or only followed the parts they liked.
>
>http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventio
There is a coding standard but unfortunately not everyone chose to follow
it, or only followed the parts they liked.
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
I am in favor of a coding standard. I like uniform looking code.
Carol
-Original Message-
From: Micha
Oh, I get it. I haven't worked much with those. But this does apply to the
mobile scene as well. Even apps like Photoshop Touch lag quite a lot on the
Galaxy tab 10.1, which came out this year. It's not a code issue, it's a
framework issue. It does apply to skinning a lot as well. Just performan
I for one vote that we suggest developers to use FlexFormatter and publish a
settings file for public consumption. I believe Adobe uses it in-house, please
someone correct me if I'm wrong? And I even believe there's a settings file
floating around from Adobe.
http://sourceforge.net/apps/mediawi
On Jan 4, 2012, at 12:42 PM, Bertrand Delacretaz wrote:
> Hi Dave,
>
> On Wed, Jan 4, 2012 at 6:35 PM, Dave Fisher wrote:
> ...
>> I have significant experience using the Apache CMS with the Apache
>> OpenOffice podling.
>>
>> See https://svn.apache.org/repos/asf/incubator/ooo/site/trunk and
And it's not only on mobile, on desktop (mostly Mac's) this is a problem
also. I'm talking about big enterprise applications and websites here
(like a CMS with graphical skin applied, nothing really in standard Flex
skin)
On 04/01/12 22:49, "Arthur Lockman" wrote:
>+1 on this. Performance defini
On 1/4/2012 4:43 PM, Fréderic Cox wrote:
So do I, it's hard to convince clients. You can convince them with good
applications but they think Adobe is abandoning it due to all the
miscommunication so they are opting for HTML5 mobile apps.
Be sure to let your clients know that AIR is the technol
+1 on this. Performance definitely needs to be addressed on Flex. I've noticed
that on newer devices, it works fine. But on the slightly older ones,
performance is a huge issue. Hopefully we can get in there and clean it up so
it performs better.
--
Arthur Lockman | Senior Developer @ Vivace
I hate this topic but it needs to be asked to the community.
Since I am an initial committer I will stand by whatever the consensus
is with the code I commit.
But then the question, what are we doing about this?
There is already ALOT of code in the sdk that uses different
conventions. I th
A very important aspect of AIR is the new ability to package the AIR runtime
in your application. That binds your app to a specific version if AIR
eliminating risk that some future version of AIR will break your app. There
are issues with the total package size, but a smaller framework could redu
Thats worth a lot. I'm glad to hear that.
-Arthur
---
Arthur Lockman
a.rthr.me
@arthurlockman
Sent from my iPhone
On Jan 4, 2012, at 4:38 PM, Jonathan Campos wrote:
> I can tell you that it is my commitment. Take that for what it is worth.
>
> On Wed, Jan 4, 2012 at 3:36 PM, Arthur Lockman wrot
I call that a very good start :-)
Thanks
On 04/01/12 22:37, "Jonathan Campos" wrote:
>I can tell you that it is my commitment. Take that for what it is worth.
>
>On Wed, Jan 4, 2012 at 3:36 PM, Arthur Lockman
>wrote:
>
>> I hope that it stays air compatible. Working with flex mobile with air
>>
Not sure if that would work but ya, kind of like that. DI could get you
there without having to rip apart the core of flex.
On Wed, Jan 4, 2012 at 3:35 PM, Roland Zwaga wrote:
> Or even better, don't need StyleManager? Throw it out completely and save a
> buttload of memory :)
>
> On 4 January 20
So do I, it's hard to convince clients. You can convince them with good
applications but they think Adobe is abandoning it due to all the
miscommunication so they are opting for HTML5 mobile apps.
I think AIR for mobile created with Flex is an extremely powerful tool
(combined with the .ane's)
On
I can tell you that it is my commitment. Take that for what it is worth.
On Wed, Jan 4, 2012 at 3:36 PM, Arthur Lockman wrote:
> I hope that it stays air compatible. Working with flex mobile with air
> is a breeze, and there's really nothing like it. I hope it continues
> to work with it.
>
> ---
I hope that it stays air compatible. Working with flex mobile with air
is a breeze, and there's really nothing like it. I hope it continues
to work with it.
---
Arthur Lockman
a.rthr.me
@arthurlockman
Sent from my iPhone
On Jan 4, 2012, at 4:30 PM, "Fréderic Cox" wrote:
> I started working with
Hi Guys,
I think that the crucial question here is how we handle version control.
For a simple bugfix committing to "trunk" and voting or submitting a
patch are OK.
The problem is how we handle bigger chunks of work like mentioned TabNavigator?
I'm all for collaboration from the very beginning of
Or even better, don't need StyleManager? Throw it out completely and save a
buttload of memory :)
On 4 January 2012 22:31, Jonathan Campos wrote:
> The problem gets a bit hairy on parts of the framework that aren't readily
> accessible (managers/singletons). These would be the first target for D
Its kind of sad since the framework RSL's then won't be put in the player's
trusted cache, but then again, if the SDK gets better modularized there
won't be a need to download half a meg worth of framework for a small
application.
So in the end, the trusted cache won't be missed hopefully...
2012/
The problem gets a bit hairy on parts of the framework that aren't readily
accessible (managers/singletons). These would be the first target for DI,
allowing swappable components following good interfaces.
Don't like StyleManager? Have a lightweight focus manager specifically for
mobile? DI could
On 1/4/2012 9:27 PM, Douglas Arthur wrote:
I was just thinking about RSL's and how Adobe hosts the framework RSL's on
their servers. Will these be migrated over to Apache, or remain on Adobe's
servers, or both? If they become hosted on Apache, will they be setup outside
of an incubator uri so
ooh, I guess I misunderstood the idea of DI, I thought about implementing other
parsley/swiz/etc inside the sdk.
I'm all for modularity and DI within the framework.
R
---
Rogelio Castillo Aqueveque
roge...@rogeliocastillo.com
On 4/01/2012, at 6:25 PM, Roland Zwaga wrote:
> I think Michael
I started working with Flex 4.6 for mobile today creating an iPad application
and must say I am amazed at the possibilities and workflow. I am wondering
though on how the Apache project will cooperate with AIR for mobile. Is there a
guarantee that future versions of the SDK work with it? Is that
Adobe is not currently planning to support Apache Flex RSLs in the flash
player.
--
Garth Braithwaite
Sent with Sparrow (http://www.sparrowmailapp.com)
On Wednesday, January 4, 2012 at 1:27 PM, Douglas Arthur wrote:
> I was just thinking about RSL's and how Adobe hosts the framework RSL's on
Rogelio, while there are a lot of DI frameworks out there for AS3,
they don't work inside the core of the framework itself and from what
I've learned at the Summit, the spoon project could implement it. From
what I understood, it's a mix of DI at runtime and AOP with help of the
compiler. I'm
>From what I've heard Adobe will no longer sign the Apache Flex binaries, so
the cached RSL's won't be supported anymore...
But I've just heard rumors, not sure if they're true...
On 4 January 2012 22:27, Douglas Arthur wrote:
> I was just thinking about RSL's and how Adobe hosts the framework R
I think everyone's pretty much on the same page as you Mike :)
Describing component functionality using sane interfaces will *allow* DI
much more easily. If some type of configuration for this can be supported
by the SDK, that would be awesome because existing DI frameworks could hook
into those so
I was just thinking about RSL's and how Adobe hosts the framework RSL's on
their servers. Will these be migrated over to Apache, or remain on Adobe's
servers, or both? If they become hosted on Apache, will they be setup outside
of an incubator uri so they don't ever have to change again? Has any
I think Michael Labriola has some ideas about modularity and DI within the
framework, his idea was definitely NOT to have Flex feature an IoC
container like Swiz/SpringAS/SmartyPants etc.
The DI features would be focused on framework modularity, not on
*application* frameworks.
On 4 January 2012 2
This is just a weird thought and I have no opinion on DI since it's
like religion to most.
Isn't the idea of OOP polymorphism, and the way you create it is
through abstract interfaces? Correct me if I'm wrong here.
Maybe I am from another planet but it seems to me, that the strength
in Ap
I've worked on Flex applications for the past 4-5 years and see a lot of
developers picking it up since it is easy to create rich applications. However
performance is often an issue.
I mostly see it when using a lot of styles (or one large CSS file) and skinned
components (It is even worse with
Rogelio, I am not saying that the Flex SDK should have a lib for DI
(like Swiz or Mate). What I would like was to be able to configure the
mappings between the interfaces and objects, so I could easily replace
TabNavigator1 with TabNavigator2 touching in code as less as possible.
Part of the DI
true, we may not need a new framework to do DI in Flex, there are plenty of
DI frameworks.
But what we DO need in the core Flex classes is the ability to inject
dependencies directly into the classes instead of having the classes create
their dependencies themselves (in worst case statically or in
I have to agree with Roland, clearly DI will require good use of
interfaces to work, no? If start getting external dependencies properly
typed into interfaces is half work done to get basic DI working ,I'm not
counting all kind of crazy AOP that could be done on top of it.
João Fernandes
1 - 100 of 219 matches
Mail list logo
