[geeklog-devel] Editor for Gl2 Content Plugin
tony at tonybibbs.com
Fri Aug 3 10:53:50 EDT 2007
I know one of Damien's issues with FCKEditor is that it's a bit "big" hence the TinyMCE suggestion. In my opinion most sane browsers cache JS so I'm not terribly concerned. Like Vinny said, I think it would make a ton of sense to make the editor configurable by providing a simple API each editor would implement for the various hooks.
On the backside of all this is the issue of input filtering. I'd be curious if anybody has used the built-in filtering stuff recently introduced into PHP.
FWIW, Damien's done a great job and we may be able to do a first alpha release at the end of the GSoC period.
----- Original Message ----
From: Damien Hodgkin <dracul01 at gmail.com>
To: Blaine Lang <devel at portalparts.com>
Cc: Geeklog Development <geeklog-devel at lists.geeklog.net>
Sent: Thursday, August 2, 2007 2:40:09 PM
Subject: Re: [geeklog-devel] Editor for Gl2 Content Plugin
Obviously I want to try to go the easiest route possible. Of course if I end
up getting an overwhelming amount of "FCKEditor is the way to go" then I am
going to implement it. I am going to start playing around with FCKEditor
tomorrow and do a personal analysis of the pros and cons of both it and
TinyMCE. I will most likely post a comparison of the two editors on my blog.
"I only have two braincells left, one is missing, and the other is putting up
On Thursday 02 August 2007 3:28:34 pm you wrote:
> Hi Damien,
> I spent a number of months trying various editors and watching their
> projects before settling on FCKeditor and implementing it for GL. I may
> be a bit biased but I've used it now for multiple other projects and
> have only had good experience including developing plugins for it like
> Mark Evans has recently.
> In just the past month YUI has released their editor as well Jack has
> released one for the JS EXT library this week. For a basic inline text
> editor or a full blown CMS solution, I still think FCKeditor is hard to
> beat. Fred is very active and we have contributed in the past to this
> project which he then replies personally with great support.
> If you choose option 4 - you may just have to develop extra JS libraries
> to initialize and possibly extend it like we have in GL 1.4 where you
> can switch modes online and flip to a basic textarea if you want. The
> FCKeditor API is pretty flexible as this shows.
> Damien Hodgkin wrote:
> > Ok, so I have been working really hard on the content plugin, I am now
> > implementing the editor. As of right now it has a very basic xhtml
> > editor. I am trying to figure out what would be best to use for a more
> > advanced editor, like Gl1 uses FCKEditor. I want to know what everyone
> > thinks. I've been eyeballing TinyMCE, as it is small and easy to
> > integrate, just two lines of code.
> > Now what I would like to know, from everyone is:
> > 1. How does everyone feel about the current editor in Gl1?
> > 2. If the editor were to change in Gl2 would it disappoint people?
> > 3. If you were to replace the editor what would you use?
> > 4. what if the content plugin used a add-in feature so a different editor
> > could be added later on, replacing the "standard" or "default" editor
> > that is put in place?
> > Your help and guidance is greatly appreciated.
> > ------------------------------------------------------------------------
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
More information about the geeklog-devel