5 Commits (59a6dac5fdbe6384fd75e7661b7c72fdf7cd4af3)

Author	SHA1	Message	Date
Sebastian Schuster	49c0273122	Renamed issue to work package where applicable	11 years ago
Sebastian Schuster	7e4602ae5b	Used dynamic looking for blocks in all plugins instead ... of some being predefined and adapted translations Also moved some step definitions to the core to be reused by the my page	11 years ago
Stefan Frank	2fd3e6e28d	Preparing the gem for release; adding project-scoped blocks from other plugins ... Following the guidelines in https://www.openproject.org/projects/openproject/wiki/Developing_Plugins, the gem was prepared for release * added copyright-headers * added readme * gemspec extended This also fixes an issue with plugins, that want to add views for the my_project_page: The mechanism now looks for blocks in the my_projects_overviews-folder of the plugin and adds them to the configuration using the document's name (Very similar to the way my_page does this in core.) An example for this can be found in the documents-plugin, which now provides views that either show all documents the user can see (in my/_documents.html.erb) and scoped to the given project (under my_projects_overviews/_project_documents.html.erb)	11 years ago
Stefan Frank	52192ee1ef	Added the remaing features (delete Attachments) and worked in the ... annotations to the pull-request. * fixed the deletion of attachments * wired the remaining routes * reworked the blocks.feature to use a step from core to setup issues * removed the custom-path reference for the overview-page * added a routing spec, that tests that the routing of the plugin is not too greedy	11 years ago
Stefan Frank	fc606ae8ec	added some cukes to test, that the blocks are actually limited to the ... selected project. Also did some housecleaning(e.g. remove unused hooks)	11 years ago