01 Jul, 2015

3 commits

29 Jun, 2015

5 commits

25 Jun, 2015

1 commit

17 Jun, 2015

7 commits

16 Jun, 2015

5 commits

15 Jun, 2015

1 commit

13 Jun, 2015

1 commit

  • 682ee5be   plugins: Support plugin to be defined as module instead of object ... Browse Dir » 
    This makes possible for a plugin to be defined as module and have its
main class defined inside it with the name Base (e.g. MyPlugin::Base).

The advantages of this is to correctly scope plugins constants inside
the module. There are many conflicts with the core if the plugin is
defined as klass, for example:
 - if you define a MyPlugin::DisplayHelper you'll get the error 'warning: toplevel constant DisplayHelper referenced by MyPlugin::DisplayHelper' and your class won't be loaded unless you put a "require 'my_plugin/display_helper'"
 - `require` is also needed for contants with the sames of constants declared under Noosfero::Plugin. For example, if you define a MyPlugin::Manager or MyPlugin::Settings, Noosfero::Plugin::Manager or Noosfero::Plugin::Settings will be returned instead of your plugin's definition.
 - other hard to debug errors may also happen.

This also encapsulates loading procedures into methods of
Noosfero::Plugin.
    Braulio Bhavamitra
     

12 Jun, 2015

3 commits

11 Jun, 2015

4 commits

08 Jun, 2015

1 commit

05 Jun, 2015

3 commits

03 Jun, 2015

6 commits