> I would hope to get any significant problems with Windows (other than > monitor drivers) sorted out for the 6.3.0 release.
The few remaining things on my list include: - r.los crashes on Win32 - progress bars do not work in module forms (get filled to 100% when the process finishes) - fiddling with the system paths in grass63.bat is too difficult. Would be better if the user needed to set only one variable to where GRASS is installed and everything else gets figured out from there. Even better would be if grass63.bat could set the paths relative to its own position in the filesystem, so that the user does not need to edit it at all. - I also find it annoying that gis.m starts up in the foreground and blocks command line input until you quit it. ... all not a real reason to delay the release of 6.3.0 though, I'd think. I can now confirm that NVIZ works fine with open source Tcl/Tk. Cheers, Benjamin > >> Thanks again, everyone, for all the support in getting these things >> figured out. I think a really smooth version of GRASS on Windows is >> just a matter of a bit of fine-tuning (and getting the Win sockets >> thing figured out) now. > > I'm not sure whether it's worth the effort; standalone monitors will > disappear altogether for 7.x. Anyone who has a desperate need for them > on Windows can always use Cygwin (where they work fine). > -- Benjamin Ducke, M.A. Archäoinformatik (Archaeoinformation Science) Institut für Ur- und Frühgeschichte (Inst. of Prehistoric and Historic Archaeology) Christian-Albrechts-Universität zu Kiel Johanna-Mestorf-Straße 2-6 D 24098 Kiel Germany Tel.: ++49 (0)431 880-3378 / -3379 Fax : ++49 (0)431 880-7300 www.uni-kiel.de/ufg _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
