[mapguide-internals] RFC 14(CartographicStylizationEngine)comments

[Traian Stanev]

> About being able to set size, etc, based on expressions...  These
would
> have to be defined at the layer level, wouldn't they?

Yes. That's why symbol expressions can be parametrized in the
SymbolInstance (which is in the layer definition). See the
ParameterOverrides element. In any case, this doesn't matter for the
ScaleX and ScaleY since those are defined in the SymbolInstance which is
already part of the layer definition.

> I don't really care about how this is stored in the schema, but if the
> UI makes it more difficult for me to perform these tasks, it will
reduce
> my productivity and increase my frustration level... :)

So we agree? :). I believe that with the schema as is, the UI can
determine enough about the symbol to make things easy for the user (not
necessarily for the programmer).

Traian


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason
Birch
Sent: Thursday, February 15, 2007 1:18 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC
14(CartographicStylizationEngine)comments

My two most common uses are:

- It has to take up about X pixels on the screen, or
- It has to be exactly N units on the ground

I don't really care about how this is stored in the schema, but if the
UI makes it more difficult for me to perform these tasks, it will reduce
my productivity and increase my frustration level... :)

About being able to set size, etc, based on expressions...  These would
have to be defined at the layer level, wouldn't they?  I mean... if
you're creating a symbol that is only relevant to a fixed feature schema
that's a bit pointless / limiting...

Jason

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Thursday, February 15, 2007 10:07
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC
14(CartographicStylizationEngine)comments


Another thing that may make sense is to change the ScaleX and ScaleY
elements to be absolute sizes (SizeX and SizeY) instead. This would
remove the need to specify a scale (it would be implied), but it would
require one to know the exact bounds of the symbol in order to compute
said scale. This is not always possible since the size of the symbol may
change depending on expressions based on feature attributes. Hence
specifying a scale seems to be a better-defined approach than specifying
a size.

Traian
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals