18 Aug
2008
18 Aug
'08
8:18 p.m.
On Aug 18, 2008, at 8:03 PM, Marius Dumitru Florea wrote:
I have a question: if we use radeox is the new editor going to be
better than the old one?
I think it's not worth doing it. When the old syntax is used there
shouldn't be any way to edit the page using the new WYSIWYG editor
IMO. That will also provide another incentive to move to the new syntax.
However moving to the new syntax is not something so we'll need to
make it as painless as possible.
I think this new wysiwyg + the new rendering may warrant us calling
this XWiki 2.0 when we activate them and make them the default. We
could release 1.6 with these as options only that can enabled in the
configuration. Then release a 2.0 with them enabled by default and
with the old ones as configurable.
WDYT?
Thanks
-Vincent
On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
The new WYSIWYG is not bound to the XWiki 2.0 syntax. I have a
XHTMLConverter component with two implementations at this time: one
(fully
working) using Vincent's new rendering module and one (needing some
adjustments) using the old Radeox engine. I could detect the page
syntax
and lookup the right implementation, but is it worth doing? If not,
how
should I react when the new WYSIWYG is forced on a page with the old
syntax?
+1
I think currently we can only use the new wysiwyg if we have a page
using XWiki 2.0 syntax right ?
yes. >> Jerome Velociter wrote:
>>> +1. I've seen the new WYSIWYG in action and think it would be
>>> great/beneficial to have it experimental in 1.6M1.
>>> What about a parameter in xwiki.cfg to have it always available in
>>> the
>>> "editors" panel, like "New WYSIWYG [experimental]" ?
>>>
>>> Regards,
>>> Jerome.
>>>
>>>
>>>> Hi devs,
>>>>
>>>> I propose to move the new WYSIWYG editor into the platform in
>>>> order to
>>>> have it as an experimental feature for 1.6M1.
>>>>
>>>> The following steps should be taken:
>>>> * Create a platform/web/wysiwyg module to host the code currently
>>>> resided
>>>> in sandbox/wysiwyg
>>>> * Change templates/edit.vm, templates/editpanels.vm and create
>>>> templates/editwysiwygnew.vm to make XE aware of the new editor.
>>>> This way
>>>> our users will be able to experiment the new WYSIWYG editor on any
>>>> page,
>>>> by having editor=wysiwygnew in the edit URL.
>>>> * Change platform/web/pom/xml and enterprise/web/pom.xml
>>>>
>>>> Here's my +1
>>>> Marius