Hi List,
I've generated a couple of color rules files that I'd like to persist across version upgrades. Is there a place to put them on Mac OSX where they will be found, but won't be lost when I upgrade? I tried creating them in $HOME/Library/GRASS/6.2/Modules/etc/colors but it appears that GRASS isn't looking in that location.
Cheers,
Mike
I recently added a function to handle an external etc/ folder, but it currently isn't used in the core modules, but was intended more for addon modules that need to use an external etc/.
You can make a feature request to support this in r.colors. I don't know if I'd be able to tackle it - the added function I mentioned strained my limited C skills. That would be a nice feature.
This would only work in 6.3 CVS, if added. There is no such external etc/ function in 6.2 and won't be added there.
On Aug 8, 2007, at 2:09 PM, Michael Perdue wrote:
Hi List,
I've generated a couple of color rules files that I'd like to persist across version upgrades. Is there a place to put them on Mac OSX where they will be found, but won't be lost when I upgrade? I tried creating them in $HOME/Library/GRASS/6.2/Modules/etc/colors but it appears that GRASS isn't looking in that location.
Cheers,
Mike
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
All generalizations are dangerous, even this one.
Oh, and it looks like "r.colors rules=" can take a path to a color rule file. So you could still put them in your home grass/etc and just use the full path them.
On Aug 8, 2007, at 2:09 PM, Michael Perdue wrote:
Hi List,
I've generated a couple of color rules files that I'd like to persist across version upgrades. Is there a place to put them on Mac OSX where they will be found, but won't be lost when I upgrade? I tried creating them in $HOME/Library/GRASS/6.2/Modules/etc/colors but it appears that GRASS isn't looking in that location.
Cheers,
Mike
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"This is a question about the past, is it? ... How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensations and my state of mind?"
- The Ruler of the Universe
Thanks for the info. It would be nice if one could have external directories where color tables and such could be stored, but it also sounds like it would be a lot of work for a small return. I think I'll keep my color tables in the etc/ folder and create symbolic links to them in the proper folder. That should be easy enough to maintain.
Cheers,
Mike
On 8-Aug-07, at 1:25 PM, William Kyngesburye wrote:
I recently added a function to handle an external etc/ folder, but it currently isn't used in the core modules, but was intended more for addon modules that need to use an external etc/.
You can make a feature request to support this in r.colors. I don't know if I'd be able to tackle it - the added function I mentioned strained my limited C skills. That would be a nice feature.
This would only work in 6.3 CVS, if added. There is no such external etc/ function in 6.2 and won't be added there.
On Aug 8, 2007, at 2:09 PM, Michael Perdue wrote:
Hi List,
I've generated a couple of color rules files that I'd like to persist across version upgrades. Is there a place to put them on Mac OSX where they will be found, but won't be lost when I upgrade? I tried creating them in $HOME/Library/GRASS/6.2/Modules/etc/colors but it appears that GRASS isn't looking in that location.
Cheers,
Mike
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/All generalizations are dangerous, even this one.
Yes, it looks like it would be a bit complex. I looked at r.colors, and it would take a bit or rewriting to handle the way I wrote the find_etc function, or I may need to consider a new variation on the function to handle the way r.colors works.
Symlinks of the color files in the application package would be marginally safer than the files themselves - you wouldn't lose the files, but you may still have to recreate the symlinks.
Did you try using the full path to the color files?
On Aug 9, 2007, at 10:54 AM, Michael Perdue wrote:
Thanks for the info. It would be nice if one could have external directories where color tables and such could be stored, but it also sounds like it would be a lot of work for a small return. I think I'll keep my color tables in the etc/ folder and create symbolic links to them in the proper folder. That should be easy enough to maintain.
Cheers,
Mike
On 8-Aug-07, at 1:25 PM, William Kyngesburye wrote:
I recently added a function to handle an external etc/ folder, but it currently isn't used in the core modules, but was intended more for addon modules that need to use an external etc/.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
Earth: "Mostly harmless"
- revised entry in the HitchHiker's Guide to the Galaxy
Did you try using the full path to the color files?
Sure did, but that functionality doesn't work in GRASS6.2.X. I looked at the man page for GRASS6.3 and it looks like that functionality will be available in future (along with some other very useful flags like logarithmic scaling of color tables for FP maps). Also, if I'm using these color tables frequently, it would be a lot of typing to type the full path to the color tables repeatedly.
Cheers,
Mike
Michael Perdue wrote:
> Did you try using the full path to the color files?
Sure did, but that functionality doesn't work in GRASS6.2.X.
You can get the same result in 6.2 by redirecting stdin, e.g.
r.colors mapname color=rules < /path/to/rules_file
--
Glynn Clements <glynn@gclements.plus.com>