I would like to make a new release of dia soon.  What we have in CVS has a
lot of bug fixes over 0.86.  So I have been tidying up a few
things.  These include:
  - linked up the new documentation to the menus for both gnome and non
    gnome builds.  Hans will probably need to adjust things for
    win32.  The relevant code is in app/commands.c(help_manual_callback),
    last 5 lines.
  - Make splash screen display correctly under x11.  It now waits until
    after the first exposure before continuing (which should work fine on
    win32 as well).
  - Add a --nosplash option for people who don't want a splash screen.
  - Fixed up the psprint print code so that it doesn't die on a SIGPIPE
    when you give an invalid printer command.  It will now show a dialog
    if any SIGPIPEs were received during printing.  This code is probably
    needs to be turned off for the win32 build.
  - fix up makefiles so that "make distcheck" completes.
  - fix up off by one error in beziershape_save which was adding an extra
    segment to beziergons during save.

Are there any showstopper problems people can see that would hold up a
release? (remember that there will always be another release).  I beleive
that what is in CVS fixes all the menu/locale issues, which was one of
those annoying bugs (gtk+ and gnome based menu code should act as
similarly as possible now).

On the topic of GTK+ 2.0, it is not yet the right choice for the x11 port,
as none of the gnome features will be able to be ported across for a
while.  At some point, we will branch dia so that we can port to gtk 2.0
while continuing to check in 1.2 bugfixes.  Is this the right time to
branch?  Note that branching early means that we will need to merge
changes between branches.

One thing which I would like to use in the gtk 2.0 update is the rewritten
dia canvas.  I changed it over to gtk 2.0, and filled in a few of the
missing features so that it actually does something.  If you want to try
it out, you will need a fairly recent build of gtk+ HEAD.  It is in the
dia-newcanvas module.  Currently it handles enter,leave and motion notify
events, and keyboard focus for canvas items, and the multiple view code
appears to be working okay.

James.

-- 
Email: [EMAIL PROTECTED]
WWW:   http://www.daa.com.au/~james/


Reply via email to