Integrate noosfero with etherpad-lite

[Daniel Tygel]

Hi Terceiro and others:

    It's not a set of obscure ifs buried everywhere. It's a tinymce 
plugin. And by itself (no in noosfero!), it works like this: if the init 
of tinymce doesn't give a pad URL, it's not initialized. So, as Terceiro 
said, it's of by default. It doesn't change anything to those who don't 
want it working in their website.

    As you can see at the code I sent in the other message, we've just 
installed a tnymce plugin, like there are other intymce plugins already 
installed. So the merge request touches three very precise areas:

1. few lines in the initiatilzation of tinymce in 
app/views/shared/tinymce.rhtml
2. the copy of the tinymce-etherpadlite-embed plugin 
(https://github.com/dtygel/tinymce-etherpadlite-embed) inside the folder 
public/javascripts/tinymce/jscripts/tiny_mce/plugins
3. the configurations of this plugin in environment.rb.

     Is there a problem in item 3? If so, do you have a better idea? I 
wouldn't like to have the plugin's settings directly in tinymce.rhtml.

     If there were an infrastructure that allowed a noosfero plugin to 
add a tinymce plugin, then I'd agree with Terceiro.

     Thanks,

         daniel


Em 29-08-2013 20:07, Antonio Terceiro escreveu:
> On Thu, Aug 29, 2013 at 07:25:47PM -0600, Daniel Tygel wrote:
>> Hi Ewout,
>>
>>     These are very good points. We installed our own pad server
>> because of that. It's http://pad.eita.org.br . And we also have the
>> liberty to say whatever we want to the user in the moment that the
>> pad is created. Right now our message is quite simple (welcome! and
>> some bare instructions), but it might be interesting to give this
>> warning to the user.
>>
>>     About the possibility of an admin to turn it off from the web
>> administration page: not yet. It's in the environment settings, and
>> can be changed by console only. But I think that a functionality
>> like this is rather a deeper decision than something we can be
>> turning on and off all the time.... anyway, it's sure that the
>> functionality will be much better when the admin can turn it on and
>> off from his/her interface. But many other funcionalities had their
>> first versions without this possibility (like for example the
>> trusted sites for iframe or the categories) before a later version
>> implemented it as another configuration option for the admin.
>>
>>      Do you think that the lack of this on/off from web admin
>> interface is a blocker for us to merge to noosfero?
> if it's off by default it shouldn't be a problem
>
> although at this point I thought we had an agreement that optional
> features should be plugins instead of yet another obscure option that you
> can check in the administration + yet another if statement buried
> somewhere in the code (or worse, several if statements buried in several
> places)
>
>
>
> _______________________________________________
> Noosfero-dev mailing list
> Noosfero-dev em listas.softwarelivre.org
> http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev