Hey,
Yes, I would make it all absolute. My need is to create windows, boxes,
animations, or other things. Those all require absolute anyways. The
static and relative positioning is probably best left for CSS rendering.
But these items in particular can't be done very easily with CSS, or
more in specifically, the 'center' and 'fromX' functions. The other ones
I take to be convenience functions for animations or effects. Having it
all in a few functions would be even better :) That's just the limit of
my mind in the list.
Ryan
Bob Ippolito wrote:
On Nov 18, 2005, at 3:11 PM, Ryan Nichols wrote:
While I don't have the time to contribute, something on my list id
like to contribute in the future (or probe some of the smarties on
this list to do) is a full positioning system. I'd love to be able
to write:
getPositionX()
getPositionY()
elementPosition covers both of these... elementPosition(e).x and
elementPosition(e).y if you really want just one or the other.
centerElement(e); (to center on the user's screen)
setPosition(e, x, y);
setElementWidth(e);
setElementHeight(e);
elementFromTop(e, px) (to set the element x pixels form the top);
elementFromLeft(e, px)
elementFromRight(e, px)
elementFromBottom(e, px)
this seems a little too redundant.. I'd rather have two or three
functions to cover all this instead of eight. Anyway, the problem
with setting positions is the whole style.display.position issue,
what's the best way to handle that? Clearly it has to be changed for
elements whose positions are static, but what to do with fixed/
relative? Should it all be forced to absolute, or what?
-bob