It is a bit hard to comment this without seeing the API:s or so.
Personally, I'm not a fan of chained API:s, so other people are sure
to value that more than me. But what would be interesting is a jQuery
compability module, mapping jQuery calls into MochiKit ones. At least
so that some jQuery plug-ins would be usable with MochiKit.
What are the use cases for the proposed MochiKit.Remote module? What
would the API look like? Why isn't the Async module sufficient? (What
is missing in your opinion?)
Cheers,
/Per
On Tue, Sep 2, 2008 at 8:53 AM, Amit Mendapara <[EMAIL PROTECTED]> wrote:
>
> Hello Everyone,
>
> As said before, I'm working on some extension modules for MochiKit.
> Those are..
>
> 1) MochiKit.Query - provides jQuery style DOM manipulation/traversing
> functionality
> 2) MochiKit.Remote - an implementation of MochiKit.Async
> 3) MochiKit.Extensions - extension helpers
>
> The Query module is based on MochiKit.Selector so selector features
> are limited then the jQuery. The Query module provides almost
> identical API to jQuery but using MochiKit. Yes, there are few
> differences also including callback function invocation, event
> handling, effects and some iteration functions.
>
> The MochiKit.Remote module is still under consideration but it will
> provide much better control over the requests, including...
>
> 1) Async/Sync requests
> 2) JavaScript evaluation & JSON
> 3) Queue of Requests
> 5) Global Notifications
>
> The MochiKit.Extensions module provides some helper functions to
> register new Extension modules or classes, taking care of dependencies
> and existing names...
>
> MochiKit.Extensions.registerModule('MochiKit.MyModule', {version: 1.4,
> depends: ['Base', 'Iter']});
>
> Which is similar to MochiKit.Base._deps
>
> MochiKit.Extensions.registerClass('MochiKit.MyClass', {version: 1.4,
> depends: ['Base', 'Iter']});
>
> It will register Class (object) under the MochiKit namespace.
>
> MochiKit.MyClass = function(...) {
> ...
> }
>
> IMHO registering classes to MochiKit namespace will make it truly
> Pythonic ;)
>
> Though, the MochiKit.Query and MochiKit.Extensions modules are almost
> finished, I haven't released the code yet due to some licensing
> issues. It contains some GPL code and portions from jQuery. So I'm
> thinking of releasing the code under MIT + GPL licenses, and thus may
> not get merged with the official MochiKit library but will remain as
> separate project.
>
> Any suggestions are welcome...
>
> 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 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
-~----------~----~----~----~------~----~------~--~---
