[GRASS5] list of modules with interface problems

GRASS GRASS developer
1

Hi 2 all,

while reworking the test suite (dejagnu) (should work now) i found some
modules not reacting correctly to the "help" parameter on command line.
I added these modules with a short description to the BUGS file.

Some modules do produce "garbage" output with the
"--interface-description" flag, which makes the output fail parsing with
a xml parser. For your information here the list of modules:

{m.lulc.USGS} {Mlulc.read} {Mlulc.USGS} {v.surf.rst} {v.out.atlas}
{v.in.dxf2} {v.in.dxf} {v.in.atlas} {s.surf.rst} {r.weighted.cn}
{r.resamp.rst} {r.random} {r.out.rlc} {r.mapcalc} {r.flow} {r.colors}
{m.in.stf1.db3} {m.in.pl94.db3} {i.tape.mss.h} {i.gensigset} {g.list}
{d.where} {d.rhumbline} {d.paint.labels} {d.colormode}

(sorry, as tcl-list structure).

The testsuite will produce an additional file "modules-list.html" in the
documents dir with a summary of the status of all modules (not perfectly
formatted). The first status field is generated from the
list5_of_modules.txt file, which can be modified by hand to reflect
differences from the automated tests.

cu,

Andreas

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

2

Hi Andreas,

On Sun, Oct 29, 2000 at 07:34:55PM +0100, Andreas Lange wrote:

Some modules do produce "garbage" output with the
"--interface-description" flag, which makes the output fail parsing with
a xml parser. For your information here the list of modules:

{m.lulc.USGS} {Mlulc.read} {Mlulc.USGS} {v.surf.rst} {v.out.atlas}
{v.in.dxf2} {v.in.dxf} {v.in.atlas} {s.surf.rst} {r.weighted.cn}
{r.resamp.rst} {r.random} {r.out.rlc} {r.mapcalc} {r.flow} {r.colors}
{m.in.stf1.db3} {m.in.pl94.db3} {i.tape.mss.h} {i.gensigset} {g.list}
{d.where} {d.rhumbline} {d.paint.labels} {d.colormode}

thanks for testing!

It seems that most people like the idea of an xml-based user interface
description for GRASS commands.

So I will now complete the xml output ('multiple' etc.), finish the
corresponding dtd and check for problems.

Cheers

  Jan

--
Jan-Oliver Wagner http://intevation.de/~jan/

Intevation GmbH http://intevation.de/
FreeGIS http://freegis.org/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

3

Hi there,

On Sun, Oct 29, 2000 at 07:34:55PM +0100, Andreas Lange wrote:

Hi 2 all,

while reworking the test suite (dejagnu) (should work now) i found some
modules not reacting correctly to the "help" parameter on command line.
I added these modules with a short description to the BUGS file.

Some modules do produce "garbage" output with the
"--interface-description" flag, which makes the output fail parsing with
a xml parser. For your information here the list of modules:

{m.lulc.USGS} {Mlulc.read} {Mlulc.USGS} {v.surf.rst} {v.out.atlas}
{v.in.dxf2} {v.in.dxf} {v.in.atlas} {s.surf.rst} {r.weighted.cn}
{r.resamp.rst} {r.random} {r.out.rlc} {r.mapcalc} {r.flow} {r.colors}
{m.in.stf1.db3} {m.in.pl94.db3} {i.tape.mss.h} {i.gensigset} {g.list}
{d.where} {d.rhumbline} {d.paint.labels} {d.colormode}

Here some comments:

{m.lulc.USGS} old "parser" (GRASS 3.x), needs update

{Mlulc.read} can we deprecate this module in src.contrib?
                (already in src/misc/!)
{Mlulc.USGS} can we deprecate this module in src.contrib?
                (already in src/misc/!)
{m.in.stf1.db3} old parser, needs update [can we deprecate this module?]
{m.in.pl94.db3} old parser, needs update [can we deprecate this module?]

{r.weighted.cn} old parser (GRASS 3.x), needs update
{r.out.rlc} : old parser (GRASS 3.x), needs update [can we deprecate this
              module?]
{r.mapcalc} : problem is parser, no idea to fix this

{v.out.atlas} just fixed by Markus.
{v.in.atlas} just fixed by Markus.

