Re: Edit XHTML Files?

On 6.6.2004 13:30 Uhr, Ulrich Fischer wrote:

> 
> Hi Cregu,
> 
> oouuh, have written already an answer to my last question.
> 
> Am 04.06.2004 15:52 schrieb Christian Stocker:
> 
>> the content in index.html is just a placeholder and gets replaced as 
>> soon as the editor loaded your xml file, therefore:
>>
>>         <div id="main"
>>             bxe_xpath="/iba/page/Article/main">
> 
> 
> 
> one posibility by the bitflux editor is to write the page,
> which should be edited, in the index.html AND in the content.xml.
> 
> In some case not only for the reason to see something, before the editor
> is loated, but also for the reason, to split editible and not editable
> areas.

right. We split content and layout this way. In the content.xml you 
ideally have the content, which can be edited, in the index.html, you 
have the rest. index.html is (at least in our case) dynamically 
generated and also takes some of the content from content.xml, but stuff 
like navigation and "right column news overview" is taken from something 
different.

> The index.html gives the "wysiwyg-look" and has it own editor-title and
> editor-head and a mixed body with editor tools and the page, which should
> be edited. The content.xml is the real native page, which should be edited.

Also right, but keep in mind, that BXE was never really meant to be 
something like a Dreamweaver replacement. It was always about editing 
content and not layout. Therefore we may use XHTML as format for storing 
the content, but we do not really store the layout in there. For this, 
we at Bitflux, usually use CSS ;)

> The bxe_xpath-areas from content.xml become integrated in the index.html.
> There they can be changed. And after editing they are safed back to the
> native page - or to a CMS data-base.

Exactly.

> Working for a CMS data-base content.xml is not really necessary.
> You can parse your page-content in the index.html. The bxe_xpath-
> attribute marks those areas, which should be editable.

That's not possible with BXE yet. Currently, you need a content.xml. And 
I don't think, we will change that very soon as we personally don't need 
it (except someone else does it, of course ;) ), but it would certainly 
be possible.

If you really want just to edit whole XHTML pages and don't need any XML 
features or RelaxNG Validation, maybe Kupu (kupu.oscom.org) is more 
something for you.

> Sorry for my slow thinking ...

No problem

chregu
-- 
christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich
phone +41 1 240 56 70 | mobile +41 76 561 88 60  | fax +41 1 240 56 71
http://www.bitflux.ch  |  [email protected]  |  gnupg-keyid 0x5CE1DECB
-- 
bx-editor-users mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-users