Hi,<br><br>I would like to help on this. I never used none of: <br><br>- TinyMCE<br>- hurry.*<br>- megrok.form<br><br>So, I need to find some time to learn how to use those tools, is there any time limit to fix all this? I think that 2 weeks from now, I will be able to show some progress. If you are looking for something faster, I think that I'm not the best to do it<br>
<br>Best Regards<br><br><div class="gmail_quote">On Fri, Apr 17, 2009 at 12:47 PM, Martijn Faassen <span dir="ltr"><<a href="mailto:faassen@startifact.com">faassen@startifact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi there,<br>
<br>
The problem:<br>
<br>
megrok.form depends on z3c.widget, which only exists in older releases<br>
on pypi. Newer releases exist in the evilll <a href="http://download.zope.org/distribution" target="_blank">download.zope.org/distribution</a>.<br>
<br>
Worse yet, z3c.javascript is a dependency of z3c.widget, and<br>
z3c.javascript only got released in the aforementioned place of evilll,<br>
not on pypi.<br>
<br>
One way to resolve this mess is to release newer versions, but we don't<br>
have the pypi access for z3c.widget. And Behrang Dadsetan wisely pointed<br>
out that z3c.javascript contains an absolute pile of random javascript<br>
libraries of various license provencance: not a nice thing to depend on.<br>
<br>
Some analysis of megrok.form was in order. The conclusions:<br>
<br>
z3c.widget only seems to be used in megrok.form in a very minimal way.<br>
It hooks up the HTML field (defined by megrok.form.interfaces) to<br>
z3c.widget.tiny.widget.TinyWidget, a rich text editing widget.<br>
Undoubtedly given the name this uses tinymce, which in turn is in<br>
z3c.javascript.<br>
<br>
Now as to the Plan, which only needs some brave hacker to execute it:<br>
<br>
* drop the dependency on z3c.widget in megrok.form<br>
<br>
* Copy the code from z3c.widget.tiny into megrok.form. Only the code we<br>
actually use, and perhaps some tests.<br>
<br>
* rearrange the ZCML so it will use that.<br>
<br>
We're still stuck with the dependency on TinyMCE. One way to deal with<br>
this is to use hurry.tinymce instead.<br>
<br>
Before this is done we'd probably need to merge the rather superfluous<br>
hurry.zopetinymce (only a configure.zcml) into it for easier management,<br>
but you could make it work by depending on hurry.zopetinymce instead today.<br>
<br>
Then you can do hurry.tinymce.tinymce.need() in the widget and get<br>
tinymce that way instead.<br>
<br>
megrok.form will gain a dependency on hurry.resource and<br>
hurry.zoperesource, but that is hardly a disaster, especially since<br>
z3c.widget and z3c.javascript (which is a minor licensing disaster) will<br>
go away.<br>
<br>
Any takers?<br>
<br>
Regards,<br>
<br>
Martijn<br>
<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Santiago Videla<br><a href="http://www.revolucionesweb.com.ar">www.revolucionesweb.com.ar</a><br><a href="http://www.linkedin.com/in/svidela">http://www.linkedin.com/in/svidela</a><br>
<br>Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el pensamiento que se hace corazón resplandece con la palabra sencilla y humilde que l@s tod@s somos.<br>