Hi Jörn,
thanks for your ideas!
Joern Nettingsmeier schrieb:
[...]
> moreover, we would need to change image references
from
> lenya-document:... to some valid local file link before
passing them to
> the editor, so that it can do proper wysiwyg, and
change them back upon
> saving. which can be a little tricky.
This already happens for BXE and Kupu (for internal links
and images).
[...]
> andreas, where should the actual saving be implemented?
my gut feeling
> says that our editor code should just throw an xml tree
somewhere and
> not be concerned with file operations or streams.
What do you mean with "throw somewhere"?
> but which lenya
> component should handle that xml tree and store it? i'm
not too familiar
> with the DAV upload handler - can we simply use it for
all editors?
I guess WebDAV would be the easiest and a quite generic
way.
The major problem is the different behaviour of the
editors,
and the large amount of customization.
I guess the Neutron protocol (http://neutron.wyona.org/) is the most
promising step in this direction, but of course it depends
on the
acceptance by editor vendors.
-- Andreas
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe lenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org
|