On Nov 21, 2005, at 10:16 AM, Eric Brunson wrote:
Leonardo Soto M. wrote:
I remember reading about someone porting Rico/Scriptaculous to
MochiKit.
What happened? I'd like to be able to contribute if help is
needed, or
use and test it if it's usable now.
The Rico demos are quite impressive, I'd never heard of it until now.
Porting would entail changing the AJAX calls to JSON, right? What
else is involved? I'd be willing to help.
Porting in this case is almost entirely a style issue.. it has
nothing to do with AJAX vs JSON -- MochiKit supports both.
OpenRico and Script.aculo.us both depend on Prototype, and they're
all developed in a certain style that tends to be incompatible with
other libraries because they add methods to built-ins and require
several things to be available in the global namespace. MochiKit and
Dojo Toolkit are developed in a style that is maximally compatible
with other libraries, specifically not making any changes to built-in
prototypes or constructors and making minimal required changes to the
global namespace. MochiKit does, by default, give you a lot of
conveniences in the global namespace but its own code does not depend
on those conveniences being available. Dojo Toolkit doesn't provide
such conveniences. Prototype requires the "conveniences".
I can only really see two particularly good reasons to port OpenRico
and/or Script.aculo.us to MochiKit: smaller code size, and marketing
MochiKit. Since MochiKit is designed to be maximally compatible, you
can just use OpenRico and/or Script.aculo.us in conjunction with it
if you want those effects.
Personally, I wouldn't "port" anything from those libraries... I'd
just write it from scratch. MochiKit encourages an entirely
different style of programming and has a very different base set of
functionality to work from than Prototype.
-bob
