News on possibility of MSIE support

[Christian Stocker]

Hi

Just to lower the doubts if BXE will ever support a MSIE version:

I had some ideas this weekend, how to get it working within MSIE and
made some tests this morning. The results were very promising and I
still think, BXE can be ported to MSIE(Win..) without having to change
our main idea of the workflow. With an appropriate wrapper, we should be
able to simulate XML-within-HTML quite well enough...

I hope, this will keep your faith with us that BXE will support MSIE
some time in the future. I can't say, when that will be, as I'm now
going back to improve the Mozilla support :)

chregu

[Lon Boonen]

Let me guess.

My guess would be you apply an extra XSLT to the stuff you want to send
to the browser...

This XSLT would have to do the following:
change <xmlnode>...</xmlnode>
into <div class="xmlnode">...</div>

You would then need to translate all CSS also:
from: xmlnode { ...}
into: .xmlnode {... }
and probably add a little 'display:inline;' kind of stuff here and
there.

It might work. But would be another translation you would have to undo
before sending back to the xml. But then... again... it might work.

Am I close with this guess?

groetjes Lon

-------------------------------------------------
Q42: http://www.q42.nl

Xopus: http://xopus.org
Xopus Mailing List: http://groups.yahoo.com/group/xopus

Lime: http://www.q42.nl/products/lime

-----Original Message-----
Christian Stocker
Sent: maandag 14 oktober 2002 12:14
To: BXE Developer List
Subject: [bx-editor-dev] News on possibility of MSIE support
Hi
I had some ideas this weekend, how to get it working within MSIE and
made some tests this morning. The results were very promising and I
still think, BXE can be ported to MSIE(Win..) without having to change
our main idea of the workflow. With an appropriate wrapper,
we should be
able to simulate XML-within-HTML quite well enough...
I hope, this will keep your faith with us that BXE will support MSIE
some time in the future. I can't say, when that will be, as I'm now
going back to improve the Mozilla support :)
chregu
--
bx-editor-dev mailing list
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev

[Christian Stocker]

Hi

Post by Lon Boonen
My guess would be you apply an extra XSLT to the stuff you want to send
to the browser...
change <xmlnode>...</xmlnode>
into <div class="xmlnode">...</div>
from: xmlnode { ...}
into: .xmlnode {... }
and probably add a little 'display:inline;' kind of stuff here and
there.

quite close :) i didn't use xslt, but regular dom stuff, but it could be
done with xslt as well. and instead of div i use span, 'cause this gets
closer to what mozilla does with unknown xml-nodes.

Post by Lon Boonen
It might work. But would be another translation you would have to undo
before sending back to the xml. But then... again... it might work.

i can live with the additional translation :) it doesnt happen that often
(at startup and save), therefore the overhead isn't that grave.

I tested it on my "powerpoint-replacement" (by the way this was just a
half day work in shattuck, without the great intention to make it a
product or something similar :) ) and if i have finished it up, i will
publish it on bitflux.ch/slideml for your inspection.

so long

chregu

[Christian Stocker]

Post by Christian Stocker
done with xslt as well. and instead of div i use span, 'cause
this gets
closer to what mozilla does with unknown xml-nodes.

I wouldn't use span if I were you.
IE has a habit of crashing if you place block-elements inside of
span-elements. So, pressing enter (resulting in a <P>) could potentially
crash it.
Use CSS to turn divs into spans instead. It does not crash if you insert
a P inside a DIV, even if that div is display:inline.

aaah, thanks for the hint, i'll change that then :)

chregu

--=20
christian stocker | bitflux GmbH | sch=F6neggstrasse 5 | ch-8004 zurich
phone [phone] | mobile [phone] | fax [phone]
http://www.bitflux.ch | ***@bitflux.ch | gnupg-keyid 0x5CE1DECB

[Roger Fischer]

I wouldn't use span if I were you.
IE has a habit of crashing if you place block-elements inside of
span-elements. So, pressing enter (resulting in a <P>)

could potentially

crash it.

which is more or less what you could expect if you see the html specs.

btw (to also say once something technical;):
we had once some problems with tables in <p>'s too.
tables in para is valid DocBook, but not very valid html.
this will change in xhtml 2, which is what i am longing for;)

best
roger

--
roger fischer | bitflux GmbH | schöneggstrasse 5 | ch-8004 zürich
tel [phone] | mobil [phone] | fax [phone]
http://www.bitflux.ch | ***@bitflux.ch

OSCOM - Open Source Content Management
http://www.oscom.org

[Lon Boonen]

Post by Roger Fischer
tables in para is valid DocBook, but not very valid html.
this will change in xhtml 2, which is what i am longing for;)

XHTML 2.0 can be yours...

Sjoerd Visscher, our most valued collegue, has made the first XHTML 2.0
implementation for browsers.
It's an XSLT that translates XHTML 2.0 pages to XHTML 1.0.
It works in your browser... IE or Mozilla.

Check it out: http://w3future.com/weblog/gems/xhtml2b.xml

Read the small article about XHTML 2.0 at the bottom of that page.
Also view the code of that page to make sure it's XHTML 2.0.


groetjes Lon

[Roger Fischer]

Thanks Lon
This is cool stuff.
My regards to Sjoerd Visscher. Anyway we use a Docbook subset in our CMS and
transform that stuff to ... whatever;)
What I am longing for is native XHTML 2.0 support in the main browsers.
But the link was well worth it:)
Best
Roger

Post by Lon Boonen

Post by Roger Fischer
tables in para is valid DocBook, but not very valid html.
this will change in xhtml 2, which is what i am longing for;)

XHTML 2.0 can be yours...
Sjoerd Visscher, our most valued collegue, has made the first
XHTML 2.0
implementation for browsers.
It's an XSLT that translates XHTML 2.0 pages to XHTML 1.0.
It works in your browser... IE or Mozilla.
Check it out: http://w3future.com/weblog/gems/xhtml2b.xml
Read the small article about XHTML 2.0 at the bottom of that page.
Also view the code of that page to make sure it's XHTML 2.0.