{s.surf.rst} problem is in output of references (Helena ?):
               -> should have extra flag
{r.resamp.rst} problem is in output of references (Helena ?):
              -> should have extra flag
{v.surf.rst} problem is in output of references (Helena ?):
              -> should have extra flag
{r.flow} problem is in output of references (Helena ?):
                -> should have extra flag

{r.random}: needs to get parameter sensivity:
             -> see d.zoom for useful implementation

Here the help parameter seems to be o.k. (for me):
{r.colors} problem?
{i.tape.mss.h} problem?
{i.gensigset} problem?
{g.list} problem?
{d.where} problem?
{d.rhumbline} problem?
{d.paint.labels} problem?
{d.colormode} problem?
{v.in.dxf2} problem?
{v.in.dxf} problem?

So it might be an XML-problem (hi Jan).

So far my short report

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

4

Hi Markus, Andreas, all others,

On Mon, Oct 30, 2000 at 11:09:10AM +0000, Markus Neteler wrote:

On Sun, Oct 29, 2000 at 07:34:55PM +0100, Andreas Lange wrote:
> while reworking the test suite (dejagnu) (should work now) i found some
> modules not reacting correctly to the "help" parameter on command line.
> I added these modules with a short description to the BUGS file.
>
> Some modules do produce "garbage" output with the
> "--interface-description" flag, which makes the output fail parsing with
> a xml parser. For your information here the list of modules:
>
> {m.lulc.USGS} {Mlulc.read} {Mlulc.USGS} {v.surf.rst} {v.out.atlas}
> {v.in.dxf2} {v.in.dxf} {v.in.atlas} {s.surf.rst} {r.weighted.cn}
> {r.resamp.rst} {r.random} {r.out.rlc} {r.mapcalc} {r.flow} {r.colors}
> {m.in.stf1.db3} {m.in.pl94.db3} {i.tape.mss.h} {i.gensigset} {g.list}
> {d.where} {d.rhumbline} {d.paint.labels} {d.colormode}

Here the help parameter seems to be o.k. (for me):
{r.colors} problem?
{i.tape.mss.h} problem?
{i.gensigset} problem?
{g.list} problem?
{d.where} problem?
{d.rhumbline} problem?
{d.paint.labels} problem?
{d.colormode} problem?
{v.in.dxf2} problem?
{v.in.dxf} problem?

So it might be an XML-problem (hi Jan).

for r.colors, g.list, v.in.dxf and v.in.dxf2 the commands output
'more_usage()' to stderr when G_parser() returns something < 0.
I would like to have these additional information in the xml
ui-description, but in that case some new features need
to be added to the structures carrying the interface information
for G_parser() - anyone volunteers to harmonizes this?

However, it does not distrub the parser since --interface-description
will invoke output to stdout. Hence on a bash with
r.colors --interface-specification 2>/dev/null you will see
only the xml description. The stuff from 'more_usage()' will
also have no influence when piping the xml stuff to the gui
builder.

I haven't found a problem for the other commands.

Cheers

  Jan

--
Jan-Oliver Wagner http://intevation.de/~jan/

Intevation GmbH http://intevation.de/
FreeGIS http://freegis.org/

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

5

Hi Markus, Hi developers,

i am a bit in a hurry, so i can only outline some of the problems in
general:

some modules have characters in their parser-descriptions that cause
errors with the xml-parser (e. g. 'w/' or control chars like '\b', '\g'
etc., '&' in texts and more).

i found that some modules exit with an error msg. before calling the
parser initialization if in a location that doesn't suit their
capabilities (e. g. module for importing utm data in ll location). This
should be avoided generally to be consistent.

For the references and authors output we should later implement
something in the parser interface.

One module opens a log file that is always left behind with the message
that nothing went wrong.

And for some modules i simply do not remember what the problem was.

I think that we should waste our time first on fixing more modules.

cu,

Andreas

Markus Neteler wrote:

Here the help parameter seems to be o.k. (for me):
{r.colors} problem?
{i.tape.mss.h} problem?
{i.gensigset} problem?
{g.list} problem?
{d.where} problem?
{d.rhumbline} problem?
{d.paint.labels} problem?
{d.colormode} problem?
{v.in.dxf2} problem?
{v.in.dxf} problem?

So it might be an XML-problem (hi Jan).

So far my short report

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

--
Andreas Lange, 65187 Wiesbaden, Germany, Tel. +49 611 807850
Andreas.Lange@Rhein-Main.de - A.C.Lange@GMX.net

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'