Thanks, quite some interesting GSoC ideas. I took the liberty to add one on “tools for generating unit tests from examples in module manuals”. Not sure if that is feasible or out of scope. Please feel free to remove it if you don`t find it suitable (I can`t mentor it anyway).
Regarding: https://trac.osgeo.org/grass/wiki/GSoC/2017#AdditionalfunctionalityforrunningGRASSGISmodulesinJupyterNotebook (which I also very much like to see become reality, esp. a function like “initGRASS()” from rgrass7) I have the question if that by chance is supposed to be related to last years GSoC on a WebGUI for GRASS (see: https://trac.osgeo.org/grass/wiki/GSoC/2016/WebGrass). In order to be really useful, WebGRASS would need a console, and here Jupyter was already mentioned as an option. In addition the WebUI struggled quite a bit with renderinig… So will this proposal be complementary? Cheers Stefan From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of Vaclav Petras Sent: torsdag 26. januar 2017 00.22 To: grass-dev@lists.osgeo.org Subject: Re: [GRASS-dev] Reviewing GSoC 2017 page Worked. Thanks for tuning the spam filter, Markus. I just put all the new things at the beginning. On Wed, Jan 25, 2017 at 10:01 AM, Vaclav Petras <wenzesl...@gmail.com<mailto:wenzesl...@gmail.com>> wrote: Can somebody reorder the ideas so that the fresh ideas are at the top? When I try it, I get "Too many links" or "Page not modified". Thanks, Vaclav
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
