Andrea Aime wrote:
> Again, I don't know how many people will be affected
> by changes in the changes of the metadata module, so I may be
> overestimating the issue.
>
People do use the metadata classes directly; and have to make use of
constructors to do it - so this change *will* break some u
Andrea Aime wrote:
> The first one is the size of the change. I would like to avoid seeing massive
> change of code in the
> gt2 codebase so close to GeoServer 1.7.x freeze. Can you svn diff you changes
> and post them somewhere?
> If they are really really big I'd prefer to have GeoTools 2.5.x c
Andrea Aime wrote:
> Two proposals:
> * move StyleAttributeExtractor to rendering, there is
>actually nothing in gt2 using it besides rendering
>
Agreed - move it.
> * subclass both of those classes in renderer to take
>care of the dynamic symbols proposal
>
Eventually I would like to
Sunburned Surveyor wrote:
> If GeoTools is an OSGeo project, might we consider using the OSGeo
> wiki? I realize the migration would be a lot of work, but we could at
> least start putting new content on an OSGeo GeoTools wiki page.
>
We can probably ask for a confluence license to run our wiki
I had some "outsider" comments on getting permission to write to the
GeoTools wiki page, which I did today, and I wanted to quickly share
them before I forgot.
I think that Step 4 and Step 5 under the "Getting Edit Permission"
section of the following page might be duplicated:
http://sites.google
GeoTools Programmers,
This is my formal request for permission to create an unsupported GPX2
module in GeoTools. GPX2 offers an alternative (not a replacement) of
the existing GPX code in GeoTools. The main difference is the purpose
of the library. The purpose of GPX2 is to provide "low-level" acc
Hi,
I'm looking into the issues brought up by Theuns about
rendering not working totally ok when attributes are
being used in mark/graphic. The issue is that
the renderer needs to know which attributes are being
used in styles for various optimizations, and it's
not being able to extract properly t
Hi,
here are a couple of bits about the upgrading styles proposal.
Generally speaking, the proposal sounds nice, and it's going
to introduce some very interesting new functionality, so
I'm favourable, but there are a couple of issues preventing
me from voting +1 on it.
The first one is the size of
Hi,
I've read the proposal, I have two concerns.
The first one has already been voiced by Jody, whenever the Metadata
classes are used, they should be used as interfaces and be created
with a factory, otherwise we'd tangle up GeoTools code and make it
difficult for future evolution. See what happen
Versioned edits may fail with invalid SeState handling
--
Key: GEOT-1863
URL: http://jira.codehaus.org/browse/GEOT-1863
Project: GeoTools
Issue Type: Bug
Components: data arcsde
10 matches
Mail list logo
