[Radiant] Interest in a WYSIWYG plugin

Fri Oct 6 18:02:11 CDT 2006

Hi,

check out the page_parts patch on the trac, it is a very simple patch that
allows a developer to extend the admin interface, it allows for different
page parts, one of the extensions I uploaded alowes uploaded before to the,
another has a wysiwyg editor (based on fckeditor) instead of the text
editor, one allows for multiple uploads of file for galleries.

I know there are a few people that use this patch and are pretty happy with.

Sean, I do not think this requires a fork, neither do any of the things you
mentioned as long as they are done in a form of an extension, so you can add
or change different parts of the radiant functionality. similar to the way
Drupal allows extensions by having a big list of places you can plugin and
changes/extend the framework functionality.

Dror

On 10/6/06, Sean Cribbs <seancribbs at gmail.com> wrote:
>
> In my full-time job, we are considering a large-scale CMS that includes a
> WYSIWYG editor.  Many of them nowadays limit or have options to limit what
> kind of formatting can be applied to the output.  I agree with the overall
> sentiment that Radiant itself does not need a WYSIWYG, but I can understand
> why some people might want it, and thus it should be a plugin.  In my mind,
> there are a few other things that need to happen if you're going to add
> WYSIWYG, most of them having to do with users/groups/permissions etc.
> Sounds like a branch/fork/huge plugin to me!
>
> Sean Cribbs
> seancribbs.com
>
> On 10/6/06, Nathan Wright <nathan.e.wright at gmail.com > wrote:
> >
> > I agree that while adding WYSIWYG editing is just about the worst
> > thing that you can do to a website (at least in terms of proper
> > markup), every client that I have ever worked with has wanted
> > something like Microsoft Word in which they could write their pages.
> >
> > While I wish that everyone would write in Markdown/Textile, most
> > clients have absolutely no desire, inclination, or time to learn how
> > to write markup ... even simplified markup. Not only that, but as
> > fantastic as Markdown and Textile are, they still leave much to be
> > desired when working with anything _other_ than text (images, flash,
> > etc.)
> >
> > The question then isn't how do we convince clients that using a
> > WYSIWYG is wrong, rather the question is how do you lock down the
> > WYSIWYG editor just enough that they can do most of the things that
> > they want without compromising the design of the site.
> >
> > Hopefully I'll have my WYSIWYG patch finished soon. I used TinyMCE for
> > the editor (along with a few tweaks of my own) and once you limit some
> > of TinyMCE's functionality and explain _why_ it needs to be limited to
> > the client, everyone seems to be happy (of course YMMV).
> >
> > Note: for those interested in my WYSIWYG patch mentioned in an earlier
> > thread, I've worked in image uploading. It's still rough around the
> > edges (especially in the looks department), but it works well enough
> > for my clients that I haven't gotten a single "how do I ...?" call
> > from them.
> >
> > On 10/6/06, Justin Grammens <justingrammens at yahoo.com> wrote:
> > > WOW! There is an extreme interest by me. I still feel
> > > like a newbie to Rails and Radiant, but I'm really
> > > hoping that a few sites that I have done in Wordpress
> > > & Drupal can be converted to using Radiant. I love the
> > > flexbility with radius tagging and behaviors.
> > > Unfortunately, without WYSIWYG editing I know it's a
> > > tough sell for my clients. I think textile is awesome
> > > but for the non-technical person they really need a
> > > WYSIWYG editor. I was planning to start hacking
> > > something together myself using TinyMCE.
> > >
> > > http://johnwulff.com/articles/2006/05/31/tinymce-with-ruby-on-rails
> > >
> > > Would this editor plug-in you are talking about also
> > > support image uploads? at the least it would be nice
> > > to integrate with another plug-in allowing user's to
> > > upload resources.
> > >
> > > --- Todd Baur <todd at tackletechnology.org> wrote:
> > >
> > > > All,
> > > >
> > > > My team is researching the plugin architecture of
> > > > Radiant and the
> > > > plan is to develop a WYSIWYG editor for Radiant that
> > > > is similar to
> > > > what is used in Wordpress. I am willing to
> > > > contribute the code we
> > > > develop if there is an interest in the community for
> > > > it.
> > > > ~*~*~~*~*~*~*~*~*~*~*~*~
> > > > Todd Baur
> > > > todd at tackletechnology.org
> > > > 858-752-1459
> > > > 11814 Westview Parkway
> > > > Unit #176
> > > > San Diego, CA 92126
> > > >
> > > >
> > > >
> > > > > _______________________________________________
> > > > Radiant mailing list
> > > > Post:   Radiant at lists.radiantcms.org
> > > > Search: http://radiantcms.org/mailing-list/search/
> > > > Site:
> > > http://lists.radiantcms.org/mailman/listinfo/radiant
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam protection around
> > > http://mail.yahoo.com
> > > _______________________________________________
> > > Radiant mailing list
> > > Post:   Radiant at lists.radiantcms.org
> > > Search: http://radiantcms.org/mailing-list/search/
> > > Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> > >
> >
> >
> > --
> > Nathan
> > _______________________________________________
> > Radiant mailing list
> > Post:   Radiant at lists.radiantcms.org
> > Search: http://radiantcms.org/mailing-list/search/
> > Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
> >
>
>
> _______________________________________________
> Radiant mailing list
> Post:   Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.radiantcms.org/pipermail/radiant/attachments/20061006/f493fa26/attachment.html