18 Aug
2008
18 Aug
'08
12:09 p.m.
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
18 Aug
18 Aug
12:18 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
On Aug 18, 2008, at 12:09 PM, Marius Dumitru Florea wrote:
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
+1 we should leave the old editor as default and make the new one
available with a config option.
Thanks
-Vincent
12:23 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Marius Dumitru Florea wrote:
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
+1
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:23 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
On Mon, Aug 18, 2008 at 12:09 PM, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
12:25 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
On Mon, Aug 18, 2008 at 3:39 PM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
1:07 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
Marius Dumitru Florea wrote:
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
--
Artem Melentyev
4:34 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:56 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
I'm eager to discover this :)
On Mon, Aug 18, 2008 at 4:34 PM, Jerome Velociter <jerome(a)xwiki.com> 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:54 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
I think currently we can only use the new wysiwyg if we have a page
using XWiki 2.0 syntax right ?
Ludovic
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.
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
6:03 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
+1
I think currently we can only use the new wysiwyg if we have a page
using XWiki 2.0 syntax right ?
yes.
-Vincent
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
8:03 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
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?
Thanks,
Marius
+1
I think currently we can only use the new wysiwyg if we have a page
using XWiki 2.0 syntax right ?
yes.
-Vincent
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8:18 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
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
19 Aug
19 Aug
2:54 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
On Aug 18, 2008, at 8:18 PM, Vincent Massol wrote:
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.
BTW we have the question for the office converter. It's converting
HTML to wiki syntax using the new rendering and thus we get new syntax
only.
We really need to decide what we want. Any comment on my previous email?
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. 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
>>> 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
3:58 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Vincent Massol wrote:
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
On Aug 18, 2008, at 8:18 PM, Vincent Massol wrote:
> On Aug 18, 2008, at 8:03 PM, Marius Dumitru Florea wrote:
>
>
>>> On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
>>>
>>>
>>>> +1
>>>>
>>>> I think currently we can only use the new wysiwyg if we have a page
>>>> using XWiki 2.0 syntax right ?
>>>>
>>> yes.
>>>
>> 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?
>>
> 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.
>
ok for me if we have a button "convert to XWiki 2.0"
BTW we have the question for the office converter. It's converting
HTML to wiki syntax using the new rendering and thus we get new syntax
only.
We really need to decide what we want. Any comment on my previous email?
Thanks
-Vincent
> However moving to the new syntax is not something so we'll need to
> make it as painless as possible.
>
>
Yes I think we need a button when a page is in xwiki syntax 1.0 to do
"convert to XWiki 2.0 syntax"
> 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.
>
>
I agree +1
WDYT?
Thanks
-Vincent
>>> 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
>>>>>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4:08 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
On Aug 19, 2008, at 3:58 PM, Ludovic Dubost wrote:
We can do some conversions relatively easily but others are hard...
but even the easy one are hard. For example transforming [link] into
[[link]] sound trivial but it's not. we need to ensure for example
that the [] is not inside a <script> element since it could be an
array in javascript. However it's also possible that this script is
expecting velocity to be executed on it and it contains some real
links in wiki syntax...
So the best we can do is propose something but the user will have to
review and edit it before saving it.
I'm worried how much time we'll have to spend on this. It's easy to do
some quick things but once we have this conversion button we'll get
lots of complaints if we don't do it right...
Right now we need to put all our energy in having the new rendering
fully work for all cases and there's nobody working on the conversion.
It would be nice if someone else (maybe a contributor. Come on, this
is a call for help, come forward! :)) could join us and start working
on this right now.
BTW I've started documenting conversions here:
http://dev.xwiki.org/xwiki/bin/view/Drafts/XWikiSyntax20
Thanks
-Vincent
Vincent Massol wrote:
This is a big amount of work and it won't be perfect for sure.
Actually it'll probably be very far from perfect.
On Aug 18, 2008, at 8:18 PM, Vincent Massol
wrote:
> On Aug 18, 2008, at 8:03 PM, Marius Dumitru Florea wrote:
>
>
>>> On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
>>>
>>>
>>>> +1
>>>>
>>>> I think currently we can only use the new wysiwyg if we have a
>>>> page
>>>> using XWiki 2.0 syntax right ?
>>>>
>>> yes.
>>>
>> 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?
>>
> 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.
>
ok for me if we have a button "convert to XWiki 2.0" BTW we have
the question for the office converter. It's converting
HTML to wiki syntax using the new rendering and thus we get new
syntax
only.
We really need to decide what we want. Any comment on my previous
email?
Thanks
-Vincent
> However moving to the new syntax is not something so we'll need to
> make it as painless as possible.
>
>
Yes I think we need a button when a page is in xwiki syntax 1.0 to do
"convert to XWiki 2.0 syntax" > 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.
>
>
I agree +1
>> WDYT?
>>
>> Thanks
>> -Vincent
>>
>>
>>>>> 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
>>>>>>>
4:30 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Vincent Massol wrote:
> On Aug 18, 2008, at 8:18 PM, Vincent Massol wrote:
>
>
>> On Aug 18, 2008, at 8:03 PM, Marius Dumitru Florea wrote:
>>
>>
>>>> On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
>>>>
>>>>
>>>>> +1
>>>>>
>>>>> I think currently we can only use the new wysiwyg if we have a page
>>>>> using XWiki 2.0 syntax right ?
>>>>>
>>>> yes.
>>>>
>>> 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?
>>>
>> I have a question: if we use radeox is the new editor going to be
>> better than the old one?
AFAIK, many of the current WYSIWYG's issues are in fact Radeox issues.
Plus, the new editor has less features at this point, so I don't think
it's going to be better with Radeox. I too think the new WYSIWYG and the
new rendering should go hand in hand.
>
> 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.
>
ok for me if we have a button "convert to XWiki 2.0"
BTW we have the question for the office converter. It's converting
HTML to wiki syntax using the new rendering and thus we get new syntax
only.
We really need to decide what we want. Any comment on my previous email?
Thanks
-Vincent
> However moving to the new syntax is not something so we'll need to
> make it as painless as possible.
>
>
Yes I think we need a button when a page is in xwiki syntax 1.0 to do
"convert to XWiki 2.0 syntax"
> 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.
>
>
I agree +1
WDYT?
Thanks
-Vincent
>>> 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
>>>>>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:57 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1 for making the new editor only available with the new rendering & the new
syntax.
We've already spent a long time coping with Radeox-related issues - let's
end it as fast as we can :-)
Guillaume
On Tue, Aug 19, 2008 at 4:30 PM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://blog.xwiki.com/
Vincent Massol
wrote:
> On Aug 18, 2008, at 8:18 PM, Vincent Massol wrote:
>
>
>> On Aug 18, 2008, at 8:03 PM, Marius Dumitru Florea wrote:
>>
>>
>>>> On Aug 18, 2008, at 5:54 PM, Ludovic Dubost wrote:
>>>>
>>>>
>>>>> +1
>>>>>
>>>>> I think currently we can only use the new wysiwyg if we have a page
>>>>> using XWiki 2.0 syntax right ?
>>>>>
>>>> yes.
>>>>
>>> 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?
>>>
>> I have a question: if we use radeox is the new editor going to be
>> better than the old one?
AFAIK, many of the current WYSIWYG's issues are in fact Radeox issues.
Plus, the new editor has less features at this point, so I don't think
it's going to be better with Radeox. I too think the new WYSIWYG and the
new rendering should go hand in hand.
>
> 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.
>
ok for me if we have a button "convert to XWiki 2.0"
BTW we have the question for the office converter. It's converting
HTML to wiki syntax using the new rendering and thus we get new syntax
only.
We really need to decide what we want. Any comment on my previous email?
Thanks
-Vincent
> However moving to the new syntax is not something so we'll need to
> make it as painless as possible.
>
>
Yes I think we need a button when a page is in xwiki syntax 1.0 to do
"convert to XWiki 2.0 syntax"
> 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.
>
>
I agree +1
WDYT?
Thanks
-Vincent
>>> 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
>>>>>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
18 Aug
18 Aug
7:47 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+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]" ?
I'm for such a parameter. I have it almost implemented locally.
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:43 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
On Mon, Aug 18, 2008 at 12:09 PM, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
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
--
Sergiu Dumitriu
http://purl.org/net/sergiu
6:01 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
+1
Marius Dumitru Florea wrote:
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
20 Aug
20 Aug
8:56 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may cause
some problems: the GWT version. A few weeks ago I switched from 1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs annotations)
* Improved API (Element#getInnerHTML() instead of DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
* Use maven magic to obtain a special XE distribution which will include
the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
WYSIWYG in the default distribution)
* Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
* Something else?
So WDYT?
Marius
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
9:32 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may cause
some problems: the GWT version. A few weeks ago I switched from 1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
AFAIK Curriki is currently on core/XE 1.4 branch, as well as watch trunk
(which could upgrade to 1.5 branch for its 1.1 release I think, or better
upgrade to core/XE 1.6 + GWT 1.5); so upgrading XE trunk to GWT 1.5-rc-2
should not be an issue IMO, there's just the uncertainty that 1.5 final
release of GWT being out by the time we are ready for XE 1.6 final...
Jerome.
* Use maven magic to obtain a special XE distribution
which will include
the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
WYSIWYG in the default distribution)
* Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
* Something else?
So WDYT?
Marius
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
9:44 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
On Aug 20, 2008, at 9:32 PM, Jerome Velociter wrote:
I don't think that's a real issue. The issue is more whether GWT
1.5RC2 works for XWiki products or not. We could release 1.6 final on
GWT 1.5RC2 if it works.
Thanks
-Vincent
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may
cause
some problems: the GWT version. A few weeks ago I switched from
1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will
soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs
annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work
on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
AFAIK Curriki is currently on core/XE 1.4 branch, as well as watch
trunk
(which could upgrade to 1.5 branch for its 1.1 release I think, or
better
upgrade to core/XE 1.6 + GWT 1.5); so upgrading XE trunk to GWT 1.5-
rc-2
should not be an issue IMO, there's just the uncertainty that 1.5
final
release of GWT being out by the time we are ready for XE 1.6 final... > * Use maven magic to obtain a special XE
distribution which will
> include
> the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
> WYSIWYG in the default distribution)
> * Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
> * Something else?
>
> So WDYT?
> Marius
>
>> 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
9:56 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Jerome Velociter wrote:
AFAIK Curriki is on its way to being moved to 1.5.
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may cause
some problems: the GWT version. A few weeks ago I switched from 1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
AFAIK Curriki is currently on core/XE 1.4 branch, as well as watch trunk
(which could upgrade to 1.5 branch for its 1.1 release I think, or better
upgrade to core/XE 1.6 + GWT 1.5); so upgrading XE trunk to GWT 1.5-rc-2
Most probable 1.6, but I didn't do it yet because I didn't need it.
should not be an issue IMO, there's just the
uncertainty that 1.5 final
release of GWT being out by the time we are ready for XE 1.6 final...
Jerome.
> * Use maven magic to obtain a special XE distribution which will include
> the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
> WYSIWYG in the default distribution)
> * Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
> * Something else?
Create the 1.7 GWT1.5ish branch for xwiki-web-gwt and depend
on that in your
experimental XE? That might be just equivalent to first option, though...
So WDYT?
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:18 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
To summarize I'm definitely +1 to move trunk to GWT 1.5RC2 since trunk
is always meant to be on the latest of everything.
As for products I don't see how that could be an issue since they can
always depend on some other branches if they don't want to upgrade.
We need to move fast here since the new WYSIWYG integration is planned
for 1.6M1 (which was planned for the last Monday and rescheduled to
the coming Monday).
So if anyone has an issue please raison it fast now so that Marius can
carry on.
Thanks
-Vincent
On Aug 20, 2008, at 9:56 PM, Anca Paula Luca wrote:
Jerome Velociter wrote:
AFAIK Curriki is on its way to being moved to 1.5.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may
cause
some problems: the GWT version. A few weeks ago I switched from
1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will
soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs
annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to
work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
AFAIK Curriki is currently on core/XE 1.4 branch, as well as watch trunk
(which could upgrade to 1.5 branch for its 1.1 release I think, or
better
upgrade to core/XE 1.6 + GWT 1.5); so upgrading XE trunk to GWT 1.5-
rc-2
Most probable 1.6, but I didn't do it yet because I didn't need it.
should not be an issue IMO, there's just the
uncertainty that 1.5
final
release of GWT being out by the time we are ready for XE 1.6 final...
Jerome.
> * Use maven magic to obtain a special XE distribution which will
> include
> the new WYSIWYG and will depend on GWT 1.5 (but we won't have the
> new
> WYSIWYG in the default distribution)
> * Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
> * Something else?
Create the 1.7 GWT1.5ish branch for xwiki-web-gwt and depend
on that
in your
experimental XE? That might be just equivalent to first option,
though...
So WDYT?
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:32 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Vincent Massol wrote:
To summarize I'm definitely +1 to move trunk to
GWT 1.5RC2 since trunk
is always meant to be on the latest of everything.
As for products I don't see how that could be an issue since they can
always depend on some other branches if they don't want to upgrade.
The problem is when a product wants to get all "latest" but not upgrade GWT --
in watch's case, get latest feedplugin (of which it also depends and which is in
core atm) but not upgrade to GWT 1.5.
This should be no longer a problem for watch, since it won't be distributed as a
xar anymore so it can configure its own module dependencies inside enterprise
(with some maven magic) and hopefully lower versions of xwiki-web-gwt are
compatible with the trunk.
Happy coding,
Anca
We need to move fast here since the new WYSIWYG integration is planned
for 1.6M1 (which was planned for the last Monday and rescheduled to
the coming Monday).
So if anyone has an issue please raison it fast now so that Marius can
carry on.
Thanks
-Vincent
On Aug 20, 2008, at 9:56 PM, Anca Paula Luca wrote:
Jerome Velociter wrote:
AFAIK Curriki is on its way to being moved to 1.5.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may
cause
some problems: the GWT version. A few weeks ago I switched from
1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will
soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs
annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to
work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
AFAIK Curriki is currently on core/XE 1.4 branch,
as well as watch trunk
(which could upgrade to 1.5 branch for its 1.1 release I think, or
better
upgrade to core/XE 1.6 + GWT 1.5); so upgrading XE trunk to GWT 1.5-
rc-2
Most probable 1.6, but I didn't do it yet because I didn't need it.
should not be an issue IMO, there's just the
uncertainty that 1.5
final
release of GWT being out by the time we are ready for XE 1.6 final...
Jerome.
> * Use maven magic to obtain a special XE distribution which will
> include
> the new WYSIWYG and will depend on GWT 1.5 (but we won't have the
> new
> WYSIWYG in the default distribution)
> * Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
> * Something else?
Create the 1.7 GWT1.5ish branch for xwiki-web-gwt and depend
on that
in your
experimental XE? That might be just equivalent to first option,
though...
So WDYT?
Marius
> 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
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
22 Aug
22 Aug
3:23 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
I'm almost done. I want to commit ASAP (like in half an hour) but there
are two things that stop me:
(1) I added a parameter in xwiki.cfg (xwiki.wysiwygnew=[1|0]) for
enabling/disabling the experimental editor. I need to retrieve its value
in a template like edit.vm. How should I do it? Options:
* Add a isWysiwygNewEnabled() method in XWiki. I don't like this solution
because XWiki is already too crowded.
* Create a WysiwygPlugin that we can extend later, and which will contain
for the moment just a isEnabled() method.
* Something else?
(2) "New WYSIWYG (experimental)" is too long for the EditModes panel (it
breaks in two lines). Is it ok to leave just "New Wysiwyg"?
WDYT?
Marius
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may cause
some problems: the GWT version. A few weeks ago I switched from 1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work on 1.5
since the new WYSIWYG depends on it and on GWT 1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
* Use maven magic to obtain a special XE distribution which will include
the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
WYSIWYG in the default distribution)
* Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
* Something else?
So WDYT?
Marius
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
2:53 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
Marius Dumitru Florea wrote:
I'm almost done. I want to commit ASAP (like in
half an hour) but there
are two things that stop me:
(1) I added a parameter in xwiki.cfg (xwiki.wysiwygnew=[1|0]) for
enabling/disabling the experimental editor. I need to retrieve its value
in a template like edit.vm. How should I do it? Options:
* Add a isWysiwygNewEnabled() method in XWiki. I don't like this solution
because XWiki is already too crowded.
* Create a WysiwygPlugin that we can extend later, and which will contain
for the moment just a isEnabled() method.
* Something else?
+1 for the plugin. We can move some other methods from XWiki.java there,
like: getEditorPreference, getWysiwygToolbars, context.getEditorWysiwyg
(2) "New WYSIWYG (experimental)" is too long
for the EditModes panel (it
breaks in two lines). Is it ok to leave just "New Wysiwyg"?
New WYSIWYG is OK.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
3:34 p.m.
New subject: [xwiki-devs] [Proposal] Move the new WYSIWYG into the platform
[snip]
(2) "New WYSIWYG (experimental)" is too long for the EditModes panel (it
breaks in two lines). Is it ok to leave just "New Wysiwyg"?
NEW WYSIWYG seems ok to me.
Guillaume
WDYT?
Marius
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://blog.xwiki.com/
11 +1
I'll move the new WYSIWYG into the platform tomorrow morning.
Regarding the integration, I forgot one important detail that may cause
some problems: the GWT version. A few weeks ago I switched from 1.4.61 to
1.5-rc1. The latest version is now 1.5-rc2 and I believe they will soon
provide a final 1.5 version (AFAIK, there's no publicly available
roadmap). Some of the reasons that made me move to GWT 1.5 are:
* Java 1.5 goodies (use of generics instead of @gwt.typeArgs annotations)
* Improved API (Element#getInnerHTML() instead of
DOM#getInnerHTML(Element))
* Curiosity
Right now, platform-web-gwt depends on GWT 1.4.61. It seems to work on
1.5
since the new WYSIWYG depends on it and on GWT
1.5. So, what are the
options?
* Move platform-web-gwt to GWT 1.5 (but may cause problems in other
projects like Watch and Curriki)
* Use maven magic to obtain a special XE distribution which will include
the new WYSIWYG and will depend on GWT 1.5 (but we won't have the new
WYSIWYG in the default distribution)
* Degrade the WYSIWYG to GWT 1.4 (but it will make me unhappy)
* Something else?
So WDYT?
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5922
days inactive
5926
days old
28 comments
13 participants
participants (13)
-
Anca Paula Luca -
Artem Melentyev -
Asiri Rathnayake -
Guillaume Lerouge -
Jerome Velociter -
Ludovic Dubost -
Marius Dumitru Florea -
Marta Girdea -
Pascal Voitot -
Sergiu Dumitriu -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol