[GRASS-dev] g.extension.py at (win)grass7-wxgui-startup needed?

hi,

system here:

System Info
GRASS version: 7.0.svn
GRASS SVN Revision: 57202
Build Date: 2013-07-18
GIS Library Revision: 56211 (2013-05-12)
GDAL/OGR: 1.9.2
PROJ.4: 4.8.0
GEOS: 3.3.6dev
SQLite: 3.7.10
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

it seems that g.extension.py is called when grass7-wxgui is started.

is this needed?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/g-extension-py-at-win-grass7-wxgui-startup-needed-tp5067923.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Hi,

On 22 July 2013 12:18, Helmut Kudrnovsky <hellik@web.de> wrote:

hi,

system here:

System Info
GRASS version: 7.0.svn
GRASS SVN Revision: 57202
Build Date: 2013-07-18
GIS Library Revision: 56211 (2013-05-12)
GDAL/OGR: 1.9.2
PROJ.4: 4.8.0
GEOS: 3.3.6dev
SQLite: 3.7.10
Python: 2.7.4
wxPython: 2.8.12.1
Platform: Windows-7-6.1.7601-SP1 (OSGeo4W)

it seems that g.extension.py is called when grass7-wxgui is started.

Since r57144 menu can contain an entry which will show the list of
installed addons. In the current version, the addons entry is included
in Search module (in module tree) if some addons are installed.

[1] http://trac.osgeo.org/grass/changeset/57144

is this needed?

g.extension is needed to list installed addons. If this is a problem,
installed addons can be retrieved from XML in addons directory
(calling `g.extension -a` is simpler, but parsing XML is also
possible).

Some days ago there was a bug in usage of find_program function which
in turn caused triggering of compilation by g.extension. This was
causing the compilation in current directory when starting wxGUI (at
least under linux). This is fixed now.

Vaclav

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/g-extension-py-at-win-grass7-wxgui-startup-needed-tp5067923.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

hi,

Since r57144 menu can contain an entry which will show the list of
installed addons. In the current version, the addons entry is included
in Search module (in module tree) if some addons are installed.

[1] http://trac.osgeo.org/grass/changeset/57144

> is this needed?

g.extension is needed to list installed addons. If this is a problem,
installed addons can be retrieved from XML in addons directory
(calling `g.extension -a` is simpler, but parsing XML is also
possible).

Some days ago there was a bug in usage of find_program function which
in turn caused triggering of compilation by g.extension. This was
causing the compilation in current directory when starting wxGUI (at
least under linux). This is fixed now.

thanks for the clarification.

I've seen it, because every call of a python-script here at my WinVista- or
Win7-box pops up a window and asks how to open the script...

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/g-extension-py-at-win-grass7-wxgui-startup-needed-tp5067923p5067944.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

On 22 July 2013 13:33, Helmut Kudrnovsky <hellik@web.de> wrote:

I've seen it, because every call of a python-script here at my WinVista- or
Win7-box pops up a window and asks how to open the script...

Yes, this is another problem there is e.g. #2015 and others you know
about. This makes the new functionality a bit unpleasant but since
there are started different scripts many times, one more is not such a
issue. If it is an issue (and #2015, in which I'm completely lost,
will not be fixed soon), I can change the way of retrieving installed
addons form module call to XML parsing (information is in XML if I
remember correctly).

[1] http://trac.osgeo.org/grass/ticket/2015