Thanks for bringing up this issue Dave. This is why I have all but stopped GT development. It's really frustrating seeing you evening disappear because some unnamed party has gone and refactored working code for the n'th time simply for the sake of it.
There is a point in time when the API may not be the best, but it is optimal simply because it is tested, and well understood (or atleast there are javadocs + tutorials). Since I joined, I have seen an exponential growth in wasted (in my opinion) resources.
I would really like to see a stable API, with a simple branch. I know there will be additional fonctionality in GT, but could we think about the costs for everyone else before making even the simplest api change?
I do like option 2 ... but and I think the individual(s) who wish to cause everyone else in the comunity the 'pain' (ok, effort) should suffer (spend effort) first prior to asking anyone else to (prove you actually think this is the correct solution). Can we adopt this as a policy? and can we make this at the public method level?
David
PS. Sorry about the circular email ... it's just been really frustrating here, hence (mainly) why there are so many open WFS bugs.
On 12/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I'm still trying to improve the rendering & style stuff, but I'm finding
that there are so many API differences (and people running automatic
code style programs) between 2.1.x and trunk that I'm spending almost
all my time moving changes over. I mean, it takes significantly longer
to move the changes over than it takes to actually do the changes in
the first place.
The truth of the matter is that I really dont want to make any
improvements anymore because its just too painful. I thought the
entire idea behind the streaming rendering was that we would keep 2.1.x
aligned with trunk.
REMEMBER - EVERY API CHANGE YOU MAKE MEANS I HAVE TO SPEND SEVERAL HOURS
OF WORK ALIGNING THINGS. Plus more hours keeping changes aligning for
every future change too.
Should we:
1. just say "ha ha - fooled you" for the people doing rendering (and
other modules) on 2.1.x. This pretty much means we're calling 2.1.x a
fork.
2. Actually try to announce, vote, and transition API changes.
3. <insert your 3rd option>
dave
PS. And *please* don't auto-format code anymore!
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
