Florent André schrieb:
On Mon, 23 Mar 2009 10:53:52 +0100, Andreas Hartmann <[email protected]>
wrote:
Florent André schrieb:
On Fri, 20 Mar 2009 11:22:01 +0100, Andreas Hartmann
<[email protected]>
wrote:
Hi André,
Florent André schrieb:
On Thu, 19 Mar 2009 16:40:44 +0100,
[...]
When I speak about sitemap and xslt editing, I think to bespin (this
mail
:
http://lenya.markmail.org/search/?q=bespin#query:bespin+page:1+mid:eaukjoacfewagi34+state:results)
In this context, when I said "in-place", I would like to say : edit a
module's sitemap and xslt directly on the web (on the lenya site) - and
your ajax module can do that if I well understand...
When you put your sitemaps and XSLTs in the Lenya repository, you can
use e.g. the source editor to edit them. After all they are just XML
documents. You need a schema, though. But I agree that Bespin would
certainly be more comfortable than the editors we have now. The AJAX
editor I mentioned is rather suited for documents, since you can only
edit a single section (paragraph etc.) at a time.
This editor sounds good ! What is the "dev status" of this editor :
experimental, little buggy, usable ? It's possible to put it in the
contribution branch ?
ATM it's experimental, but maybe I can add it to the contribution branch
(if I can isolate it from the rest of the code).
I have a more global question about editors in lenya :
Why editors open in a new page and not in the "site template" (editable
area with the navigation tree, the top and bottom of the site,...) ? This
is a development choice or an architectural constraint ?
Regarding the WYSIWYG editors, this is not our choice – it's is just how
those editors work. BTW, TinyMCE is embedded in the page, i.e. only the
content area is changed into a rich-text editor. I think for the source
editor it wouldn't make much sense to embed the editing area in the
page, and using an otherwise empty page allows a better performance.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
