Adam wrote:
>>* I had trouble getting the project filters to work, for example, when I hid
>>:services but left :services:webservice shown.
What were trying to do here? The current implementation assumes that if you
were hiding services, that you wanted everything underneath it hidden as well,
tasks and projects. Should the project filter be displayed as a tree and/or
should it highlight the children to better indicate that they will be hidden?
>>* What would you use favourites for? Is there something missing from the
>>build file, such that you can declare this (or some of it) in the build file
>>instead, and thereby share it with everyone?
We currently have over 40 projects and foresee this becoming much larger in the
future. Our developers tend to work within a subset of maybe 3 to 5 (gradle)
projects at a time – often only caring about a single specific task within
certain projects. Favorites was meant to allow a developer to easily focus on
what's currently important to them without having to scroll through a giant
tree. This probably won't be a static list, but will change as they change
assignments. As such, nothing would need to be done to the build file.
One other factor is the time it takes to do a full build on our system. Since
it is substantial, we don't always want to do a full build. Hence, we focus on
a few tasks at a time.
Mike
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
