LOCATION: This is the name of an available geographic location.
-spearfish- is the sample data base for which all tutorials are written.
This is not true and incomplete. How do I correct it? I suggest:
LOCATION: This is the name of an available Grass location
(data set). "spearfish" is the sample data set for which many
tutorials are written. You can obtain it at http://grass.itc.it.
On Wed, 30 Aug 2006 15:24:12 +0200
Maciej Sieczka <tutey@o2.pl> wrote:
Hi,
Grass text startup screen says:
LOCATION: This is the name of an available geographic location.
-spearfish- is the sample data base for which all tutorials are written.
This is not true and incomplete. How do I correct it? I suggest:
LOCATION: This is the name of an available Grass location
(data set). "spearfish" is the sample data set for which many
tutorials are written. You can obtain it at http://grass.itc.it.
OK?
FWIW, your changes sound good to me. Carefully planned language use
very important.
There were no objections - I will commit this if there still are none.
Paul
On Wed, 30 Aug 2006, Maciej Sieczka wrote:
Hi,
Grass text startup screen says:
LOCATION: This is the name of an available geographic location.
-spearfish- is the sample data base for which all tutorials are written.
This is not true and incomplete. How do I correct it? I suggest:
LOCATION: This is the name of an available Grass location
(data set). "spearfish" is the sample data set for which many
tutorials are written. You can obtain it at http://grass.itc.it.
There were no objections - I will commit this if there still are none.
I must have missed it, sorry.
I prefer my version of location description though. -spearfish- to
"spearfish" or 'spearfish', as this how we usually quote, and explain
where actually spearfish is (few years ago when I used Grass for the
first time (it was the first time I saw linux as well) I thought it
would be delivered together with the program, maybe even already
installed for me somewhere; believe it or not :)).
Wow, you are saying: "-spearfish- is the sample LOCATION provided with
GRASS.". That would puzzle anyone :).
And not "all tutorials", but do mention it - as "many tutorials". It's
no harm, might help.
There were no objections - I will commit this if there still are none.
Paul,
Reading through the text at the link you provide the definition of
database as a unix directory. Perhaps, since there are other platforms
involved it should be rephrased to read
--
DATABASE: This is the directory (folder) containing all the GRASS
locations.
--
I think this terminology would be more understandable to Mac/Windows
users.
I would suggest the following change for two additions for MAPSET. The
first short sentence about a location containing one or more is
intended to make clear that a MAPSET is a subset of a LOCATION. The
second addition at the end is an introduction to the concept of
managing data for different users, modified from the GRASS Quickstart
page. Perhaps the second sentence is too long, but I think the first is
a worthy addition.
--
MAPSET: Every GRASS session runs under a particular MAPSET.
[Addition1] Each LOCATION has one or more MAPSET.
Associated with each MAPSET is a rectangular REGION and a set of maps.
[Addition2] When creating a new location GRASS automatically creates a
special MAPSET called PERMANENT, which is readable by other GRASS
sessions accessing the LOCATION.
--
T
Paul
On Wed, 30 Aug 2006, Maciej Sieczka wrote:
> Hi,
>
> Grass text startup screen says:
>
> LOCATION: This is the name of an available geographic location.
> -spearfish- is the sample data base for which all tutorials are written.
>
> This is not true and incomplete. How do I correct it? I suggest:
>
> LOCATION: This is the name of an available Grass location
> (data set). "spearfish" is the sample data set for which many
> tutorials are written. You can obtain it at http://grass.itc.it.
>
> OK?
>
> Maciek
>
> P.S.
> http://grass.itc.it/download/data.php contains:
>
> GRASS locations (databases)
>
> Let's not mix location and database. I think it could be:
>
> GRASS locations (data sets)
>
> instead.
>
> Maciek
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
There were no objections - I will commit this if there still are none.
Paul
On Wed, 30 Aug 2006, Maciej Sieczka wrote:
Hi,
Grass text startup screen says:
LOCATION: This is the name of an available geographic location.
-spearfish- is the sample data base for which all tutorials are written.
This is not true and incomplete. How do I correct it? I suggest:
LOCATION: This is the name of an available Grass location
(data set). "spearfish" is the sample data set for which many
tutorials are written. You can obtain it at http://grass.itc.it.
I'd recommend changing "the" to "a" and removing the word "all" from the
DATABASE line.
DATABASE: This is a directory (folder) containing the GRASS locations.
There is no reason a user cannot have more than one "DATABASE", but GRASS
needs to know what the database is in order to find locations and mapsets.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
There were no objections - I will commit this if there still are none.
Paul,
Reading through the text at the link you provide the definition of
database as a unix directory. Perhaps, since there are other platforms
involved it should be rephrased to read
--
DATABASE: This is the directory (folder) containing all the GRASS
locations.
--
I think this terminology would be more understandable to Mac/Windows
users.
I would suggest the following change for two additions for MAPSET. The
first short sentence about a location containing one or more is
intended to make clear that a MAPSET is a subset of a LOCATION. The
second addition at the end is an introduction to the concept of
managing data for different users, modified from the GRASS Quickstart
page. Perhaps the second sentence is too long, but I think the first is
a worthy addition.
--
MAPSET: Every GRASS session runs under a particular MAPSET.
[Addition1] Each LOCATION has one or more MAPSET.
Associated with each MAPSET is a rectangular REGION and a set of maps.
[Addition2] When creating a new location GRASS automatically creates a
special MAPSET called PERMANENT, which is readable by other GRASS
sessions accessing the LOCATION.
--
T
Paul
On Wed, 30 Aug 2006, Maciej Sieczka wrote:
Hi,
Grass text startup screen says:
LOCATION: This is the name of an available geographic location.
-spearfish- is the sample data base for which all tutorials are written.
This is not true and incomplete. How do I correct it? I suggest:
LOCATION: This is the name of an available Grass location
(data set). "spearfish" is the sample data set for which many
tutorials are written. You can obtain it at http://grass.itc.it.
There were no objections - I will commit this if there still are none.
Paul,
Reading through the text at the link you provide the definition of
database as a unix directory. Perhaps, since there are other platforms
involved it should be rephrased to read
--
DATABASE: This is the directory (folder) containing all the GRASS
locations.
--
I think this terminology would be more understandable to Mac/Windows
users.
I would suggest the following change for two additions for MAPSET. The
first short sentence about a location containing one or more is
intended to make clear that a MAPSET is a subset of a LOCATION. The
second addition at the end is an introduction to the concept of
managing data for different users, modified from the GRASS Quickstart
page. Perhaps the second sentence is too long, but I think the first is
a worthy addition.
Yes we only have a limited number of lines to work with! (Without it getting very complicated and having to look at other code and adjust things, which is probably more than it's worth doing for this.)
So yes Trevor's additions seem quite worthy but a little bit long. I thought there perhaps there is no need to really mention spearfish seeing (as
Maciek said) that it no longer comes with GRASS by default (AFAIK it used to many years ago) and mentioning it there just confuses things. So if we don't mention spearfish then we can save a line from the Location description and make the Mapset description a line longer. Also took on board all the comments about the Database description and here is the latest version:
LOCATION: This is the name of a geographic location. It is defined by a
co-ordinate system and a rectangular boundary.
MAPSET: Each GRASS session runs under a particular MAPSET. This consists of
a rectangular REGION and a set of maps. Every LOCATION contains at
least a MAPSET called PERMANENT, which is readable by all sessions.
DATABASE: This is a directory (folder) containing the GRASS locations.
The REGION defaults to the entire area of the chosen LOCATION.
You may change it later with the command: g.region
On Thu, 31 Aug 2006 03:07:55 +0100 (BST)
Paul Kelly <paul-grass@stjohnspoint.co.uk> wrote:
-snip-
description and make the Mapset description a line longer. Also took on
board all the comments about the Database description and here is the
latest version:
LOCATION: This is the name of a geographic location. It is defined by a
co-ordinate system and a rectangular boundary.
MAPSET: Each GRASS session runs under a particular MAPSET. This consists of
a rectangular REGION and a set of maps. Every LOCATION contains at
least a MAPSET called PERMANENT, which is readable by all sessions.
DATABASE: This is a directory (folder) containing the GRASS locations.
The REGION defaults to the entire area of the chosen LOCATION.
You may change it later with the command: g.region
The wording looks great. But I did think of one more thing (sorry
Paul). Looking at the text interface to check your comment about
Spearfish, I remembered that when I first used GRASS (some years ago
now) I thought the ordering of fields was odd. Wouldn't it be more
logical to put the DATABASE first and the associated entry field also
first? Since locations are dependent on databases? Thus the order of
description and input would be from the largest unit to the smallest.
It would also place the comment about the region default directly under
the MAPSET description.
If it isn't a big hassle to change it would make the text interface
more similar to the graphic one as well as more logical, so it would be
a nice refinement IMNSHO.
T
--
Trevor Wiens
twiens@interbaun.com
The significant problems that we face cannot be solved at the same
level of thinking we were at when we created them.
(Albert Einstein)
Yes we only have a limited number of lines to work with! (Without it
getting very complicated and having to look at other code and adjust
things, which is probably more than it's worth doing for this.)
So yes Trevor's additions seem quite worthy but a little bit long. I
thought there perhaps there is no need to really mention spearfish
seeing (as Maciek said) that it no longer comes with GRASS by default
(AFAIK it used to many years ago) and mentioning it there just
confuses things. So if we don't mention spearfish then we can save a
line from the Location description and make the Mapset description a
line longer. Also took on board all the comments about the Database
description and here is the latest version:
LOCATION: This is the name of a geographic location. It is defined by
a
co-ordinate system and a rectangular boundary.
MAPSET: Each GRASS session runs under a particular MAPSET. This
consists of
a rectangular REGION and a set of maps. Every LOCATION
contains at least a MAPSET called PERMANENT, which is
readable by all sessions.
DATABASE: This is a directory (folder) containing the GRASS locations.
The REGION defaults to the entire area of the chosen
LOCATION. You may change it later with the command: g.region
sorry if I missed the answer, but what became of the idea to use multi-
sentence tool-tips to explain each field?
The wording looks great. But I did think of one more thing (sorry
Paul). Looking at the text interface to check your comment about
Spearfish, I remembered that when I first used GRASS (some years ago
now) I thought the ordering of fields was odd. Wouldn't it be more
logical to put the DATABASE first and the associated entry field also
first? Since locations are dependent on databases? Thus the order of
description and input would be from the largest unit to the smallest.
It would also place the comment about the region default directly under
the MAPSET description.
Well I guess the thinking with the Database at the bottom is it isn't something you're going to change very much. The cursor is automatically placed in the Location box which is fairly user-friendly.
The order of the descriptions could be changed though as it is most likely to be read by a new user and ease of introduction should be more important here. I'm going to be away for a few days so will look at it next week. The wording of the database description would need to be slightly changed to avoid it looking out of place at the top.
sorry if I missed the answer, but what became of the idea to use multi-
sentence tool-tips to explain each field?
Well Helena said it was a good idea but I didn't receive any further replies. Have to admit I wouldn't actually know where to look to change it myself.
sorry if I missed the answer, but what became of the idea to use multi-
sentence tool-tips to explain each field?
Well Helena said it was a good idea but I didn't receive any further replies. Have to admit I wouldn't actually know where to look to change it myself.
Hamish, this discussion is about the text that shows-up with the old, text-based interface.
The suggestion for tool-tips was for the startup GUI.
After the FOSS4G conference we should start looking into the startup GUI again,
as creating a new location is still problematic,
You can't use tooltips on a text startup screen. For the TclTk startup, the
widgets don't support this kind of help. Rewriting the startup to allow
mouseover help is possible but non-trivial.
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
From: Paul Kelly <paul-grass@stjohnspoint.co.uk>
Date: Fri, 01 Sep 2006 00:23:56 +0100
To: Hamish <hamish_nospam@yahoo.com>
Cc: <grass-dev@grass.itc.it>
Subject: Re: [GRASS-dev] grass63 -text startup screen
Hamish wrote:
sorry if I missed the answer, but what became of the idea to use multi-
sentence tool-tips to explain each field?
Well Helena said it was a good idea but I didn't receive any further
replies. Have to admit I wouldn't actually know where to look to change
it myself.
The suggestion for tool-tips was for the startup GUI.
After the FOSS4G conference we should start looking into the startup
GUI again, as creating a new location is still problematic,
Indeed, maybe folks can start working on a replacement WxPython GUI
welcome screen and new location wizard for 6.3 as a small project.
My hope is that the various WxGUI components can be worked on somewhat
separately by several teams of devels, so the load is not all on 2-4
people. Hopefully in some coordinated way so that we don't get 5
different styles.