What about taking smaller steps on the long way?
I believe xinha editor is quite stable now and all features related to
xinha might be postponed to 3.1
I believe we should concentrate to 3.0, to upgrade process.
The editor change can come later, after 3.0 is out and stable.

But if the editor switch is simple, will take few hours you have and you
are safe it brings something new that worth to have in 3.0, go ahead.

Ondra

On Wed, 2006-08-30 at 15:20 +0100, Paul Baranowski wrote:
> Due to the problems with IE, I propose we swap Xinha for FCKEditor,
> now that FCKEditor has its new "Extremely fast loading" feature.
> Previously Xinha was much much faster than FCKEditor, but now they
> seem pretty much the same. FCKEditor also has much nicer capabilities
> now (try out the demo, you will be impressed). For example, the popup
> dialogs dont start in the upper left hand corner of the screen and
> then move themselves to the middle of the screen like Xinha does.
> Everything about it looks nicer.
>
> We would have to port the Campsite Internal Link button plugin (which
> needs updating anyhow), add the subhead button, and modify how images
> are handled.
>
> Comments?
>
> Paul
>

If I may add, You should try tinyMCE, looks maybe nicer(if that matter at all, also I dont see so big issue for popups to open in top-left and then move to middle, but tinyMCE also have popups in the middle anyway), and what is more important has better support for Opera browser (doesnt work all features but IS useable). I think its fast as FCK anyway. And I think that code produced is much better than Xinxa so keeping in W3C proposal would be easy without jumping to HTML and editing it manualy...You really should check it out http://tinymce.moxiecode.com/index.php

As for Ondra's statement, he is right, we should prioritize release of 3.0 unless its simple(and I dont think that is 2 hour job from my conversation with Mugur regarding WYSIWYG editor)

Boban
----- Original Message -----
From: Paul Baranowski
To: campsite-dev@campware.org
Sent: Wednesday, August 30, 2006 4:20 PM
Subject: [campsite-dev] WYSIWYG editor change proposal


Due to the problems with IE, I propose we swap Xinha for FCKEditor, now that FCKEditor has its new "Extremely fast loading" feature. Previously Xinha was much much faster than FCKEditor, but now they seem pretty much the same. FCKEditor also has much nicer capabilities now (try out the demo, you will be impressed). For example, the popup dialogs dont start in the upper left hand corner of the screen and then move themselves to the middle of the screen like Xinha does. Everything about it looks nicer.

We would have to port the Campsite Internal Link button plugin (which needs updating anyhow), add the subhead button, and modify how images are handled.

Comments?

Paul

Guys,

If we change the editor, it will go into 3.1. We are adding no new
features to 3.0.

The problem is indeed with the Explorer, and it only happens if you have
huge numbers of text-type fields. I didn't hear Raed and his hordes of IE
users crying too much about it for the moment. Plus IE 7.0 solves this
problem (as far as I hear, the beta, or whatever it is now, is already
stable enough for daily use). So the choice for IE users will be to use
the latest release of 7.0 or to plug their noses and use a superior
browser t.e.m.p.o.r.a.r.i.l.y for their work. After all, M$ Windoze is a
powerful multitasking environment

We can nonetheless continue the discussion.

To answer your question, Holman, the target Campsite user is a journalist,
i.e. person who is even occasionally at war with his own mouse (yep, i've
seen those) -- sure, new generations will be more tech-savvy, but the
simpler the editor is, the better. That's why we have made a full
customization of Xinha (i.e. you can turn ALL features on and off) -- and
Paul, wouldn't we have to do that part of work as well for the new editor?
So in short, we don't want something too avantguarde (with gmail-like
clever features, which puzzle the heck of many a nongeek), though an AJAX
editor would certainly rock. Anybody know of any good free AJAX editors we
could use?

Maybe we could start a Wiki page about the wysiwyg editor requirements
(i.e. what work needs to be done to Campsitize it).

Sava








