Dear SS
If the survey is widely contributed to, then I would expect we would get
a good view of what plugins are being used and thus could easily form
the basis for a catalogue. I am quite happy to help with this.
Geoff
Sunburned Surveyor wrote:
> Guiseppe,
>
> I think that this would be tota
Paul,
I've got the book. I'm trying to avoid reading the whole sticking
thing to get this done. I think I can do it with your continued
assistance. :]
Stefan,
Thank you for the correction. I will set up the branch to be 1.2, when
and if I get that far. :]
SS
On 6/13/07, Paul Austin <[EMAIL PRO
Stefan,
Therefore the branch is 1.2 and you would have a tag/1.2b3 for example,
you put stuff under 1.2 that will go into a 1.2 release and then tag it
why you make a public release.
There is a good free online subversion book that covers these topics
http://svnbook.red-bean.com/nightly/en/svn.br
that is really great!!!
i have set a link on the jpp project news and the openjump wiki
tomorrow we should do an anouncement on the jump user list
thanx a lot
stefan
Geoffrey G Roy schrieb:
> To Developers
>
> It has occurred to me that some knowledge of the usage of various Jump
> plugins mi
mhm.. btw.
1.2 is not yet released we are still with 1.2 Beta
;o)
stefan
Sunburned Surveyor schrieb:
> Paul wrote: "In my code I maintain separate branches for each minor release
> (so branches/1.2) so that I can make patches to that code base, while
> also working on the next release 1.3..."
>
Paul wrote: "In my code I maintain separate branches for each minor release
(so branches/1.2) so that I can make patches to that code base, while
also working on the next release 1.3..."
So should I do something like "branches/stable/1.3"?
SS
On 6/13/07, Paul Austin <[EMAIL PROTECTED]> wrote:
>
SS,
We would just do a tag when we do a release.
With SVN there isn't really tags and branches per se it's just a
convention, what is actually happening behind the scenes is that you are
creating a "copy" of the sub directory under say branches/stable to
tags/2.2.0. When it copies all it does is
Hi Landon!
I had a closer look now at the SVN stuff you've set up.
Losing the CVS history is bad. You should really start over.
See it as a first learning attempt. :-)
- Sascha
Sunburned Surveyor schrieb:
> Stefan,
>
> Thanks for the links.
>
> You wrote: "but a side effect may be that the new
Something we may want to do at some point is to have separate modules
for each part of the code base; vivid, openjump, geotiff, geotools etc
to manage them and have a meta project that brings them all back
together. The nice thing with SVN is when we want to do that you can
create a link in your pr
Paul,
Do I need to create a tag when I make the stable branch? Or do we just
do this for a release?
SS
On 6/13/07, Paul Austin <[EMAIL PROTECTED]> wrote:
> SS,
>
> We should also create tags when we do a numbered version release so that
> we can recreate that release if required.
>
> Paul
>
> Su
Stefan,
Thanks for the links.
You wrote: "but a side effect may be that the new structure would be
the old one -
if we can't do changes after migration"
One nice thing about SVN is that it is much easier to make "structure"
changes. I will convert the existing CVS repository and then use the
"tr
Hmm. This is proving to be a real pain in the rear end.
Alright. I can start over and try and do the conversion, but it will
take me a few more days.
I think at some point we need to do a freeze on the commits to the CVS
so I am sure that everything is captured in the conversion process. We
d
Landon,
have you seen this:
https://sourceforge.net/project/admin/svn_migration.php?group_id=118054
and the link from that side to the doc:
https://sourceforge.net/docs/E09#import
but a side effect may be that the new structure would be the old one -
if we can't do changes after migration
s
SS,
We should also create tags when we do a numbered version release so that
we can recreate that release if required.
Paul
Sunburned Surveyor wrote:
> I'm afraid I was already well into the process of setting up the SVN
> when I read the helpful e-mails in this thread. :[
>
> I have made a stab
Hei all and Landon
i know I didn't do anything for the svn setup right now, so i am in a
weak position for advises. But may i suggest that we try a *new setup*
of the svn repository by using the Sourceforge tools and following their
guidelines (which i haven't read)?
Because it would be benefi
I probably missed them. I will add them.
SS
On 6/13/07, Sascha L. Teichmann <[EMAIL PROTECTED]> wrote:
> Hi!
>
> What about the ChangeLog, Changes.txt and TODO.txt?
> I cannot find them in the SVN trunk.
>
> Regards, Sascha
>
> Sunburned Surveyor schrieb:
> > I'm afraid I was already well into th
Hi!
What about the ChangeLog, Changes.txt and TODO.txt?
I cannot find them in the SVN trunk.
Regards, Sascha
Sunburned Surveyor schrieb:
> I'm afraid I was already well into the process of setting up the SVN
> when I read the helpful e-mails in this thread. :[
>
> I have made a stab at setting
I'm afraid I was already well into the process of setting up the SVN
when I read the helpful e-mails in this thread. :[
I have made a stab at setting up the SVN for OpenJUMP at the JPP, and
it *may* be ready for use.
I made a "trunk" and "branches" folders under the "openjump" folder. I
then crea
I understand much better now, thank you. The class names are a little
confusing. :]
I think this would be a great design and look forward to seeing your
UI in action. Let me know if you want a user to try this out. :]
SS
On 6/13/07, Paul Austin <[EMAIL PROTECTED]> wrote:
> SS,
>
> FilterStyle ex
I typed Guiseppe when I meant Geoff. (Both names start with "g".)
Sorry about that guys.
SS
On 6/13/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
> Guiseppe,
>
> I think that this would be totally awesome. If none of the other
> developers object, I say we go for it. (I don't know how they
Guiseppe,
I think that this would be totally awesome. If none of the other
developers object, I say we go for it. (I don't know how they would
respond.)
By the way Guiseppe, if you think you would be interested in some more
work with plug-ins I could use some help setting up a plug-in catalog.
Th
SS,
FilterStyle extends Style and all it does is loop through the list of
StyleFilters invoking the isMatched method on each one until one of
those is matched and uses the Style associated with that StyleFilter.
See coee at the end of the email. I need to come up with better names as
the current o
Roger that.
On 6/12/07, Giuseppe Aruta <[EMAIL PROTECTED]> wrote:
> Thanks SS,
> I think I wait for the template on Source forge.
> By
>
> Giuseppe
>
>
> ___
> L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
> http://it.docs.yahoo.com
Paul,
This sounds pretty slick. I just want to make sure that I understand
your design. A FilterStyle object would implement and/or extend the
current Style object. It would apply a Style filter object depending
on the attribute values of each Feature in a layer.
It sounds like a FilterStyle is s
Landon,
While your process should move the current copy of the source code ... I
do not believe it will include the history (a valuable component to a
stable project). There are some conversion utilities around for this,
but you may need to coordinate with the SF staff as I believe they are
intend
David,
There is a note on the FAQ about downloading a copy of the CVS
repository to your local machine so you can run cvs2svn against that.
Paul
P.S. Who is Landon?
David Zwiers wrote:
> Landon,
>
> While your process should move the current copy of the source code ... I
> do not believe it wil
You might want to try this tool http://cvs2svn.tigris.org/ with
sourceforge instructions at
http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#import
Paul
Sunburned Surveyor wrote:
> The migration to SVN from CVS wasn't as easy as I thought it was going
> to be. I didn't realiz
The migration to SVN from CVS wasn't as easy as I thought it was going
to be. I didn't realize that SourceForge had discontinued support for
the "one click" repository conversion.
I did get some of OpenJUMP's CVS into the JPP Subversion repository.
Let me explain my process so that if something is
Great idea Paul.
I've got something started on the JPP wiki. I have figured out how we
might incorporate definitions from other forks of JUMP, as Larry
suggested, but I'm completely agreeable to modifying the format of
these couple wiki pages.
Note that I tried to get us started with some discuss
As an example of what I was saying:
under WMSLayer
SIDLayer extends WMSLayer and provides access to local MRSID raster
files - implemented in SkyJUMP and OpenJUMP.
Larry
On 6/13/07, Larry Becker <[EMAIL PROTECTED]> wrote:
> Hi Paul,
>
> Great! I think this is a useful list. I would extend i
Hi Paul,
Great! I think this is a useful list. I would extend it to show
columns of JUMP forks (JUMP, OpenJump, SkyJUMP, Kosmo, Pirol Jump,
deeJUMP, SIGLE JUMP, etc.) with an "x" showing which forks have
implemented which model concepts. In this way, OpenJump development
can best benefit from
> Feature - An in memory representation of user's data, which can have
> geometry and attribution. Question: can we use the Feature concept for
> data without geometry or should Feature be a subtype of a DataObject
> interface that has the same interface but without the
> Geometry methods.
If I re
A comment that SS made regarding Layers vs. FeatureSchema objects made
me think that we probably need a Wiki page where we can define the
concepts and purpose of these concepts within OpenJUMP before we start
changing around anything to do with the feature model, schema etc. So
I've put together a
Good Idea Geoff,
I will send you some consideration about the plugins I
use
Giuseppe Aruta
___
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail:
http://it.docs.yahoo.com/nowyoucan.html
-
To Developers
It has occurred to me that some knowledge of the usage of various Jump
plugins might be of interest in identifying a need to improve existing
plugins, creating new plugins or simply knowing who is using what; and
perhaps what plugins might migrate into the core if they are widely
35 matches
Mail list logo
