Hi there, first of all thanks for the answer!
Godefroid Chapelle wrote: > Pleased you liked it. Indeed :-) > > Unfortunately I miserably failed to use the scriptaculous effects like > > 'fade', 'appear' and all that. I tried it as an server action and as an > > client action as described on the kssproject pages. > > Those pages should state that the code for effects is very > experimental... and outdated. I see. So the script.aculo.us code currently contained in kss.core will go away as well? > I do not know of anyone having done any work for effects. I saw Balazs > proposed that as a topic for Plone Conference sprint. > > IOW, if you wait a few weeks, code could be available. Too long ;-) I tried to write a little plugin myself just to support some basic effects. It turned out to be quite simple and worked like a charm, although I am sure, that some real JavaScript gurus could improve it a lot (and there was nothing complicated to implement ;-). I'd now like to share the code with others and publish it in some repository. Two problems have to be solved before: (1) I need a better name. Currently the package is called kss.plugin.effects, which is not very specific nor does it express, that the package is currently for Zope 3 (Grok to be more specific) only. It depends on `megrok.kss`. For use with Zope 2 (Plone 3) possibly only some minor modification would be necessary, for use with django or other frameworks, probably much more changes would be needed (but django already has some srcipt.aculo.us-KSS integration, right?). So at least `megrok`, `zope` or `z3c` should appear in the package name. Maybe `megrok.kss.scriptaculous`? That's pretty long, but, well... (2) To put that package into the Zope repository is not possible because it includes current versions of the script.aculo.us libs, which are BSD-licensed. No problem for me, but a problem for the Zope repository, that explicitly accepts only self-written, ZPL-licensed code. Possibly this could become the first external megrok-package? The code runs, by the way, much faster than the older script.aculo.us scripts currently shipped with `kss.core`. > > Is this still true? Could I help to make it Python2.5-ready ? > > Definitely. First by exploring what is wrong ;-) Until now I found no Python2.5 blockers :-) > Second by changing the constructs if you do not need our help. > > Do you have codespeak access ? No, but for megrok.kss.scriptaculous it might help. How can one gain access? Best regards, -- Uli
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Kss-devel mailing list Kss-devel@codespeak.net http://codespeak.net/mailman/listinfo/kss-devel
