Changes between Version 6 and Version 7 of GSoC/2018/IntegrationInQGIS3


Ignore:
Timestamp:
Jun 10, 2018, 2:12:31 PM (6 years ago)
Author:
radeknovotny94
Comment:

Add week 4 report

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2018/IntegrationInQGIS3

    v6 v7  
    5858}}}
    5959{{{#!td
    60 In progress
     60Done
    6161}}}
    6262|-----------------------
     
    8080}}}
    8181{{{#!td
     82In progress
    8283}}}
    8384|-----------------------
     
    9091}}}
    9192{{{#!td
     93In progress
    9294}}}
    9395|-----------------------
     
    240242'''3) Is there any blocking issue?'''\\
    241243
    242 I am blocked with generating XML descriptions from GRASS.(1) 
     244I am blocked with generating XML descriptions from GRASS. (1) 
    243245
    244246(1) https://github.com/radeknovotny94/GRASS_Parse_to_QGIS_UI/blob/master/generate_batch_for_xml.py \\
     
    269271'''What did you get done this week?'''\\
    270272
    271 - I was almost working on the improvement of the library for parsing description files for QGIS Processing plugin. (1)
     273- I was working on the improvement of the library for parsing description files for QGIS Processing plugin. (1)
    272274- I test creating of GUI from descriptions.
    273275
     
    282284
    283285(1) https://github.com/radeknovotny94/GRASS_Parse_to_QGIS_UI\\
     286
     287== Week 4 ==
     288
     289'''What did you get done this week?'''\\
     290
     291- I finalized the library for parsing description files for QGIS Processing plugin. But of course I suppose, there will occur some bugs, after testing modules in QGIS Processing plugin. (1)
     292- Add 'Controversy decision' in building parser to wiki. (2)
     293
     294'''What do you plan on doing next week?'''\\
     295
     296- Split GRASS module parameters in Processing plugin to basic and advanced tabs - it should be required and optional tab.
     297- Check GRASS X QGIS parameter descriptions in order to take care of differences in terminology.
     298
     299'''Are you blocked on anything?'''\\
     300
     301- No, at the moment I’m not blocked.
     302
     303(1) https://github.com/radeknovotny94/GRASS_Parse_to_QGIS_UI\\
     304(2) https://trac.osgeo.org/grass/wiki/GSoC/2018/IntegrationInQGIS3
     305
     306== Controversy decision: ==
     307If 'prompt' is 'raster_3d'
     308        - if this parameter is required - delete description file for QGIS Processing, because Processing does not have 3D Raster class. Could be resolve later.
     309        - if it is optional - pass this parameter
     310        - in both cases is give information about the parameter to log
     311
     312Examples:
     313Not required parameter:
     314r.colors
     315Not recognized >>> raster_3d
     316
     317Required parameter:
     318r.to.rast3
     319Need of 3D raster for module >>> r.to.rast3
     320----------------------------------------------------------------------------------
     321If 'prompt' is 'group':
     322        - only in module 'i.group' is parameter 'group' output
     323        - in all other modules should be 'group' input
     324                -if it is in 'r.' module, it is treated like raster multilayer
     325                -if it is in 'v.' module, it is treated like vector multilayer
     326----------------------------------------------------------------------------------
     327What is treating as the string in QGIS Processing:
     328
     329        - Separators - 'separator' and all names which have not equivalent class in Processing plugin - 'color', 'cats', 'dbname', 'dbtable'.
     330----------------------------------------------------------------------------------
     331GRASS GIS layer and sublayer is passed because it is no equivalent in QGIS.