> New OJ does not open my old project files which I have created in 2009. It
> is not a problem because I have the corresponding OpenJUMP version in the
> same zip file. Big advantage from a small footprint. I still wonder what
> has changed and how the old project files could be edited to be usasable
> with a fresh OJ.
> Have you got error messages ? Is it just a matter of unrecognized paths or
> some incompatible change.
> Anyway, this would be interesting to gather old projects and to aks benjamin
> how he would include
> a unit test to keep sure new version don't break the compatibility :o) <
The test enviroment contains already a function to open files
(TestTools.openFile()). I would first look what exceptions will throw when
a project could not be loaded. We also could make some assertions on the
Task object. That would be the easy part.
If this would not fullfill sufficient needs we'll need to test some methods
directly.
2012/1/10 Larry Becker <becker.la...@gmail.com>
> I haven't posted for a while, but I'm still listening. Your post reminded
> me that OJ still doesn't have one of my favorite features in SkyJUMP: the
> layer file. These are basically project files per layer. They are created
> when you use the Archive Selected Datasets menu option. It creates a zip
> file containing all of the selected layers (using their current file
> format) along with a project file (with the jmp extension) that has the
> same filename as each archived layer . The zip file can then be used to
> deliver data along with associated style information to others without any
> file path problems. The recipient of the archive can choose to open it
> directly and work on it in-place (all changes will be written back into the
> zip file), or extract it and Merge the selected layer project files into
> their current project.
>
I also thought about the problems with absolute paths. Maybe we could add
both
a relative path and an absolute path to the project file. The file on the
relative path
would tried first and when not found the file on the absolute path would
tried to load.
This would also keep compatibility to older versions of OpenJUMP.
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
