I am OK with any Javascript library which is small but also handles all of our 
needs.

It needs to help manage events, handle drag/drop and also offer a few effects 
to produce a modern web UI.

And it definitely needs to have online documentation which we can use.

What we need to do is come up with a list of requirements for a Javascript 
library and then we can evaluate each available library to see which ones fill 
the requirements.  I still like the Dean Edwards event library.  It is small 
and just handles the cross-browser events API.  It has not effects or 
drag/drop, but will allow us to reliably attach our custom behavior.

http://brennan.offwhite.net/rcdev/scripts/events.js

Sam,

As you work through your list of hooks for the plugin, could you maintain a 
list of potential requirements for the Javascript library?

Brennan

On Thu, 18 Jan 2007 4:04:48 -0600, Gnative <[EMAIL PROTECTED]> wrote:
> 
> I agree with scriptolicious being a big library for the roundcube project.
> There would be so many redundant functionality in the library that we just
> dont need.
> I would suggest looking at either of
> 
> 1. moo.fx - http://moofx.mad4milk.net/
> 2. jqeury  - http://jquery.com/
> 
> for a small, documented and cross browser solutions to use. Both compress
> down to under 20k and looking at RC's javascript this is posible to get
> down to this size or under with the existing JS.
> 
> They both use a javascript compression
> http://www.phpclasses.org/browse/package/3158.html system developed by
> Andrea Giammarchi.
> Which i think sould maybe be considered as an addition to the core of
> Roundcube. When a plugin is newly activated in the roundcube enviroment the
> compressor is called to create one compress Js file.
> 
> Other advantages of useing these libraries are an already strong team of
> developers working toward a clean javascript library and documented
> functions.
> 
> Shane
> 
> 
> 
> 
> On Thu, 18 Jan 2007 10:12:20 +0100, Mathieu Lecarme
> <[EMAIL PROTECTED]> wrote:
>>
>>>>
>>> May we should start a list of event handlers/wrappers. Obviously there
>>> will be a lot of them, but maybe try and get the basics down. Then we
>>> can try to get them interacting together safely.
>> Have a look of dotclear website, the plugin architecture is small and
>> nice.
>> You have to manage event, but also preference panel, persistance, and
>> little thing like i18n, icon, and templating (with widgets).
>>
>>>
>>> I haven't used JSON before, only AJAX requests, so I'll be off to
>>> learn how it all works. Don't worry about the stylesheet, as long as
>>> it is functional that is all we need for the moment.
>> JSON is just a serialization, with a javascript syntax. From javascript
>> you use it like ajax, with a callback, but without XML parsing.
>>
>> M.
> ----------------------------------------------------------------------------
> Variety is the spice of life .. except in Thailand where the spice
> makes your life slip out your arsehole.
> ----------------------------------------------------------------------------
-- 
Brennan Stehling
Offwhite.net LLC
[EMAIL PROTECTED]



Reply via email to