03 Mar, 2014
1 commit
01 Oct, 2013
1 commit
25 Feb, 2013
1 commit
18 Feb, 2013
1 commit
19 Jan, 2013
1 commit
11 Jan, 2013
1 commit
30 Nov, 2012
3 commits
-
Sorry, couldn't organize thing in micro-commits... =/
01 Nov, 2012
1 commit
-
Conflicts: db/schema.rb test/functional/cms_controller_test.rb test/unit/article_test.rb
25 Oct, 2012
2 commits
-
…into merge-requests/233 Conflicts: test/integration/routing_test.rb
24 Oct, 2012
1 commit
21 Oct, 2012
1 commit
15 Oct, 2012
2 commits
-
…into merge-requests/218 Conflicts: lib/noosfero/plugin.rb
07 Oct, 2012
1 commit
-
…into merge-requests/213 Conflicts: app/controllers/application_controller.rb app/helpers/application_helper.rb app/views/content_viewer/_comment.rhtml app/views/content_viewer/view_page.rhtml lib/noosfero/plugin.rb test/functional/content_viewer_controller_test.rb test/unit/comment_test.rb
01 Oct, 2012
2 commits
-
Conflicts: po/pt/noosfero.po public/javascripts/application.js
13 Sep, 2012
1 commit
11 Sep, 2012
1 commit
06 Sep, 2012
2 commits
05 Sep, 2012
2 commits
31 Aug, 2012
1 commit
30 Aug, 2012
2 commits
28 Aug, 2012
5 commits
25 Aug, 2012
1 commit
24 Aug, 2012
2 commits
-
Undo some things, fix some tests, etc
-
Conflicts: lib/noosfero/plugin/context.rb lib/noosfero/plugin/manager.rb test/unit/plugin_manager_test.rb
23 Aug, 2012
3 commits
-
This way any class can just include Noosfero::Plugin::HotSpot and just invoke the plugins.
-
It was just a wrapper around controller, with no clear goal. In the end, the context will the object which invokes the plugins. Rigth now it means basically a controller, but wait a little bit and see. ;-)
-
This a way the controller is optional, because all data needed to obtain the list of plugins to be instantiated comes from the environment.
21 Aug, 2012
1 commit
-
ActionItem2306