Paul,
I figured some funky stuff out with how to manage menu properties and
visibility. This would be much nicer if we targeted 3.4 but I think we can
still make do. At the top of the plugin.xml you can see a couple of
additions. I added a property tester that accepts an IResource and tests
for some properties, our method of testing it is handled programmatically in
the property tester class. I added an expression definition which says
iterate over what you pass it, make sure they are IResource's and then call
the property tester to see if it's a git resource. The team menu has a
clause now that says with the current selection reference the definition I
created above.
Different definitions can be made, and this can be fine tuned later. For
example, you may wish a team menu to be visible if this is a git project,
but you might want the command handlers to be grayed out if the selected
resource has a certain git status.
http://linserv3.cims.nyu.edu:11000/changelog/OSP/?cs=430
--
Patrick
|
