[kupu-dev] Extending Kupu to edit XML in another namespaces

[Roché Compaan]

Xopus doesn't seem to be open source and the fact that bitflux doesn't
work with IE takes it out of consideration.

Do you know what javascript library and what function in Kupu is
responsible for stripping away non-HTML tags? 

-- 
Roché Compaan
Upfront Systems                   http://www.upfrontsystems.co.za

On Wed, 2009-06-24 at 07:15 -0500, Andy Altepeter wrote:
> I don't know about javascript restrictions, but I know that http://xopus.com 
> is an in-browser wysiwyg xml editor.  Check out the demos -- they're xml (not 
> html) and pretty sweet.
> 
> Andy
> 
> On Wednesday 24 June 2009 01:47:53 am Johnny deBris wrote:
> > Roché Compaan wrote:
> > > Is what we are trying to do feasible, or is Kupu meant to edit HTML
> > > only?
> >
> > I don't think it's feasible, unfortunately the 'contentEditable' editor
> > component on which Kupu is based isn't very flexible, and to make
> > matters worse non-HTML parts of the DOM are not accessible from
> > JavaScript. I think if you want to write a 'proper' XML editor in
> > JavaScript, you will want to avoid the contentEditable component,
> > perhaps by implementing your own cursor and editable area (though that
> > won't be easy), or perhaps by using some of Mozilla/Firefox's XML
> > editing support, which as far as I understood is a lot more flexible...
> >
> > You might want to take a look at the Bitflux editor
> > (http://bitfluxeditor.org/), an XML editor written in JavaScript that
> > doesn't use contentEditable, perhaps you can use it as-is, else it might
> > provide you with some clues.
> >
> > Cheers,
> >
> > Guido
> > _______________________________________________
> > kupu-dev mailing list
> > kupu-dev at codespeak.net
> > http://codespeak.net/mailman/listinfo/kupu-dev
> 
>