[JPP-Devel] JUMP as OSGEO project (some additional thoughts)
Hey folks, Thought I'd pop back in after my requested hiatus. I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? When we went thought the simmilar process in the GRASS community we relied mainly on the user community with representation from from the developers. If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This would be an opportunity for users to have a lasting impact on JP and leave a legacy. Remember that we are all about an open community (or at least that is what I understand Open Source to be), so why close out the users in this process? Second, I am sure you are aware of Degree entering OSGEO incubation... http://www.osgeo.org/node/723 Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP http://www.jump-project.org/project.php?PID=JUMPSID=CRED) My final thought is to address some of the concernes that joining OSGEO will change how you operate. If you are an open community with transparent processes then there should not be any negative changes. Some positive changes might come out that will strengthen the project though. On the other hand if JUMP calls itself an open source project but does not realy play the open source game, then the reservations might be well founded as OSGEO would only want to adopt transparent and open projects. We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. Again, OSGEO wants to avoid associating with such projects. Their processes are in place to ensure that contributors are protected and users can exercise their rights under the license. Some thoughts. Cheers - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] JUMP as OSGEO project (some additional thoughts)
I just had to respond to some comments in this e-mail. :] (I do appreciate you prodding us along on this issue David.) You wrote: I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? I think you are correct in this statement. You wrote: If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This is an excellent suggestion. I will post an inquiry on the JUMP users list. You wrote: Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I could ask the deegree folks about this. However, they are likely over committed as we are. You wrote: I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP) I don't know if you are talking about consolidating our web presence, or something else. I contacted Vivid Solutions as a first step. They are going to discuss it internally and respond to me in a few days. I don't think Refractions will be a problem, but I'll have to talk to Jody Garnett about it. I thought I would get a response from Vivid Solutions first. You wrote: If you are an open community with transparent processes then there should not be any negative changes. This is a good description of our community. You wrote: We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. This isn't OpenJUMP. In fact, it sounds like a good description of the original OpenJUMP. The reality is that we forked the code because Vivid Solutions maintained a choke hold, at least at the time, and JUMP has endured a slow death. The Sunburned Surveyor On Tue, Jun 17, 2008 at 5:39 AM, Sampson, David [EMAIL PROTECTED] wrote: Hey folks, Thought I'd pop back in after my requested hiatus. I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? When we went thought the simmilar process in the GRASS community we relied mainly on the user community with representation from from the developers. If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This would be an opportunity for users to have a lasting impact on JP and leave a legacy. Remember that we are all about an open community (or at least that is what I understand Open Source to be), so why close out the users in this process? Second, I am sure you are aware of Degree entering OSGEO incubation… http://www.osgeo.org/node/723 Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP http://www.jump-project.org/project.php?PID=JUMPSID=CRED) My final thought is to address some of the concernes that joining OSGEO will change how you operate. If you are an open community with transparent processes then there should not be any negative changes. Some positive changes might come out that will strengthen the project though. On the other hand if JUMP calls itself an open source project but does not realy play the open source game, then the reservations might be well founded as OSGEO would only want to adopt transparent and open projects. We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. Again, OSGEO wants to avoid associating with such projects. Their processes are in place to ensure that contributors are protected and users can exercise their rights under the license. Some thoughts. Cheers
Re: [JPP-Devel] JUMP as OSGEO project (some additional thoughts)
One quick comment - Refractions has essentially no code in the JUMP codebase. So you don't need to clear anything with them. Martin Sunburned Surveyor wrote: I just had to respond to some comments in this e-mail. :] (I do appreciate you prodding us along on this issue David.) You wrote: I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? I think you are correct in this statement. You wrote: If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This is an excellent suggestion. I will post an inquiry on the JUMP users list. You wrote: Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I could ask the deegree folks about this. However, they are likely over committed as we are. You wrote: I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP) I don't know if you are talking about consolidating our web presence, or something else. I contacted Vivid Solutions as a first step. They are going to discuss it internally and respond to me in a few days. I don't think Refractions will be a problem, but I'll have to talk to Jody Garnett about it. I thought I would get a response from Vivid Solutions first. You wrote: If you are an open community with transparent processes then there should not be any negative changes. This is a good description of our community. You wrote: We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. This isn't OpenJUMP. In fact, it sounds like a good description of the original OpenJUMP. The reality is that we forked the code because Vivid Solutions maintained a choke hold, at least at the time, and JUMP has endured a slow death. The Sunburned Surveyor On Tue, Jun 17, 2008 at 5:39 AM, Sampson, David [EMAIL PROTECTED] wrote: Hey folks, Thought I'd pop back in after my requested hiatus. I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? When we went thought the simmilar process in the GRASS community we relied mainly on the user community with representation from from the developers. If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This would be an opportunity for users to have a lasting impact on JP and leave a legacy. Remember that we are all about an open community (or at least that is what I understand Open Source to be), so why close out the users in this process? Second, I am sure you are aware of Degree entering OSGEO incubation… http://www.osgeo.org/node/723 Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP http://www.jump-project.org/project.php?PID=JUMPSID=CRED) My final thought is to address some of the concernes that joining OSGEO will change how you operate. If you are an open community with transparent processes then there should not be any negative changes. Some positive changes might come out that will strengthen the project though. On the other hand if JUMP calls itself an open source project but does not realy play the open source game, then the reservations might be well founded as OSGEO would only want to adopt transparent and open projects. We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. Again, OSGEO wants to avoid associating with such projects. Their
Re: [JPP-Devel] JUMP as OSGEO project (some additional thoughts)
I think your community is ready for the OSGEO challenge. Thanks for the responses... Sometimes my comments might be tounge-and cheeck. But the goal is to sift out the gems from the mud (smile). I think you guys have most of what you need right now. I will leave my mailbox open if you have any questions or find yourselves in a pickle a need some more proding. I think this will be a rewarding process. P.S At some point it might make sense to contact someone from OSGEO and ask for an unofficial assesment of where you are at in the process. They are the ones who make the final call after all. I personaly think that JUMP has a lot going for it as an OSGEO project. Cheers -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sunburned Surveyor Sent: Tuesday, June 17, 2008 12:00 To: OpenJump develop and use Subject: Re: [JPP-Devel] JUMP as OSGEO project (some additional thoughts) I just had to respond to some comments in this e-mail. :] (I do appreciate you prodding us along on this issue David.) You wrote: I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? I think you are correct in this statement. You wrote: If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This is an excellent suggestion. I will post an inquiry on the JUMP users list. You wrote: Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I could ask the deegree folks about this. However, they are likely over committed as we are. You wrote: I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP) I don't know if you are talking about consolidating our web presence, or something else. I contacted Vivid Solutions as a first step. They are going to discuss it internally and respond to me in a few days. I don't think Refractions will be a problem, but I'll have to talk to Jody Garnett about it. I thought I would get a response from Vivid Solutions first. You wrote: If you are an open community with transparent processes then there should not be any negative changes. This is a good description of our community. You wrote: We all know of Projects that call themselves open source but you could never contribute code or influence the direction of the project because the project is run as a closed source project that gives away its code but never allows contributions because it is held captive by a few key players. A closed club with free source code that dies when it forks. This isn't OpenJUMP. In fact, it sounds like a good description of the original OpenJUMP. The reality is that we forked the code because Vivid Solutions maintained a choke hold, at least at the time, and JUMP has endured a slow death. The Sunburned Surveyor On Tue, Jun 17, 2008 at 5:39 AM, Sampson, David [EMAIL PROTECTED] wrote: Hey folks, Thought I'd pop back in after my requested hiatus. I notice that your development community is very busy and perhaps over committed. May I suggest that approaching only the developer crowd may return positive support in general but a lack of ability to administer the proces? When we went thought the simmilar process in the GRASS community we relied mainly on the user community with representation from from the developers. If you think that that are more users than developers (hopefuly) then it it not make more sense that the user community can contributed to this process more than the developers can. Often users want to contribute to Open Source projects but are not commited to producing code or maintaining documentation. This would be an opportunity for users to have a lasting impact on JP and leave a legacy. Remember that we are all about an open community (or at least that is what I understand Open Source to be), so why close out the users in this process? Second, I am sure you are aware of Degree entering OSGEO incubation... http://www.osgeo.org/node/723 Since they have a version of jump, would it not make good sense to work with Degree to get the core of deeJump (mainly Jump Pilot) into OSGEO. I saw discussion of Vivid Solutions, but what about Degree and what about Refractions (as they also developed the initial JUMP http://www.jump-project.org/project.php?PID=JUMPSID=CRED) My final thought is to address some of the
Re: [JPP-Devel] Draft of OpenJUMP Plug-in Programmer's Guide
I forgot to attach the PDF. SS On Tue, Jun 17, 2008 at 1:35 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: I've decided to split my lunch breaks between my GeoTools GPX module and a new guide for OpenJUMP plug-in programmer's. This guide will build on some of the existing material in the old JUMP Developer Guide. However, it will not deal with programming OpenJUMP's core, but will deal only with what can be accomplished using methods of extension that do not require modifications to the core. The guide will be written with a very informal style, and will be geared to users of OpenJUMP that do not have an expert knowledge of Java programming. My goal with the guide is to allow more power users to make the jump to contributing programmers. I've attached the first few pages of the guide to this e-mail as a PDF. A preliminary table-of-contents is included. If you have suggestions on something that should be included please let me know. I welcome any contributions of additional material or translation efforts. :] The Sunburned Surveyor Plug-In_Programmers_Guide.pdf Description: Adobe PDF document - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Draft of OpenJUMP Plug-in Programmer's Guide
Great idea!! It looks a very good guide reading the index and initial pages! 2008/6/17 Sunburned Surveyor [EMAIL PROTECTED]: I forgot to attach the PDF. SS On Tue, Jun 17, 2008 at 1:35 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: I've decided to split my lunch breaks between my GeoTools GPX module and a new guide for OpenJUMP plug-in programmer's. This guide will build on some of the existing material in the old JUMP Developer Guide. However, it will not deal with programming OpenJUMP's core, but will deal only with what can be accomplished using methods of extension that do not require modifications to the core. The guide will be written with a very informal style, and will be geared to users of OpenJUMP that do not have an expert knowledge of Java programming. My goal with the guide is to allow more power users to make the jump to contributing programmers. I've attached the first few pages of the guide to this e-mail as a PDF. A preliminary table-of-contents is included. If you have suggestions on something that should be included please let me know. I welcome any contributions of additional material or translation efforts. :] The Sunburned Surveyor - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] OpenJUMP as an OSGEO project - Assessing the Requirements
hello, i am of the opinion -1. until such a time all outstanding issues are addressed and resolved, and all is consolidated and cleaned, and clear direction is sought out, reduced to mutual understanding(short-mid- long term) by those involved, in fully disclosed and understood pecking order, as well as worship order for those who drafted the plans, laid the foundation, and built the initial floors/walls. full understanding of it's history, and full understanding and disclosure of it's present, by and between the current power's-that-be, and those who laid the pioneered oj, but have since retired themselves and their interest from the project. understanding where it stands, and where it's participants would like to take it. how it compares to the other cross-platform gis java apps currently in development, and on and on. many questions need to be realized and asked and answered, and then a collective plan of action needs to be decided, and then a considerable amount of clean-up and filtration need to occur, and then issues like osgeo can be entered into unencumbered and without any perplexities and uncertainties. respectfully, eric On Jun 17, 2008, at 2:04 PM, Michael Michaud wrote: Hi Stefan, +0 I think joining OSGEO should be fine for OpenJUMP (more visibility, more developpers, more users...), but I'm not sure we have enough human resources to move on. As far as I'm concerned, I have'nt contributed for a while, but I'll keep helping when I can, whatever the decision is. Thank you so much for all the work you and Sunburned Surveyor do to keep the project in good health. Michaël Stefan Steiniger a écrit : Dear OJ user/developer. I send this email to the devel list, as here rather the core people are listening and this is also a discussion list for us. Now, I have read all the docs required for an OSGEO incubation. I will attach a rather lenghtly file where I added comments to the different questions/criteria. A couple of things will require some work and mentorship but I think it would be doable to join OSGEO, as the restrictions in terms of managements seem not to be so tight (i.e. we are require to document the managment processes, but it is actually not said what management rules we should implement) Here is a list of the major things that need to be done (see also the very end of the text file): Summary - Major Issues with respect to human resources required: . document (established) license policy . code contributors need to agree to project's license policy (written form?). . do a Code Provenance Review - check of licenses in the source code (Ohloh may help here) = problem: we probably can not GPL or LGPL (i.e. relicense) source code that has been inherited from other projects, without the author permission (such code needs to be externalized into a library). . found a Steering Comittee . establish documentation on project management procedures for PSC decisions, contributor guidelines, etc. (see Project Graduation Checklist point B3) . start documentation of project decisions . define release rules and process (not sure if that is a requirement) . provide marketing material (handout, feature-matrix) optional: . wiki + webpage transfer to OSGEO . introduce automated testing system (junit) . certification of standards? = The only thing I am personally struggling is the definition of release rules and a development plan if that is required (as this would play against our I contribute when I like idea) I am awaiting your coments and a OJ-Joins-OSEGEO decision (+1: yes, 0: don't know, -1 too much work) from the regular contributors, i.e. at least an oppinion from: Larry, Michael, Peppe, Andreas, Paul, Landon, Martin. I also welcome oppinions from Jukka, Jon, Paolo, Eric, Geoff, Sascha, Lat/Lon, Intevation, Erwan, Arnd, Edgar, Ugo + Steve (if listening ;),... and who ever wants to my personal vote: 0 (influenced by the work that needs to be done, listed above) cheers from sunny Calgary Stefan - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace.
Re: [JPP-Devel] Draft of OpenJUMP Plug-in Programmer's Guide
yep.. the content sounds good. I would additionally suggest the topics from wiki and the vividsolutions doc: a) the Hello World-PlugIn (should be probably the first thing to present.. directly after introducing the PlugIn/-Interface So you start with an example and then refer in the description to the parts that will be explained in detail in the next chapters/paragraphes. b) ways to programming and testing a plugin (I mean here that writing an Extension is the last step, and that one should plugins in a separate project... see the wiki) For the topic: Accessing OpenJUMP Internal’s From A Plug-In I would the bring in detail the frequently asked topics: . accessing features from a layer (requires Layer selection + some parameter) . modifying geometries (i.e. a buffer), set attributes . create a new layer . create a new feature collection (i.e. the use of FeatureSchema) + layer (see also the wiki example ;) The first thing to do before writing, may be to set up a style template (I guess Uwe used something alike for his tutorial). This is helpful if somebody else will particpate in writing (using unique naming for styles). Be here careful with the use of unusual fonds (i.e. check that they are build-in for the word-processor or choice on every OS. If doubts exists, then rather go with a serife-less common known fond such as Areal or Verdana). I know actually some Word-Templates from publishers that could be used after some changes. Are you using Word or OpenOffice or the doc-book stuff? Stefan PS: Maybe you should consider renaming yourself to the lunch-break-jumper ;) Sunburned Surveyor schrieb: Thank you for the comments Nacho. The Sunburned Surveyor On Tue, Jun 17, 2008 at 2:12 PM, Nacho Uve [EMAIL PROTECTED] wrote: Great idea!! It looks a very good guide reading the index and initial pages! 2008/6/17 Sunburned Surveyor [EMAIL PROTECTED]: I forgot to attach the PDF. SS On Tue, Jun 17, 2008 at 1:35 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: I've decided to split my lunch breaks between my GeoTools GPX module and a new guide for OpenJUMP plug-in programmer's. This guide will build on some of the existing material in the old JUMP Developer Guide. However, it will not deal with programming OpenJUMP's core, but will deal only with what can be accomplished using methods of extension that do not require modifications to the core. The guide will be written with a very informal style, and will be geared to users of OpenJUMP that do not have an expert knowledge of Java programming. My goal with the guide is to allow more power users to make the jump to contributing programmers. I've attached the first few pages of the guide to this e-mail as a PDF. A preliminary table-of-contents is included. If you have suggestions on something that should be included please let me know. I welcome any contributions of additional material or translation efforts. :] The Sunburned Surveyor - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Draft of OpenJUMP Plug-in Programmer's Guide
upps.. I haven't seen that there is also some text. I looked only on the outline ;) stefan Stefan Steiniger schrieb: yep.. the content sounds good. I would additionally suggest the topics from wiki and the vividsolutions doc: a) the Hello World-PlugIn (should be probably the first thing to present.. directly after introducing the PlugIn/-Interface So you start with an example and then refer in the description to the parts that will be explained in detail in the next chapters/paragraphes. b) ways to programming and testing a plugin (I mean here that writing an Extension is the last step, and that one should plugins in a separate project... see the wiki) For the topic: Accessing OpenJUMP Internal’s From A Plug-In I would the bring in detail the frequently asked topics: . accessing features from a layer (requires Layer selection + some parameter) . modifying geometries (i.e. a buffer), set attributes . create a new layer . create a new feature collection (i.e. the use of FeatureSchema) + layer (see also the wiki example ;) The first thing to do before writing, may be to set up a style template (I guess Uwe used something alike for his tutorial). This is helpful if somebody else will particpate in writing (using unique naming for styles). Be here careful with the use of unusual fonds (i.e. check that they are build-in for the word-processor or choice on every OS. If doubts exists, then rather go with a serife-less common known fond such as Areal or Verdana). I know actually some Word-Templates from publishers that could be used after some changes. Are you using Word or OpenOffice or the doc-book stuff? Stefan PS: Maybe you should consider renaming yourself to the lunch-break-jumper ;) Sunburned Surveyor schrieb: Thank you for the comments Nacho. The Sunburned Surveyor On Tue, Jun 17, 2008 at 2:12 PM, Nacho Uve [EMAIL PROTECTED] wrote: Great idea!! It looks a very good guide reading the index and initial pages! 2008/6/17 Sunburned Surveyor [EMAIL PROTECTED]: I forgot to attach the PDF. SS On Tue, Jun 17, 2008 at 1:35 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: I've decided to split my lunch breaks between my GeoTools GPX module and a new guide for OpenJUMP plug-in programmer's. This guide will build on some of the existing material in the old JUMP Developer Guide. However, it will not deal with programming OpenJUMP's core, but will deal only with what can be accomplished using methods of extension that do not require modifications to the core. The guide will be written with a very informal style, and will be geared to users of OpenJUMP that do not have an expert knowledge of Java programming. My goal with the guide is to allow more power users to make the jump to contributing programmers. I've attached the first few pages of the guide to this e-mail as a PDF. A preliminary table-of-contents is included. If you have suggestions on something that should be included please let me know. I welcome any contributions of additional material or translation efforts. :] The Sunburned Surveyor - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - Check out the new
