[Kss-devel] drag & drop

[Balazs Ree]

On Mon, 23 Jul 2007 09:52:25 +0200 Duco Dokter wrote:

> Is there a list of features that a drag & drop implementation should
> provide? Or a general description of this? For instance to list all KSS
> attributes that may be set on an element, and what kind of parameters
> they would take. I assume drag & drop would look something like:
> 
> #someElt {
>   allow-drag: True;
>   snap-grid: True;
>   allow-parents: <whatever list>
> }

There is no docs. We need to work together on this.

This would require a deeper knowledge of the kss internals. The current 
drag and drop implementation is one of the most complex plugins we have 
because it operates on internal state and incorporates more kss events 
that need to be bound together (because that's what the underlying 
libraries require.)

We have a working implementation that is based on the prototype/
scriptaculous library, however I did not have time to write a working 
demo for it that would show you how to use evt-xxx parameters to 
parametrize the events. More importantly, the way the js wrapper for kss 
e constructed is sparsely documented. This documentation will be coming 
soon but not right now.

I can only repeat now that at the moment I can give you zero time for 
help, I don't even attempt to show you why the parameters need to be done 
a bit differently then in your example. The plone release and my other 
project work keeps me 100% busy for this week. I would however be more 
then happy to work together with you and give you all the necessary 
support to make a kss binding for the javascript library you use, 
following the next week or after.

The main reason for why this would be a priority, is that it turned out 
that scriptaculous drag and drop is not usable in its current form for 
general application building, because it does not support more 
independent drag and drop "pools" within the same page. Of course we 
could fix that which would practically mean a significant rewrite of the 
scriptaculous code. However this is not an option for us. Not because we 
cannot write the program, but because it is an impossible burden (and 
luxury) to maintain our own javascript code for something that is used in 
every single application on the web. Instead, we prefer to reuse 
libraries that are widely used outside the Plone community too and make 
kss wrapper for them. So replacing scriptaculous with one of jQuery or 
MochiKit or something else is a must.

By the way, which is the library that you reuse in your product? I did 
not remember mentioned it so far.

-- 
Balazs Ree