incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Kwiatkowski <nicho...@spoon.as>
Subject Re: Starling + Flex
Date Sun, 21 Oct 2012 19:22:00 GMT
Essentially, anything that references the Stage (do a search/replace for
Stage), and any component that has addChild in it needs to be re-designed.
 This could be as simple as re-creating our own DisplayList object, and
pushing that functionality to certain sub-components.  I'm not one who
would even attempt to do that because if done incorrectly would be a
performance nightmare.  The other issues that persists is the simple
drawing techniques (which could be taken care of by re-doing most of the
skins of existing components -- assuming everything is an fx style
component) that almost every visual component relies on.

By the way, that would fix our base SDK, but would massacre the ecosystem
as existing components (think, ESRI's components) would no longer be
compatible unless they update their component set as well.  There is
no backwards compatibility mode if you change the SDK to use Stage3D.

-Nick


On Sun, Oct 21, 2012 at 2:12 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:

> > It looks to be a pretty big task.  The biggest problem is the lack of a
> > DisplayList, which is the model that Flex is based on.  That in itself
> will
> > cause well over 900 classes to have to be re-engineered.  After you've
> > re=engineered those, all you would have left is the networking stack, and
> > some one-offs (like Mike's favorite -- binding!).
>
> Would you mind elaborating on this a bit (if only so other's won't
> have to heave half a day on this again, later on)? What did you look
> at, and where did the first "problems" appear? In other words, I'm
> interested to hear what WILL be usable as well as what won't.
> Refactoring or re-engineering 900 classes can either be a lot of hard
> work or a lot of easy work (maybe automate some?)...
>
> > the short-term.  There are LOTS of other things I'd like to see happen
> > before we refactor to use the "this is Adobe's direction today"
> technology.
>
> One of Alex's comments actually made me sit up and take note: he's
> proposing to abstract the framework from the delivery platform. This
> would mean LESS dependence on Adobe's "tech du jour", or whatever
> tickles the internet's fancy at any one time.
>
> EdB
>
>
>
> >> Considering the discussions on the various forums, it doesn't look very
> >> promising
> >> On Oct 21, 2012 3:59 PM, "sébastien Paturel" <sebpatu.flex@gmail.com>
> >> wrote:
> >>
> >> > Thanks for the update,
> >> > but why would it require a "fairly massive rewrite" exactly?
> >> > when you say "I would look at that" about feathersui, you mean as an
> >> > alternative to flex?
> >> >
> >> > its quite a bad news IMO. if flex can't "easely" target a new
> rendering
> >> > layer like starling, which stay in an Adobe runtime,
> >> > what is the future of flex as a multi platform framework, and
> especially
> >> > as a mobile SDK?
> >> >
> >> >
> >> >  After discussing with Thibault and spending time working on this I've
> >> >> determined that a fairly massive rewrite would be required. Shortly
> >> after
> >> >> they released http://feathersui.com/ and I will say that it is a
> nice
> >> bit
> >> >> of work. I would look at that.
> >> >>
> >> >> On Sat, Oct 20, 2012 at 8:40 AM, sébastien Paturel
> >> >> <sebpatu.flex@gmail.com>wrote:
> >> >>
> >> >>  Hi jonathan,
> >> >>> What is the state of this very promising project?
> >> >>>
> >> >>> Le 14/06/2012 18:46, Jonathan Campos a écrit :
> >> >>>
> >> >>>   Recently I've been getting aquatinted with Starling to see if
it
> >> could
> >> >>>
> >> >>>> work
> >> >>>> with Flex. After a few days of playing I think that it is possible
> >> but I
> >> >>>> do
> >> >>>> see the issues now and there is plenty of work that is necessary
to
> >> make
> >> >>>> it
> >> >>>> happen.
> >> >>>>
> >> >>>> To get things going I basically cut down the UIComponent (to
the
> parts
> >> >>>> that
> >> >>>> I cared about), made a copy of the entire Flex framework (as
many
> >> >>>> interfaces rely on DisplayObject, etc), replaced them with
Starling
> >> >>>> classes, rebuilt some of the Spark primitives, and "adjusted"
some
> of
> >> >>>> the
> >> >>>> starling classes to fit some of the Flash interfaces.
> >> >>>>
> >> >>>> At this point I'm definitely going to wait to get the 4.8 release
> out
> >> >>>> before giving this more time but I think it is possible. I'm
sure
> >> other
> >> >>>> developers are already aware of it but if we could make some
new
> >> >>>> interfaces
> >> >>>> such as an IDisplayObject it would be much easier switching
out
> >> >>>> DisplayObject for a Starling DisplayObject.
> >> >>>>
> >> >>>> Just thinking out loud at this point.
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>
> >> >
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

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