TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
405 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: 37381c8cab
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '37381c8cab'
${ noResults }
openproject/app/views/my_projects_overviews/blocks/_subprojects.html.erb

35 lines
1.0 KiB
Raw Normal View History Unescape

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
<%#-- copyright
Updated copyright notices
11 years ago
OpenProject My Project Page Plugin
Copyright (C) 2011-2014 the OpenProject Foundation (OPF)
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
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License version 3.
Updated copyright notices and readme
11 years ago
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
See doc/COPYRIGHT.md for more details.
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
++#%>
Add subproject widget.
13 years ago
<h3><%=l(:label_subproject_plural)%></h3>
Fixes tab order of block heading and buttons
11 years ago
<% if defined? block_name_id %>
<%= content_for block_name_id %>
<% end %>
replaces instance variable in view by methods in controller Replaces every instance variable in the view layer by a method call to the controller. This is done in order to: 1) better separate concerns. 2) Lazy loading of objects that might be used by a block. As the purpose of the plugin is to allow the user to choose from a list of available blocks, not all blocks will be used all the times. This also means that not all information is required to be loaded all the time. With this commit, we load only what is required for the current block selection by having each block call a method that loads the information it requires.
12 years ago
<% if childprojects.any? %>
<div class="subprojects overview">
<p>
Basic functionality is now working again: * fixed missing translations * fixed several errors that derive from the issue/workpackage-changes * templates renamed (rhtml -> .html.erb) * several html_safe-issues fixed * mappings/routes changed (there are still two mappings missing) * basically copied the blocks from core/mypage(again!) to make it working: many of these blocks still don't make sense, as they are not limited to the project * several minor issues
11 years ago
<%= childprojects.collect{ |p| link_to(h(p), project_url(p)) }.join(", ").html_safe %>
replaces instance variable in view by methods in controller Replaces every instance variable in the view layer by a method call to the controller. This is done in order to: 1) better separate concerns. 2) Lazy loading of objects that might be used by a block. As the purpose of the plugin is to allow the user to choose from a list of available blocks, not all blocks will be used all the times. This also means that not all information is required to be loaded all the time. With this commit, we load only what is required for the current block selection by having each block call a method that loads the information it requires.
12 years ago
</p>
</div>
Add subproject widget.
13 years ago
<% end %>