[kupu-dev] Why disable the text_format select in Plone?

[Jean Lagarde]

I wanted to make the default content type of my AT Content Types other than
HTML. In principle that should have been trivial by editing
atcontenttypes.conf, but Kupu has all sorts of ways to insist on forcing the
content type select input to HTML and then disabling it.

I was able to make Kupu do what I wanted by editing kupuploneinit.js and
contentUsesKupu (I also changed a couple of things in kupu-wysiwyg-support,
but that was not necessary), and it seems to behave pretty much as I would
want, but I wonder why it was decided to make Kupu behave that way in the
first place? Am I missing some dangerous side effect of allowing to go back
and forth between different content types with Kupu enabled? I can't see why
the behavior would be worse than when not having Kupu selected as one's
editor, or when using a browser that does not support it (in both of which
cases one can freely go back and forth between different types using the
select control).

Cheers,

Jean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codespeak.net/pipermail/kupu-dev/attachments/20061228/f0f41d16/attachment.htm