Jump to: navigation, search

Difference between revisions of "Connectivity:Usability"

(Driver Definitions)
(Too Many Drivers)
Line 33: Line 33:
==Driver Definitions==
==Driver Definitions==
===Too Many Drivers===
===Too Many Drivers===
This list of available drivers can be a bit long and hard to navigate.
This list of available drivers can be a bit long and hard to navigate. [[Image:Driver_definition_preference_page.jpg|Screenshot]].

Revision as of 21:40, 6 November 2006

Back to Connectivity Page

Connectivity Usability Page

It has been voiced that the connectivity framework is a bit awkward to use and that it could be simpler. These are rather vague comments which don't provide much insight into what is wrong with the framework or how it could/should be corrected. This page has been created to try to understand the awkwardness and complexity of the framework.

Areas of focus are:

Please be as honest as possible, and brutal as necessary (we've got thick skin). Also, keep in mind that providing specific examples will help us better understand your comments and suggestions.

Our goal is to use this page to improve the usability and user experience of the connectivity related features within DTP.

General Issues


There are too many steps required to create a connection:

  1. Create a driver instance
    Available through a preference page or a shortcut from most connection profile new wizards.
    1. Specify a driver type
    2. Specify driver jars
    3. Specify driver class
    4. Specify default connection URL
    5. etc.
  2. Create a connection profile
    1. Specify a driver instance
    2. Specify connection specific properties
  3. Connect to the server
    1. Locate newly created connection profile in DSE
    2. Right-click-->Connect...


  • Create default driver instances. These would be available at startup, but the user might have to fix the paths to the JAR files.
  • Create custom connection profile wizard/property pages for each vendor DB. This would greatly reduce the number of drivers displayed when browsing for a driver. It also allows connection information to be specified in a vendor specific format. (We'll be updating the Derby connection profile wizard to do this, 163614.)

Driver Definitions

Too Many Drivers

This list of available drivers can be a bit long and hard to navigate. Screenshot.


  • Add filtering to the list.
  • Flatten the list (so it's displayed as a list instead of a tree).

Version Groups

The list of drivers contains many templates with the same name, but are contained within a version numbered category. This extra layer of navigation makes it difficult to find driver templates.


  • Remove version categories and add version number to driver template name (e.g from "10.0/Informix JDBC Driver" and "9.2/Informix JDBC Driver" to "Informix 10.0 JDBC Driver" and "Informix 9.2 JDBC Driver").
  • Find a better way to specify dbdefinition version information. The current problem is caused by the way dbdefinition's are resolved. If a mechanism were in place to discover which dbdefinition to use simply by the type of connection created or the server version, as retrieved by the DB metadata, that could help significantly. I don't know the feasibility of this and it may require changes to both the connection factories and the dbdefinition extension points.

Connection Profiles

Data Source Explorer (DSE)