Re: [GRASS-dev] [GRASS GIS] #2895: Define dependencies for GRASS addons

[GRASS GIS]

#2895: Define dependencies for GRASS addons
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.3
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:  g.extension
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by wenzeslaus):

 Replying to [comment:19 sbl]:
 > Pyhon modules are supposed to use lazy imports and should catch if a
 required python library is available at runtime.

 +1

 > For C modules, installation of libraries through g.extension is probably
 not very straight forward.

 Right. For some addons, we actually have that as an optional dependency in
 the core. However, pip, R, and conda can actually do that, so perhaps if
 we use them in background, they could take care of that.

 There have been suggestions like this in the past, but a lot of changed in
 past years. pip is now basically part of Python. conda is quite common.
 There is a lot of R packages using C++. For example //itzi// is using pip
 rather than g.extension.

 > Silently installing stuff can be a bit scary...

 Why do you think it is scary for GRASS GIS? pip, R, conda, apt, yum, ...
 all install dependencies of a package you asked for. Why this should not
 happen for GRASS GIS?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Miss d.split.frame

[Nikos Alexandris]

Thank you Vero!

I did not manage to make `d.frame` to work. I have ever since 2013 weird
setups and (the) Terminology (terminal) on my Funtoo-boxes and `d.mon`
segfaults ever since.

However, your link made me re-read the 'RENDER' environment variables
and I managed to make some proof-of-concept using the
GRASS_RENDER_FRAME environment variable.  I hope to develop
the custom functions I need to help me type less commands.

I'll probably share these at some point along with my other tygrass
commands (https://gitlab.com/NikosAlexandris/tygrass).

Cheers, Nikos


* Veronica Andreo  [2020-12-10 14:49:50 -0300]:


Hi Nikos,

Last time I used it was for teaching. See here:
https://www.github.com/veroandreo/grass_opengeohub2019/tree/master/code%2Flst_time_series_code.sh
(line 304 onwards)

I found the example in a workshop by Vashek, IIRC.

HTH,
Vero

El jue., 10 dic. 2020 14:24, Nikos Alexandris 
escribió:


I miss d.split.frame, to do draw many maps in one image
(somethiing like

https://grasswiki.osgeo.org/wiki/File:Mean_monthly_global_rad_maps_over_a_study_area_in_central_Greece.png
).

Is anybody using successfully `d.frame` with `-c` successfully
currently?

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



--
Nikos Alexandris | Remote Sensing & Geomatics
GPG Key Fingerprint 6F9D4506F3CA28380974D31A9053534B693C4FB3 
___

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

[GRASS-dev] Results of two surveys focused on GRASS GIS startup mechanism

[L.Kladivova]

Hello guys! :-)




as you recall, you could recently take part in two surveys that dealt with
both the GRASS startup mechanism in general and how to improve the first-
time user experience, which is, of course, closely related to the startup 
mechanism.
 



I am still working on the final version of Info Bars but the results of 
surveys are more or less analyzed and I would like to share them with you:


https://drive.google.com/drive/folders/1E77b4Eko6OxwQcurRB0KBP9oSxZqn4Ww?usp
=sharing


The implementation of the new InfoBar solution for first-time users is
already in process. (After all, I'm submitting my master thesis on January
3, so I'd like to make it by Christmas. :-) )


 

So far, the first Info Bar has been implemented. You can see it here:

https://drive.google.com/drive/folders/1E77b4Eko6OxwQcurRB0KBP9oSxZqn4Ww

or in the master branch. :-)




A total of three are planned - at startup (already implemented), then to 
import data and then to guide the user to the Display and Modules tab so 
that he/she can see imported data and perform analyzes on it.





However, we are still not sure about texts in Info Bars.. how to make them
as short as possible and at the same time helpful and clear.




So we would be very happy for your feedback! :-).




Best,


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

Re: [GRASS-dev] [GRASS GIS] #1434: g.extension: option to specify proxy server

[GRASS GIS]

#1434: g.extension: option to specify proxy server
-+-
  Reporter:  hamish  |  Owner:  grass-dev@…
  Type:  | Status:  reopened
  enhancement|
  Priority:  major   |  Milestone:  7.6.2
 Component:  |Version:  svn-trunk
  Installation   |
Resolution:  |   Keywords:  g.extension, urllib, wget, r.in.wms
   CPU:  All |   Platform:  All
-+-

Comment (by sbl):

 Is this still relevant in more recent versions of 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 GIS] #2010: r.in.wms2 fails to install on 6.x

[GRASS GIS]

#2010: r.in.wms2 fails to install on 6.x
-+-
  Reporter:  hamish  |  Owner:  grass-dev@…
  Type:  defect  | Status:  new
  Priority:  major   |  Milestone:  7.8.3
 Component:  Addons  |Version:  svn-releasebranch64
Resolution:  |   Keywords:  r.in.wms2
   CPU:  All |   Platform:  Linux
-+-

Comment (by sbl):

 Is this still relevant, or can we close it? Anyone planning to work on it?

-- 
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] #2895: Define dependencies for GRASS addons

[GRASS GIS]

#2895: Define dependencies for GRASS addons
--+-
  Reporter:  pmav99   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.8.3
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:  g.extension
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 Pyhon modules are supposed to use lazy imports and should catch if a
 required python library is available at runtime. The same should be true
 for dependency on other addons (should probably added to the SUBMITTING
 guidelines).

 For C modules, installation of libraries through g.extension is probably
 not very straight forward.

 So the question is a bit, where this is supposed to be handeled.
 Personally, I would probably prefer if the addon itself catches evtl.
 missing dependencies and gives a clear error message. Silently installing
 stuff can be a bit scary...

-- 
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] #3179: g.extension not installing addons behind proxy

[GRASS GIS]

#3179: g.extension not installing addons behind proxy
--+
  Reporter:  madi |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.3
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:  g.extension, proxy, addons
   CPU:  Unspecified  |   Platform:  Unspecified
--+

Comment (by sbl):

 Is there anything left here? Can the ticket be closed? Installation
 through proxies should work now...

-- 
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] #3455: Grass 7.2.1 returns "Extension(...)not found" when installing addon

[GRASS GIS]

#3455: Grass 7.2.1 returns "Extension(...)not found" when installing addon
--+-
  Reporter:  bcbernardo   |  Owner:  grass-dev@…
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Addons   |Version:  7.4.0
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  MSWindows
--+-

Comment (by sbl):

 Is this still an issue with more recent versions?

-- 
Ticket URL: 
GRASS GIS 

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