This page is somehow outdated, since it covers the old Bitflux Editor and not the new, completely rewritten one. Please also have a look at our wiki, which has some more up to date information
Which Browser do I need?
You need Mozilla 1.0 or 1.1, not 0.9.x. Download Mozilla 1.0. right here. You can also download Mozilla from the official Mozilla Site.
Microsoft Windows (95,98,ME,NT,2000,XP)
If you are more adventureous, you can also download Mozilla 1.1.
Microsoft Windows (95,98,ME,NT,2000,XP)
Hitting RETURN when in edit mode does not go to a new line. I tried this in more that one place with the same result.
This is a known issue. You should be at the new line, but since it's an empty node, it doesn't render it. If you type something after hitting RETURN, it does render it correctly.
I can place the cursor in the page heading (where search box and links are, and where "Universität Zurich" image is) but it accepts no input.
You just can edit the stuff, which is in the dotted boxes, since only this information is provided with the XML. The rest is defined in the XSLT. In this demo, it doesn't make sense to edit the surrounding, since this is always the same and should not be editable by the Bitflux Editor. However, theoretically it's well possible to make the whole site editable, but since the editor will mostly be used within the CMS I think, not much people want that ;)
If I for example add a table with the editor, this table is not shown in the live page
If some tags are not or differently defined in the xslt-template of the live page, they are shown differently on the webpage. One has to adjust either of both the get the correct behaviour. UPDATE: For the uni-demo, tables and lists should now work.
I want to add some XML-Special chars (like
, ", etc) with the clipboard, but it doesn't work.
If you want to use those special characters, just click on the "Append CDATA" button on the top and write whatever you want between <![CDATA[ and ] ]> . Everything which is between those "tags" will not be interpreted by the xml-processor.
How do I add XHTML Code. For example I have a very complicated XHTML-Table, which I'd like to include in the page.
Just open the clipboard and write or copy&paste your xhtml code into it. Be sure it's really well formed (not just HTML, but XHTML), otherwise you get parsing errors. If your XHTML is not shown on the Live-Page, then the XSLT-Stylesheet of the Live-Page does not interpret XHTML (But it should be done on the Uni Zurich demo page).
You should not use the attributes id and style, as they are changed internally by Bitflux Editor (for the time being, it will be fixed some day).
Most certainly, you don't want to replace linebreaks with paragraphs, if you insert XHTML. Therefore uncheck the box "Add Paras", before you click "Insert".
The Editor complains about wrong Mime/Content-Type. What's this about?
Mozilla needs Content-Type for xml-documents to be set to text/xml. Otherwise it won't parse those files. Make sure your webserver serves files with the endings .xsl/.xml/.xsd as text/xml. In Apache you have to adjust conf/mime.types for this.
With newer versions you need also to make sure, that the content-type for css files is set to text/css.
I use the latest mozilla nightly build and some things don't work.
We can't support Mozilla-nightlies, since they are too much of a moving target (see for example bug http://bugzilla.mozilla.org/show_bug.cgi?id=167786 ) and it's well possible, that some stuff does not work. Use one of the officially released Mozilla builds and it should work. Moreover, as soon as there is a new release, we will try hard to fix the stuff, which does not work anymore.
What about Galeon? Does it work with it?
It works, but Galeon seems not to have a Caret Browsing Mode, so you won't see a cursor.
Why is Mozilla required? Is it because Mozilla is the only browser that supports the standards, or is it because Mozilla has proprietary features that you use?
Mozilla does indeed support the standards very well and we don't use proprietary features of Mozilla (no XUL, no XBL..), except where there are no standards (xslt-transformation within JS, for example).
Or is it just because you only do testing using Mozilla, and don't want to deal with browser compatability issues?
The main point why it's Mozilla only at the moment is because of the cross-plattform availability of Mozilla. One of our main sponsors uses a lot of Apple computers and on a Mac you don't have any other choice than Mozilla for doing something like that. MSIE/Mac 5.2 is very feature-limited compared to MSIE/Win 6 and Mozilla.
Another reason is indeed the amount of work needed to get it running on different browsers. Our resources are very limited right now. But as this is now an open source project now, we hope to get some support from other people and we welcome any contribution.
What about Netscape 6.x ? Or Opera? Or IE 6. These should be pretty close to the more recent W3C standards, right?
MSIE 6 support is planned and it should be possible to port it.
We had Netscape 6.2 support some time ago, but Netscape 6.2 was based on Mozilla 0.9.4 and it changed a lot since then. Mozilla was (and still is to some extend) a moving target concerning JS and DOM support, therefore we dumped support for Mozilla < 1.0 as this was just too much to take care of (especially between 0.9.9 and 1.0 were quite some changes). I think, it would be possible to backport it again, but since Netscape 7.0 is released, i don't know, if this is worth it. Netscape releases < 6.2 will never work, since they don't have xslt-support.
The images button is greyed out, is this functionality not active here, or am I doing something wrong?
For the University of Zurich test site there is no image-upload-function available. This wasn't a requirement at this stage, because we already demonstrated the image function with our own Bitflux CMS. You can see a screenshot of the image function with our own CMS here.
BTW: greyed out buttons are not available.
How do I edit/add text in the Related Content Section
We have the standard template changed a little, so there is already content in the "Related Content" box, if you open a new document. You can then change and add new components as you wish. Deleting of nodes happens as always in the bottom "Quick Element Bar".
The "Related Content" xml is a little bit confusing at the beginning. It looks (for the editor, at the end it is something different again) something like the following:
</NewsComponent>Therefore every NewsComponent has a Role (it's the bold titel), with one or more NewsLines. The NewsLines can contain zero or one HeadLine and zero or one SlugLine. The HeadLine should have also a link (the href attribut, this can be changed on the bottom bar, if you click on the attribute).
If you want to add another NewsComponent (another bold title), then right click somewhere in the old NewsComponent and click on "Insert NewsComponent after NewsComponent". Then you can change the Role (= title) and just hit return after editing it. It will automatically add a headline, which you can edit as well. Hitting Return in the headline should add a SlugLine, so there is no need for using always the mouse. Sometimes you still need it, though :)
The same principle ("right click on a node and add further nodes") goes for everywhere, and if you're not sure, just do it and try what happens. You have always the undo button on the top button bar (or hit CTRL+Z resp Apple+Z), if something went wrong.