"Holman Romero"
08/30/2006 05:18 PM
Please respond to campsite-dev


To: campsite-dev@campware.org
cc:
Subject: Re: [campsite-dev] WYSIWYG editor change proposal


I did use tinyMCE some time ago and i did not like it, more important,
users did not feel comfortable with it, so we changed to FCK and
everybody was happy.

however, it was some time ago (around 1 year or so), and i do not how
well it has evolved.

i think it is very important to have clear what we need from a wysiwyg
editor in order to make a good decision around this. fortunately we
have very good open source wysiwyg editors around to take a look.

you have been working with Campsite users, so... what wysiwyg features
an editor or writer really need?


On 8/30/06, Slobodan Gogic wrote:
>
>
> If I may add, You should try tinyMCE, looks maybe nicer(if that matter
at
> all, also I dont see so big issue for popups to open in top-left and
then
> move to middle, but tinyMCE also have popups in the middle anyway), and
what
> is more important has better support for Opera browser (doesnt work all
> features but IS useable). I think its fast as FCK anyway. And I think
that
> code produced is much better than Xinxa so keeping in W3C proposal would
be
> easy without jumping to HTML and editing it manualy...You really should
> check it out http://tinymce.moxiecode.com/index.php
>
> As for Ondra's statement, he is right, we should prioritize release of
3.0
> unless its simple(and I dont think that is 2 hour job from my
conversation
> with Mugur regarding WYSIWYG editor)
>
> Boban
>
>
> ----- Original Message -----
> From: Paul Baranowski
> To: campsite-dev@campware.org
> Sent: Wednesday, August 30, 2006 4:20 PM
> Subject: [campsite-dev] WYSIWYG editor change proposal
>
> Due to the problems with IE, I propose we swap Xinha for FCKEditor, now
that
> FCKEditor has its new "Extremely fast loading" feature. Previously
Xinha
> was much much faster than FCKEditor, but now they seem pretty much the
same.
> FCKEditor also has much nicer capabilities now (try out the demo, you
will
> be impressed). For example, the popup dialogs dont start in the upper
left
> hand corner of the screen and then move themselves to the middle of the
> screen like Xinha does. Everything about it looks nicer.
>
> We would have to port the Campsite Internal Link button plugin (which
needs
> updating anyhow), add the subhead button, and modify how images are
handled.
>
> Comments?
>
> Paul
>
>


--
/holman

Paul,

You know that I like the latest and greatest as much as anybody out there.
But let's not squander our resources on something that clearly has at
least two workarounds.

If somebody buys a support contract, we will instruct them to use the
workaround (I will personally warn them that there is this IE issue before
they fork out the money). Meanwhile, we will make note of the problem in
the documentation.

So let's not fix it if it ain't very broke. The 3.0 deadline is near, and
we need all hands on deck for that. If you tell me otherwise, I have some
other features I'd like to see implemented as we'd advertised

Also, why rush into another editor without doing more research? Surely,
FCK looks good (and Cream and Dream use it, btw), but maybe Boban's
tinymce suggestion also merits a serious consideration (crossbrowser
support, etc.).

Sava






"Paul Baranowski"
08/30/2006 06:04 PM
Please respond to campsite-dev


To: campsite-dev@campware.org
cc:
Subject: Re: [campsite-dev] WYSIWYG editor change proposal




On 8/30/06, sava.tatic@mdlf.org wrote:
If we change the editor, it will go into 3.1. We are adding no new
features to 3.0.

Not quite...if one of the customers complaining about IE buys a support
contract, then we have to fix it, which means swapping the editor. I cant
think of anything else we could do. I figure we should do it now rather
than be caught by surprise later... but let me know if you see things
differently.


Anybody know of any good free AJAX editors we could use?

We'll have to AJAX the whole page, not just the editor. (In other words,
you click "Save" and the page doesnt refresh.) I've been doing some
research in my spare time and I know how to do this now...just have to get
around to doing it, it actually isnt that hard.

Paul