Community
Participate
Working Groups
We've encountered a use case where a particular driver template doesn't require any jar files (i.e. a driver template with "empty jar list is OK" set to true). It would be nice to be able to hide the jar list section of the Edit Driver dialog if it isn't needed for a particular driver definition. We could also hide the Properties area if there are no editable properties for the driver definition. In some cases, this may end up with the jar list and properties sections hidden and the user just left with the ability to change the name of the driver. Should we add some additional functionality to the Driver framework, including: * Give driver developers the option of making their default driver instance read only * Add additional helper classes for editing of driver properties - such as a Boolean combo box or a String List combo box property descriptor
Brian, Is this required for 1.5. Rob
Not necessarily required. Just "nice to have". (In reply to comment #1) > Brian, > Is this required for 1.5. > Rob
Assigning to Brian, since he will drive the Connectivity usability effort in 1.6.
This has been delivered in the changes made for BZ 225651. Should appear in an upcoming build this week
Closing bugs
