Hi all, Victor Olaya and myself are currently at the AGIT in Salzburg and doing a bit of work on the SEXTANTE GRASS interface.
We would like to make two major changes to the current code. From our point of view, they will make the task of maintaining the GRASS interface a lot easier. But since they could also have consequences on people's workflows that we did not consider, I would like to tell you about them here and give you a chance to discuss them in case you have any ideas/objections. 1. Focus development and support on bundled GRASS: Since GRASS is a large collection of individually designed modules, it can be very hard to keep track with all the little changes between GRASS versions and provide a consistently good user experience. Therefore, we would like to consider the intergrated GRASS distribution (the one that also ships with gvSIG OADE) our primary development target. By default, SEXTANTE will automatically find and set up that version so that the user can start working with it right away. The GUI will no longer have the options to set another GRASS version. If users want to do that, they can adjust the configuration files accordingly -- and use any other version of GRASS at their own risk. (We are planning to apply the same strategy to SAGA) 2. Exclusively use temporary mapsets: There are no user-visible benefits to using pre-existing mapsets with the current version of the GRASS interface. To change this situation would require a lot of additional work. Instead, we would like to always have the GRASS interface create a temp mapset and remove the setting from the GUI. Best, Ben ------ Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information. _______________________________________________ Sextante-users mailing list Sextante-users@lists.forge.osor.eu https://lists.forge.osor.eu/listinfo/sextante-users
