30 Dec
2008
30 Dec
'08
6:13 p.m.
Hi devs,
This is not a priority (we need to finish our first stable release of
the WYSIWYG editor first) but I wanted to propose 2 things and start a
discussion on it:
* That we make our new GWT WYSIWYG editor a top level project (i.e.
with a separate jira, separate wiki like http://wysiwyg.xwiki.org with
a better name, etc)
* Make it usable by someone who is not using XWiki
The rationale is:
* If we want our editor to become strong and compete with the likes of
FCKEditor/TinyMCE we need to open it up to others and for that we need
to:
- advertise it (hence the http://wysiwyg.xwiki.org that would lists
all features same as http://www.fckeditor.net/)
- make it be usable easily and thus without dragging xwiki dependencies
Other options:
1) Don't do anything. Cons: we won't get enough help and it'll be hard
to compete with other editors. They'll have more features/less bugs
and we'll have a hard time keeping up. In addition it's possible
someone else creates a new GWT WYSIWYG editor and it would be better
if we could all join force on that and using what we have started
2) Externalize it on some forge other than the xwiki forge. This is
nice from a marketing point of view (i.e. easier to show it as a pure
wysiwyg editor) but it has some drawbacks:
- further from the xwiki community and thus harder for us to maintain
it there
- doesn't strengthen our xwiki project
In addition, what we need to evaluate is how do we make it independent
of xwiki and how long would that take. This is probably more a
question for Marius. Marius this is not urgent compared to the 1.7.1
release. Whenever you have time.
Thanks
-Vincent
30 Dec
30 Dec
6:55 p.m.
New subject: [xwiki-devs] [Proposal] Make our new GWT WYSIWYG editor a top level standalone project
On Tue, Dec 30, 2008 at 6:13 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
This is not a priority (we need to finish our first stable release of
the WYSIWYG editor first) but I wanted to propose 2 things and start a
discussion on it:
* That we make our new GWT WYSIWYG editor a top level project (i.e.
with a separate jira, separate wiki like http://wysiwyg.xwiki.org with
a better name, etc)
* Make it usable by someone who is not using XWiki
The rationale is:
* If we want our editor to become strong and compete with the likes of
FCKEditor/TinyMCE we need to open it up to others and for that we need
to:
- advertise it (hence the http://wysiwyg.xwiki.org that would lists
all features same as http://www.fckeditor.net/)
- make it be usable easily and thus without dragging xwiki dependencies
Other options:
1) Don't do anything. Cons: we won't get enough help and it'll be hard
to compete with other editors. They'll have more features/less bugs
and we'll have a hard time keeping up. In addition it's possible
someone else creates a new GWT WYSIWYG editor and it would be better
if we could all join force on that and using what we have started
2) Externalize it on some forge other than the xwiki forge. This is
nice from a marketing point of view (i.e. easier to show it as a pure
wysiwyg editor) but it has some drawbacks:
- further from the xwiki community and thus harder for us to maintain
it there
- doesn't strengthen our xwiki project
In addition, what we need to evaluate is how do we make it independent
of xwiki and how long would that take. This is probably more a
question for Marius. Marius this is not urgent compared to the 1.7.1
release. Whenever you have time.
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
big +1, as Vincent said if we want it to be a strong WYSIWYG editor,
we need people to use it and contribute. And we would get a lot more
people and especially developers if make it standalone.
For the details I would be in favor of really externalize it as I
think it will get more people if it's clear it's a generic WYSIWYG
editor but yes it would not be seen as a XWiki strength anymore.
--
Thomas Mortagne
6:58 p.m.
New subject: [xwiki-devs] [Proposal] Make our new GWT WYSIWYG editor a top level standalone project
On Tue, Dec 30, 2008 at 11:25 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com
wrote:
> On Tue, Dec 30, 2008 at 6:13 PM, Vincent Massol <vincent(a)massol.net>
wrote:
> > Hi devs,
> >
> > This is not a priority (we need to finish our first stable release of
> > the WYSIWYG editor first) but I wanted to propose 2 things and start a
> > discussion on it:
> >
> > * That we make our new GWT WYSIWYG editor a top level project (i.e.
> > with a separate jira, separate wiki like http://wysiwyg.xwiki.org with
> > a better name, etc)
> > * Make it usable by someone who is not using XWiki
> >
> > The rationale is:
> > * If we want our editor to become strong and compete with the likes of
> > FCKEditor/TinyMCE we need to open it up to others and for that we need
> > to:
> > - advertise it (hence the http://wysiwyg.xwiki.org that would lists
> > all features same as http://www.fckeditor.net/)
> > - make it be usable easily and thus without dragging xwiki dependencies
> >
> > Other options:
> > 1) Don't do anything. Cons: we won't get enough help and it'll be
hard
> > to compete with other editors. They'll have more features/less bugs
> > and we'll have a hard time keeping up. In addition it's possible
> > someone else creates a new GWT WYSIWYG editor and it would be better
> > if we could all join force on that and using what we have started
> > 2) Externalize it on some forge other than the xwiki forge. This is
> > nice from a marketing point of view (i.e. easier to show it as a pure
> > wysiwyg editor) but it has some drawbacks:
> > - further from the xwiki community and thus harder for us to maintain
> > it there
> > - doesn't strengthen our xwiki project
> >
> > In addition, what we need to evaluate is how do we make it independent
> > of xwiki and how long would that take. This is probably more a
> > question for Marius. Marius this is not urgent compared to the 1.7.1
> > release. Whenever you have time.
> >
> > Thanks
> > -Vincent
> >
> > _______________________________________________
> > devs mailing list
> > devs(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
> big +1, as Vincent said if we want it to be a strong WYSIWYG editor,
> we need people to use it and contribute. And we would get a lot more
> people and especially developers if make it standalone.
>
> For the details I would be in favor of really externalize it as I
> think it will get more people if it's clear it's a generic WYSIWYG
> editor but yes it would not be seen as a XWiki strength anymore.
>
*BIG* +1!
- Asiri
5 Jan
5 Jan
6:15 p.m.
New subject: [xwiki-devs] [Proposal] Make our new GWT WYSIWYG editor a top level standalone project
On Tue, Dec 30, 2008 at 6:13 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
This is not a priority (we need to finish our first stable release of
the WYSIWYG editor first) but I wanted to propose 2 things and start a
discussion on it:
* That we make our new GWT WYSIWYG editor a top level project (i.e.
with a separate jira, separate wiki like http://wysiwyg.xwiki.org with
a better name, etc)
* Make it usable by someone who is not using XWiki
The rationale is:
* If we want our editor to become strong and compete with the likes of
FCKEditor/TinyMCE we need to open it up to others and for that we need
to:
- advertise it (hence the http://wysiwyg.xwiki.org that would lists
all features same as http://www.fckeditor.net/)
- make it be usable easily and thus without dragging xwiki dependencies
+1
Other options:
1) Don't do anything. Cons: we won't get enough help and it'll be hard
to compete with other editors. They'll have more features/less bugs
and we'll have a hard time keeping up. In addition it's possible
someone else creates a new GWT WYSIWYG editor and it would be better
if we could all join force on that and using what we have started
2) Externalize it on some forge other than the xwiki forge. This is
nice from a marketing point of view (i.e. easier to show it as a pure
wysiwyg editor) but it has some drawbacks:
- further from the xwiki community and thus harder for us to maintain
it there
- doesn't strengthen our xwiki project
2) would be great and I guess it would be a natural long-term
evolution if the wysiwyg.xwiki.org project succeed in gathering a
strong community.
JV.
6:29 p.m.
New subject: [xwiki-devs] [Proposal] Make our new GWT WYSIWYG editor a top level standalone project
On Jan 5, 2009, at 6:15 PM, Jean-Vincent Drean wrote:
On Tue, Dec 30, 2008 at 6:13 PM, Vincent Massol
<vincent(a)massol.net>
wrote:
Maybe but not sure. The point is to host it on our forge since we have
a forge... Why would we want to host somewhere else where we have a
less good quality of service, where we don't control the tools, etc? :)
Unless we join a community related to WYSIWYG or GWT and not a forge
(SourceForge vs Apache Software Foundation for ex).
Thanks
-Vincent
http://xwiki.com
http://massol.net
http://xwiki.org
Hi devs,
This is not a priority (we need to finish our first stable release of
the WYSIWYG editor first) but I wanted to propose 2 things and
start a
discussion on it:
* That we make our new GWT WYSIWYG editor a top level project (i.e.
with a separate jira, separate wiki like http://wysiwyg.xwiki.org
with
a better name, etc)
* Make it usable by someone who is not using XWiki
The rationale is:
* If we want our editor to become strong and compete with the likes
of
FCKEditor/TinyMCE we need to open it up to others and for that we
need
to:
- advertise it (hence the http://wysiwyg.xwiki.org that would lists
all features same as http://www.fckeditor.net/)
- make it be usable easily and thus without dragging xwiki
dependencies
+1
Other options:
1) Don't do anything. Cons: we won't get enough help and it'll be
hard
to compete with other editors. They'll have more features/less bugs
and we'll have a hard time keeping up. In addition it's possible
someone else creates a new GWT WYSIWYG editor and it would be better
if we could all join force on that and using what we have started
2) Externalize it on some forge other than the xwiki forge. This is
nice from a marketing point of view (i.e. easier to show it as a pure
wysiwyg editor) but it has some drawbacks:
- further from the xwiki community and thus harder for us to maintain
it there
- doesn't strengthen our xwiki project
2) would be great and I guess it would be a natural long-term
evolution if the wysiwyg.xwiki.org project succeed in gathering a
strong community.
5733
days inactive
5739
days old
4 comments
4 participants
participants (4)
-
Asiri Rathnayake -
Jean-Vincent Drean -
Thomas Mortagne -
Vincent Massol