13 Jun, 2015

1 commit

  • 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
     

07 Apr, 2015

1 commit


31 Mar, 2015

1 commit


03 Feb, 2015

1 commit

  • Conflicts:
    	app/controllers/my_profile/profile_editor_controller.rb
    	app/helpers/search_helper.rb
    	app/models/invitation.rb
    	app/models/person.rb
    	app/views/cms/view.html.erb
    	app/views/templates/index.html.erb
    	plugins/community_track/views/content_viewer/_step_item.html.erb
    	test/functional/home_controller_test.rb
    	test/unit/person_test.rb
    	test/unit/profile_test.rb
    Rodrigo Souto
     

26 Jan, 2015

1 commit


30 Jun, 2014

1 commit


30 Mar, 2014

1 commit


17 Mar, 2014

1 commit


22 Aug, 2013

1 commit


16 Jul, 2013

1 commit


15 Jul, 2013

1 commit


08 Jul, 2013

1 commit


27 Jun, 2013

1 commit


20 Feb, 2013

1 commit


15 Jan, 2013

1 commit


08 Mar, 2012

1 commit


27 Nov, 2011

1 commit

  • Conflicts:
    	app/controllers/admin_controller.rb
    	app/controllers/application.rb
    	app/controllers/public/account_controller.rb
    	app/controllers/public/content_viewer_controller.rb
    	lib/noosfero/i18n.rb
    	test/functional/account_controller_test.rb
    	test/functional/admin_controller_test.rb
    	test/unit/contact_test.rb
    	test/unit/profile_test.rb
    Antonio Terceiro
     

08 Aug, 2011

1 commit

  • also:
    - fix noosfero/i18n: error_messages_for should works as documented in
      Rails API (accept param :header_message => '...')
    - new helper method to display errors in a dialog box
    - now Plugins knows what is URL to admin itself
    - defining paths to cucumber steps and setup files in config/cucumber.yml
    - allow plugins to have documentation in same way as Noosfero core
    
    (ActionItem2056)
    Joenio Costa
     

22 Feb, 2011

1 commit


04 Jan, 2011

1 commit

  • Done:
      * Plugin loading process
      * Infra-structure for plugins registering and event activations.
      * Three fixed routes for plugins.
      * Methods to define plugins meta-information.
      * Interface for activation and deactivation of plugins in the
        environment panel.
      * Hotspots:
        - Buttons in the control panel.
        - Tabs in the profile (including expanded_template method).
        - New attributes for profile.
      * Possibility for the plugin to add new tables.
      * Mezuro prototype.
    
    Missing:
      * Test integration.
      * Dependencies integration.
      * Possibility to add behaviours in noosfero base models.
    Rodrigo Souto