Re: task lists / todo lists / manual issue ordering

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday, June 4, 2003, at 02:07 AM, Felix Ulrich-Oltean wrote:
> I'd like to implement some "work lists" for our tracker, i.e. a list
> of issues that can be ordered arbitrarily and then linked either to a
> topic or a person, or a client, etc.

I'm not sure, but I believe this may already be achievable with the 
current issue class if you add the arbitrary "ordering" attribute on 
that class. The issue class has:

- - linking to topic
- - linking to person (assignedto)
- - I would assume that "client" is a person too...

I may be misunderstanding your proposal though...


> My idea at the moment is to make 2 new classes: WorklistEntry and
> Worklist.
>
> WorklistEntry will have a position attribute (for ordering) and a link
> to issue.
>
> Worklist will have a name, maybe a textual description, and a link to
> either a topic, client or user.  Dunno how to do this bit, I guess a
> cheat would be to store a classname string and an id, and then
> manually construct the appropriate links, rather than relying on
> Link/Multilink.

Hurm. So a WorklistEntry is really an issue? And a Worklist is really a 
collection of WorklistEntry items with some additional info. So:

   worklist = Class(db, 'worklist', name=String(), description=String(),
                   topic=Multilink('keyword'), ?client?=Link('user'),
                   ?user?=Link('user'))
   workentry = Class(db, 'workentry', issue=Link('issue'), 
ordering=Number(),
                     worklist=Link('worklist'))

I'm not sure what relationship you're trying to capture with ?client? / 
?user? so I can't really name them appropriately.

I'd consider just adding the worklist and ordering properties of 
workentry to the issue class itself:

    issue = IssueClass(db, "issue",
                    assignedto=Link("user"), topic=Multilink("keyword"),
                    priority=Link("priority"), status=Link("status"),
                                        ordering=Number(), 
worklist=Link("worklist"))


The worklist -> workentries relationship is handled by the child side - 
each workentry knows what its parent worklist is. The standard Roundup 
index displays may be used to display a sorted list of workentries for 
a particular worklist.


> The thing I'm unsure about is the interface and accompanying code for
> re-ordering stuff in a worklist.  I'm sure I'll figure it out, but any
> headstart would be appreciated.

You'll be figuring this one on your own - though once you figure out 
what the UI should look like, feel free to ask about any implementation 
details.


    Richard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iD8DBQE+3UeZrGisBEHG6TARAmStAJ9tplfvLWVxI2CpEmxq3ouxHppjcgCfdovW
C2QfytPqM6UPbGOwWdMYyUk=
=92bc
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.