jody>>Changing the xsd (that sounds standard 
)
It has to be changed:
1. add options for <TextSymbolizer> so you can control how labeling is
done
2. change <Geometry> to accept <Expr> instead of just <PropertyName>
The SLD 1.1 stuff will be slowly merging in.
Chris said:
I assume that it uses the SAX parser to parse <Filter>.
No, this is my other big problem with it. It uses a different
(crappier, less tested) filter parser, a DOM one. This has been a big
thorn in my side, as I constantly had to fix bugs with it. It probably
works decently now, but it's still quite lame that we use different
filter parsers. I suppose you could change it to use SAX, but it'd be
weird. You'd probably have to do it at a higher level, and parse
through the document twice, once with DOM and once with SAX...
oh, I thought it passed the Filter stuff off to the SAX filter parser.
Then, I'm more inclined to transition to XDO.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
dblasby@anonymised.com wrote:
jody>>Changing the xsd (that sounds standard 
)
It has to be changed:
1. add options for <TextSymbolizer> so you can control how labeling is
done
2. change <Geometry> to accept <Expr> instead of just <PropertyName>
The SLD 1.1 stuff will be slowly merging in.
Cool - will any of these functions be in SLD 1.1?
If you are coloring outside the SLD box (metaphorically) remember to take a bit of time and write up change request documents for the SLD RWG. They are working now, so this is an excellent time to turn your vision of reality into the standard. You control the horizontal and the vertical!
Paul
On 12-May-05, at 1:50 PM, dblasby@anonymised.com wrote:
jody>>Changing the xsd (that sounds standard )
It has to be changed:
1. add options for <TextSymbolizer> so you can control how labeling is
done
2. change <Geometry> to accept <Expr> instead of just <PropertyName>
The SLD 1.1 stuff will be slowly merging in.
Chris said:
I assume that it uses the SAX parser to parse <Filter>.
No, this is my other big problem with it. It uses a different
(crappier, less tested) filter parser, a DOM one. This has been a big
thorn in my side, as I constantly had to fix bugs with it. It probably
works decently now, but it's still quite lame that we use different
filter parsers. I suppose you could change it to use SAX, but it'd be
weird. You'd probably have to do it at a higher level, and parse
through the document twice, once with DOM and once with SAX...
oh, I thought it passed the Filter stuff off to the SAX filter parser.
Then, I'm more inclined to transition to XDO.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
As editor of the spec I asked Dave to try the changes out to see if
they are practical and exactly what the concequences would be. I'm
working on a formal change proposal right now to cover the geometry as
expression case.. The css param stuff I feel needs more thought.
James
On 5/12/05, Paul Ramsey <pramsey@anonymised.com> wrote:
If you are coloring outside the SLD box (metaphorically) remember to
take a bit of time and write up change request documents for the SLD
RWG. They are working now, so this is an excellent time to turn your
vision of reality into the standard. You control the horizontal and the
vertical!
Paul
On 12-May-05, at 1:50 PM, dblasby@anonymised.com wrote:
> jody>>Changing the xsd (that sounds standard )
>
> It has to be changed:
>
> 1. add options for <TextSymbolizer> so you can control how labeling is
> done
> 2. change <Geometry> to accept <Expr> instead of just <PropertyName>
>
> The SLD 1.1 stuff will be slowly merging in.
>
> Chris said:
>
>>> I assume that it uses the SAX parser to parse <Filter>.
>> No, this is my other big problem with it. It uses a different
>> (crappier, less tested) filter parser, a DOM one. This has been a big
>> thorn in my side, as I constantly had to fix bugs with it. It
>> probably
>> works decently now, but it's still quite lame that we use different
>> filter parsers. I suppose you could change it to use SAX, but it'd be
>> weird. You'd probably have to do it at a higher level, and parse
>> through the document twice, once with DOM and once with SAX...
>
> oh, I thought it passed the Filter stuff off to the SAX filter parser.
> Then, I'm more inclined to transition to XDO.
>
> dave
>
>
>
>
>
> ----------------------------------------------------------
> This mail sent through IMP: https://webmail.limegroup.com/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel