> > > MochiKit.Async > > MochiKit.Cookie -- new module in [trac] > > MochiKit.Ajax -- new module in [me], names not exported (so no collisions) > > I never liked that the XmlHttpRequest stuff was in Async. I also > dislike the name Ajax as it is imprecise and has become very > overloaded. I suggest trimming Async down to just the generic > mechanisms of deferreds etc. and creating a new module, called HTTP. > This module would contain the XmlHttpRequest wrappers (relying on > Async of course), utilities for url-encoding, dealing with HTTP > headers and cookies. >
I agree, the signal names should be renamed something like `httpStart, httpStop, httpSuccess, httpError` for `ajaxStart, ajaxStop, ajaxSuccess, ajaxError` respectively. Also, I think it's not good to expose the names globally, so MochiKit.HTTP.get(...) MochiKit.HTTP.post(...) MochiKit.HTTP.JSON.get(...) MochiKit.HTTP.JSON.post(...) MochiKit.HTTP.Cookie.get(...) MochiKit.HTTP.Cookie.set(...) MochiKit.HTTP.Cookie.del(...) and so on... would be nice. > > MochiKit.Query -- new module in [me] > > -- I won't document this module here, but it seems (mostly?) API > > compatible with jQuery. It uses MochiKit to implement (part of) that > > API. > > I'm not entirely convinced this fits in MochiKit. Why not just use jQuery? > May be, but I think I have said about this in my previous response why people like me don't like to mix them up... Regards -- Amit Mendapara --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
