architecture of BXE

[Sandro Zic]

Hi!

I thought about the general concept of the BXE architecture and came up with the following conclusions. Plase consider them as "unbound fresh thinking" which might be wrong, hillarious, stupid, not down to earth, etc. :)

1) native XML vocabulary

Thinking of BXE as a XML WISIWYG editor made me think about parallels between BXE and OpenOffice. Considering the OpenOffice XML vocabulary, this office suit is also a XML WISIWYG editor.

Why does BXE not clone the concept of OpenOffice? This means, why does BXE try to support different XML input vocabularies internally instead of defining and working only with it's own internal XML, just like OpenOffice does with OpenOfficeXML? Shouldn't BXE support its own XML only, so that developers now, they have to translate other XML vocabularies (e.g. OpenOffice XML) to BXE XML if they want to use BXE to edit the XML document?

2) XSLT templates

Having said the above, it would be consequent to provide a default XSLT template for the BXE XML vocabulary - simmilar to the use of XSLT in OpenOffice as the formatting engine. The XSLT would transform the BXE XML to HTML displayed in Mozilla. This way, XML nodes do not have to be presented in in the same sequence as they occure in the DOM representation - would be useful e.g. for footnotes stored somewhere in the middle of the XML, but displayed at the bottom of the HTML page.

3) CSS

CSS would be used to format the HTML created by the XSLT stylesheet.


To sum up, BXE would do the following:

a) get the BXE XML document the user provided
b) transform the BXE XML document to HTML with the XSLT
c) format the HTML with CSS

Does that make sense? Is it useful? Should/can it be done?

Sandro
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13

[Christian Stocker]

Hi Sandro

I thought a lot about your proposal, but I don't think it's the final
solution for BXE. I think, you loose a lot with something like that and
I'm not sure, if it then would be possible to do something like our
demo, which has some very special XML elements (relatedcontent et al.)

BUT, it could be an idea for some kind of a subproduct, let's say, if
you provide BXE-XML (DocBook anyone?) to the Editor, you don't have to
do your own schema and customization (except maybe for the CSS, if you
want a different look), 'cause BXE knows "natively" how to handle such a
document.

To sum up, I think, BXE should be able to handle "all" possible
XML-formats, but there is certainly room for something like that.

What do others think about that?

chregu

Post by Sandro Zic
Hi!
I thought about the general concept of the BXE architecture and came up with the following conclusions. Plase consider them as "unbound fresh thinking" which might be wrong, hillarious, stupid, not down to earth, etc. :)
1) native XML vocabulary
Thinking of BXE as a XML WISIWYG editor made me think about parallels between BXE and OpenOffice. Considering the OpenOffice XML vocabulary, this office suit is also a XML WISIWYG editor.
Why does BXE not clone the concept of OpenOffice? This means, why does BXE try to support different XML input vocabularies internally instead of defining and working only with it's own internal XML, just like OpenOffice does with OpenOfficeXML? Shouldn't BXE support its own XML only, so that developers now, they have to translate other XML vocabularies (e.g. OpenOffice XML) to BXE XML if they want to use BXE to edit the XML document?
2) XSLT templates
Having said the above, it would be consequent to provide a default XSLT template for the BXE XML vocabulary - simmilar to the use of XSLT in OpenOffice as the formatting engine. The XSLT would transform the BXE XML to HTML displayed in Mozilla. This way, XML nodes do not have to be presented in in the same sequence as they occure in the DOM representation - would be useful e.g. for footnotes stored somewhere in the middle of the XML, but displayed at the bottom of the HTML page.
3) CSS
CSS would be used to format the HTML created by the XSLT stylesheet.
a) get the BXE XML document the user provided
b) transform the BXE XML document to HTML with the XSLT
c) format the HTML with CSS
Does that make sense? Is it useful? Should/can it be done?
Sandro
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
--
bx-editor-dev mailing list
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev