MochiKit.Style.getElementDimensions is the preferred function, since
the other two will probably be removed soon (they are not documented,
and thus not part of the supported API).
There are some issues with border and padding size in this function
that is being discussed in another thread on the
Ah, I forgot. MochiKit.Animator is not an official part of MochiKit
(as the name suggests). You can find it here:
http://gr.ayre.st/~grayrest/animator/animator.html
MochiKit.Visual was adapted from Scriptaculous (mostly), but
MochiKit.Animator is instead adapted from Bernard Sumption's
Yes, well. I was thinking simpler is better. So I though a single flag
would be sufficient to either remove both padding and borders, or to
keep the values unchanged (as today). If someone wants more detail,
there is always the helper functions for retrieving padding and border
widths.
I was
packed/MochiKit/MochiKit.js
Cheers,
/Per
On Thu, Jun 12, 2008 at 2:31 PM, Ragnar Rova [EMAIL PROTECTED] wrote:
Is there a recommended way of combining MochiKit stable to a
single .js file to reduce the number of http requests?
--~--~-~--~~~---~--~~
You
I really like your idea of making the creation of the input functions
more generalized. However, if we wanted to preserve the:
CHECKBOX(myNameIsBox1) ==
input type=checkbox name=myNameIsBox1/
functionality we'd need a slight modification to createDOMFuncExt.
Specifically, we'd need one more
Also have a look at scripts/pack.py - you can use it to pack your own,
selecting only those modules you care to have (being mindful, of course, of
dependencies between them).
FYI: In order to use pack.py, you will need a python interpreter and
apparently, someone correct me if I am wrong, Java.
I've now fixed the fix so that it also works in Safari. :-)
And also modified the API to support horizontal scrolling (currently
only available in Safari 3 though).
Tested to work correctly with the following browser/platform/version
combinations:
o Safari/Mac 3.1
o Firefox/Mac 2.0
o Opera/Mac
If I understand you correctly, I think createDOMFuncExt already
accomodates this:
CHECKBOX = createDOMFuncExt(null, input, [name], { type: checkbox });
HIDDEN = createDOMFuncExt(null, input, [name, value], { type: hidden });
I'm using this to create SVG functions with required parameters (such
When I first looked at your function I completely missed the
significance of this line:
myAttrs[args[pos]] = arguments[pos];
and thought that argument was only for specifying which attributes are
required. Having looked at it again, I now understand how it allows
for CHECKBOX(myName) syntax.
