[geeklog-devel] Registering My Favorite WYSIWYG HTML Editor

[Wim Niemans]

Agree with Tom, with one exception.

I agree that is not up to the user to select a specific editor. But it is up the role the user is playing.
Comment posting could do entirely with the most basic editor available. See what I mean at LinkedIn: they are using a fine feature for posting comments; no decorations, only user experience.
Than I guess a story admin, aka CMS user, would like to use the most advanced editor available for drafting new stories.

My euro cents.

Wim

Op 16 aug. 2013, om 22:33 heeft Web Site Master het volgende geschreven:

> I like solution 2 better as well. This way Geeklog has full control of the editor selected and you can have more than one editor installed. Doing it the other way may create problems if you have 2 plugins installed that each have a different editor. 
> 
> My one question is do we want the user to be able to select their own advance editor if more than one is installed? I personally would say no. I would want them to only use the one I have selected for the site.
> 
> The only other downside to me is that plugins are easy to install since you can do it from the Geeklog plugin interface. At some point in the future we should try to add an interface so webmasters can install themes and editors directly from the Geeklog Admin.
> 
> By the way, thanks for your work Dengen.
> 
> Tom
> 
> 
> 
> On 08/16/13, Yoshinori Tahara <taharaxp at gmail.com> wrote:
>> 
>> Hi all,
>> 
>> Now, two WYSIWYG HTML editors (CKEditor and FCKEditor) are integrated
>> with Geeklog in the repository, and you can change an editor by
>> changing a value of variable $_CONF['advanced_editor_name'] defined in
>> the lib-common.php provisionally.
>> Finally, I want to allow an administrator to change
>> $_CONF['advanced_editor_name'] in the configuration page easily by
>> selecting an editor name from the drop down list ('CKEditor',
>> 'FCKEditor', 'TinyMCE', ...).
>> But what we should do more first is to build a mechanism to allow an
>> administrator to register his favorite editor.
>> 
>> I assumed that there are following two solutions.
>> 
>> 1. Register the editor as the plugin
>> 
>> To that end, it is necessary to add new API to lib-plugins.php.
>> This means that it is necessary to provide a mechanism to pick valid
>> editors from the crowd of plugins and to register the result into
>> somewhere.
>> 
>> 2. Treat the editor like the theme
>> 
>> Just as there is a "theme" directory for storing some themes, create
>> an "editor" directory for storing some editors.
>> Of course, it does not matter if you change the directory name to
>> "adveditor" from "editor".
>> 
>> Directory image before change:
>>     /public_html/fckeditor
>>     /public_html/ckeditor
>>     /public_html/tinymce
>> 
>> Directory image after change:
>>     /public_html/editor/fckeditor
>>     /public_html/editor/ckeditor
>>     /public_html/editor/tinymce
>> 
>> 
>> I like Solution 2 personally. Because it will be able to build a
>> mechanism more easily.
>> 
>> I wish to know your opinion.
>> 
>> Thanks
>> 
>> -- 
>> Yoshinori Tahara - dengen
>> _______________________________________________
>> geeklog-devel mailing list
>> geeklog-devel at lists.geeklog.net
>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20130816/6fe6cc02/attachment.html>