· File/Save using the nwb persister isn't actually saving where i tell it to. I loaded w/ the file/load then after that went file/save, chose where to save it, and it wasn't saved there.
FileàSave… works in windows. But there’s a bug. The new saved file can’t be accessed before closing the cishell application. The error message is file “is in use by another application and cannot be accessed.” Please fix it.
[mailto:email@example.com] On Behalf Of Bruce
Sent: Thursday, September 28, 2006 6:51 PM
To: Weixia(Bonnie) Huang;
Subject: persistence plugin changes to make
Ben and Bonnie,
I looked over the persistence plugin. I made a couple fixes on some minor things (moved load and save to the start group of the File menu, added OSGI-INF to build.properties...).
Here are some minor things i'd like you to do:
* I have committed the new gui builder (and updated plugins to use it). Please update the load and save plugins so that errors are popped up to the user rather than on the console log when loading/saving.
* Get rid of some debugging messages that are printed to system.out
* nwb persisters should use file-ext:nwb NOT file-ext:.(dot)nwb
* File/Save should also extend DataValidator and make itself clickable only when the selected datamodel(s) can possibly be saved (must have at least one converter)
* File/Save should start off with a suggested name like: data.$EXTENSION_USED or $THE_LABEL_OF_THE_DATA.$EXTENSION_USED
* File/Save using the nwb persister isn't actually saving where i tell it to. I loaded w/ the file/load then after that went file/save, chose where to save it, and it wasn't saved there.
Other related things:
* We will need to make converters that will hook in file:text/nwb data too (what santo outputs). This may mean we need 4 converters (file:text/nwb->file-ext:nwb, file-ext:nwb->file:text/nwb, file:text/nwb-> java.blah.NWBModel, java.blah.NWBModel->file:text/nwb). We will need less once we get multi-step conversions going.
* edu.iu.nwb.converters isn't compiling...
* Please email the developer list with any other bugs/things we need to fix so that we can get them done.
One final thing,
>From here on out, ALL developer talk should be done through firstname.lastname@example.org so that outsiders can see what we are up to and possibly join in discussions as well.