Hei Paul, about the file loading: it is not clear to me why you think we need both (open file and add layer), but it is clear to me that we need both in the background. Anyway, as you implement the changes, it is your decission! I was only proposing something that i found of high "usuability". Something like this can still be an option for future releases or "OJ Starter Versions". I will welcome every decission you do :)
On the tabs.. I can't comment as I am not sure on what you really like to point on. What kind of lack, or even misdevlopment, do you identify? But introducing the tab-sytle is something what I currently consider a "user friendly" and "nice to have sometime" option. (you know.. ideas are many out there but time and man power to realize is limited ;) stefan Paul Austin schrieb: > Stefan, > > I can see the need for two approaches to adding layers, both of them > provide a simple approach to loading data > > 1. Open File.. > * This is what I'm currently working on > * Behaves like any Open File.. menu item/toolbar button in MS > Word and other apps > * Only works with file based data sets > * Lets the user select one or more files to add as layers and > to have a filter to only view files of certain types > * If a particular type of file has options or if there are a > couple of choices of loaders to display a second dialog will > be displayed to accept those options > * Will work for imagery, vector layers, compressed files > (containing 1 or more file) > 2. Add Layer... > 1. Wizard approach as shown in your screen shot, provides a > slick approach for novice and advanced users > 2. Works with any type of layer from files, databases to Web > Services > 3. I'll let someone else tackle this one > > > For the Open File.. plugin there will be an interface FileLoader that > each loader of files will implement, the interface will contain methods > to get the file extensions, description, open a file and get the > options. I have all this working except the options part. > > I have defined two implementations of FileLoader, one to work with > existing DataSource implementations (e.g. SHP, WKT, GML, JML, FME) and > another to work with ReferencedImageFactories (e.g. jpg, ecw, mrsid) so > there is minimal work to implement this new approach. > > I'm going to start setting up a daily build of my plugins so I can share > what I've done for review. > > I like the ideas of the tabs to display things other than layers, the > big one I think we need is the concept of a Project Catalogue that lists > the sources of data that are loaded as part of a project (e.g. shp > files, databases, wms servers etc). From this list a user would be able > to say navigate a postgres database select a table and say add this as a > layer to my current view. > > Paul > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > 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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel