[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.1.x was always a fork? Stable branches by their nature are always
forks - I do expect 2.1.1 to
be released at some point.
2. Actually try to announce, vote, and transition API changes.
I asked back in september if I could add events in, I have not harmed
the interfaces on route. Justin putting
defaults into the interfaces have also not changed things with respect
to StyleFactory use. Many of the incompatiable
changes are due to mistakes, not having a StyleFactoryFinder, not
breaking things out into interfaces, not
matching SLD 1.0 ... I asked long and hard for a couple weeks how people
wanted me to proceed and
have done a good job sticking with that.
3. <insert your 3rd option>
dave
PS. And *please* don't auto-format code anymore!
I have been good :-( Although I think the answer is to auto format all
the time... as it was when I joined the project.
Maybe I should phrase this question another way, can we arrange the IRC
meeting at a better time to increase attendance, or
set up a breakout IRC meeting on these things. I found that IRC was in
almost constant use last week as problem after problem
was found in the Style classes. We also wrote up a web page describing
what had been done...
Jody
-------------------------------------------------------
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
