I agree with the above comments. We should keep new classes or major
overhauls of an existing class out of the com.vividsolutions package
hierarchy.

I'm curious if David or Ed could offer thoughts on Vivid Solutions
eventually merging OpenJUMP and JUMP. I know there would be some code
quality concerns, but it seems like Vivid Solutions would have a lot
of work to do to keep up with the improvements being made to OpenJUMP.
I think that would require a pretty serious financial sponsor.

Think about the work required just to incorporate internationalization
into JUMP, which our developers work hard to support in OpenJUMP.

The Sunburned Surveyor

On 8/28/07, Michaël Michaud <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Fixed
> Sorry for the disturbance and thanks to Paul for having noticed the
> missing files.
>
> Michael
>
> Paul Austin a écrit :
>
> >Michael,
> >
> >can you checkin  org.openjump.core.ui.images.IconLoader as your new
> >VertexZValueStyle needs it.
> >
> >Paul
> >
> >Michaël Michaud wrote:
> >
> >
> >>Hi,
> >>
> >>If everyone is ok, I'll commit a Z value decorator (looking like the
> >>index decorator or the xy one),
> >>
> >>@developpers
> >>- I added the style in the org package, as O. Bedel and P. Austin
> >>before, then I had to add also a new image directory in the org package
> >>as well as a new IconLoader : wonder if it is a good thing to duplicate
> >>so many file structures between com and org packages (or maybe org
> >>package must be considered as a big extension, or as a developement
> >>package for plugins waiting for approval to be included into the core...
> >>just a thought, nothing urgent
> >>
> >>Michaël
> >>
> >>-------------------------------------------------------------------------
> >>This SF.net email is sponsored by: Splunk Inc.
> >>Still grepping through log files to find problems?  Stop.
> >>Now Search log events and configuration files using AJAX and a browser.
> >>Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >>_______________________________________________
> >>Jump-pilot-devel mailing list
> >>Jump-pilot-devel@lists.sourceforge.net
> >>https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>
> >>
> >>
> >
> >
> >
> >-------------------------------------------------------------------------
> >This SF.net email is sponsored by: Splunk Inc.
> >Still grepping through log files to find problems?  Stop.
> >Now Search log events and configuration files using AJAX and a browser.
> >Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >_______________________________________________
> >Jump-pilot-devel mailing list
> >Jump-pilot-devel@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >
> >
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to