<html><head></head><body>Eric,<br>
<br>
So far everything I've tried on Cygwin works with the sockets version. That's
what I've been using for the last several days. I'll keep testing but I
think that from this point any problems I have will be module problems not
driver problems.<br>
<br>
Just a note, I've only been successful on WinNT. Win98 is not able to run
the XDRIVER. I'm looking into this, but its a cygwin thing, not a grass
issue.<br>
<br>
<br>
Malcolm<br>
<br>
Eric G. Miller wrote:<br>
<blockquote type="cite" cite="mid:20010219093422.A29256@calico.local"><pre wrap="">On Mon, Feb 19, 2001 at 04:15:06PM +0000, Markus Neteler wrote:<br></pre>
<blockquote type="cite"><pre wrap="">Hi all,<br><br>the sockets driver is maturing quickly. Question is if<br>we should make it default for the forthcoming 5.0.0<br>or not. <br><br> - we need a platform report about it's quality<br> o Linux: running well (better than fifos)<br> o SGI:<br> o Windows/Cygnus:<br> o FreeBSD:<br> o Solaris2.6/SUN: running well (better than fifos)<br> o Solaris8/SUN:<br> o Solaris/Intel:<br></pre></blockquote>
<pre wrap=""><!----><br>Yes, I'd like to hear a few more reports first. Does it work okay on<br>CygWin? and every other target platform?<br><br></pre>
<blockquote type="cite"><pre wrap=""> - what's missing (hi Eric)<br> - locks directory moved to $HOME/.grass5/ (?)<br></pre></blockquote>
<pre wrap=""><!----><br>Correct me if I'm wrong, but the global lock directory was only used for<br>monitors under the fifo scheme? The sockets code doesn't use/need any<br>such locks (drivers only handle one connection at a time -- all other<br>connections wait or are refused; users no longer share a limited<br>resource like fixed fifos).<br><br>However, I like the $HOME/.grass5/ directory for other reasons. There's<br>already the G_home(), so it's only a little bit of work to set up<br>element handling (e.g. subdirs). I want to make sure ~/.grass5 is chmod<br>4700 for a modicum of security. Is there a reason we might want it<br>readable by processes not owned by the $USER?<br><br></pre>
<blockquote type="cite"><pre wrap=""> - what's to be postponed to 5.1:<br> - scale in top line of monitor (?)<br></pre></blockquote>
<pre wrap=""><!----><br>In theory, this doesn't seem real hard (you already have put together<br>some working code). However, there's the problem where the server<br>process is never "informed" if a user changes region settings midstream.<br>So, somewhere there'd have to be a mechanism for requery/update of the<br>title bar.<br><br></pre>
<blockquote type="cite"><pre wrap=""> - auto-redraw when resizing (?)<br></pre></blockquote>
<pre wrap=""><!----><br>This seems to be more difficult, when you consider frames in addition to<br>the window itself. The current code just deletes everything from the<br>PAD list, clears the screen, and sets up a new pixmap buffer (if<br>necessary). It would be nice to have, and seems like it should be<br>doable. I think the resize code maybe needs to make a backup of the<br>PAD, and then try to recreate the commands after the resize. I don't<br>know?<br><br></pre>
<blockquote type="cite"><pre wrap="">I have the impression that the sockets driver is the last thing<br>missing for 5.0.0 (stable) except the few release-critical bugs in BUGS.<br>We won't be able to get G3D stable, so that will be postponed to<br>GRASS 5.1 (and left out of 5.0.0).<br></pre></blockquote>
<pre wrap=""><!----><br>I agree that the g3d stuff isn't really ready for prime time. There's<br>little that you can do with the data right now anyway, so maybe we give<br>it a hard look in 5.1?<br><br></pre>
<blockquote type="cite"><pre wrap="">What about the NVIZ troubles? I cannot reproduce Helena's problems.<br></pre></blockquote>
<pre wrap=""><!----><br>I dunno. Those compass marks make a big difference in understanding<br>what the controls are doing (thanks Bob).<br><br></pre>
</blockquote>
<br>
</body></html>
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'