Hi
a word from Bitflux :)
Further developement of Bitflux Editor (aka BXE) is currently a little
bit stalled, since we are very involved in some other projects. But we
hope to do some new stuff in December and solving all the misterious
problems and flaws Felix certainly has also encountered.
We will try to set BXE to some new codebase, which should make stuff
easier, have more features and which will hopefully lead some day to a
MSIE version as well. We keep you updated.
For the wyonacms mailling list subscribers: if you are interested in BXE
developement and the discussion around it, subscribe to our mailing list
at http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
nice weekend
chregu
On Fri, 2002-11-22 at 16:22, Felix Maeder wrote:
> Hi Hendrik,
>
> The Bifluxeditor is working with Wyona, it is implemented in the
> unipublic sample publication. You can have a look at it in your own
> installation or on our demo site:
> http://demo.wyona.org
>
> Bitfluxeditor currently is implemented for the articles and the dossiers
> of unipublic (where Xopus is not working at the moment). Dossiers are a
> bit simpler and therefore maybe a better starting point (e.g.
> /wyona-cms/unipublic/authoring/dossiers/2002/ada/index.html).
>
> Look at the documentation at:
> http://demo.wyona.org:8080/wyona-cms/docs/xdocs/bitflux.html
>
> You have to provide bitfluxeditor with the following files:
> - xml: your xml data
> - xsl: the xslt that bitflux uses to display the page and to define what
> sections are editable. You will have to adapt the xslt(s) your are using
> to display the page in order to define what can be edited (and e.g.
> there's no support for xslt variables). If you have a complex page where
> only a section needs to be edited it is the easiest way to use the xhtml
> of the page (generated dynamically by cocoon) and add the stylesheet
> specific stuff and the code needed for editing through a xslt. I am
> doing this for the frontpage of unipublic right now and it will be in
> the cvs in a couple of days.
> - xsd: the bitflux-specific schema that basically tells the editor what
> elements exist and where which elements can be inserted.
> - css: here you define how the xml elements that are editable get
> displayed in the editor: you assign a style to every xml element. That's
> because it is the xml itself that is displayed and edited in the
> browser, and the styles define the look of the elements.
>
> Recommendation: Because neither the xsd nor the css is
> "context-sensitive" (head/title, document/title, block/title are treated
> all the same) you save a lot of hassle if you use unique element names.
>
> Good luck!
>
> Felix
>
>
>
>
> Hendrik Bunke wrote:
>
> > What about the Bitflux-Editor? I was trying to use
> > it some weeks ago, it didn't work for me with Wyona. Don't know
> > what the problem was (i focused on Xopus then), but on bitflux's
> > website it looks quite promising.
>
>
> _______________________________________________
> WyonaCMS-users mailing list
> WyonaCMS-users@xxxxxxxxx
> http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-users
--
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 | chregu@xxxxxxxxxx | gnupg-keyid 0x5CE1DECB
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
| 
