Andreas Hartmann wrote:
But how should we determine whether to add the bxe_xpath attribute
without using the rendertype parameter? The BXE-editable areas depend
on the resource type.
currently we do not provide support for multiple editable areas by
default. to do that in an editor-agnostic way, we could alter our
storage format to allow multiple "body" sections or add a "collection"
type document that aggregates multiple single editable sections, which
would be plain xhtml doctypes. this needs careful consideration. but it
does not have any implications to removing the rendertype parameter iiuc
(see below).
Maybe we can add the bxe_xpath attributes by
default and filter them out for the view mode in a single place,
preferrably in the bxe module?
-1. as a tinymce fan, i absolutely do not care about spurious hacks for
other editors in my data :)
if we use pipeline usecase views for bxe (like tinymce does), doing some
preprocessing to add bxe requirements is trivial. since it happens in
src/modules/bxe/sitemap.xmap, SoC is honored and doctype modules can be
editor-agnostic.
if people want to use bxe's capabilities to edit and render arbitrary
xml doctypes, they will perhaps have to introduce a new module that does
indeed have bxe specifics in it, but for generic xhtml, it is not necessary.
i'd like to file this issue as a "critical" bug for 1.4.1. wdyt?
We should definitely think about this issue, but I don't think it is
critical.
it's an architectural ball-and-chain we should get rid of, and i chose
"critical" to make it visible on the radar, but i agree stuff such as
this is still somewhat cosmetic in the short term and should not delay
any releases.
--
Jörn Nettingsmeier
Kurt is up in heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
