[Golist] Sneek peak at DepthTween

[Joel Stransky]

Thanks for the input Alan. I seriously contemplated and still might do just
that. I wanted to avoid adding methods to everything if only a few will need
them.
--Joel

On Fri, Jul 4, 2008 at 5:29 PM, Alan Shaw <nodename at gmail.com> wrote:

> > A lot of trouble could be saved if I could just figure out a way to add
> dynamic methods to all Display Objects.
>
> You can try putting them on DisplayObject's prototype!
>
> -A
>
>
>
> On Tue, Jun 24, 2008 at 2:30 PM, Joel Stransky <joel at stranskydesign.com>
> wrote:
>
>> Thanks for the feedback Donovan! It's been fun to develop so far thanks to
>> Moses but I sense there's even more power I could leverage so I'll be
>> hitting you guys up for tips soon.
>>
>> I think I'll add a toggle for upper left and mid/center locations. A lot
>> of trouble could be saved if I could just figure out a way to add dynamic
>> methods to all Display Objects.
>>
>> --Joel
>>
>> On Mon, Jun 23, 2008 at 5:49 PM, donovan at hydrotik.com <
>> donovan at hydrotik.com> wrote:
>>
>>>  This is great Joel! Very useful.
>>>
>>> Personally I would go for a center/middle registration point just because
>>> it's standard with most 3D environments, but some conversion methods would
>>> definitely be useful:)
>>>
>>> Looking forward to seeing what comes of this.
>>>
>>> Donovan
>>>
>>>
>>>
>>> On 6/23/08 8:10 PM, "Joel Stransky" <joel at stranskydesign.com> wrote:
>>>
>>> Hey peeps,
>>> My first Go package is finally taking shape. It's very early in
>>> development but I couldn't wait to show you all.
>>> I really wanted to have this done in time for flashbelt but hey, maybe
>>> next time. :)
>>> DepthTween is a 2.5D position manager. It basically manages a list of
>>> objects and updates their stacking order when any of their draw() methods
>>> are called.
>>> You first create an instance of DepthManager and pass a
>>> DisplayObjectContainer. Children of that DOC can then be initialized and
>>> have 3d tween methods called on them.
>>>
>>> http://lab.stranskydesign.com/depthTween.html
>>>
>>>
>>> Currently I'm struggling with what form of virtual x and virtual y to go
>>> with. The goal of the class is to simply add a z property to existing
>>> DisplayObjects. Currently I'm using a right-hand system which makes calling
>>> 3dtweens a little weird if you're not used to thinking in 3d as an objects
>>> 0,0,0 point becomes the center of the DisplayObjectContainer and half way
>>> between the foreground and background instead of the upper left corner like
>>> we're used to.
>>>
>>> The catch is, if I keep x and y relative to the upper left corner
>>> (reverse cartesian), you still have to get used to thinking in terms of
>>> those coordinates augmented by z-depth.
>>>
>>> I've got a lot of planned features and although it's very early I'd
>>> appreciate any feedback/questions/suggestions.
>>>
>>>
>>>
>>> _______________________________________________
>>> GoList mailing list
>>> GoList at goasap.org
>>> http://goasap.org/mailman/listinfo/golist_goasap.org
>>>
>>>
>>
>>
>> --
>> --Joel
>> _______________________________________________
>> GoList mailing list
>> GoList at goasap.org
>> http://goasap.org/mailman/listinfo/golist_goasap.org
>>
>>
>
> _______________________________________________
> GoList mailing list
> GoList at goasap.org
> http://goasap.org/mailman/listinfo/golist_goasap.org
>
>


-- 
--Joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://goasap.org/pipermail/golist_goasap.org/attachments/20080704/01c3485b/attachment.html