[GRASS-dev] Re: [GRASS-user] Freetype fonts in gis.m

[Michael Barton]

You should also be able to set a 'default' font. The font= argument should
be optional. If left out of the command, it defaults to the default font.
The default font could be set (as now) with d.font*

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Hamish <hamish_nospam at yahoo.com>
> Date: Mon, 12 Jun 2006 20:06:09 +1200
> To: Michael Barton <michael.barton at asu.edu>
> Cc: <glynn at gclements.plus.com>, <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-user] Freetype fonts in gis.m
> 
> [might as well move this off the -user list]
> 
> Michael Barton wrote:
>> More generally, to make the d.* commands most efficiently useable from
>> the command line and for scripting, it makes sense to add a font=
>> option to all that need it. That is, d.legend by itself should be able
>> to set which font it uses. It can already set everything else except
>> the font.
> 
> The question remains how to easily retain a font setting if the display
> monitors will be stateless. From the command line having to retype it
> for every module is highly annoying. Right now I just need to set my TTF
> font once per session.
> 
> * I want to be able to set a default font. (optionally TTF)
> * I want to keep the modules as simple as possible. (e.g. d.vect+new user)
> 
> 
> 
> fyi, Matlab's way:   [each is a child of the one above]
> 
> "root" has certain settings (CLI and system wide settings)
>   (More = off, ScreenDepth = [24], Children =, etc)
> 
> then
> "figure" windows have their settings
>   (DoubleBuffer = on, PaperType = a4, MenuBar =, Position =, Children =, ...)
> 
> then
> "axes" have their settings
>   (GridLineStyle =, Title =, XTickLabel =, Projection = orthographic, Children
> =, ...)
> 
> then
> "lines" [etc] have their settings
>   (Color =, LineStyle =, LineWidth =, Data = [X Y], ...)
> 
> 
> each level has a pointer you can get() or set() features with. e.g. root
> is 0, figure1 is 1, figure2 is 2, etc.
> 
> 
> maybe a useful paradigm to consider, as the two programs are
> structurally very similar creatures.
> 
> 
> Hamish