Hi James,
I like the idea of synchronizing the Dia release for the major platforms,
but will probably be unable to test the required hacking until the next
weekend. But please read on.
At 23:09 17.03.01 +0800, James Henstridge wrote:
>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.
Done. But there is a problem with all the png in Dia's cvs. To be readable
on win32 they need to be marked as binary files in cvs. Otherwise the nice
LF -> CR,LF translation takes place ...
> - 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).
Works fine now. Simply required a Gtk Expert :-)
> - 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.
All your signal code isn't compileable with msvc, but it is not needed on
windoze anymore anyway. I've changed the - never working - pipe execution
to something more appropriate for windoze. Direct writing to the default
printer.
[
It is to introduce the next Win User FAQ:
Q: When printing I get many pages of text starting with:
%!PS-Adobe-2.0. What to do?
A: Buy a postscript printer or implement GDI printing ... :-)
]
> - 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).
>
Not that I know of despite the never ending you-need-a-home-dir-faq ...
Maybe it should be simply ignored and translated subdir of the installation
dir?
>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.
>
IHMO we now could wait for the API freeze as well, but waiting much longer
may lead to a frozen api, which lacks some highly needed capabilities.
Additionally porting and using one of the mayor apps early could probably
improve Gtk-2.0 release stability a lot.
Have fun,
Hans
-------- Hans "at" Breuer "dot" Org -----------
Tell me what you need, and I'll tell you how to
get along without it. -- Dilbert
