Re: [JPP-Devel] Google Summer of Code 2009
of course I am interested to supervise a person. About students.. not sure how/where to do a call - on the other hand I could put something on the blackboard? I also need to think about some topics - but we still have a long list of here: well... the wiki doesn't work? .. so somewhere on the wiki stefan Sunburned Surveyor wrote: It doesn't sound like Google will be sponsoring as many students for this year's summer of code, and we aren't sure if the OSGeo will even get a spot. The OSGeo would like us to start early on looking for students and project ideas so we can get things vetted and present some good projects to Google. Do we have any students that are interested in participating in the Google Summer-of-Code for OpenJUMP/JTS this year? I'd be comfortable mentoring again, but I think I will only commit to one student this time. I'd prefer if the student spoke proficient English, only because my ability to speak other languages stinks! Please let me know if you are interested. I'll present any idea for a OpenJUMP SoC project to the mailing list for discussion. The Sunburned Surveyor -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ 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: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Google Summer of Code 2009
Sunburned Surveyor wrote: Stefan, Thanks for your offer to mentor. What languages would you be able to mentor a student in? German and English my French is way to bad. stefan -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Greetings from Santiago! Informations about OJ manual
One comment - it should be Table of Contents 8^) Looks like a very worthwhile product... Martin Giuseppe Aruta wrote: Greetings from Santiago (Chile), I am here to visit my in-laws and for job. Meanwhile I carried some OJ job with my laptop. I attached two files to this mail: the Table of Context and the Index of the manual I am working around: Table of Context.pdf: * Blue chapters are already written. Basically is an extended version of the wiki pages, with more figures and more explanations. As you can see Part 3 is basically an extended version of all the list of functions pages (here List of Tools). I image this as the core of the manual. * Green chapters are on wiki pages and partially on the manual. I have to add more infos and figs, * Red chapters are to be written right now. As you can see (if you have time to give a look at the Table of Context.PDF, the manual is devided in 3 parts: 1) A small tutorial (OpenJUMP User Guide) which has to be as simple as possible - for uses who want to use OJ quickly 2) The OpenJUMP List of Tools, which will be the core of the manua 3) OpenJUMP Developer Guide. I followed as sample the good Kosmo Developer Guide (Kosmo Guia de Desarollo) of ourn SAIG companeros. Includin the usage of Eclipse ans Subeclipse. Other chapters (already writte) are connected to pratical usages (How to write translate OJ into another language using babelfish, Portable OpenJUMP in windows and Linux, etc) ... not really Java developing but somehow pratical. Index.pdf this is a partial index of the documentation (only about the List of the functions/tools). I think this is worthfull to understand and to search information about OJ. Some other infos: the maual is written in Openoffice. Actually it has 1.2 Mb for 87 pages (included indeces). I hope to finish the first alpha version of the manual for the next 2 months (depending to my time in Chile - 35 to 37 Celsius degrees yesterday!). Any comment will be really appreciate. @SS thanks for your availability to correct the text. I will send as soon as possible the parts of the manual I wrote. @ Stefan some weeks ago you wrote that the developer wiki section of OJ is probabily already useful. I partially agree with your idea. My project is to resume the most inmportant informations, from the point of view of a non-developer - to make the info easy. In any case, when I finish to write all, the developer section of my manual can easly go to the wiki pages instead as a separate PDF Hasta luego Peppe -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
[JPP-Devel] Adding an attribute to all Feature objects in a FeatureCollection.
I'm in the midst of writing the unit tests for my plugin that adds attributes to all the Feature objects in a layer using information stored in a CSV file. I'm having some trouble adding an attribute to all of the Feature objects in a Feature Collection. I can sucessfully modify the FeatureSchema for the FeatureCollection and all of the Feature objects it contains, but this isn't modifying the internal array used to store the feature attribute values in each Feature object. I checked the Feature interface, and it doesn't have an addAttribute method. This means my modifications of the FeatureSchema for the Feature aren't modifying the underlying number of attributes in the Feature implementation. So even though the FeatureSchema object I get from the Feature object reflects my addition, the actual Feature object itself does not. This seems like odd behavior and I'm surprised I haven't noticed it before. So do I have to create a copy of each Feature object in the FeatureCollection using the new schema and over write the existing Feature objects to implement my change, or is there an easier way? On a related note, would it be handy to have a Feature implementation that changed its internal state when its FeatureSchema reference was changed? Maybe I am missing something obvious. Thanks for any suggestions. The Sunburned Surveyor -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Adding an attribute to all Feature objects in a FeatureCollection.
Sounds like normal behavior to me. Larry On Mon, Jan 12, 2009 at 3:13 PM, Sunburned Surveyor sunburned.surve...@gmail.com wrote: I'm in the midst of writing the unit tests for my plugin that adds attributes to all the Feature objects in a layer using information stored in a CSV file. I'm having some trouble adding an attribute to all of the Feature objects in a Feature Collection. I can sucessfully modify the FeatureSchema for the FeatureCollection and all of the Feature objects it contains, but this isn't modifying the internal array used to store the feature attribute values in each Feature object. I checked the Feature interface, and it doesn't have an addAttribute method. This means my modifications of the FeatureSchema for the Feature aren't modifying the underlying number of attributes in the Feature implementation. So even though the FeatureSchema object I get from the Feature object reflects my addition, the actual Feature object itself does not. This seems like odd behavior and I'm surprised I haven't noticed it before. So do I have to create a copy of each Feature object in the FeatureCollection using the new schema and over write the existing Feature objects to implement my change, or is there an easier way? On a related note, would it be handy to have a Feature implementation that changed its internal state when its FeatureSchema reference was changed? Maybe I am missing something obvious. Thanks for any suggestions. The Sunburned Surveyor -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- http://amusingprogrammer.blogspot.com/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Adding an attribute to all Feature objects in a FeatureCollection.
yes... you have to copy every feature to the new schema. There is an class and method in the api package (taken from pirol) that does copy from an old to a new schema. (It could be that the examples on the wiki provide code for that too. But I think I also answered an email on that issues just a while ago on one of the lists) I think this was designed that way for some safety reasons. stefan Larry Becker wrote: Sounds like normal behavior to me. Larry On Mon, Jan 12, 2009 at 3:13 PM, Sunburned Surveyor sunburned.surve...@gmail.com mailto:sunburned.surve...@gmail.com wrote: I'm in the midst of writing the unit tests for my plugin that adds attributes to all the Feature objects in a layer using information stored in a CSV file. I'm having some trouble adding an attribute to all of the Feature objects in a Feature Collection. I can sucessfully modify the FeatureSchema for the FeatureCollection and all of the Feature objects it contains, but this isn't modifying the internal array used to store the feature attribute values in each Feature object. I checked the Feature interface, and it doesn't have an addAttribute method. This means my modifications of the FeatureSchema for the Feature aren't modifying the underlying number of attributes in the Feature implementation. So even though the FeatureSchema object I get from the Feature object reflects my addition, the actual Feature object itself does not. This seems like odd behavior and I'm surprised I haven't noticed it before. So do I have to create a copy of each Feature object in the FeatureCollection using the new schema and over write the existing Feature objects to implement my change, or is there an easier way? On a related note, would it be handy to have a Feature implementation that changed its internal state when its FeatureSchema reference was changed? Maybe I am missing something obvious. Thanks for any suggestions. The Sunburned Surveyor -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net mailto:Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- http://amusingprogrammer.blogspot.com/ -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ 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: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Adding an attribute to all Feature objects in a FeatureCollection.
Sunburned Surveyor wrote: So do I have to create a copy of each Feature object in the FeatureCollection using the new schema and over write the existing Yup On a related note, would it be handy to have a Feature implementation that changed its internal state when its FeatureSchema reference was changed? Or just make a helper class to perform all the changes for you. JUMP tried to make Feature objects immutable, since we thought it was more useful to all them to be shared safely than to allow them to be mutated. I would strongly recommend continuing with this philosophy. Mutating features introduces potential for all sorts of nasty aliasing bugs. In general I think mutating objects made more sense when memory was scarce and memory allocation was expensive. Neither is true in modern machines and modern Java. My 2c M Maybe I am missing something obvious. Thanks for any suggestions. The Sunburned Surveyor -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Adding an attribute to all Feature objects in a FeatureCollection.
Maybe a better solution would be to create a new layer with that contains clones of the Feature objects with the modifications. That seems like the best way to go... Yup, I think that's the best pattern to use. -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
