BRIDGE currently uses a number of configuration files, loaded as resources from edu/vt/cs/collab/bridge/resources. These are:
- default-componentviews.properties
- Path is defined in constant
DefaultComponentViewSource.DEFAULT_MAP_PATH and loaded in DefaultComponentViewSource.loadDefaults()
- Loaded on BasicComponentContext construction in the client only
- Could use classname-based lookup as a fallback [Done]
- default-creatable-objects.properties
- Used client-side in
apps.web.WebSiteExplorer to populate the admin menu
- Used server-side in
apps.web.WebSiteWebView to look up names for directory listing
- Could have JOptionPane-based class name input [Done -- adds to tmp menu]
- default-icons.properties
- Used client-side in
DefaultComponentView to initialize IconManager
- Could default to generic icon [Done]
- default-webviews.properties
- Defined in
DefaultWebViewSource.DEFAULT_MAP_PATH and loaded in DefaultWebViewSource.loadDefaults()
- Used both client-side and server-side
- Could use classname-based lookup as a fallback [Done]
We need a longer-term solution to these configuration issues. The stop-gap measures (marked as [Done]) are sufficient to allow external CVs and WVs to be used, but in a hack-ish and inflexible way.
|