side by side
lines around each change
Show the changes in full context
White space changes
Oct 17, 2007, 1:26:21 PM (
* Example plugin implementation included (!SampleValidOwnerProvider.py)
== Installation ==
=== How do I install it? ===
Just like any other Trac (0.11) plugin -- see step 1 in the 'How do I use it' section below for details. [[BR]]
''Note that by itself, this plugin won't make any visible changes to your Trac instance.''
=== Prerequisites ===
* Trac 0.11+ (built and tested against 0.11dev trunk r6047)
* Python 2.5+ (I can't confirm that Python 2.5 is actually required -- but it's the version I developed under and the only one I've tested with. If you successfully use this plugin with another version of Python, please update this wiki with your notes. - Morris)
== How do I use it? ==
'''1. Install !FlexibleAssignTo plugin''' [[BR]]
To get started, install the base !FlexibleAssignTo plugin. Build the .egg file following the plugin packaging instructions [http://projects.edgewall.com/trac/wiki/TracDev/PluginDevelopment here]. If you already have setuptools (v0.6+) installed, your command is
python setup.py bdist_egg
Once you've built the .egg, copy it into your Trac environment's plugin directory. You still need to activate the plugin -- in trac.ini:
flexibleassignto.* = enabled
'''NOTE:''' the plugin ''by itself'' doesn't do anything -- you have to write your own plugin/component that implements IValidOwnerProvider (step 3 below).
'''2. Try out the demo''' [[BR]]
Once you've installed the base !FlexibleAssignTo plugin, copy the !SampleValidOwnerProvider.py file from the install package into your Trac environment's plugin directory (alongside the !FlexibleAssignTo .egg). Restart your server and note the new (bogus) entries in your 'assign to' dropdowns.
'''3. Create your IValidOwnerProvider component'''
a. Create a .py file in your Trac environment's plugins directory -- this module is where you'll write your own class that implements the IValidOwnerProvider Extension point provided by FlexibleAssignTo. This is where your custom logic goes for deciding what users should appear as valid 'assign to' targets for each state -- whether that logic involves querying a database, an LDAP directory, or getting input from your custom array of highly trained homing pigeons. See the !SampleValidOwnerProvider.py module included with this plugin for a simple example on how it works.
b. IValidOwnerProvider component requirements
If you want to just jump right in, then all you really need to know is the following:
* The class should declare that it implements IValidOwnerProvider
* The class should provide a getUsers method that takes a 'next_action_obj' as it's sole param and returns a list of instances of SimpleUser (or a subclass) representing valid owners of that next state. If this sounds confusing, just look at the getUsers() method in !SampleValidOwnerProvider.py
== Bugs/Feature Requests ==
== Author/Contributors ==
rfmorris (aka gt4329b)