[Kss-devel] will megrok.kss ever go "live"?

[Balazs Ree]

On Tue, 08 Apr 2008 14:15:23 +0200, Godefroid Chapelle wrote:

> Brandon Craig Rhodes wrote:
>> Godefroid Chapelle <gotcha at bubblenet.be>
>> writes:
>> 
>>> Brandon Craig Rhodes wrote:
>>>> By the way: my examples would look much nicer if I could call jQuery
>>>> animation actions in addition to the plain-old KSS actions.
>>>>
>>> There are no effects module for now.  This is definitely sthing that
>>> we should add asap. We need to improve the sexyness ;-) ...  The
>>> biggest problem is to decide which library to use.
>> 
>> I don't think you should decide on one library, and then make KSS even
>> larger by adding native support for that one library.  Instead, keep
>> kss.core as small as possible, and add a kss.jquery, kss.mochikit,
>> kss.dojo, and so forth, as users need them.  That way, a user who is
>> going to need to do a few complicated things in raw JavaScript, but who
>> wants to adopt KSS for all of the other actions on his web page, gets
>> to choose which Javascript library gets pulled in.
> 
> Makes sense, I like the idea.
> 
> However, I think it would be nice for KSS to have a single way of
> expressing effects through various libraries even if their
> implementation differ because of underlying libraries
> 


I second Godefroid. At present, there is an express interest in making 
the effects work with at least two libraries: Yahoo UI and jQuery. I 
believe both plugins should be done in the way choosen freely by the 
implementor.

As a second step - only after we have more working implementations - we 
should look at the two implementations and come up with a unified action 
set from kss. That way an application should not be aware if an effect is 
implemented with one or the other library. Naturally, some library can 
offer more effects or more parameters with a given effect.

For package name I would propose not kss.jquery but some name under the 
plugin namespace that tells that this implements the effects. Like:
"kss.plugins.jquery_effects"

For the action namespace, I would propose to use something like: jqeffects

Naturally, you are free to choose your own way, beyond these suggestions.
 

-- 
Balazs Ree