<HTML dir=ltr><HEAD>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6001.18023" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#000000 size=2>Hi all,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I would like to talk with you about new ideas/changes related to the WinGRASS Project:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>ITEM 1</FONT></DIV>
<DIV><FONT face=Arial size=2>--------------------------------</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I bought a new notebook with Vista installed, and I'm building a new MSYS environment (+ GRASS, obviously) on it; I hope that future testings will confirm that the binaries built here will be fine for both XP and Vista.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Since now (I'm still building) I introduced the following changes:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>- added the libjpeg support (specially needed for QGIS, actually)</FONT></DIV>
<DIV><FONT face=Arial size=2>- upgraded libpng from the 1.2.24 to the 1.2.29 release</FONT></DIV>
<DIV><FONT face=Arial size=2>- upgraded GSL from the 1.9 to the 1.11 release (actually, only another QGIS requirement)</FONT></DIV>
<DIV><FONT face=Arial size=2>- upgraded PostgreSQL from the 8.2.6 to the 8.3.1 release</FONT></DIV>
<DIV><FONT face=Arial size=2>- upgraded SQLite from the 3.5.6 to 3.5.9 release</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>then I planned to add:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>- AVCE00 and E00Compr Libraries (built from source, see here for the license: <A href="http://avce00.maptools.org/avce00/avce00.html#license">http://avce00.maptools.org/avce00/avce00.html#license</A>) for the v.in.e00 module</FONT></DIV>
<DIV><FONT face=Arial size=2>- GPSBABEL (prebuilt binaries, released under GPL; see <A href="http://www.gpsbabel.org/download.html">http://www.gpsbabel.org/download.html</A>) for the v.in.gpsbabel module</FONT></DIV>
<DIV><FONT face=Arial size=2>- FFMPEG (built from source; it is released under LGLP/GPL; see <A href="http://ffmpeg.mplayerhq.hu/legal.html">http://ffmpeg.mplayerhq.hu/legal.html</A>) for the 3D NVIZ animations</FONT></DIV>
<DIV><FONT face=Arial size=2>- gettext (GNU GPL?) for the nls GRASS support</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>any suggestions? what should I add more?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read:</FONT><FONT face=Arial size=2> compile with wx for wx gui v.digit replacement</FONT></DIV>
<DIV><FONT face=Arial size=2>IIRC, to enable wxWidgets in the MSYS build we need a compiled (not prebuilt) version of Python, but, at the moment, it's not possible to compile Python under MSYS/MinGW. Is it (or will it be) strictly necessary to build the new v.digit module?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>ITEM 2</FONT></DIV>
<DIV><FONT face=Arial size=2>--------------------------------</FONT></DIV></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial><FONT size=2>Since now, the WinGRASS installer comes with a README html file built in. That file is the same published on the GRASS website; that means that we actually have a <FONT color=#000000>redundant replication in our SVN: the same file in /root/grass-web/trunk/grass63/mswindows/native and in /root/grass/branches/develbranch_6/mswindows/Extras</FONT></FONT></FONT></DIV>
<DIV>
<DIV><FONT face=Arial size=2>I would like to remove the REAME.html file from the installer (and thus from the grass/..../Extras folder) and replace it with an http link to the README.html into the GRASS web site. Thus we will remove the redundant replication and I will avoid the problem to always check the differences from those two files.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>ITEM 3</FONT></DIV>
<DIV><FONT face=Arial size=2>--------------------------------</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I would like to add some images and *icons* to the WinGRASS web page, as done here <A href="http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html">http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html</A>, and change the page structure such as the web-page of GRASS on MacOSX (<A href="http://grass.osgeo.org/grass63/binary/macosx/">http://grass.osgeo.org/grass63/binary/macosx/</A>), moving the *download section* from the top of the page to the main html document itself (that also means that I'll probably need to rename it from README.html to index.html, but it depends on the current apache settings)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Then it would be good to also add a *Binary Revision History* section where to explain the changes occurred between the different GRASS binary releases</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>ITEM 4</FONT></DIV>
<DIV><FONT face=Arial size=2>--------------------------------</FONT></DIV>
<DIV> </DIV>
<DIV>Since I'm very short of spare time, but the GRASS BuildFromSource document is a relevant documentation for the GRASS community, I think that I could move the Building Guide directly into the grass-web mswindows folder, waiting for better times when I'll definetely put it into the official wiki.</DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>ITEM 4</FONT></DIV>
<DIV><FONT face=Arial size=2>--------------------------------</FONT></DIV>
<DIV> </DIV>
<DIV>Since Windows users cannot build binaries by themselves, it would be good to build and distribute also the GRASS AddOns. I'm not sure now how to distribute them (even if I've got some WIP ideas), but I surely need to create a simple procedure to build and install them all in a separated directory, with a build procedure indipendent from the GRASS build procedure itself.</DIV>
<DIV> </DIV>
<DIV>Since now I built addons putting the sources in the GRASS source tree and adding the addons to build in the general make files (for example adding r.horizon into the list of building modules in /raster/Makefile). But if I put the addons sources outside the main GRASS source tree, I would need to change the paths from relative to absolute in each module, and then create a Makefile for each addon module... too much work for a frequent task! Any suggestions?</DIV>
<DIV> </DIV>
<DIV>Thanks for all your patience,</DIV>
<DIV> </DIV>
<DIV>Marco</DIV></DIV></FONT></DIV></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>