Users in the FFJ user test would like the option to see all feedback from
their CVS actions, not only those that result in errors. Currently, successful
CVS actions are indicated by short feedback in the status area of the main
window, and doesn't provide any details that the user may require when working
with large numbers of files.
Suggestion would be to pipe all CVS output to the output window and display it
after a CVS action has been selected.
That's a good idea.
Now, a "Debugging" property exists in CVS FS - > Customizer.
IT prints all error output and command(s) which is performed.
In future there should appear a property allowed print all standart output.
(BTW: the printing into Output window makes IDE terribly slow)
I'd like to ask UI team how this functionality should be accessible to users?
IMHO:It could be one of the property of
CVS FS (customizer) or it could be also depending on property
"Ask for advance options".
the vcscvs module should consider following closely the ui that is being
developed around the javacvs module. many of these issues are being addressed
there and the behavior should be consistent between the two.
as it stands now the current design approach is to have each command have a
property for extended options. if true then when the user clicks of the command
a dialog opens that allows the user to set flags for the command before the
command is issued. if the property is false then whatever flags were set
(either by the user or from default or some .rc file) the command is issued
straight away without the dialog. additionally, if false the user can still get
to the dialog with a ctrl+click on the command.
to reitterate from the top, it's really important that general behavior and ui
between javacvs and vcscvs be the same -consistency for the user and all
Automaticaly changed Version from "Other" to "Dev"
Version "Other" is nonsence
Fixed in NBdev, and NB32
Now you can see commands output from RunTime TAB in Explorer -> VCS Commands ->
under the appropriate node of CVS FS. Here is the history of run commands.
On a commands double clisk to open its output history.
Target milestone -> 3.2