Bug 109430 - Add reserved areas (flow-around objects) + list of fields
Summary: Add reserved areas (flow-around objects) + list of fields
Status: RESOLVED INTENTIONAL
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.x
Platform: unspecified Solaris
: VLO wishlist
Target Milestone: ---
Assignee: kst
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-21 19:13 UTC by Nicolas Brisset
Modified: 2006-02-15 00:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Brisset 2005-07-21 19:13:47 UTC
Version:           1.2.0_devel (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.4.3
OS:                SunOS (sun4u) release 5.8

In another (internal) tool that is used here, a number of context information are shown around the graph area, and it makes it *really* easier to remember what you are looking at 3 months later, when you have a couple hundred sheets lying around.

I've been thinking about this a bit, and I'd suggest to implement an extra "flow around" property for the forthcoming drawing objects (I'll attach a comment to bug #108027 since it really belongs there). To keep things fairly simple, the area in which graphs can be drawn would be the internal rectangle delimited by all such objects and it could be left up to the user to put them on the sides...
Now, if that is implemented, the next thing would be to have special fields that can be used and substituted at drawing time (very much like date/time/name/etc... fields in your favorite word processor). For a start, I'd include:
- list of datasources in use
- date
- time
- page number
- total number of pages
- user name
- organization
- user e-mail
- I suppose it wouldn't be too difficult to allow the user to add custom fields as well...
Comment 1 George Staikos 2005-10-26 19:23:50 UTC
Those fields should be a separate feature request and can easily be implemented as scalars and strings I think.  Some will require deriving.  As for the flow-around idea, that requires some layouting and relative positioning to do in a useful way, and we don't really have a concept of that yet.  It needs quite some design work.
Comment 2 Nicolas Brisset 2005-11-02 11:37:10 UTC
I am not sure I completely understand the idea behind bug #115136. Does this new bug obsolete the "reserved areas" part of this one ? In other words, if a rectangle on one side of the page is set to not follow the flow, will plots be drawn in the remaining part of the page ?
If that is the case, I should close this bug and open a new one for "special fields"...
Comment 3 George Staikos 2005-11-02 17:00:57 UTC
On Wednesday 02 November 2005 05:37, Nicolas Brisset wrote:
> 11:37 ------- I am not sure I completely understand the idea behind bug
> #115136. Does this new bug obsolete the "reserved areas" part of this one ?
> In other words, if a rectangle on one side of the page is set to not follow
> the flow, will plots be drawn in the remaining part of the page ? If that
> is the case, I should close this bug and open a new one for "special
> fields"...


  Slightly different.  The other one is mainly about the grid concept.  Your 
feature would build on what is in that one.
Comment 4 Netterfield 2006-02-15 00:49:44 UTC
Text boxes provide a place to put scalars and labels.
Strings need to implemented for the rest.