On Mon, 19 Mar 2001, Hans Breuer wrote:
> 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.
I don't want to force a release schedule for the win32 port. I was just
mentioning those changes I had made that I knew would be broken on
win32. Release when you are ready.
>
> 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 ...
I will tell Kevin to be a bit more careful when checking things in. I
can't remember the CVS incantation to convert a text file to a binary file
though. This is a bit strange though, as the cvswrappers file for GNOME
CVS has the following in it:
*.png -kb
which should make sure all png files get added as binary files.
> > - 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 ... :-)
> ]
The other option is to install ghostscript along with its print redirector
so you can have a windows printer that filters things through gs.
>
> > - 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?
Is there some other appropriate place to put this sort of stuff on win32
if $HOME is not set? In the user's profile somewhere (that seems like the
place where all the MS progs put things).
There are only 4 calls to g_get_home_dir() in dia, judging by a quick
grep. The call in preferences.c can probably be removed (I think
everyone's preferences have been migrated from ~/.diarc to ~/.dia/diarc),
and the code that uses it in app_procs.c could probably be moved to a
function in dia_dirs.c, localising the use even further. It would be
fairly easy to add a special case for win32 without $HOME in that file
then.
>
> >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.
Well, I have been posting gtk bug reports when I find problems. And
getting the new canvas up and running on gtk 2.0 helped find some
problems.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
