2006-08-28 02:12 PM
2006-09-01 08:24 AM
alexliz wrote:not at all. a pen set would have two states. simple.
... but you are making the working Environment a Pen Set attribute rather than Pen Sets an attribute of Saved Views. From a conventional end user's level of database schema, I think this tends to be a little removed.
2006-09-01 02:59 PM
~/archiben wrote:So, if I read you correctly, I'm thinking: it is somewhat disjointed to have to define pens themselves twice for each Pen Set. Just think about it: you go into the Pen Sets dialog, arrange the pen colors and thicknesses, first Pen 1, then Pen 2, then Pen 3 and so on all the way to Pen 255; then go over them again and arrange their alternate state for output use, Pen 1, then Pen 2, then Pen 3 and so on all the way to Pen 255 again. What this does, is, effectively, rendering the working environment (i.e. modelling or outputting) a parameter for the Pen Set; the Pen Set has to ask itself 'What is my current environment?' in order to define itself. Not to mention that you would have to go through the tedious ritual of specifying pen colors and thicknesses unnecessarily for the various Pen Sets, even if their settings are identical (e.g. Pen Sets 'FormalPlots' and 'WorkingPlots' might have different definitions for outputting, but they might share the same definitions for modelling - although both of the same definitions would have to be copiously arranged by the user).
what if the pensets themselves were able to change automatically when in particular environments? so: penset 'A' has a model and layout definition attached to it. depending on the environment you're working in, the pens change themselves?