5 Commits (78edeaec3706781f8b43b5c61f9a8715ef066b9d)

Author	SHA1	Message	Date
Alex Coles	f2af0595e1	Cleanup whitespace ... Signed-off-by: Alex Coles <alex@alexbcoles.com>	11 years ago
Sebastian Schuster	6c39125a26	Updated copyright notices	11 years ago
Sebastian Schuster	1a33fe5ac5	Updated copyright notices and readme	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	7f9a7c4a58	Making the specs/features of core behave properly with the plugin. ... To make the core-features/specs run through, I added a fix to skip showing the contents of the members-block, when there are no members. Also disabled the "Show Projects"-Feature, as this one uses the layout/features of the original/non-customisable Project-Overview. The specs/features of core now run through in core in conjunction with this plugin.	11 years ago