Hello Community, I am sending my report for Week 1 (June 1-June 5). The report can also be found in the project wiki: https://trac.osgeo.org/…dow (https://trac.osgeo.org/grass/wiki/GSoC/2020/StartupWindow). 1) What did I complete this week? I created a single PR related to the bigger topic related to changes in EPSG page ( https://github.com/OSGeo/grass/pull/670 (https://github.com/OSGeo/grass/pull/670)). I made a change in layout definition. Now it is defined by boxSizer instead of gridBagSizer. Also, path to usr/share/proj/epsg was removed. Search and EPSG code text inputs were merged into one search input. An informative link to epsg.io was added. Removing the picture of the world: https://github.com/OSGeo/grass/pull/657 (https://github.com/OSGeo/grass/pull/657) was already merged into master. Similarly, I am already done with the automatic detection of case- independent cases of grassdata directory: https://github.com/OSGeo/grass/ pull/664(https://github.com/OSGeo/grass/pull/664) (issue: https://github. com/OSGeo/grass/issues/644(https://github.com/OSGeo/grass/issues/644).) 2) What am I going to achieve next week? Next week I am going to continue on PR regarding the EPSG page ( https:// github.com/OSGeo/grass/pull/670(https://github.com/OSGeo/grass/pull/670)). The layout is done, now I am gonna focus on events. There are several requirements: * searching in a list on the fly * choose automatically the first row and permit "next" button * if epsg code is empty, nothing is selected and "next" button is not active * change informative URL according to a query string Furthermore, I am gonna work on improvement when GRASS should create a grassdata directory in the default path for its platform automatically ( https://github.com/OSGeo/grass/issues/682 (https://github.com/OSGeo/grass/issues/682)). 3) Is there any blocking issue? No, it isn't. Regards, Linda Kladivova
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
