Re: [GRASS-dev] [GRASS GIS] #3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work (almost)

[GRASS GIS]

#3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work
(almost)
--+-
  Reporter:  vince|  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by hcho):

 By default (without {{{#define OPENGL_AGL}}} in config.h), trunk uses the
 Core OpenGL (CGL), which is the lowest-level OpenGL API for the Mac. The
 AGL code is still there just in case, but not used anymore since r73006.

-- 
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] #3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work (almost)

[GRASS GIS]

#3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work
(almost)
--+-
  Reporter:  vince|  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:
 Component:  Default  |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by cmbarton):

 I don't understand the NVIZ comment. It is currently working fine with the
 newest High Sierra OS X, compiled 64 bit, with wxPython 4.0. We may run
 into problems down the line of course, but it is not a problem now. Also
 Huidae Cho just managed to fix m.nviz.image for the Mac, updating its use
 of OpenGL.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [SoC] Week 11 Report - Full support of Python 3 in GRASS GIS

[Sanjeet]

Hi everyone,

This is my week Week 11 report for the project "Full support of Python
3 in GRASS GIS"

1) What did I complete this week?

Replaced instances of old wx.* code with wrapper classes where suitable
Fixed forms.py string errors
Added cmp function in utils
Fixed remaining gui command files
Decoded strings where necessary gui files
Added encoding in gmcd before hashing

2) What am I going to achieve for the next week?

Fix assertion errors
Fix remaining warnings in GUI library
Do testing for GUI
Prepare for evaluation, prepare deliverables

3) Is there any blocking issue?
Not at the moment.

The link to my wiki page is here [1].

[0] 
https://github.com/sanjeetbhatti/FullSupportPython3/blob/master/grass_trunk/gui/patch_gui.diff
[1] https://trac.osgeo.org/grass/wiki/GSoC/2018/FullSupportPython3#Week11

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

[GRASS-dev] [GRASS GIS] #3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work (almost)

[GRASS GIS]

#3610: Python ctypes MacOS: add more “-D” options to CTYPESFLAGS to make it work
(almost)
-+-
 Reporter:  vince|  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 **ctypesgen** miserably fails on MacOS.
 I found the situation could be much improved if you add this defines:
 ''\"-Drestrict=\" \"-D_ _attribute_
 _(x)=\" \"-D_Nullable=\" \"-D_Nonnull=\"'' to CTYPESFLAGS

 The situation is not ideal, however. ''cpl_port.h'' as installed by GDAL
 needs a small patch too, because  won’t parse. I’m planning
 to ask the GDAL developers if this line is mandatory with CLANG. In the
 meanwhile the Makefile should make a private copy of this file, modify it
 and use it.

 Also, a system file needs a patch, though that might not be necessary
 (#warning condition treated as an error).

 Finally, NVIZ is beyond hope. The AGL framework is deprecated, uses Carbon
 as a framework, which is still more deprecated, and that makes the parsing
 almost impossible to set straight. Does grass rely on NVIZ, or it is
 possible to add an option to disable 3D viz? That'd be nice.

 Thanks.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GSoC 2018 report week 11 - GRASS GIS module for Sentinel-2 cloud and shadow detection

[Roberta Fagandini]

Hi all!
I'm Roberta Fagandini and I'm working on my GSoC project, a GRASS GIS
module for Sentinel-2 cloud and shadow detection.
This is my report for the eleventh week of coding.

1) What did I complete this week?

   - Added a control check on input folder to check if it belongs to a L1C
   image [0]
   - Fixed relevant bugs on the -a flag [0]
   - Fixed a bug on the control file writing in case of a visibility map is
   provided [0]
   - Small changes to the code and the GUI
   - Discussed with dev community the implementation of a new download
   procedure in order to avoid too many dependencies and as the community
   suggested I decided to not write a new procedure but to use the existent
   addon i.sentinel.download
   - Wrote the manual page [1]
   - Tested i.sentinel.preproc both with sentinel 2A and 2B scenes (for
   Sentinel 2B it works only with GRASS GIS 7.5)

2) What am I going to achieve for next week?

   - Implement i.sentinel.download
   - Write the manual page for the download procedure
   - Test and fix bugs for both i.sentinel.preproc and i.sentinel.mask
   - Start preparing deliverables for the final evaluation

3) Is there any blocking issue?
No at the moment.

Here the links to my GitHub repository [2] and wiki page [3]

Kind regards,
Roberta

[0] 
*https://github.com/RobiFag/GRASS_clouds_and_shadows/commit/1ad8f397b1eb6b2b76cf9d037e50a3dfe1a74c0c
*
[1] 
*https://github.com/RobiFag/GRASS_clouds_and_shadows/commit/5758b6c796f8b32c35f35e02a581247ed9ba48a5
*
[2] https://github.com/RobiFag/GRASS_clouds_and_shadows
[3] https://trac.osgeo.org/grass/wiki/GSoC/2018/CloudsAndShadowsDetection
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Help text for r.stats

[Nikos Alexandris]

One observation: `r.stats`'s `--help` returns

```
Parameters:
..
  separator   Field separator
  default: space
..
```

Shouldn't all separator options be listed here?

They are described in the `.html ` page:

```
..
separator=character
   Field separator
   Special characters: pipe, comma, space, tab, newline
   Default: space
..
```

Does this deserve a ticker?

Nikos


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