Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

Tried that and it seems to be ignored too. Here is the output from a terminal 
in the shell (outside GRASS):

Last login: Thu Jul 27 22:04:37 on ttys001
CMB-MacBook-Pro:~ cmbarton$ echo $GRASS_PYTHON
/Applications/anaconda/bin/python

This should make anaconda python (2.7.13) the default.

But here is the output from a GRASS terminal:

GRASS 7.3.svn (nc_spm_08_grass7):~ > echo $GRASS_PYTHON
python
GRASS 7.3.svn (nc_spm_08_grass7):~ > python
Python 2.7.10 (default, Feb  7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

Also:

GRASS 7.3.svn (nc_spm_08_grass7):~ > echo $GRASS_PYTHONWX
/usr/bin/pythonw2.7

This environmental variable is set inside GRASS somewhere. It does not show up 
in the shell outside GRASS.

It GRASS ignoring the environmental variable setting for some reason. Is there 
something hardwired in that insists on looking for Python in /usr/bin?

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Jul 27, 2017, at 9:43 PM, Vaclav Petras 
> wrote:



On Thu, Jul 27, 2017 at 11:13 PM, Michael Barton 
> wrote:
I don't remember the exact wording. I had set up a conda virtual environment to 
force GRASS to compile and run with Anaconda Python and wxPython 4. When I 
launched GRASS (trunk), I got an error message that it would only run with a 
system Python. I thought that is weird.

Anyway, I tried setting GRASS_PYTHON to no avail. See below:

 g.gisenv get=GRASS_PYTHON
"/Applications/anaconda/bin/python"GRASS 7.3.svn (nc_spm_08_grass7):~ > python
Python 2.7.10 (default, Feb  7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

GRASS_PYTHON, is set, but it is still using system Python 2.7.10 instead of 
Anaconda Python 2.7.13



GRASS_PYTHON is actually an environmental variable (system driven, not by 
GRASS) , so you need to use:

export GRASS_PYTHON=/.../python  # set value
echo $GRASS_PYTHON  # get value

g.setenv changes the GRASS (environment) variables (aka "GIS env" or "GRASS 
variables").

https://grass.osgeo.org/grass72/manuals/variables.html
https://grass.osgeo.org/grass72/manuals/g.gisenv.html

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

OK. I'll put it into my .profile and see what happens. Thanks.

The other issue I'm hitting is that the configure argument to enable wxPython, 
'-with-wxwidgets=' expects a path to a wx_config file. AFAICT, wxPython 4 does 
not have such a file. And I can't yet find anything that seems to serve the 
same function. I can put in a path to the folder/directory where the wxPython 4 
files live. While this compiles without error, I don't think it is using 
wxPython 4.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Jul 27, 2017, at 9:43 PM, Vaclav Petras 
> wrote:



On Thu, Jul 27, 2017 at 11:13 PM, Michael Barton 
> wrote:
I don't remember the exact wording. I had set up a conda virtual environment to 
force GRASS to compile and run with Anaconda Python and wxPython 4. When I 
launched GRASS (trunk), I got an error message that it would only run with a 
system Python. I thought that is weird.

Anyway, I tried setting GRASS_PYTHON to no avail. See below:

 g.gisenv get=GRASS_PYTHON
"/Applications/anaconda/bin/python"GRASS 7.3.svn (nc_spm_08_grass7):~ > python
Python 2.7.10 (default, Feb  7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

GRASS_PYTHON, is set, but it is still using system Python 2.7.10 instead of 
Anaconda Python 2.7.13



GRASS_PYTHON is actually an environmental variable (system driven, not by 
GRASS) , so you need to use:

export GRASS_PYTHON=/.../python  # set value
echo $GRASS_PYTHON  # get value

g.setenv changes the GRASS (environment) variables (aka "GIS env" or "GRASS 
variables").

https://grass.osgeo.org/grass72/manuals/variables.html
https://grass.osgeo.org/grass72/manuals/g.gisenv.html

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Vaclav Petras]

On Thu, Jul 27, 2017 at 11:13 PM, Michael Barton 
wrote:

> I don't remember the exact wording. I had set up a conda virtual
> environment to force GRASS to compile and run with Anaconda Python and
> wxPython 4. When I launched GRASS (trunk), I got an error message that it
> would only run with a system Python. I thought that is weird.
>
> Anyway, I tried setting GRASS_PYTHON to no avail. See below:
>
>  g.gisenv get=GRASS_PYTHON
> "/Applications/anaconda/bin/python"GRASS 7.3.svn (nc_spm_08_grass7):~ >
> python
> Python 2.7.10 (default, Feb  7 2017, 00:08:15)
> [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
>
> GRASS_PYTHON, is set, but it is still using system Python 2.7.10 instead
> of Anaconda Python 2.7.13
>
>

GRASS_PYTHON is actually an environmental variable (system driven, not by
GRASS) , so you need to use:

export GRASS_PYTHON=/.../python  # set value
echo $GRASS_PYTHON  # get value

g.setenv changes the GRASS (environment) variables (aka "GIS env" or "GRASS
variables").

https://grass.osgeo.org/grass72/manuals/variables.html
https://grass.osgeo.org/grass72/manuals/g.gisenv.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

I just discovered something that has probably been giving increasing problems 
lately. Because I've been building binaries, I have not looked at the grass.app 
that is built from just running 'make install' in a long time.

It turns out that whatever creates the *.app automatically bundles some version 
of wxPython. I've been trying to bundle versions made outside of system folders 
to avoid the SIP issue, but there is code that is grabbing wxPython from 
somewhere and putting it into *.app/MacOS/etc/python folder inside the app. 
Hopefully someone reading this can figure out where this is happening and how 
to control it.

It explains why I have not been able to really test wxPython 4, and maybe even 
not wxPython 3. Certainly, it is NOT packaging wxPython 4 files into the app, 
even though I've compiled with explicit paths to the relevant wxPython 4 files.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Jul 27, 2017, at 6:34 PM, Anna Petrášová 
> wrote:

On Thu, Jul 27, 2017 at 8:13 PM, Michael Barton 
> wrote:
It seems that GRASS (at least GRASS for Mac) will only use the system
Python. If I set up an environment in which Anaconda python is default,
GRASS will not start and gives an error message that it will only run with
the system Python. I don't know where this is coming from. It doesn't seem
to be from the python_wrapper script. This will need to be changed if I am
to package Python with GRASS.

What exactly is the error? I know I was able to use GRASS_PYTHON
variable previously to set the python I needed.

Anna


Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=ejnQRWolrucufjW07P5RKvDkaAo__J6-niGuF5D7eNg=97LlCjf7C4a6iG9wGSVOYu1lQuVXSps_-yEnDAGKWIE=
 , 
https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=ejnQRWolrucufjW07P5RKvDkaAo__J6-niGuF5D7eNg=-IglMTXE4z0Ek6alARnfLbHdyXb7iyo7bg3-Gf0Uyb8=















On Jul 27, 2017, at 1:33 PM, Anna Petrášová 
> wrote:

On Thu, Jul 27, 2017 at 3:03 PM, Michael Barton 
>
wrote:



On Jul 27, 2017, at 12:46 PM, Anna Petrášová 
> wrote:

I think you can use pip to install it with whatever Python you use, at
least that's what works on Linux.


How do you specify which Python in pip?


It uses whichever Python is first on the path, you can find out with

which python

probably you can use also something like this:

https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_a_4910393_1058453=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=_vBpVdLmTTjrHrftXdNANYEvTAotd9_enwM-I1H_YFQ=


Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=9rsZ1tUV9snbiCH4rN8yrhhd4hDrfvamcPxF7y3cvRE=
,
https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=8dy6hAPGI8vce9HOn68hYqtyg7hzPG5nT_Nt0fQIGCk=














___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

I don't remember the exact wording. I had set up a conda virtual environment to 
force GRASS to compile and run with Anaconda Python and wxPython 4. When I 
launched GRASS (trunk), I got an error message that it would only run with a 
system Python. I thought that is weird.

Anyway, I tried setting GRASS_PYTHON to no avail. See below:

 g.gisenv get=GRASS_PYTHON
"/Applications/anaconda/bin/python"GRASS 7.3.svn (nc_spm_08_grass7):~ > python
Python 2.7.10 (default, Feb  7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

GRASS_PYTHON, is set, but it is still using system Python 2.7.10 instead of 
Anaconda Python 2.7.13

I went ahead and installed wxPython 4 to my system Python and recompiled. GRASS 
launches and runs fine, looking exactly like it does in wxPython 3, including 
the same bugs. But I'm not sure that it is actually running wxPython 4. When I 
try to test, I get odd errors (see below).

GRASS 7.3.svn (nc_spm_08_grass7):~ > python
Python 2.7.10 (default, Feb  7 2017, 00:08:15)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import wxversion
>>> import wx
Traceback (most recent call last):
  File "", line 1, in 
  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/__init__.py", 
line 45, in 
from wx._core import *
  File "/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core.py", 
line 4, in 
import _core_
ImportError: 
/Applications/GRASS-7.3.app/Contents/MacOS/etc/python/wx/_core_.so: no 
appropriate 64-bit architecture (see "man python" for running in 32-bit mode)
>>>

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Jul 27, 2017, at 6:34 PM, Anna Petrášová 
> wrote:

On Thu, Jul 27, 2017 at 8:13 PM, Michael Barton 
> wrote:
It seems that GRASS (at least GRASS for Mac) will only use the system
Python. If I set up an environment in which Anaconda python is default,
GRASS will not start and gives an error message that it will only run with
the system Python. I don't know where this is coming from. It doesn't seem
to be from the python_wrapper script. This will need to be changed if I am
to package Python with GRASS.

What exactly is the error? I know I was able to use GRASS_PYTHON
variable previously to set the python I needed.

Anna


Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=ejnQRWolrucufjW07P5RKvDkaAo__J6-niGuF5D7eNg=97LlCjf7C4a6iG9wGSVOYu1lQuVXSps_-yEnDAGKWIE=
 , 
https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=ejnQRWolrucufjW07P5RKvDkaAo__J6-niGuF5D7eNg=-IglMTXE4z0Ek6alARnfLbHdyXb7iyo7bg3-Gf0Uyb8=















On Jul 27, 2017, at 1:33 PM, Anna Petrášová 
> wrote:

On Thu, Jul 27, 2017 at 3:03 PM, Michael Barton 
>
wrote:



On Jul 27, 2017, at 12:46 PM, Anna Petrášová 
> wrote:

I think you can use pip to install it with whatever Python you use, at
least that's what works on Linux.


How do you specify which Python in pip?


It uses whichever Python is first on the path, you can find out with

which python

probably you can use also something like this:

https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_a_4910393_1058453=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=_vBpVdLmTTjrHrftXdNANYEvTAotd9_enwM-I1H_YFQ=


Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Anna Petrášová]

On Thu, Jul 27, 2017 at 8:13 PM, Michael Barton  wrote:
> It seems that GRASS (at least GRASS for Mac) will only use the system
> Python. If I set up an environment in which Anaconda python is default,
> GRASS will not start and gives an error message that it will only run with
> the system Python. I don't know where this is coming from. It doesn't seem
> to be from the python_wrapper script. This will need to be changed if I am
> to package Python with GRASS.

What exactly is the error? I know I was able to use GRASS_PYTHON
variable previously to set the python I needed.

Anna

>
> Michael
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Jul 27, 2017, at 1:33 PM, Anna Petrášová  wrote:
>
> On Thu, Jul 27, 2017 at 3:03 PM, Michael Barton 
> wrote:
>
>
>
> On Jul 27, 2017, at 12:46 PM, Anna Petrášová  wrote:
>
> I think you can use pip to install it with whatever Python you use, at
> least that's what works on Linux.
>
>
> How do you specify which Python in pip?
>
>
> It uses whichever Python is first on the path, you can find out with
>
> which python
>
> probably you can use also something like this:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_a_4910393_1058453=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=_vBpVdLmTTjrHrftXdNANYEvTAotd9_enwM-I1H_YFQ=
>
>
> Michael
>
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=9rsZ1tUV9snbiCH4rN8yrhhd4hDrfvamcPxF7y3cvRE=
> ,
> https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=8dy6hAPGI8vce9HOn68hYqtyg7hzPG5nT_Nt0fQIGCk=
>
>
>
>
>
>
>
>
>
>
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

It seems that GRASS (at least GRASS for Mac) will only use the system Python. 
If I set up an environment in which Anaconda python is default, GRASS will not 
start and gives an error message that it will only run with the system Python. 
I don't know where this is coming from. It doesn't seem to be from the 
python_wrapper script. This will need to be changed if I am to package Python 
with GRASS.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Jul 27, 2017, at 1:33 PM, Anna Petrášová 
> wrote:

On Thu, Jul 27, 2017 at 3:03 PM, Michael Barton 
> wrote:


On Jul 27, 2017, at 12:46 PM, Anna Petrášová 
> wrote:

I think you can use pip to install it with whatever Python you use, at
least that's what works on Linux.


How do you specify which Python in pip?

It uses whichever Python is first on the path, you can find out with

which python

probably you can use also something like this:

https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_a_4910393_1058453=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=_vBpVdLmTTjrHrftXdNANYEvTAotd9_enwM-I1H_YFQ=


Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=9rsZ1tUV9snbiCH4rN8yrhhd4hDrfvamcPxF7y3cvRE=
 , 
https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=MCkZA0y-uOGAo8gOeYPoP_uqc1lzXM6XCXuCQayAyS0=8dy6hAPGI8vce9HOn68hYqtyg7hzPG5nT_Nt0fQIGCk=













___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Vincent Bain]

Hello Luca,

Le jeudi 27 juillet 2017 à 08:06 +0200, Luca Delucchi a écrit :

> what do you think about this?

all's fine, I understand OSGeo's concern about these brochures.

> > Besides this, as you said, a horizontal version of the logo is probably
> > lacking. We could recycle the startup banner layout ?
> >

> +1

I try to send you that soon,
Thanks,

Vincent.



___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Vincent Bain]

Hello Luca,

Le jeudi 27 juillet 2017 à 08:06 +0200, Luca Delucchi a écrit :

> what do you think about this?

all's fine, I understand OSGeo's concern about these brochures.

> > Besides this, as you said, a horizontal version of the logo is probably
> > lacking. We could recycle the startup banner layout ?
> >

> +1

I try to send you that soon,
Thanks,

Vincent.


___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Anna Petrášová]

On Thu, Jul 27, 2017 at 3:03 PM, Michael Barton  wrote:
>
>
> On Jul 27, 2017, at 12:46 PM, Anna Petrášová  wrote:
>
> I think you can use pip to install it with whatever Python you use, at
> least that's what works on Linux.
>
>
> How do you specify which Python in pip?

It uses whichever Python is first on the path, you can find out with

which python

probably you can use also something like this:

https://stackoverflow.com/a/4910393/1058453

>
> Michael
>
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
>
>
>
>
>
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

On Jul 27, 2017, at 12:46 PM, Anna Petrášová 
> wrote:

I think you can use pip to install it with whatever Python you use, at
least that's what works on Linux.

How do you specify which Python in pip?

Michael


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu












___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Anna Petrášová]

On Thu, Jul 27, 2017 at 2:32 PM, Michael Barton  wrote:
> Anna,
>
> Thanks for the quick response. See below.
>
> Michael
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
> On Jul 27, 2017, at 12:07 PM, Anna Petrášová  wrote:
>
> On Thu, Jul 27, 2017 at 1:54 PM, Michael Barton 
> wrote:
>
> Here is a report on this effort, including identifying several items that
> will need to be changed by others for this to be successful.
>
> I've successfully compiled GRASS 7 64bit, with wxPython 3.0.2.0 under the
> current OS (Sierra = OS X 10.12.x). I'm using the most current Kyngesburye
> frameworks for GDAL, Numpy, and MatPlotLib.
>
> No binaries or bundled dependencies yet.
>
> Issues that need to be resolved.
>
> 1. the 'python_wrapper' bash script in ../macosx/app needs to be updated to
> allow for full 64bit compiling with wxPython. It currently tries to force
> 32bit Python if wxPython is present. I've done a hack but it is probably not
> the right thing for the long term.
>
> 2. wxGUI needs a several fixes to run correctly with wxPython 3.
>
> 2.1 When switching from 3D to 2D, the 'rotate 3D' and 'airplane' buttons are
> not destroyed. They overprint the zoom to map extents button of 2D mode and
> will crash the GUI if pressed.
>
>
> I know about this one.
>
>
> OK. Probably not too hard I hope.
>
>
>
> 2.2 A custom control needs to be updated or replaced because it does not
> recognize mouse clicks. It is used in a number of different places,
> including in the bivariate histogram tool where it is used to select pairs
> of maps for histogramming. You can navigate this control (a pulldown) with
> arrow keys but not a mouse.
>
> This is hard to solve, I don't think there is a good widget to replace this
> one.
>
>
> I don't see any noticeable difference between this control and the one used
> for r.patch (which works).

Maybe I got confused about this one, I need to look at it then.

>
>
> 2.3 selecting g.gui.iclass will crash the GUI. I cannot get any error to
> come up on the console before the crash, and there is nothing in the
> terminal.
>
>
> I don't know about this one, maybe some ctypes thing, but at least
> it's not a major component.
>
>
> Right. But hopefully someone can figure it out.
>
>
> Another one I know about is the raster digitizer, where I need to
> tweak the toolbar code to not crash, but I didn't get to it yet.
>
>
> Haven't tested that.
>
>
> Could you possibly try wxPython 4 (Phoenix) with trunk? I am wondering
> how that looks like...
>
>
> Sure. Is the configure script similar? My worry with wxPython 4 currently,
> is that it seems like it must be installed into a system folder where it
> might cause SIP problems.

I think you can use pip to install it with whatever Python you use, at
least that's what works on Linux.

Anna

>
> Michael
>
>
> Thanks,
>
> Anna
>
>
> That's all I've hit so far. I hope to start working on bundling for a binary
> next week.
>
> Michael
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIBaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=47Q9MXJZRCcL5i9M9PgT2F3tdAlQVBzW92JuJlbxyu8=2nHCPVvo7tAxX8GU1RH1_aM-1_Bgdb9GDAtSEebe1Rc=
> ,
> https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIBaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=47Q9MXJZRCcL5i9M9PgT2F3tdAlQVBzW92JuJlbxyu8=-yI7_BSCJLWbfaDFGLVJN7xdKGL4heYGzAbjoFboEus=
>
>
>
>
>
> On Jul 18, 2017, at 2:26 PM, Michael Barton  wrote:
>
> Yesterday, I sent this message off-list to Anna and Vaclav. Anna asked if I
> could repost to the dev list. So I'm doing so here.
>
> I have some time (I hope) on an upcoming research trip to NCAR, along with
> some promised help of software engineers at the CSDMS NSF facility. So I'm
> going to try again to come up with a new GRASS compiling and binary creation
> protocol.
>
> I think this will involve the following components:
>
> 1. Switch from the outdated PackageMaker.app to the current way of making
> Mac packages. This requires changes to the current binary bundling scripts.
>
> 2. Bundle all 

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Michael Barton]

Here is a report on this effort, including identifying several items that will 
need to be changed by others for this to be successful.

I've successfully compiled GRASS 7 64bit, with wxPython 3.0.2.0 under the 
current OS (Sierra = OS X 10.12.x). I'm using the most current Kyngesburye 
frameworks for GDAL, Numpy, and MatPlotLib.

No binaries or bundled dependencies yet.

Issues that need to be resolved.

1. the 'python_wrapper' bash script in ../macosx/app needs to be updated to 
allow for full 64bit compiling with wxPython. It currently tries to force 32bit 
Python if wxPython is present. I've done a hack but it is probably not the 
right thing for the long term.

 2. wxGUI needs a several fixes to run correctly with wxPython 3.

2.1 When switching from 3D to 2D, the 'rotate 3D' and 'airplane' buttons are 
not destroyed. They overprint the zoom to map extents button of 2D mode and 
will crash the GUI if pressed.

2.2 A custom control needs to be updated or replaced because it does not 
recognize mouse clicks. It is used in a number of different places, including 
in the bivariate histogram tool where it is used to select pairs of maps for 
histogramming. You can navigate this control (a pulldown) with arrow keys but 
not a mouse.

2.3 selecting g.gui.iclass will crash the GUI. I cannot get any error to come 
up on the console before the crash, and there is nothing in the terminal.

That's all I've hit so far. I hope to start working on bundling for a binary 
next week.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu




On Jul 18, 2017, at 2:26 PM, Michael Barton 
> wrote:

Yesterday, I sent this message off-list to Anna and Vaclav. Anna asked if I 
could repost to the dev list. So I'm doing so here.

I have some time (I hope) on an upcoming research trip to NCAR, along with some 
promised help of software engineers at the CSDMS NSF facility. So I'm going to 
try again to come up with a new GRASS compiling and binary creation protocol.

I think this will involve the following components:

1. Switch from the outdated PackageMaker.app to the current way of making Mac 
packages. This requires changes to the current binary bundling scripts.

2. Bundle all dependencies (including the current, separate frameworks) into 
the new package distribution so that everything needed is in the grass7.app Can 
this be done with binary "framework" installations of dependencies or is it 
necessary to compile all from scratch to do this?

3. As part of 2, make sure that all dependencies are compiled outside of the 
/usr folders on the Mac to avoid SIP conflicts

4. To accomplish #2 and #3 for wxPython, we probably need to switch to wxPython 
3 (or the new wxPython Phoenix if it is working correctly). This would also 
permit compiling ALL GRASS 64 bit, alleviating additional issues.

5. Because of recent change to GRASS GUI and a bug in Mac system Python 2.7.10, 
it may be necessary to also bundle an updated Python (2.7.11 or higher) with 
the new grass7.app. This (and #2) would make the installation package 
significantly larger, but would avoid mismatched versions of Python and 
wxPython. It would also avoid potential conflicts between Mac system Python and 
other versions a user might have installed (e.g., with Anaconda).

Last fall, I was stuck on gettext. I will try again with bundline it, but this 
may not be solvable by me because it involves a hard-coded path in the build 
files that point to gettext files in /usr/local and no way to send an alternate 
path (e.g., a configure argument like '--with_gettext_libs='. This will need to 
be fixed by whoever manages the build system. Otherwise, I'll have to drop 
internationalization support for the Mac, which would be a shame.

An additional thing to note. While it may be possible for some to get GRASS 
compiled on the Mac using Homebrew, Macports, etc., the goal here is to create 
a normal DMG binary that any Mac user can download and install, without having 
to compile GRASS--or to install Linux like package managers first.

If anyone has experience in creating Mac DMGs, with bundled dependencies, I'd 
love to hear from you. Any other suggestions are welcome too.


Cheers
Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 

Re: [GRASS-dev] New attempt to update GRASS for Mac

[Anna Petrášová]

On Thu, Jul 27, 2017 at 1:54 PM, Michael Barton  wrote:
> Here is a report on this effort, including identifying several items that
> will need to be changed by others for this to be successful.
>
> I've successfully compiled GRASS 7 64bit, with wxPython 3.0.2.0 under the
> current OS (Sierra = OS X 10.12.x). I'm using the most current Kyngesburye
> frameworks for GDAL, Numpy, and MatPlotLib.
>
> No binaries or bundled dependencies yet.
>
> Issues that need to be resolved.
>
> 1. the 'python_wrapper' bash script in ../macosx/app needs to be updated to
> allow for full 64bit compiling with wxPython. It currently tries to force
> 32bit Python if wxPython is present. I've done a hack but it is probably not
> the right thing for the long term.
>
>  2. wxGUI needs a several fixes to run correctly with wxPython 3.
>
> 2.1 When switching from 3D to 2D, the 'rotate 3D' and 'airplane' buttons are
> not destroyed. They overprint the zoom to map extents button of 2D mode and
> will crash the GUI if pressed.

I know about this one.

>
> 2.2 A custom control needs to be updated or replaced because it does not
> recognize mouse clicks. It is used in a number of different places,
> including in the bivariate histogram tool where it is used to select pairs
> of maps for histogramming. You can navigate this control (a pulldown) with
> arrow keys but not a mouse.
>
This is hard to solve, I don't think there is a good widget to replace this one.

> 2.3 selecting g.gui.iclass will crash the GUI. I cannot get any error to
> come up on the console before the crash, and there is nothing in the
> terminal.

I don't know about this one, maybe some ctypes thing, but at least
it's not a major component.

Another one I know about is the raster digitizer, where I need to
tweak the toolbar code to not crash, but I didn't get to it yet.

Could you possibly try wxPython 4 (Phoenix) with trunk? I am wondering
how that looks like...

Thanks,

Anna

>
> That's all I've hit so far. I hope to start working on bundling for a binary
> next week.
>
> Michael
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
>
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>
>
>
>
> On Jul 18, 2017, at 2:26 PM, Michael Barton  wrote:
>
> Yesterday, I sent this message off-list to Anna and Vaclav. Anna asked if I
> could repost to the dev list. So I'm doing so here.
>
> I have some time (I hope) on an upcoming research trip to NCAR, along with
> some promised help of software engineers at the CSDMS NSF facility. So I'm
> going to try again to come up with a new GRASS compiling and binary creation
> protocol.
>
> I think this will involve the following components:
>
> 1. Switch from the outdated PackageMaker.app to the current way of making
> Mac packages. This requires changes to the current binary bundling scripts.
>
> 2. Bundle all dependencies (including the current, separate frameworks) into
> the new package distribution so that everything needed is in the grass7.app
> Can this be done with binary "framework" installations of dependencies or is
> it necessary to compile all from scratch to do this?
>
> 3. As part of 2, make sure that all dependencies are compiled outside of the
> /usr folders on the Mac to avoid SIP conflicts
>
> 4. To accomplish #2 and #3 for wxPython, we probably need to switch to
> wxPython 3 (or the new wxPython Phoenix if it is working correctly). This
> would also permit compiling ALL GRASS 64 bit, alleviating additional issues.
>
> 5. Because of recent change to GRASS GUI and a bug in Mac system Python
> 2.7.10, it may be necessary to also bundle an updated Python (2.7.11 or
> higher) with the new grass7.app. This (and #2) would make the installation
> package significantly larger, but would avoid mismatched versions of Python
> and wxPython. It would also avoid potential conflicts between Mac system
> Python and other versions a user might have installed (e.g., with Anaconda).
>
> Last fall, I was stuck on gettext. I will try again with bundline it, but
> this may not be solvable by me because it involves a hard-coded path in the
> build files that point to gettext files in /usr/local and no way to send an
> alternate path (e.g., a configure argument like '--with_gettext_libs='. This
> will need to be fixed by whoever manages the build system. Otherwise, I'll
> have to drop internationalization support for the Mac, which would be a
> shame.
>
> An additional thing to note. While it may be possible for some to get GRASS
> compiled on the Mac using Homebrew, Macports, etc., the goal here is to
> create a normal DMG binary that any Mac user can download and 

[GRASS-dev] compilation of addons for windows

[Anna Petrášová]

Hi Martin,

I noticed the last log of addon Windows compilation is from May:

https://wingrass.fsv.cvut.cz/grass72/x86_64/addons/latest/logs/

Are you aware of that?

Thank you,

Anna
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Vaclav Petras]

Update for the flyer: Number of modules in the flyer is "more than 450". It
is actually better than that: "more than 500" if we simply count all in 7.2
branch using:

$ python -c "print(`ls dist.x86_64-pc-linux-gnu/bin | grep "\." | grep test
-v | wc -l` + `ls dist.x86_64-pc-linux-gnu/scripts | grep "\." | wc -l`)"
514

GRASS > g.search.modules xxx -n -g | wc -l
504
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Jeff McKenna]

Hi Luca,

Some feedback from me:

- remove "a" from the first sentence:   GRASS GIS is free and open 
source software for performing spatial analysis.


- add an "s" to "consist" in the second sentence:  It consists of more 
than 450 modules


- in the third sentence, the term "map web services" confuses me, did 
you mean "web map services" instead??


- in the next sentence, change "but still at the bleeding edge" to "but 
is still at the bleeding edge"


- in the section "A long term endeavor":

   - change "wide contributors community. Both combine" to "wide 
contributors community; both combine"


- in the section "Interfaces":

   - change "the simpler for new user" to "the simplest for the new user"

   - change "text based" to "text-based"



-jeff




On 2017-07-27 1:05 PM, Anna Petrášová wrote:

Hi Luca,


great effort! Let me also comment on couple small things:

* The bottom 'GRASS GIS' seems unnecessary, I would keep only the
logo, which I would align to the left and the url to the right
* In interfaces, I would skip "called wxGUI", I am not sure whether we
need to mention it's in wxPython, new users probably won't know about
the old GUI?
* Now you have there twice that GRASS is old, maybe I would replace
the sentence "It is the oldest..." with something like "GRASS GIS can
serve you as a desktop GIS, the backbone of a geospatial
infrastructure or as an innovation platform for scientific modeling."

Thank you for working on this

On Thu, Jul 27, 2017 at 8:39 AM, Luca Delucchi  wrote:

On 27 July 2017 at 09:21, Moritz Lennert  wrote:


Great !

Again a few remarks after a rapid glance:

- If we say in the opening paragraph that it is the "oldest" free GIS, then
we should probably add in the same sentence something like "but still at the
bleeding edge of innovation in GIS technology".

- I don't find that the paragraph on the top right really explains "Data
management capabilities" since most of what is in it concerns data analysis.
Maybe entitle it "Features" ?

- psmap is not the tool that "interactively compares two maps"

And just an idea: maybe replace the paragraph entitles "Graphical tools"
(the list of which I find a bit abstract for new users) by one called
"Multiple forms of use" [better title needed] explaining that you can use
GRASS via a GUI (maybe cite some of the GUI modules in parantheses there),
via command line (e.g. on headless servers) and via easy integration into
different programming languages.



done!


Moritz




--
ciao
Luca

www.lucadelu.org

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Anna Petrášová]

Hi Luca,


great effort! Let me also comment on couple small things:

* The bottom 'GRASS GIS' seems unnecessary, I would keep only the
logo, which I would align to the left and the url to the right
* In interfaces, I would skip "called wxGUI", I am not sure whether we
need to mention it's in wxPython, new users probably won't know about
the old GUI?
* Now you have there twice that GRASS is old, maybe I would replace
the sentence "It is the oldest..." with something like "GRASS GIS can
serve you as a desktop GIS, the backbone of a geospatial
infrastructure or as an innovation platform for scientific modeling."

Thank you for working on this

On Thu, Jul 27, 2017 at 8:39 AM, Luca Delucchi  wrote:
> On 27 July 2017 at 09:21, Moritz Lennert  wrote:
>>
>> Great !
>>
>> Again a few remarks after a rapid glance:
>>
>> - If we say in the opening paragraph that it is the "oldest" free GIS, then
>> we should probably add in the same sentence something like "but still at the
>> bleeding edge of innovation in GIS technology".
>>
>> - I don't find that the paragraph on the top right really explains "Data
>> management capabilities" since most of what is in it concerns data analysis.
>> Maybe entitle it "Features" ?
>>
>> - psmap is not the tool that "interactively compares two maps"
>>
>> And just an idea: maybe replace the paragraph entitles "Graphical tools"
>> (the list of which I find a bit abstract for new users) by one called
>> "Multiple forms of use" [better title needed] explaining that you can use
>> GRASS via a GUI (maybe cite some of the GUI modules in parantheses there),
>> via command line (e.g. on headless servers) and via easy integration into
>> different programming languages.
>>
>
> done!
>
>> Moritz
>
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Luca Delucchi]

On 27 July 2017 at 09:21, Moritz Lennert  wrote:
>
> Great !
>
> Again a few remarks after a rapid glance:
>
> - If we say in the opening paragraph that it is the "oldest" free GIS, then
> we should probably add in the same sentence something like "but still at the
> bleeding edge of innovation in GIS technology".
>
> - I don't find that the paragraph on the top right really explains "Data
> management capabilities" since most of what is in it concerns data analysis.
> Maybe entitle it "Features" ?
>
> - psmap is not the tool that "interactively compares two maps"
>
> And just an idea: maybe replace the paragraph entitles "Graphical tools"
> (the list of which I find a bit abstract for new users) by one called
> "Multiple forms of use" [better title needed] explaining that you can use
> GRASS via a GUI (maybe cite some of the GUI modules in parantheses there),
> via command line (e.g. on headless servers) and via easy integration into
> different programming languages.
>

done!

> Moritz



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3380: v.what.vect query_column dropdown button doesn't show attribute columns of query_map

[GRASS GIS]

#3380: v.what.vect query_column dropdown button doesn't show attribute columns 
of
query_map
--+-
  Reporter:  rorschach|  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Vector   |Version:  7.2.1
Resolution:   |   Keywords:  v.what.vect
   CPU:  Unspecified  |   Platform:  Linux
--+-

Comment (by rorschach):

 Replying to [comment:1 mlennert]:
 > Replying to [ticket:3380 rorschach]:
 > > A pleasant day to everyone.
 > >
 > > Does anyone else encounter this problem? When I'm using v.what.vect,
 the query_column dropdown button doesn't show the attribute columns of the
 vector layer specified by query_map.
 > >
 > > It's not too much of an issue since the user can always type the
 column names manually but the dropdown button is supposed to be there to
 allow the user to select the attribute columns of their query_map.
 > >
 > > If anyone knows a fix or wants to fix this, I would highly appreciate
 it.
 > >
 > > By the way, I'm using GRASS 7.2.1 on Xubuntu 16.04.
 >
 > This was fixed in trunk in r70518, but apparently never backported. I
 don't know if there are objections to backporting... Martin ?

 Saw that fix when I searched for 'v.what.vect' tickets which is why I
 found it weirder that the dropdown button wasn't working.

 I copied the fix on my machine and everything seems to be working fine
 now. A backport would also be appreciated.

 Thank you.

 -- Ben

--
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #2940: Compiling Grass-7.0.3 under FreeBSD: tplot directory (with log)

[GRASS GIS]

#2940: Compiling Grass-7.0.3 under FreeBSD: tplot directory (with log)
--+-
  Reporter:  pieside  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.2
 Component:  Default  |Version:  7.2.0
Resolution:   |   Keywords:  FreeBSD
   CPU:  x86-64   |   Platform:  Other Unix
--+-

Comment (by mmetz):

 Replying to [comment:15 lbartoletti]:
 > Hello,
 >
 > Good news, it's works! :)
 >
 > There was an error in the configuration for the package and also some
 grass' files need to be patched.

 Could you point to or attach the patches? Maybe we can include them in
 GRASS.

--
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Moritz Lennert]

On 27/07/17 09:17, Luca Delucchi wrote:

On 27 July 2017 at 08:52, Moritz Lennert  wrote:



Ah, I think this needs some clarification. Could you please explain for
those that are not as informed exactly what this "OSGeo brochure for GRASS"
is ? Or are we speaking about a page about GRASS in a general OSGeo brochure
?



Sorry early morning and the brain is not really working today...

We can continue to use our flyer, but also the new one. What I'm
working now is a flyer following the new OSGeo Branding. the idea of
Marketing Committee (that I joined few days ago) is to have a generic
OSGeo brochure [0] (this is not the last version, there will be some
changes, please no comment on this :-) ) and flyers for all the OSGeo
Projects/Community projects/Initiatives. During events a person that
doesn't know OSGeo go to the OSGeo booth and he ask for more info,
when the OSGeo member at the booth understand what the person is
looking for (desktop, web, programming...) he will fill the brochure
only with the right flyers.

I hope now it is more clear...


Very much so. And I like the initiative !

Thanks !

Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Moritz Lennert]

On 27/07/17 09:06, Luca Delucchi wrote:

On 26 July 2017 at 11:31, Moritz Lennert  wrote:


Some quick remarks:

- First of all: who are why addressing with this ? Users or developers ? The
following remarks assume users.



new users


- The first title reads "A mature mapping suite". I'm not sure I would
advertise GRASS first and foremost for mapping. I'd rather present it as
"A mature spatial analysis suite" or something similar.



+1, you are completely right


- Maybe an extract of the "GRASS GIS capabilities" on
https://grass.osgeo.org/documentation/general-overview/ would be more
important than the interoperability and development information. I think
people should first get a vision of what GRASS GIS actually does before
thinking about how interoperable it is...

- Paragraphs could possibly be rearranged to create a drilling down from the
most important general info to more specific info. I would say that for
first contact with users the most important elements are: what is it/what
does it do ? who uses it ? On what OS's does it run ? Is there documentation
? Is there a community ? Is it "certified" (I agree that the fact that it is
an OSGeo project needs to be prominently present) ?  ...



I follow this two idea and revisit the flyer, please look the new version

https://github.com/lucadelu/osgeo/blob/grass/marketing/print/grass_a4.svg


Great !

Again a few remarks after a rapid glance:

- If we say in the opening paragraph that it is the "oldest" free GIS, 
then we should probably add in the same sentence something like "but 
still at the bleeding edge of innovation in GIS technology".


- I don't find that the paragraph on the top right really explains "Data 
management capabilities" since most of what is in it concerns data 
analysis. Maybe entitle it "Features" ?


- psmap is not the tool that "interactively compares two maps"

And just an idea: maybe replace the paragraph entitles "Graphical tools" 
(the list of which I find a bit abstract for new users) by one called 
"Multiple forms of use" [better title needed] explaining that you can 
use GRASS via a GUI (maybe cite some of the GUI modules in parantheses 
there), via command line (e.g. on headless servers) and via easy 
integration into different programming languages.


Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Luca Delucchi]

On 27 July 2017 at 08:52, Moritz Lennert  wrote:

>
> Ah, I think this needs some clarification. Could you please explain for
> those that are not as informed exactly what this "OSGeo brochure for GRASS"
> is ? Or are we speaking about a page about GRASS in a general OSGeo brochure
> ?
>

Sorry early morning and the brain is not really working today...

We can continue to use our flyer, but also the new one. What I'm
working now is a flyer following the new OSGeo Branding. the idea of
Marketing Committee (that I joined few days ago) is to have a generic
OSGeo brochure [0] (this is not the last version, there will be some
changes, please no comment on this :-) ) and flyers for all the OSGeo
Projects/Community projects/Initiatives. During events a person that
doesn't know OSGeo go to the OSGeo booth and he ask for more info,
when the OSGeo member at the booth understand what the person is
looking for (desktop, web, programming...) he will fill the brochure
only with the right flyers.

I hope now it is more clear...

> Moritz

[0] https://github.com/OSGeo/osgeo/blob/master/marketing/print/brochure_a3.pdf

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Luca Delucchi]

On 26 July 2017 at 11:31, Moritz Lennert  wrote:
>
> Some quick remarks:
>
> - First of all: who are why addressing with this ? Users or developers ? The
> following remarks assume users.
>

new users

> - The first title reads "A mature mapping suite". I'm not sure I would
> advertise GRASS first and foremost for mapping. I'd rather present it as
> "A mature spatial analysis suite" or something similar.
>

+1, you are completely right

> - Maybe an extract of the "GRASS GIS capabilities" on
> https://grass.osgeo.org/documentation/general-overview/ would be more
> important than the interoperability and development information. I think
> people should first get a vision of what GRASS GIS actually does before
> thinking about how interoperable it is...
>
> - Paragraphs could possibly be rearranged to create a drilling down from the
> most important general info to more specific info. I would say that for
> first contact with users the most important elements are: what is it/what
> does it do ? who uses it ? On what OS's does it run ? Is there documentation
> ? Is there a community ? Is it "certified" (I agree that the fact that it is
> an OSGeo project needs to be prominently present) ?  ...
>

I follow this two idea and revisit the flyer, please look the new version

https://github.com/lucadelu/osgeo/blob/grass/marketing/print/grass_a4.svg

>
> That's all for now, especially since I will not have time to work on this in
> the near future... ;-)
>
> Moritz
>
>



-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Moritz Lennert]

On 27/07/17 08:06, Luca Delucchi wrote:

On 25 July 2017 at 15:30, Vincent Bain  wrote:



* GRASS GIS wording (and possibly the slogan) be consistent with our
identity (esp. font).



eh this is a problem... you need to think that this is the OSGeo
brochure for GRASS and the idea is to have a consistent fonts/color of
OSGeo.

We will continue to use our flyer that it is really cool.



Ah, I think this needs some clarification. Could you please explain for 
those that are not as informed exactly what this "OSGeo brochure for 
GRASS" is ? Or are we speaking about a page about GRASS in a general 
OSGeo brochure ?


Moritz
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Luca Delucchi]

On 25 July 2017 at 15:30, Vincent Bain  wrote:
> Hello Luca and Vaclav,

Hi Vincent,

> thank you for forwarding me this thread.
>

sorry if I didn't add you before..

> [I'm not sure how pertinent is my comment on this, given I don't know
> much of the OSGeo context where this flyer is meant to be published --
> soory if I misunderstand]
>
> I would just recommend (just my 2 c., not any kind of claim) to take
> into account the effort we made some time ago to enhance the graphical
> identity of GRASS, esp. concerning fonts, colors, usage of GRASS GIS
> logo. It is probably not that easy to clearly distinguish between OSGeo
> and GRASS identity clues (all is more or less green and black and
> white...), but I suggest that:
> * we keep using the original GRASS "green" definition on this paper, I
> mean for the logo only (not titles, I understand they belong to OSGeo
> guidelines), or alternatively decline the logo in greyscale;

+1 instead I will leave our official logo

> * GRASS GIS wording (and possibly the slogan) be consistent with our
> identity (esp. font).
>

eh this is a problem... you need to think that this is the OSGeo
brochure for GRASS and the idea is to have a consistent fonts/color of
OSGeo.

We will continue to use our flyer that it is really cool.

Maybe use could distinguish between this flyer and our:
- this should be more generic for an ample public
- our a little more technical

what do you think about this?

> Besides this, as you said, a horizontal version of the logo is probably
> lacking. We could recycle the startup banner layout ?
>

+1

>
> Yours,
> Vincent.
>

thanks

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS flyer for the new osgeo branding

[Luca Delucchi]

On 25 July 2017 at 15:17, Vaclav Petras  wrote:
>
>
> I'm pretty sure I attached two SVGs 15KB each (should be ok with for the
> mailing list, right?). Trying again.
>

now they arrived, I think I prefer our version, so I'm going to leave
the actual logo (with the text under the logo)

>> however with i'm going to add the logo with
>> GRASS GIS text in black and leave also the GRASS GIS text with OSGeo
>> colors
>
> Now that seems to be something which should be same across all the projects
> if that goes to a brochure.

yes, that's right!

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev