Hei Harvey,
as you are interested in modeling demographic trends.. it seems to me
quite related to raster modeling. So if you aim to work with raster
tools: we don't have map algebra at all for now. Thus, if you got your
first experiences in OJ and want to extend the core for raster "tools"..
I look forward to working with you Harvey. Please let us know what
questions you have, and definitely post any patches. After you've
submitted a couple of patches we can get you SVN access if you would
like it.
The Sunburned Surveyor
On 7/23/07, Harvey Harrison <[EMAIL PROTECTED]> wrote:
> On 7/2
On 7/23/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
> Harvey,
>
> I see you have already received a welcome from some of our active
> developers. I believe that they have done a good job answering your
> questions. I also want to welcome you to our mailing list. I'd love to
> know what contex
Harvey,
I see you have already received a welcome from some of our active
developers. I believe that they have done a good job answering your
questions. I also want to welcome you to our mailing list. I'd love to
know what context you are using OpenJUMP in, if you are willing to
share that. Also,
ups.. i did not thought about the plugins.
they would be really a major issue, as there should be a lot of plugins
outhere (actually i estimate that our university research group only has
developed 50 plugins which would be hard to change). but this holds
probably only for the com.vividsolutions
On 7/19/07, Larry Becker <[EMAIL PROTECTED]> wrote:
> Hi Harvey,
>
>Welcome to the list! We can always use more developers. :-)
>
>I'm not sure package name changes would be helpful due to the
> number of dependent and related projects. Many plugins depend on the
> vividsolutions namespa
Hei Harvey,
we welcome you (and others) on the list
Harvey Harrison schrieb:
> I'm new to the list and was wondering how welcome patches would be to
> do some codingstyle / pachage name cleanup?
>
> Is there a standard codingstyle accepted for the project?
>
> Is there any move afoot to unify u
Hi Harvey,
Welcome to the list! We can always use more developers. :-)
I'm not sure package name changes would be helpful due to the
number of dependent and related projects. Many plugins depend on the
vividsolutions namespace.
I think we have a standard Eclipse code style around some
Harvey,
There is no point doing coding style cleanups as these can be done
automatically by tools. We decided a little while ago to adopt the sun
coding conventions, but most of the code doesn't follow these yet.
In terms of the namespaces, the reason for keeping the
com.vividsolutions namespace
I'm new to the list and was wondering how welcome patches would be to
do some codingstyle / pachage name cleanup?
Is there a standard codingstyle accepted for the project?
Is there any move afoot to unify under the org.openjump.* namespace
and remove the com.vividsolutions, etc namespaces to make
10 matches
Mail list logo
