I made a limited hack into the wyisiwyg.js to add a toggle button to the buttonbar. I also had to replace the <div contentEdit="true"> fields by <iframe/>'s to make it work. The Wysiwyg fields are all rendered client side by Javascript/DHTML. This was probably done because clientside browser version checks are more easy (Wysiswyg editing only works on IE >=5.0).
Imho, a more solid solution would be to adjust the wizard.xsl, detect browser version from the request object, and render the <iframes> from there for the ftype="html" fields. This would make life easier and the integration of scripts like htmlArea could be done more cleanly this way. The toggle button also obsoletes the need for a Wordfilter. Toggling the field to SOURCE modus before pasting from Word prevents unwanted HTML tags to be pasted in. I will provide the adjusted wysiwyg.js when it becomes stable. > Clarinus Rietberg <[EMAIL PROTECTED]> wrote: > > Bart de Man wrote: > > > If you need a more "advanced" Html WYSIWYG editor for your content > > editors, > > > you might consider using the eWebEditPro WYSIWYG editor > > >(http://www.ektron.com/ewebeditpro.cfm). We have > integrated it with MMBase > > > for one of our projects, and it works really fine. > > > > > > And there IS a HTML/TEXT toggle button... One disadvantage: it's a > > commercial > > > product (though not *that* expensive). > > > > We have recently implemented htmlArea WYSIWYG Editor in a project. > > It's simple, powerful, has HTML/Text toggle AND BEST OF ALL > ITS FREE. > > Look at: http://www.interactivetools.com/products/htmlarea/ > > Looks cool, and works in mozilla. So much for seperation of > content and > style, but I think this would still be appreciated. Perhaps > somebody can > build it in the editwizards, to replace the current thing? > > > Michiel > > > -- > Michiel Meeuwissen > Mediapark C101 Hilversum > +31 (0)35 6772979 > nl_NL, eo, en_US > mihxil' > []() > >
