[GRASS-dev] instructions for programming of a g.gui.* module

Hi,

A computer science student of our university will probably start working on an active learning framework for image classification in GRASS. This means (in brief) selecting some pixels/objects and assigning them to a class, using them to train a machine learning classifier and then identifying those unclassified pixels/objects that would best improve the classification if the user assigned them a class.

There will, therefore, be some interaction between the user and the GUI and I was wondering if there is some howto explaining how to approach the coding of a g.gui.* module. I know there is the GUI part of the programmers manual [1], but this is "just" a list of functions and classes, but no introduction.

Any pointers ?

Thanks !

Moritz

[1] https://grass.osgeo.org/programming6/wxpythonlib.html

On Mon, Oct 17, 2016 at 11:59 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Hi,

A computer science student of our university will probably start working on
an active learning framework for image classification in GRASS. This means
(in brief) selecting some pixels/objects and assigning them to a class,
using them to train a machine learning classifier and then identifying those
unclassified pixels/objects that would best improve the classification if
the user assigned them a class.

There will, therefore, be some interaction between the user and the GUI and
I was wondering if there is some howto explaining how to approach the coding
of a g.gui.* module. I know there is the GUI part of the programmers manual
[1], but this is "just" a list of functions and classes, but no
introduction.

Any pointers ?

I believe the only thing there is is this example of GUI application:
https://trac.osgeo.org/grass/browser/grass/trunk/doc/gui/wxpython/example

but I am pretty sure it needs to be updated, because it's couple years old.

Anna

Thanks !

Moritz

[1] https://grass.osgeo.org/programming6/wxpythonlib.html
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Le 17 octobre 2016 18:10:59 GMT+02:00, "Anna Petrášová" <kratochanna@gmail.com> a écrit :

On Mon, Oct 17, 2016 at 11:59 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Hi,

A computer science student of our university will probably start

working on

an active learning framework for image classification in GRASS. This

means

(in brief) selecting some pixels/objects and assigning them to a

class,

using them to train a machine learning classifier and then

identifying those

unclassified pixels/objects that would best improve the

classification if

the user assigned them a class.

There will, therefore, be some interaction between the user and the

GUI and

I was wondering if there is some howto explaining how to approach the

coding

of a g.gui.* module. I know there is the GUI part of the programmers

manual

[1], but this is "just" a list of functions and classes, but no
introduction.

Any pointers ?

I believe the only thing there is is this example of GUI application:
https://trac.osgeo.org/grass/browser/grass/trunk/doc/gui/wxpython/example

but I am pretty sure it needs to be updated, because it's couple years
old.

Thanks, Anna !

Moritz

Anna

Thanks !

Moritz

[1] https://grass.osgeo.org/programming6/wxpythonlib.html
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

On 17/10/16 18:10, Anna Petrášová wrote:

On Mon, Oct 17, 2016 at 11:59 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Hi,

A computer science student of our university will probably start working on
an active learning framework for image classification in GRASS. This means
(in brief) selecting some pixels/objects and assigning them to a class,
using them to train a machine learning classifier and then identifying those
unclassified pixels/objects that would best improve the classification if
the user assigned them a class.

There will, therefore, be some interaction between the user and the GUI and
I was wondering if there is some howto explaining how to approach the coding
of a g.gui.* module. I know there is the GUI part of the programmers manual
[1], but this is "just" a list of functions and classes, but no
introduction.

Any pointers ?

I believe the only thing there is is this example of GUI application:
https://trac.osgeo.org/grass/browser/grass/trunk/doc/gui/wxpython/example

but I am pretty sure it needs to be updated, because it's couple years old.

Well, for starters,

make MODULE_TOPDIR=../../../../dist.x86_64-pc-linux-gnu/

gives me:

Traceback (most recent call last):
   File "/home/mlennert/SRC/GRASS/grass_trunk/dist.x86_64-pc-linux-gnu/scripts/g.gui.example", line 45, in <module>
     from core.utils import _, GuiModuleMain
ImportError: cannot import name GuiModuleMain

I'll look at this more in detail when I have the time...

Moritz

On Mon, Oct 17, 2016 at 3:16 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 17/10/16 18:10, Anna Petrášová wrote:

On Mon, Oct 17, 2016 at 11:59 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

Hi,

A computer science student of our university will probably start working
on
an active learning framework for image classification in GRASS. This
means
(in brief) selecting some pixels/objects and assigning them to a class,
using them to train a machine learning classifier and then identifying
those
unclassified pixels/objects that would best improve the classification if
the user assigned them a class.

There will, therefore, be some interaction between the user and the GUI
and
I was wondering if there is some howto explaining how to approach the
coding
of a g.gui.* module. I know there is the GUI part of the programmers
manual
[1], but this is "just" a list of functions and classes, but no
introduction.

Any pointers ?

I believe the only thing there is is this example of GUI application:
https://trac.osgeo.org/grass/browser/grass/trunk/doc/gui/wxpython/example

but I am pretty sure it needs to be updated, because it's couple years
old.

Well, for starters,

make MODULE_TOPDIR=../../../../dist.x86_64-pc-linux-gnu/

gives me:

Traceback (most recent call last):
  File
"/home/mlennert/SRC/GRASS/grass_trunk/dist.x86_64-pc-linux-gnu/scripts/g.gui.example",
line 45, in <module>
    from core.utils import _, GuiModuleMain
ImportError: cannot import name GuiModuleMain

I think I removed GuiModuleMain, which tried to fork the process
because it didn't work on other platforms than linux

I'll look at this more in detail when I have the time...

Moritz