for the record (as a framework team member) i'd like to support martin
on this issue.
the formlib wysiwyg support is a *new* feature, and if it happens to
*not* work for fckeditor, eventhough wysiwg support used to work for
kupu *and* fckeditor prior to formlib, then that's (understandably)
unfortunate, but IMHO no show stopper. i appreciate martin's
willingness to look into that matter, but by no means would let that
influence/diminish my support for plip 200 per se.
just my $0.02, hope this doesn't sound too formal, but i just happen
to disagree with wiggy's assesment that 'something that worked in 3.0
is about to break in 3.1'.
tom
On 15.01.2008, at 23:41, Martin Aspeli wrote:
Wichert Akkerman wrote:
Previously Raphael Ritz wrote:
Martin Aspeli wrote:
Ho ho ho,
I'd like to officially submit for consideration for Plone 3.1 a
bundle that comprises the following PLIPs (in separate packages):
- PLIP 184 - additional portlets (has a dependency on PLIP 200)
- PLIP 200 - Kupu formlib widget
Hi Martin,
just playing with this I noticed the following:
If I install FCKeditor, select this as my personal
preference (under WYSIWYG editor) and then try
to create or edit a static portlet I get the attached
traceback.
I know it's borderline and I don't know how popular
FCKeditor is but so far it's been OK to offer and use
them both on a site.
It is not borderline: we can't break things in 3.1 that work in Plone
3.0.
This isn't breaking anything that worked in 3.0 - it just means that
a new 3.1 feature (formlib wysiwyg editor) won't work with a
particular third-party product installed and enabled.
Of course, it should be fixed, but it may be that the fix needs to
go into FCKeditor if it's doing something non-kosher; alternatively,
we may need to build a bit more safety into the 3.1 feature to deal
with a special case for FCKeditor.
I don't think I can do anything to fix before the Planning Summit
(after the submission deadline), but I also don't see why that
should matter. If someone else who actually uses FCKeditor has some
time to look at it, I suspect it'll be a simple fix.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
_______________________________________________
Framework-Team mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/framework-team
