[chandler-users] mouse-free status advancement, dependency display

[Alan F]

Jeffrey,

Thanks for the replies. Now that I look at the menus,
I see that everything in the menus already has a
shortcut. So that's good. 

As for adding an item to the menu whose purpose is to
advance the triage status -- I can see how to add an
item to the menu. The tricky part is figuring out how
to link that item with advancing the triage status. I
suspect that it involves something like a call to
advanceState, but I'll take a longer look at it, and
then if I have questions, I'll post them to the
chandler-dev mailing list.

Adding "future-proofing" for the dependency plugin
sounds great. But I'd like to know what ideas people
have had about displaying dependencies. The pair of
pull-down lists ("Dependency:" and "Blocked:") doesn't
really do much for me. I would like to only have to
indicate the dependency relation once, after which I
should always be able to see it without having to take
an extra step (such as clicking on the list heading).
Not sure whether that relation should be illustrated
by indentation (which might be tricky with many-to-one
relations), or by arrows. Arrows might require vector
graphics? and might make the interface a little more
crowded, but I would gladly put up with that in order
to see dependencies at a glance, which I think should
be core functionality for any project management tool.
But then that's easy for me to say...

Thanks again,
Alan

> ------------------------------
> 
> Message: 5
> Date: Mon, 17 Mar 2008 16:47:33 -0700
> From: Jeffrey Harris <jeffrey at osafoundation.org>
> Subject: Re: [chandler-users] mouse-free hotkeys in
> Chandler Desktop
...

> Hi Alan,
> 
> >  Has anyone else asked for mouse-free
> functionality in
> >  Chandler Desktop?
> 
> This is definitely an oft-requested feature.
> 
> As it happens, it's trivial to add this for any
> command that appears in 
> a menu.  So trivial, in fact, that the real issue
> for existing menu 
> items is about what the keyboard shortcuts should be
> on the various 
> platforms :)
> 
> There aren't currently menu items for changing
> triage status, but adding 
> them would be pretty easy.  I think there's already
> a bug to allow 
> multi-select -> change triage status en masse.
> 
> I think this issue is an almost ideal starter
> project for someone who'd 
> like to contribute to Chandler.
> 
> If you're interested in playing around with this,
> look at your local 
> version of this file:
> 
>
http://lxr.osafoundation.org/source/chandler/parcels/osaf/views/main/menus.py
> 
> Once you've changed or added shortcuts, you'll need
> to restart Chandler 
> with the ctrl key held down, and select "clean up,
> but keep my data" (I 
> think that works, if not, you'll need to start with
> a fresh repository).
> 
> Adding menu items for triage status would take a
> little more effort, but 
> not much more, so if you're interested in working on
> that, please speak 
> up!  I think probably questions about doing that
> should live on 
> chandler-dev, though.
> 
> Sincerely,
> Jeffrey
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Mon, 17 Mar 2008 17:50:45 -0700
> From: Jeffrey Harris <jeffrey at osafoundation.org>
> Subject: Re: [chandler-users] task dependencies,
> PDA-readable output
>     file
> To: Chandler users
> <chandler-users at osafoundation.org>
> Message-ID: <47DF11E5.8050203 at osafoundation.org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
> 
> Hi Alan,
> 
> > (1) the ability to grant and revoke multiple
> tickets
> > from Chandler Desktop (which can currently be done
> > only from Chandler Server)
> > 
> > (2) the ability to write out collection names, the
> > list of items in the collection, and associated
> pieces
> > of information, such as notes and times, to a text
> > file
> 
> While I think Andre has worked on 2), many of the
> features you mention 
> aren't in his initial plugin.  I don't think either
> of these are likely 
> to happen soon without additional effort.
> 
> > (3) the ability to show dependencies between tasks
> 
> > 
> > I know there's a plugin for item (3), but I've
> warned
> > that it doesn't preserve data across upgrades and
> > might have some other problems, so I've been a
> little
> > too intimidated to install it. Does anyone here
> know
> > what the known issues with it are?
> 
> Well, I wrote the plugin, so I guess I should answer
> this in more detail 
> than I gave you in IRC :)
> 
> The dependency plugin's UI is quite limited, it only
> shows dependencies 
> in a drop down in the detail view.  But if that's
> enough to satisfy your 
> use case, I think it's working now.
> 
> To make the dependency data last between upgrades of
> the software, and 
> to make the data share-able, a small amount of work
> would need to be 
> done.  The architecture is all there to do this,
> someone would just need 
> to implement it, which is straightforward.
> 
> Tell you what.  I'll try to add the necessary
> future-proofing as a quick 
> weekend project when I get back from vacation in
> early April.
> 
> Sincerely,
> Jeffrey
> 



      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs