[mochikit] partial vs. curry

[troelskn]

In the documentation, under MochiKit.Base.partial it says:

This could be used to implement, but is NOT currying.

I don't understand the distinction - would someone explain to me, why
this is not currying?

--
troels


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---

[mochikit] setRequestHeader vs. IE

[troelskn]

I ran into a wierd problem with XmlHttpRequest. It seems that IE for
some reason lowercases the key of custom headers (such as
X-Ajax-Engine) set with setRequestHeader().
Is this a known error of IE, or does the problem come from mochikit ?


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] forEach

[troelskn]

prototype's implementation of Array.prototype.each corresponds to
mochikits Iter.forEach. While I was porting a script from prototype to
mochikit, I had some trouble because, each() pass the key of the
iterable as second argument, while forEach() doesn't. For the sake of
compatibility, perhaps it was a good idea to let forEach pass the same
second argument ?


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] MochiKit.Async

[troelskn]

I think I mentioned it before, but here I go again:

In MochiKit.Async line 442 :
sendContent = null;
Should be changed to
sendContent = ;
To work in Opera.

Amen.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] Re: MochiKit.Async

[troelskn]

I should investigate better before posting. Turns out that Deferred
already works in synchroneous mode. (Eg. if a callback is added after
it fired, the callback will be triggered)

There's still the issue of http-statuscodes though.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] MochiKit.Async

[troelskn]

I have two observations after doing some work with Async :

Regarding this line in Async.sendXMLHttpRequest :

if (status == 200 || status == 304) { // OK

All statuscodes in the range 200 - 299 should validate to success. Is
there any reason why they aren't atm ?
I'm currently just returning 200 on success, but a PUT would more
acurately have to reply with 201 Created.

Furthermore - During testing, it's convenient to fire all requests in
sync, rather than async mode. For this reason it would be nice if the
Deferred, returned from sendXMLHttpRequest supported this. In
particular, addCallback and it's kind can't be used since the Deferred
is only returned after it has actually been completed. A solution could
be to let the Deferred remember it's state, and fire the handler
immediately when it's attatched. If this conflicts in any way, you
could subclass Deferred as SyncDeferred or similar to provide this
behaviour.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] Re: stopping an event

[troelskn]

Appoligies - it was in the documentation, I just didn't look hard
enough.

Signals triggered by DOM events are called with a custom event object as a 
parameter.
Use customObject.stop() to do the W3C equivalent of stopPropagation and 
preventDefault.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---

[mochikit] Re: Mochikit performance with big Documents

[troelskn]

It could be an extension for ff, that's causing the trouble.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~--~~~~--~~--~--~---