Hi all,
I had created an interface for v.net.path currently works with only spearfish data . but soon will be changed to use any map after getting response from grass-dev ML.
http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.path
Any comments and suggestion are always welcome.
Rashad
Hi,
2010/6/19 Mohammed Rashad <rashadkm@yahoo.com>:
I had created an interface for v.net.path currently works with only
spearfish data . but soon will be changed to use any map after getting
response from grass-dev ML.
http://trac.osgeo.org/grass/browser/grass-addons/gui/wxpython/wx.pathAny comments and suggestion are always welcome.
see my already sent comment...
please don't use full copies of wxGUI classes (similar for data
catalog) when you are implementing new features. Better is to define
subclasses based on the original wxGUI classes and to provided patches
via trac for superclasses from trunk if necessary. Otherwise the code
is unreadable, hard to maintain and timeconsuming task to merge it
with trunk.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
As I understand, d.path with its coor= option should do
everything needed already. What is needed is to integrate d.path
into a new tool for the wx GUI which prompts the user to set
start and end points in the map display window. then it draws a
shortest path graphics layer on the screen. The legend and
scalebar "Add map elements" mini-drop down menu in the map display
GUI shows some similar rendering examples which might help. The
actual shortest path tool should probably be put in the "Analyze"
drop down menu.
Between the "measure distance" to grab the coordinates, and "add
scalebar" as an example of drawing it the basic method can be
worked out.
regards,
Hamish