#190: Extend the Trac Components list for GRASS
-------------------------+--------------------------------------------------
Reporter: mloskot | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Website | Version: unspecified
Keywords: trac |
-------------------------+--------------------------------------------------
I've found there are some options missing in the list of components of New
Ticket form. I'd suggest to add:
* Building/Setup
* Vector support
* Raster support
* GUI (or separate component for each GUI version)
#190: Extend the Trac Components list for GRASS
--------------------------+-------------------------------------------------
Reporter: mloskot | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: closed
Priority: major | Milestone:
Component: Website | Version: unspecified
Resolution: fixed | Keywords: trac
--------------------------+-------------------------------------------------
Comment (by martinl):
I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is
also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to
rename 'Tcl' to 'Tcl/Tk GUI' and add 'wxGUI' component for wxPython-based
GUI. Existing 'Python' component could be used for Python/Swig or maybe
for python scripts in GRASS.
I added new component for wxGUI and moved all the related tickets. I am
not sure about renaming 'Tcl' to 'Tcl/Tk GUI'...
Martin
> I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is
also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to
rename 'Tcl' to 'Tcl/Tk GUI' and add 'wxGUI' component for wxPython-based
GUI. Existing 'Python' component could be used for Python/Swig or maybe
for python scripts in GRASS.
#190: Extend the Trac Components list for GRASS
--------------------------+-------------------------------------------------
Reporter: mloskot | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: reopened
Priority: major | Milestone:
Component: Website | Version: unspecified
Resolution: | Keywords: trac
--------------------------+-------------------------------------------------
Comment (by neteler):
We have to ask the QGIS people how they made this "platform" property.
From the trac Webadmin interface it isn't visible. Anyone having a good
contact to a QGIS trac admin?
#190: Extend the Trac Components list for GRASS
--------------------------+-------------------------------------------------
Reporter: mloskot | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: closed
Priority: major | Milestone:
Component: Website | Version: unspecified
Resolution: fixed | Keywords: trac
--------------------------+-------------------------------------------------
Comment (by martinl):
I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is
also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to
rename 'Tcl' to 'Tcl/Tk GUI'
It could also refer to the "form" library used by d.what.vect, v.what
and NVIZ, the Tcl/Tk version of v.digit, or to the Tcl/Tk version of
d.rast.edit.
I agree, currently 'Tcl' component is used for Tcl/Tk GUI (note there is
also 'Nviz' component) and 'Python' for wxGUI. Here I would suggest to
rename 'Tcl' to 'Tcl/Tk GUI'
It could also refer to the "form" library used by d.what.vect, v.what
and NVIZ, the Tcl/Tk version of v.digit, or to the Tcl/Tk version of
d.rast.edit.
yes, if no objections I will rename 'Tcl' to 'Tcl/Tk GUI' (seems to me
less confusing for the trac users)... Maybe 'NVIZ' component can be
removed (as part of 'Tcl/Tk GUI')?
#190: Extend the Trac Components list for GRASS
--------------------------+-------------------------------------------------
Reporter: mloskot | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: reopened
Priority: major | Milestone:
Component: Website | Version: unspecified
Resolution: | Keywords: trac
--------------------------+-------------------------------------------------
Comment (by glynn):
Replying to [comment:4 hamish]:
> A "Platform" property would be nice too, like qgis has in their trac.
>
> eg MSWindows/OSX/Linux/Solaris/BSD/All/Unspecified
I think that you can combine all non-Linux Unices into "Other Unix". OTOH,
we might want to distinguish between Windows 2K/XP/Vista (we also need a
separate entry for Cygwin, but I don't know if it matters which version of
Windows Cygwin is running on). It may also be worth recording the CPU
type, as there are quite a few issues which only show upon on e.g. x86-64
or OSX/PPC.