Initial UI options

What direction(s) does the community want me to go toward with regards to integrating the H2 database into OpenJUMP?

Here's some initial options I've come up with:

1. Project as a database - When creating or saving a new project, you could select to make it a database project. Then all layers that are created are automatically saved into the database and when external layers are opened, the option for copying them into the database or leaving them external is given. To open a database project, simply open the associated H2 database. With this option, all project data can be stored in one file that can easily be moved around.

1. Database as a file folder - This is in the ArcMap style where the open file menu and save layer menus treats the database as simply another folder that you can navigate into and select individual files.

1. Database as a Data Store Layer - Use that Open Data Store and Connection Manager dialogues to manage opening and saving of layers. This would probably be the simplest to code with the least amount of core modification (if any), but I'm not sure that it would be as intuitive and invisible as it could be.

Any comments or other suggestions?

--Christopher