Re: improving the cvs UI

Jens,

>Jerzy, what are your thoughts about leveraging this approach to provide
>a more GUI like output?

My thoughts are mixed.

Even though it looks like a good idea at first I have the strong feeling
that it will lead to abuse in the form of constant "refreshing" in order to
get the visual feedback which people don't really need to work with CVS...

>I could imagine a window being created for each cvs operation you do
>(unless there just is no output at all).

We have discussed something like that already, a sort of "basket" to drop
the files from command output, file view or even file manager. It will
appear only in the next version if ever.

Another approach would be to implement the CVSNT Lockserver client protocol:
http://www.cvsnt.org/wiki/LockServerProtocol

That would give the real live information in an effective way as people
would not have to poll the server for information.

Best Regards,
Jerzy

----- Original Message ----- 
From: Jens Miltner
To: [email protected]
Sent: Thursday, February 05, 2004 13:01
Subject: [cvsgui-dev] improving the cvs UI



Am 05.02.2004 um 13:12 schrieb Oliver Giesen on the cvsgui list:

> There once existed a patched WinCvs 1.3b5 under the name of MGMAddon
> (http://mgmaddon.sf.net) which implemented a feature called "command
> output visualizing" (http://mgmaddon.sf.net/cvs_output.htm) which, when
> combined with Query Update or Status could be used as a kind of "update
> preview". It basically presented the result of certain commands
> (checkout, export, update and status) in a new _static_ file view
> window. I think that was a nice idea.

Wow, I didn't know this exists...
Jerzy, what are your thoughts about leveraging this approach to provide
a more GUI like output? One of the things I'm sorely missing in MacCvs
is the ability to e.g. select a conflicting/locally modified/updated
etc. file directly from the cvs output and do a diff, or open it in my
editor to fix the conflict.
Right now, one would need to go to the browser, either turn on flat
mode with the appropriate filters, or browse to the file location and
then one can perform operations on the file. While this is not _all_
that much work, it's enough to wish I could directly interact with the
cvs output.

This approach seems to provide a good basis for improving the display
of the cvs output...

I could imagine a window being created for each cvs operation you do
(unless there just is no output at all). Of course, this might be an
option, so if you happen to like the console output for some reason or
other, you could keep it with plain console output...
The advantage of having one output window per operation is that you
could easily keep parts of the output for a while, but discard others
that are not interesting, you'd have a quick overview of which command
caused which output, etc.
Not that you couldn't get all this information from the console, too,
but as the web page above mentions, the console style output lacks a
lot of the direct interoperability and organization of a 'modern' UI
output...

</jum>

P.S.: it's okay if we implement this only after you're finished with
your release ;-)


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/