Changes between Version 47 and Version 48 of SimpleMultiProjectPlugin

Timestamp:

Mar 12, 2015, 9:51:36 AM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes, tagged with license

SimpleMultiProjectPlugin

@@ -1 +1 @@
 [[PageOutline(2-5,Contents,pullout)]]
 
-= SimpleMultiProjectPlugin =
+= SimpleMultiProjectPlugin
 
-== Description ==
+== Description
+
 Lets you easily '''manage multiple user projects with one Trac instance''' or, respectively, one Trac database (.db file).
 
@@ -15 +16 @@
 Note: The Multiple Project feature in the sense of having a meta Trac project on top of several Trac projects is discussed in T:#130 and scheduled for [T:milestone:topic-multiproject Trac topic-multiproject] which is eventually part of [T:milestone:next-dev-1.1.x Trac next-dev-1.1.x].
 
-== Plan ==
-in testing state:
+== Plan
+
+In testing state:
+
 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords=~testing)]]
 
-work in progress:
+Work in progress:
+
 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords$=planned&status=assigned|reopened)]]
 
-still just an idea:
+Still just an idea:
+
 [[TicketQuery(component=SimpleMultiProjectPlugin&keywords$=planned&status!=assigned|reopened|closed)]]
 
-== Technical thoughts ==
+== Technical thoughts
 
 This plugin adds a new resource 'project' implemented by database table:
- 1. smp_project: a list of all defined projects
-Actually, most database tables of Trac core related to resources would need a new column 'project_id'. This way tickets, components, milestones, versions or even wikis could attach to certain projects. Since a plugin just adds stuff but cannot change the core structure, it implements the new dimension 'project' not by adding a new column to each resource table but rather by adding several mapping tables smp_[resource]_project, each one mapping a certain resource to projects:
- 2. smp_milestone_project: the association of milestones to projects
- 3. smp_version_project:   the association of versions to projects
- 4. smp_component_project: the association of components to projects
+ 1. smp_project: a list of all defined projects[[BR]]
+ Actually, most database tables of Trac core related to resources would need a new column 'project_id'. This way tickets, components, milestones, versions or even wikis could attach to certain projects. Since a plugin just adds stuff but cannot change the core structure, it implements the new dimension 'project' not by adding a new column to each resource table but rather by adding several mapping tables smp_[resource]_project, each one mapping a certain resource to projects:
+ 1. smp_milestone_project: the association of milestones to projects
+ 1. smp_version_project:   the association of versions to projects
+ 1. smp_component_project: the association of components to projects
 
-== Example ==
+== Example
 
 '''''Admin Interface''''':
@@ -74 +79 @@
 [[Image(timeline_projects_filter.png)]]
 
-== Bugs/Feature Requests == 
+== Bugs/Feature Requests
 
 total issue record:
@@ -84 +89 @@
 [http://trac-hacks.org/newticket?component=SimpleMultiProjectPlugin&owner=falkb new ticket].
 
-== Download ==
+== Download
 
 Download the zipped source from [download:simplemultiprojectplugin here].
 
-== Source ==
+== Source
 
 You can check out SimpleMultiProjectPlugin from [http://trac-hacks.org/svn/simplemultiprojectplugin here] using Subversion, or [source:simplemultiprojectplugin browse the source] with Trac.
 
-== Installation ==
+== Installation
 
  1. Add a custom ticket field 'project' in your trac.ini to give tickets the information to which project they belong. Milestones selection depends on that as well.
@@ -136 +141 @@
 
 '''Author:''' [wiki:crossroad], [wiki:falkb], [wiki:thomasd] [[BR]]
-'''Maintainer:''' [wiki:falkb] [[BR]]
+'''Maintainer:''' [[Maintainer]] [[BR]]
 '''Contributors:'''