Very cool interesting work Alex. Going to need to stop and check this out. I've been using feathers recently for a few display object heavy mobile apps and it has worked well. Would like to get back some parts from flex. When I was playing with making a starling version of flex I felt the need for a new way for add child also. So yea... Long story short definitely understand and like where you are going. On Jan 18, 2013 1:49 PM, "Alex Harui" <aha...@adobe.com> wrote:
> Changing subject because GPU rendering usually gets a lot of replies. > > In this new framework, I am trying to separate everything into little > chunks > I call "beads". The visual components are supposed to have a minimum of > three beads, one each for MVC, and the V is essentially the Skin. > > Components don't assume they are on the Flash display list. Instead of > calling addChild, you call child.addToParent. > > So, yes, you could write new view beads that create their visuals using > starling. I suppose we could rewire addToParent to do what you want. > > I didn't explicitly design the new framework for starling. I still need > convincing that it truly makes a difference for the vast majority of > business applications. I still think your Flex apps are busy running AS > code > or suffering from having too many display objects per component which I do > want to tackle in this new framework. Early versions of this new framework > are probably not going to support 3D effects and 3D rendering so I think I > have time before I have to really deal with it. > > I did consider that the new framework would favor bitmaps over vectors, at > least in the early versions. I'm not planning support on the JS side for > vector graphics right away, so you are reduced to using bitmaps for many > more things, which I think most folks do in HTML/JS and which GPUs seem to > like more. > > The prototype is checked in: FalconJS is in the falcon/trunk/compiler.js > folder. The latest ASJS framework is in asjs/branches/develop/framework, > and the example that uses it is in > asjs/branches/develop/examples/FlexJSTest_again. > > > On 1/18/13 11:04 AM, "Om" <bigosma...@gmail.com> wrote: > > > On Fri, Jan 18, 2013 at 10:00 AM, Alex Harui <aha...@adobe.com> wrote: > > > >> That's why I've chosen a new > >> parallel framework: I've already got a prototype up and running, and I > >> would not be able to do that with the current Flex SDK. Hopefully the > >> patterns I am using the new framework are extensible enough to allow it > to > >> grow up to match the old Flex SDK over time. > >> > > > > This sounds very interesting to me. I have been playing around with > > Starling and Stage3D to see how best to render Flex via the GPU. I've > come > > to the conclusion that this would entail rewriting a lot of of existing > > Flex code. In your new framework, do you think it would be possible to > > switch from DisplayObject based rendering to GPU based rendering as > needed? > > Did you consider this option when designing your new framework? > > > > Any chance we could see your prototype any time soon? > > > > Thanks, > > Om > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
