Re: R: [GRASS-dev] WinGRASS Plans
hi, strange, when we started to develop the wx-gui, I just used my old laptop. it was celeron with 600 MHz and I had 192 MB RAM. It was usable j 2008/6/10 Marco Pasetti <[EMAIL PROTECTED]>: > Hy Glynn, > > did you ever estimated the speed of the Python GUI Vs a generic compiled > GUI? > > On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA > GPU with shared 64 MB VRAM) I noticed that, very often, just opening a > module GUI or a dialoge window caused the system to freeze for a while (XP > Pro SP2, 32bit, very well maintained). This said, all the other GUI parts, > such as the GIS Layer Manager and the Map Display, always worked very well, > and never (maybe rarely) freezed. > > Is that because the GUI is interpreted or is it only a Windows problem? > actually, many Windows native application GUIs frequently freeze, even if > they are compiled and not interpreted GUIs... > > Thanks for your precious explanations, as always.. :-) > > Marco > > - Original Message - From: "Glynn Clements" > <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: "Michael Barton" <[EMAIL PROTECTED]>; > Sent: Friday, June 06, 2008 6:37 PM > Subject: Re: R: [GRASS-dev] WinGRASS Plans > > >> >> [EMAIL PROTECTED] wrote: >> >>> Since we are talking about, why an interpretated language for the GUI >> >> It makes it easier for the user to customise the code, and to apply >> updates. >> >> -- >> Glynn Clements <[EMAIL PROTECTED]> > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Jachym Cepicky e-mail: jachym.cepicky gmail com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Hi Moritz, Just saw this: http://wxconfig.googlepages.com/ Maybe it can help you. Fantastic! It looks very promising! I'll try it. Many thanks Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Marco Pasetti wrote: > > Check carefully throughout your entire implementation of wxPython. > > For the Mac version, wx-config exists in the binaries, but in a > > place very different from it Linux location. > > I checked carefully. No wx-config file! > Remember that Mac is Unix-like, so it's normal that you have it, > even if in another location than on linux; while Windows it's > definetly another *place to live* :-) Apart from anything else, wx-config is a bash script, and most Windows systems don't have bash (and even if they do, they don't understand the #! mechanism used to run scripts on Unix). -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Marco, Just saw this: http://wxconfig.googlepages.com/ Maybe it can help you. Moritz On 13/06/08 20:34, Marco Pasetti wrote: Hi Michael, Check carefully throughout your entire implementation of wxPython. For the Mac version, wx-config exists in the binaries, but in a place very different from it Linux location. I checked carefully. No wx-config file! Remember that Mac is Unix-like, so it's normal that you have it, even if in another location than on linux; while Windows it's definetly another *place to live* :-) We'll solve it in another way, soon or later... Regards, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Re: R: [GRASS-dev] WinGRASS PlansHi Michael, >Check carefully throughout your entire implementation of wxPython. For the Mac >version, wx-config exists in the binaries, but in a place very different from >it Linux location. I checked carefully. No wx-config file! Remember that Mac is Unix-like, so it's normal that you have it, even if in another location than on linux; while Windows it's definetly another *place to live* :-) We'll solve it in another way, soon or later... Regards, Marco___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Marco, Check carefully throughout your entire implementation of wxPython. For the Mac version, wx-config exists in the binaries, but in a place very different from it Linux location. Michael On 6/12/08 3:23 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Michael, > >> >Maybe this is what you have in mind, but I think that the wx-config is only >> >needed for compiling vdigit, not for using it. Also, I'm pretty sure that if >> >you install the Windows dev package, it has wx-config. > > I downloaded the Windows dev package, but unfortunately it doesn't contain the > wx-config file; maybe because it has been built using MS Visual C++. I think > I'll need to build wxPython from source using MinGW to have the wx-config file > and, thus, build the new GRASS v.digit. > > I'll let you know. > > Regards, > > Marco > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: R: R: [GRASS-dev] WinGRASS Plans
Many thanks :-) Marco Da: Benjamin Ducke [mailto:[EMAIL PROTECTED] Inviato: gio 12/06/2008 14.42 A: [EMAIL PROTECTED] Cc: grass-dev@lists.osgeo.org Oggetto: Re: R: R: [GRASS-dev] WinGRASS Plans Here you go: this one taken from 2.8.4. But I really do not expect any major difference. Just adjust the version number in the script ... Ben [EMAIL PROTECTED] wrote: > Hi Michael, > > >maybe try and snatch a copy of the wx-config script > >from a Linux install, then just edit the variables in there > >to fit your MinGW/MSYS setup? > > yes! it could be a perfect soultion :) > > at the moment I suspended the wxWidgets support task for better times (I > read the documentation... too much work and uncertain solutions for the > moment...) > If the Linux script will woork ... good! otherwise I will delay the task. > > is there anyone outhere that could send me a linux wx-config script > please? wxPython version is 2.8.7.1 > > Many thanks, > > Marco > > > > *Da:* [EMAIL PROTECTED] per conto di Benjamin Ducke > *Inviato:* gio 12/06/2008 13.24 > *Cc:* grass-dev@lists.osgeo.org > *Oggetto:* Re: R: [GRASS-dev] WinGRASS Plans > > Confirmed: no wx-config script in the Windows bin package :( > > However, before you go through the pain of building the whole > thing with MinGW: maybe try and snatch a copy of the wx-config script > from a Linux install, then just edit the variables in there > to fit your MinGW/MSYS setup? > > Ben > > [EMAIL PROTECTED] wrote: > > Hi Michael, > > > > >Maybe this is what you have in mind, but I think that the wx-config is > > only > > >needed for compiling vdigit, not for using it. Also, I'm pretty sure > > that if > > >you install the Windows dev package, it has wx-config. > > > > I downloaded the Windows dev package, but unfortunately it doesn't > > contain the wx-config file; maybe because it has been built using MS > > Visual C++. I think I'll need to build wxPython from source using MinGW > > to have the wx-config file and, thus, build the new GRASS v.digit. > > > > I'll let you know. > > > > Regards, > > > > Marco > > > > > > > > > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > http://lists.osgeo.org/mailman/listinfo/grass-dev > > > -- > Benjamin Ducke > Senior Applications Support and Development Officer > > Oxford Archaeological Unit Limited > Janus House > Osney Mead > OX2 0ES > Oxford, U.K. > > Tel: +44 (0)1865 263 800 (switchboard) > Tel: +44 (0)1865 980 758 (direct) > Fax :+44 (0)1865 793 496 > [EMAIL PROTECTED] > > > > > -- > Files attached to this email may be in ISO 26300 format (OASIS Open > Document Format). If you have difficulty opening them, please visit > http://iso26300.info <http://iso26300.info/> <http://iso26300.info/> for > more information. > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- Benjamin Ducke Senior Applications Support and Development Officer Oxford Archaeological Unit Limited Janus House Osney Mead OX2 0ES Oxford, U.K. Tel: +44 (0)1865 263 800 (switchboard) Tel: +44 (0)1865 980 758 (direct) Fax :+44 (0)1865 793 496 [EMAIL PROTECTED] -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info <http://iso26300.info/> for more information. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: R: [GRASS-dev] WinGRASS Plans
Here you go:
this one taken from 2.8.4.
But I really do not expect any major difference.
Just adjust the version number in the script ...
Ben
[EMAIL PROTECTED] wrote:
Hi Michael,
>maybe try and snatch a copy of the wx-config script
>from a Linux install, then just edit the variables in there
>to fit your MinGW/MSYS setup?
yes! it could be a perfect soultion :)
at the moment I suspended the wxWidgets support task for better times (I
read the documentation... too much work and uncertain solutions for the
moment...)
If the Linux script will woork ... good! otherwise I will delay the task.
is there anyone outhere that could send me a linux wx-config script
please? wxPython version is 2.8.7.1
Many thanks,
Marco
*Da:* [EMAIL PROTECTED] per conto di Benjamin Ducke
*Inviato:* gio 12/06/2008 13.24
*Cc:* grass-dev@lists.osgeo.org
*Oggetto:* Re: R: [GRASS-dev] WinGRASS Plans
Confirmed: no wx-config script in the Windows bin package :(
However, before you go through the pain of building the whole
thing with MinGW: maybe try and snatch a copy of the wx-config script
from a Linux install, then just edit the variables in there
to fit your MinGW/MSYS setup?
Ben
[EMAIL PROTECTED] wrote:
> Hi Michael,
>
> >Maybe this is what you have in mind, but I think that the wx-config is
> only
> >needed for compiling vdigit, not for using it. Also, I'm pretty sure
> that if
> >you install the Windows dev package, it has wx-config.
>
> I downloaded the Windows dev package, but unfortunately it doesn't
> contain the wx-config file; maybe because it has been built using MS
> Visual C++. I think I'll need to build wxPython from source using MinGW
> to have the wx-config file and, thus, build the new GRASS v.digit.
>
> I'll let you know.
>
> Regards,
>
> Marco
>
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke
Senior Applications Support and Development Officer
Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.
Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
[EMAIL PROTECTED]
--
Files attached to this email may be in ISO 26300 format (OASIS Open
Document Format). If you have difficulty opening them, please visit
http://iso26300.info <http://iso26300.info/> for more information.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke
Senior Applications Support and Development Officer
Oxford Archaeological Unit Limited
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.
Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
[EMAIL PROTECTED]
--
Files attached to this email may be in ISO 26300 format (OASIS Open Document
Format). If you have difficulty opening them, please visit http://iso26300.info
for more information.
#!/bin/sh
#
# Name:wx-config{.in,}
# Purpose: wx configuration search and query tool {template,}
# Author: Ron <[EMAIL PROTECTED]>
# Modified by:
# Created: 8/9/2004
# RCS-ID: $Id: wx-config.in,v 1.132 2006/12/24 01:20:33 VZ Exp $
# Copyright: (c) 2004 Ron <[EMAIL PROTECTED]>
# Essentially a fresh start this time around, but for maximum
# compatibility basic code was taken from, and heavy reference
# made to, the previously unattributed wx-config from cvs.
# All the usual suspects contributed to the dicussion that led
# to this new work and likewise to the ideas and content in the
# original (which was probably influenced by gtk), among them:
# Robert Roebling, Vadim Zeitlin, Vaclav Slavik, Robin Dunn
# Licence: wxWindows licence
# Extra^2 debug mode, for if things ever get really weird.
[ -z "$WXDEBUG_X" ] || set -x
# On with some basic stuff, like the ability to die gracefully,
# and to tell people what we are about.
# --
# decho _message
# Output a message to stderr.
decho() { echo "$*" 1>&2; }
# usage _exitcode
# Outputs a usage message to stderr and exits with _exitcode.
# Try to keep this to a single page (ie. < 25 lines). We can add
# alternate or interactive help targets if people want more detail.
#
# Exit codes are now subject to a more strict interpretation.
# wx-config should return 0 upon success
R: R: [GRASS-dev] WinGRASS Plans
Hi Michael, >maybe try and snatch a copy of the wx-config script >from a Linux install, then just edit the variables in there >to fit your MinGW/MSYS setup? yes! it could be a perfect soultion :) at the moment I suspended the wxWidgets support task for better times (I read the documentation... too much work and uncertain solutions for the moment...) If the Linux script will woork ... good! otherwise I will delay the task. is there anyone outhere that could send me a linux wx-config script please? wxPython version is 2.8.7.1 Many thanks, Marco Da: [EMAIL PROTECTED] per conto di Benjamin Ducke Inviato: gio 12/06/2008 13.24 Cc: grass-dev@lists.osgeo.org Oggetto: Re: R: [GRASS-dev] WinGRASS Plans Confirmed: no wx-config script in the Windows bin package :( However, before you go through the pain of building the whole thing with MinGW: maybe try and snatch a copy of the wx-config script from a Linux install, then just edit the variables in there to fit your MinGW/MSYS setup? Ben [EMAIL PROTECTED] wrote: > Hi Michael, > > >Maybe this is what you have in mind, but I think that the wx-config is > only > >needed for compiling vdigit, not for using it. Also, I'm pretty sure > that if > >you install the Windows dev package, it has wx-config. > > I downloaded the Windows dev package, but unfortunately it doesn't > contain the wx-config file; maybe because it has been built using MS > Visual C++. I think I'll need to build wxPython from source using MinGW > to have the wx-config file and, thus, build the new GRASS v.digit. > > I'll let you know. > > Regards, > > Marco > > > > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev -- Benjamin Ducke Senior Applications Support and Development Officer Oxford Archaeological Unit Limited Janus House Osney Mead OX2 0ES Oxford, U.K. Tel: +44 (0)1865 263 800 (switchboard) Tel: +44 (0)1865 980 758 (direct) Fax :+44 (0)1865 793 496 [EMAIL PROTECTED] -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info <http://iso26300.info/> for more information. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Confirmed: no wx-config script in the Windows bin package :( However, before you go through the pain of building the whole thing with MinGW: maybe try and snatch a copy of the wx-config script from a Linux install, then just edit the variables in there to fit your MinGW/MSYS setup? Ben [EMAIL PROTECTED] wrote: Hi Michael, >Maybe this is what you have in mind, but I think that the wx-config is only >needed for compiling vdigit, not for using it. Also, I'm pretty sure that if >you install the Windows dev package, it has wx-config. I downloaded the Windows dev package, but unfortunately it doesn't contain the wx-config file; maybe because it has been built using MS Visual C++. I think I'll need to build wxPython from source using MinGW to have the wx-config file and, thus, build the new GRASS v.digit. I'll let you know. Regards, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev -- Benjamin Ducke Senior Applications Support and Development Officer Oxford Archaeological Unit Limited Janus House Osney Mead OX2 0ES Oxford, U.K. Tel: +44 (0)1865 263 800 (switchboard) Tel: +44 (0)1865 980 758 (direct) Fax :+44 (0)1865 793 496 [EMAIL PROTECTED] -- Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: [GRASS-dev] WinGRASS Plans
Hi Michael, >Maybe this is what you have in mind, but I think that the wx-config is only >needed for compiling vdigit, not for using it. Also, I'm pretty sure that if >you install the Windows dev package, it has wx-config. I downloaded the Windows dev package, but unfortunately it doesn't contain the wx-config file; maybe because it has been built using MS Visual C++. I think I'll need to build wxPython from source using MinGW to have the wx-config file and, thus, build the new GRASS v.digit. I'll let you know. Regards, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Marco Pasetti wrote: > did you ever estimated the speed of the Python GUI Vs a generic compiled > GUI? > > On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA > GPU with shared 64 MB VRAM) I noticed that, very often, just opening a > module GUI or a dialoge window caused the system to freeze for a while (XP > Pro SP2, 32bit, very well maintained). This said, all the other GUI parts, > such as the GIS Layer Manager and the Map Display, always worked very well, > and never (maybe rarely) freezed. > > Is that because the GUI is interpreted or is it only a Windows problem? > actually, many Windows native application GUIs frequently freeze, even if > they are compiled and not interpreted GUIs... If you're talking about standalone GUIs (i.e. running a module from the command-line with --ui, or with no arguments when it needs some), that's probably the overhead of starting up the Python interpreter, initialising the libraries, etc. I wouldn't expect that to be an issue when creating dialogs from within the wxPython GUI. In any case, using C/C++ for the GUI is a non-starter. The advantages of being able to modify the code (whether for ongoing development or for local customisations) without needing to re-compile everything far outweigh any performance issues. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Hy Glynn, did you ever estimated the speed of the Python GUI Vs a generic compiled GUI? On my old Notebook (AMD Athlon64 3000+, 1.25 GB RAM DDR, integrated NVIDIA GPU with shared 64 MB VRAM) I noticed that, very often, just opening a module GUI or a dialoge window caused the system to freeze for a while (XP Pro SP2, 32bit, very well maintained). This said, all the other GUI parts, such as the GIS Layer Manager and the Map Display, always worked very well, and never (maybe rarely) freezed. Is that because the GUI is interpreted or is it only a Windows problem? actually, many Windows native application GUIs frequently freeze, even if they are compiled and not interpreted GUIs... Thanks for your precious explanations, as always.. :-) Marco - Original Message - From: "Glynn Clements" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Michael Barton" <[EMAIL PROTECTED]>; Sent: Friday, June 06, 2008 6:37 PM Subject: Re: R: [GRASS-dev] WinGRASS Plans [EMAIL PROTECTED] wrote: Since we are talking about, why an interpretated language for the GUI It makes it easier for the user to customise the code, and to apply updates. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
Marco, You can read the history of the discussions that led to wxPython on the GRASS WIKI. Michael On 6/6/08 1:04 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Glynn, > > Thanks for the explanation. > Since we are talking about, why an interpretated language for the GUI and not, > for example, QT-OpenSource (that is compiled, cross-platform, GPL and has also > Python bindings)? It's not a critic, just curiosity ;-) > > Marco > > PS: I didn't ignore your last e-mail about locking on Win; I'm just waiting to > finish the new MSYS environment and then work again on the GRASS code... > > > > Da: Glynn Clements [mailto:[EMAIL PROTECTED] > Inviato: ven 06/06/2008 3.19 > A: [EMAIL PROTECTED] > Cc: Michael Barton; grass-dev@lists.osgeo.org > Oggetto: Re: [GRASS-dev] WinGRASS Plans > > > > Marco Pasetti wrote: > >>> > > Maybe this is what you have in mind, but I think that the wx-config is >>> > > only >>> > > needed for compiling vdigit, not for using it. >> > >> > Good! sorry, confused: I always thought that Python was an interpreted >> > language. > > It is. But it also supports extension through binary modules > (libraries) written in e.g. C or C++. > >> > I don't know anything about the new vdigit: does it have some C or >> > C++ code parts to be compiled in Python? > > The vdigit module has a mixture of C++ and Python code. The C++ code > is compiled into a binary module (.so, .dll); you need to configure > with --with-wxwidgets, which needs wx-config to get the compilation > and linking switches for the C++ code. > > -- > Glynn Clements <[EMAIL PROTECTED]> > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: R: [GRASS-dev] WinGRASS Plans
[EMAIL PROTECTED] wrote: > Since we are talking about, why an interpretated language for the GUI It makes it easier for the user to customise the code, and to apply updates. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: [GRASS-dev] WinGRASS Plans
Michael, sorry, forgot my last question; Martin already solved it. Thanks Marco Da: [EMAIL PROTECTED] per conto di [EMAIL PROTECTED] Inviato: ven 06/06/2008 10.17 A: Michael Barton; grass-dev@lists.osgeo.org Oggetto: R: [GRASS-dev] WinGRASS Plans Michael, >Yes. That's it. Perfect. Thanks ;-) Just another thing: If I intended correctly, the dev is needed only for compile the C++ code in v.digit, while the *normal* release suffices to run it (since it has been compiled using the dev), right? Marco Da: Michael Barton [mailto:[EMAIL PROTECTED] Inviato: ven 06/06/2008 8.25 A: [EMAIL PROTECTED]; grass-dev@lists.osgeo.org Oggetto: Re: [GRASS-dev] WinGRASS Plans Yes. That's it. Michael On 6/5/08 4:54 PM, "Marco Pasetti" <[EMAIL PROTECTED]> wrote: > Michael, > >> Also, I'm pretty sure that if >> you install the Windows dev package, it has wx-config. > > I'm so stupid (or only tired?)!! > > wxPython, obviously, not Python! > > From the wxpython.org download page, Microsoft Windows section: > -- > If you have a need to compile other Python extension modules or applications > that link with the same version of the wxWidgets DLL that wxPython does, > then you will want to get the development package. It includes a snapshot of > the wx headers and the import libraries found on my system when I made the > wxPython binaries. > > wxPython2.8-win32-devel > -- > > I should download that package, right? > > Marco > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: [GRASS-dev] WinGRASS Plans
Michael, >Yes. That's it. Perfect. Thanks ;-) Just another thing: If I intended correctly, the dev is needed only for compile the C++ code in v.digit, while the *normal* release suffices to run it (since it has been compiled using the dev), right? Marco Da: Michael Barton [mailto:[EMAIL PROTECTED] Inviato: ven 06/06/2008 8.25 A: [EMAIL PROTECTED]; grass-dev@lists.osgeo.org Oggetto: Re: [GRASS-dev] WinGRASS Plans Yes. That's it. Michael On 6/5/08 4:54 PM, "Marco Pasetti" <[EMAIL PROTECTED]> wrote: > Michael, > >> Also, I'm pretty sure that if >> you install the Windows dev package, it has wx-config. > > I'm so stupid (or only tired?)!! > > wxPython, obviously, not Python! > > From the wxpython.org download page, Microsoft Windows section: > -- > If you have a need to compile other Python extension modules or applications > that link with the same version of the wxWidgets DLL that wxPython does, > then you will want to get the development package. It includes a snapshot of > the wx headers and the import libraries found on my system when I made the > wxPython binaries. > > wxPython2.8-win32-devel > -- > > I should download that package, right? > > Marco > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
R: [GRASS-dev] WinGRASS Plans
Hi Glynn, Thanks for the explanation. Since we are talking about, why an interpretated language for the GUI and not, for example, QT-OpenSource (that is compiled, cross-platform, GPL and has also Python bindings)? It's not a critic, just curiosity ;-) Marco PS: I didn't ignore your last e-mail about locking on Win; I'm just waiting to finish the new MSYS environment and then work again on the GRASS code... Da: Glynn Clements [mailto:[EMAIL PROTECTED] Inviato: ven 06/06/2008 3.19 A: [EMAIL PROTECTED] Cc: Michael Barton; grass-dev@lists.osgeo.org Oggetto: Re: [GRASS-dev] WinGRASS Plans Marco Pasetti wrote: > > Maybe this is what you have in mind, but I think that the wx-config is > > only > > needed for compiling vdigit, not for using it. > > Good! sorry, confused: I always thought that Python was an interpreted > language. It is. But it also supports extension through binary modules (libraries) written in e.g. C or C++. > I don't know anything about the new vdigit: does it have some C or > C++ code parts to be compiled in Python? The vdigit module has a mixture of C++ and Python code. The C++ code is compiled into a binary module (.so, .dll); you need to configure with --with-wxwidgets, which needs wx-config to get the compilation and linking switches for the C++ code. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Marco, 2008/6/6 Marco Pasetti <[EMAIL PROTECTED]>: > Michael, > >> Maybe this is what you have in mind, but I think that the wx-config is >> only >> needed for compiling vdigit, not for using it. > > Good! sorry, confused: I always thought that Python was an interpreted > language. I don't know anything about the new vdigit: does it have some C or > C++ code parts to be compiled in Python? you need to compile Python extension (written in C++) located in gui/wxpython/vdigit. Python just loads this extension when vector digitizer is started. Martin -- Martin Landa * http://gama.fsv.cvut.cz/~landa * ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Yes. That's it. Michael On 6/5/08 4:54 PM, "Marco Pasetti" <[EMAIL PROTECTED]> wrote: > Michael, > >> Also, I'm pretty sure that if >> you install the Windows dev package, it has wx-config. > > I'm so stupid (or only tired?)!! > > wxPython, obviously, not Python! > > From the wxpython.org download page, Microsoft Windows section: > -- > If you have a need to compile other Python extension modules or applications > that link with the same version of the wxWidgets DLL that wxPython does, > then you will want to get the development package. It includes a snapshot of > the wx headers and the import libraries found on my system when I made the > wxPython binaries. > > wxPython2.8-win32-devel > -- > > I should download that package, right? > > Marco > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Marco Pasetti wrote: > > Maybe this is what you have in mind, but I think that the wx-config is > > only > > needed for compiling vdigit, not for using it. > > Good! sorry, confused: I always thought that Python was an interpreted > language. It is. But it also supports extension through binary modules (libraries) written in e.g. C or C++. > I don't know anything about the new vdigit: does it have some C or > C++ code parts to be compiled in Python? The vdigit module has a mixture of C++ and Python code. The C++ code is compiled into a binary module (.so, .dll); you need to configure with --with-wxwidgets, which needs wx-config to get the compilation and linking switches for the C++ code. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Michael, Maybe this is what you have in mind, but I think that the wx-config is only needed for compiling vdigit, not for using it. Good! sorry, confused: I always thought that Python was an interpreted language. I don't know anything about the new vdigit: does it have some C or C++ code parts to be compiled in Python? Also, I'm pretty sure that if you install the Windows dev package, it has wx-config. Windows dev package? I always used the *normal* installers; do you mean from here http://www.python.org/dev/daily-msi/? BTW, I'm sure that the *normal* installer doesn't include the wx-config. Just trying to save you some work. Thank you very much. I really appreciate that ;-) I don't have anyone in my lab currently using Vista for testing. There will be some students once we all come back for classes in mid-August. OK. I'll try to do that with my XP notebook. Thanks, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Markus, That's not needed. You can compile with: cd grass-addons/raster/r.sun_horizon/ make MODULE_TOPDIR=$HOME/grass64/ This will compile it into the main GRASS code tree. very good! Thanks the last thing I have to check (when I'll finish to build all) is where the binaries will be created. I'll see when I'll try to build one. Then I'll need to create a script to automatically build all the addons in the repository. I will work on it. Thanks, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Marco, Maybe this is what you have in mind, but I think that the wx-config is only needed for compiling vdigit, not for using it. Also, I'm pretty sure that if you install the Windows dev package, it has wx-config. Just trying to save you some work. I don't have anyone in my lab currently using Vista for testing. There will be some students once we all come back for classes in mid-August. Michael On 6/5/08 12:59 PM, "Marco Pasetti" <[EMAIL PROTECTED]> wrote: > Hi Michael, > >> You can get wxPython as an installable binary for Windows from the >> wxPython >> site. No need to compile Python from source. > > yes, I know that > (http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#wxPython), > but I cannot enable the wxWidgets support (--with-wxwidgets=path/wx-config), > because the wx-config file is available only if I built wxPython from > source. > > This said, I'm finishing the Vista build, but I need help for testings. Do > you have some students *available* to make cross testings on both XP and > Vista? I could test the build on Vista by myself, while on XP it's more > difficult for me (I still have the old XP notebook, but I don't work at > home, and I cannot keep 2 notebooks travelling..) > > Thanks, > > Marco > > > - Original Message ----- > From: "Michael Barton" <[EMAIL PROTECTED]> > To: > Sent: Thursday, June 05, 2008 9:40 PM > Subject: Re: [GRASS-dev] WinGRASS Plans > > >> >> >> >> On 6/5/08 9:00 AM, "[EMAIL PROTECTED]" >> <[EMAIL PROTECTED]> wrote: >> >>> >>> In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: >>> compile >>> with wx for wx gui v.digit replacement >>> 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? >>> >> >> You can get wxPython as an installable binary for Windows from the >> wxPython >> site. No need to compile Python from source. >> >> Mihcael >> __ >> Michael Barton, Professor of Anthropology >> Director of Graduate Studies >> School of Human Evolution & Social Change >> Center for Social Dynamics & Complexity >> Arizona State University >> >> phone: 480-965-6213 >> fax: 480-965-7671 >> www: http://www.public.asu.edu/~cmbarton >> >> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev > __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
[EMAIL PROTECTED] wrote: > In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: > compile with wx for wx gui v.digit replacement > 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. The GUI *should* work with the official Windows (and MacOSX) releases of Python and wxPython. If it doesn't, that needs to be fixed; requiring a "custom" version of either isn't acceptable. That includes the vdigit module. -- Glynn Clements <[EMAIL PROTECTED]> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
On Thu, Jun 5, 2008 at 3:20 PM, <[EMAIL PROTECTED]> wrote: [ great stuff skipped] ... > 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. I feel that the *build* procedure is pretty dependent on the GRASS build procedure. But that's no problem: > 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? That's not needed. You can compile with: cd grass-addons/raster/r.sun_horizon/ make MODULE_TOPDIR=$HOME/grass64/ This will compile it into the main GRASS code tree. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
Hi Michael, You can get wxPython as an installable binary for Windows from the wxPython site. No need to compile Python from source. yes, I know that (http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#wxPython), but I cannot enable the wxWidgets support (--with-wxwidgets=path/wx-config), because the wx-config file is available only if I built wxPython from source. This said, I'm finishing the Vista build, but I need help for testings. Do you have some students *available* to make cross testings on both XP and Vista? I could test the build on Vista by myself, while on XP it's more difficult for me (I still have the old XP notebook, but I don't work at home, and I cannot keep 2 notebooks travelling..) Thanks, Marco - Original Message - From: "Michael Barton" <[EMAIL PROTECTED]> To: Sent: Thursday, June 05, 2008 9:40 PM Subject: Re: [GRASS-dev] WinGRASS Plans On 6/5/08 9:00 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: compile with wx for wx gui v.digit replacement 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? You can get wxPython as an installable binary for Windows from the wxPython site. No need to compile Python from source. Mihcael __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] WinGRASS Plans
On 6/5/08 9:00 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: compile > with wx for wx gui v.digit replacement > 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? > You can get wxPython as an installable binary for Windows from the wxPython site. No need to compile Python from source. Mihcael __ Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution & Social Change Center for Social Dynamics & Complexity Arizona State University phone: 480-965-6213 fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] WinGRASS Plans
Hi all, I would like to talk with you about new ideas/changes related to the WinGRASS Project: ITEM 1 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. Since now (I'm still building) I introduced the following changes: - added the libjpeg support (specially needed for QGIS, actually) - upgraded libpng from the 1.2.24 to the 1.2.29 release - upgraded GSL from the 1.9 to the 1.11 release (actually, only another QGIS requirement) - upgraded PostgreSQL from the 8.2.6 to the 8.3.1 release - upgraded SQLite from the 3.5.6 to 3.5.9 release then I planned to add: - AVCE00 and E00Compr Libraries (built from source, see here for the license: http://avce00.maptools.org/avce00/avce00.html#license) for the v.in.e00 module - GPSBABEL (prebuilt binaries, released under GPL; see http://www.gpsbabel.org/download.html) for the v.in.gpsbabel module - FFMPEG (built from source; it is released under LGLP/GPL; see http://ffmpeg.mplayerhq.hu/legal.html) for the 3D NVIZ animations - gettext (GNU GPL?) for the nls GRASS support any suggestions? what should I add more? In the WinGRASS Current Status Wiki (ToDo -> Dependencies) I read: compile with wx for wx gui v.digit replacement 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? ITEM 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 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 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. ITEM 3 I would like to add some images and *icons* to the WinGRASS web page, as done here http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html, and change the page structure such as the web-page of GRASS on MacOSX (http://grass.osgeo.org/grass63/binary/macosx/), 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) 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 ITEM 4 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. ITEM 4 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. 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? Thanks for all your patience, Marco ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
