| [corona-dev] PCX UI behavior |
|
Do you think that the following solutions in user interface are
fine?: 1. a workbench project (WP) participates in collaboration if
it is "activated" for Corona, i.e. either it has been "Add
nature" from Project collaboration or it has been checked out from PCX
view 2. Corona plugin maintains the list of "activated"
WPs (not yet implemented) 3. In PCX we have (now partially implemented): a.
open action for project container (PC), the action prompts if it should open WPs
(only activated for Corona) -
if at least one WP (activated) has not been opened successfully, it displays a
warning -
? what if there are repositories of workbench project type that are not
assigned to any WP ? b.
display action is available for PC, the action opens PCV view, open action does
not display PCV c.
open / checkout action for WP (also invoked on double click) -
opens the WP if the project is activated -
checks out the WP from CVS, if the project is unavailable -
enables Corona if a project exists but it is not activated, prompting to
confirm CVS settings d.
related containers are displayed as grayed if they are not available e.
PC properties are not displayed in PCX The package ...project.container.explorer contains the
current work in progress for PCX. Comments are welcomed. Pawel |