[QGIS-trac] Re: [Quantum GIS] #1385: "Field" Support for Print Composer

[Quantum GIS]

#1385: "Field" Support for Print Composer
--------------------------------+-------------------------------------------
   Reporter:  neumann           |              Owner:  mhugent      
       Type:  enhancement       |             Status:  new          
   Priority:  minor: annoyance  |          Milestone:  Version 1.6.0
  Component:  Printing          |            Version:  HEAD         
   Keywords:                    |   Platform_version:               
   Platform:  Debian            |           Must_fix:  No           
Status_info:  0                 |  
--------------------------------+-------------------------------------------
Changes (by pcav):

  * milestone:  Version 1.0.3 => Version 1.6.0


Old description:

> It would be useful to have "field" support in the print composer. Fields
> are variables and would be part of text labels in the print composer. The
> field value/content would be replaced when printing/previewing the map
> layout. Fields are common in text-processing.
>
> Potential candidates for fields are:
> * current date, proposed fieldname: currentDate
> * current username (on an operating system level), proposed fieldname:
> currentUser
> * current project title, proposed fieldname: currentProjectTitle
> * current projection, proposed fieldname: currentProjection
> * current map units, proposed fieldname: currentMapUnits
>
> Are there more useful field names in this context?
>
> There would have to be delimiters who separate fieldnames from regular
> text, potential formats:
> <fieldName>
> $fieldName$
> §fieldName§

New description:

 It would be useful to have "field" support in the print composer. Fields
 are variables and would be part of text labels in the print composer. The
 field value/content would be replaced when printing/previewing the map
 layout. Fields are common in text-processing.

 Potential candidates for fields are:

 * current date, proposed fieldname: currentDate

 * current username (on an operating system level), proposed fieldname:
 currentUser

 * current project title, proposed fieldname: currentProjectTitle

 * current projection, proposed fieldname: currentProjection

 * current map units, proposed fieldname: currentMapUnits

 Are there more useful field names in this context?

 There would have to be delimiters who separate fieldnames from regular
 text, potential formats:

 <fieldName>

 $fieldName$

 §fieldName§

--

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/1385#comment:2>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats