The Django ecosystem is almost entirely made up of BSD/MIT licensed software. My guess is that licensing this as LGPL is going to hurt its adoption.<p>Jacob Kaplan-Moss has a good talk on licensing here, <a href="http://www.youtube.com/watch?v=vhuF0oalOi8" rel="nofollow">http://www.youtube.com/watch?v=vhuF0oalOi8</a>
I've implemented this kind of thing in Django before, and I found that the problem I have with inline editing in general is one of affordance. Like the example in the video, if there are no controls, you have to be already familiar with the site to know that text is editable. 'Hover-over' affordance isn't really acceptable, because you won't move your mouse there unless you already have a reason to, and a user shouldn't be required to 'scan' the page with the mouse to find out which bits are reactive.<p>On the other hand, having "edit" links or buttons next to every field really litters up the page.<p>Has anybody written about good solutions to this?
Neat! It might be interesting to have a tag for 'replace-with-edited-text-if-available'. (This falls somewhere between the editable-model-fields and alternate-translations cases.) For example:<p><pre><code> {% replaceable %}
<h1>Hello</h1>
<p>This text might not appear, <i>if</i> it
is ever edited-in-place.</p>
{% endreplaceable %}
</code></pre>
When edited, the module would derive a deterministic unique key for the modified HTML and store in the database. Future redisplays would use the edited text. (Optional parameters might help control how the unique key is derived, from either actual access URI or template name, to affect the range of pages over which one edited-replacement-text appears.)
Hi all,<p>I am the main developer to django-inplaceedit.<p>I encourage you to collaborate with this egg, the last releases have been thanks to the community, and for me this is very nice:<p><a href="https://github.com/Yaco-Sistemas/django-inplaceedit/blob/master/CHANGES.rst" rel="nofollow">https://github.com/Yaco-Sistemas/django-inplaceedit/blob/mas...</a><p>Best regards,
Nice for those who like it, but I never liked "edit on the fly" on a CMS.<p>Except if it was an additional method, for quick edits, corrections etc. Else, it artificially restricts tons of stuff that could be done in a proper admin interface.