Hi there,
Those are all good additions imo.
On 2/7/07, Chris Nokleberg [EMAIL PROTECTED] wrote:
// reverse of itemgetter (perhaps there is a better name)
getteritem: function (obj) {
return function (arg) {
return obj[arg];
}
}
Maybe propertygetter? When I started using
The following is a couple bugfixes in Selector (just some unqualified
names that have been lurking)
There's also a few times in Selector where MochiKit.Format.trim could
be used, but isn't. It's not too big a deal, but it seems like if it's
already in MochiKit, it should be used in MochiKit.
Hello Arnar and folks.
Sorry for the late response, but i finally had the chance to spend
some days off in the snow with skiing.
Thanks a lot for your suggestions!
This did help me a lot!
I hope that with some more experience i can get way deeper in
MochiKit.
Regards, Frank
On 27 Jan.,
We definitely won't be extending itemgetter to do two entirely
different things based upon the argument passed. However, we could
create a differently named function (e.g. rowgetter or something of
that sort) that does that.
-bob
On 2/7/07, Johnny Blonde [EMAIL PROTECTED] wrote:
One more
There is already a patch for this in Trac:
http://trac.mochikit.com/ticket/221
Arnar
On 2/7/07, Bob Ippolito [EMAIL PROTECTED] wrote:
We definitely won't be extending itemgetter to do two entirely
different things based upon the argument passed. However, we could
create a differently named
On 2/7/07, Aaron Faanes [EMAIL PROTECTED] wrote:
Oops, I meant Format.strip, not trim. There's just a couple places
where:
expression.replace(/(^\s+|\s+$)/g, '')
These are leftovers from the Prototype selectors, which
MochiKit.Selector was initially ported from. This may actually be a
