[GRASS-dev] Weekly reports #2 wxNviz

Hi all,

1) What did I do last week [1]

* I have fixed some bugs mostly related to the redesigned GUI (nviz
tool window integrated into Layer Manager) and started working on
lighting.

2) What do I plan to do this week [3]

* Finish lighting and probably I would like to start implementing decorations.

3) Do I have any problems/obstacle which interfere with my work

* Not really, I just a little bit behind the schedule because of the
time I have spent by fixing unexpected bugs in wxNviz.

Best regards, Martin Landa

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

Martin,

I think you forgot the links :wink:

--Wolf

Hi Wolf,

2010/6/8 Wolf Bergenheim <wolf+grass@bergenheim.net>:

I think you forgot the links :wink:

right, thanks for pointing this out.

Martin

[1] http://grass.osgeo.org/wiki/WxNviz_GSoC_2010#Week_1_.28May_31.29
[2] /dev/null :wink:
[3] http://grass.osgeo.org/wiki/WxNviz_GSoC_2010#Week_1_.28May_31.29

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

Martin Landa wrote:

2) What do I plan to do this week [3]

* Finish lighting and probably I would like to start implementing decorations.

I don't suppose there's any chance that you can take this opportunity
to sort out the mess that is OGSF's state management?

The lighting and material parameters are stored in half a dozen
different places (some of them completely pointless, e.g.
ogl_{light,mat}_* in gsd_prim.c).

A good test of whether the design is sane is to try replicating the
current view in another window with a different context. If it takes
pages of code to get the current state out of the libraries, or if you
end up storing the same information in both the application and the
libraries, then the design is wrong.

--
Glynn Clements <glynn@gclements.plus.com>