infrequent grumblings of a software engineer and then some… (also some Delphi programming)

“Build Custom ChangeLog” with advanced GUI committed (preview)

Posted by tier777 on 2005-09-12

Here’s what you’ll most likely get with WinCvs 2.0.3 (not scheduled for release yet):

New "Build Custom ChangeLog" dialog

from cvsgui/ChangeLog (rev 1.950):

Mon Sep 12 2005  Oliver Giesen <ogware AT gmx DOT net>
* WinCvs 2.0.3 / Macros:
  - SafeTk: added generic base classes for creating Tk-based macros
  - cvs2clTk: added new experimental Tk-GUI version of advanced ChangeLog macro
               (replaces old CvsAlert-based version when Tk is available)
  - cvs2cl: moved Build ChangeLog selection macros onto their own menu
  - cvs2cl: added options to omit authors and/or files from ChangeLog
             (not yet available for command line version)
  - cvs2cl: very long lines are now wrapped even when there already are line
             breaks in the original log message;
             default wrap point for these is currently at 100 characters
  - RecursiveAddTk: improved error reporting
  - added new component for experimental/new macros to installer and made new and
     old macros sub-components of the Macros component

If you want to try it out now (it also works with WinCvs as long as you don’t try to use the non-Tk version of the Custom ChangeLog macro), here’s what you’ll need to checkout/download from the CVSGUI repository:

(note that the ViewCvs server usually lags behind a few hours – if the revisions given above are not there yet, just try again a little later or, if you have developer access, just get them via SSH) now also contains a set of generic base classes that could be used to build Tkinter-based WinCvs macros with advanced GUIs. I will probably write up a little post about how to use this when I get some time. For now, just take a look at the above Build Custom ChangeLog macro (i.e. which was already built from those classes.

Another thing that I’m rather fond of in this new macro is that it works by invoking another macro. This was to separate the GUI from the actual functionality, especially considering that also works as a standalone command line tool. A rather handy concept, I found. There are a few gotchas though. More on that also later (hopefully).




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: