RE: [dtp-pmc] Requesting permission to make change for BZ 140493

["Linda Chan" <LChan@xxxxxxxxxxx>]

+1.

 

Linda

---

From: dtp-pmc-bounces@xxxxxxxxxxx [mailto:dtp-pmc-bounces@xxxxxxxxxxx] On Behalf Of brian.fitzpatrick@xxxxxxxxxx
Sent: Monday, April 30, 2007 12:08 PM
To: DTP PMC mailing list
Subject: Re: [dtp-pmc] Requesting permission to make change for BZ 140493

Also note that this is additive and 
will not affect existing adopters. Forgot to mention that. 

Thanks. 
--Fitz 

Brian 
Fitzpatrick
Senior Software Engineer/DTP Committer
Sybase, Inc.

brian.fitzpatrick@xxxxxxxxxx
Sent by: dtp-pmc-bounces@xxxxxxxxxxx

04/30/2007 12:57 PM

Please respond to
DTP PMC mailing list <dtp-pmc@xxxxxxxxxxx>

To	dtp-pmc@xxxxxxxxxxx
cc
Subject	[dtp-pmc] Requesting permission to make change for BZ 140493

Hi all... 

There has been a request (BZ 140493) out from the DTP 
community for a while to allow adopters to override the static text associated 
with a driver template. The individuals who made the request recently attached a 
patch to their request, which made us look a little closer at the issue. Though 
their patch did solve their problem, it was a little limited in scope and we 
reworked it to allow more flexibility. They have taken a look at our revamped 
solution and it will work for them. 

The revamped solution allows adopters to do the 
following: 

       * override any of the values for a driver 
template, including: 
              
 name 
  
             description 
          
     parentCategory 
              
 jarList 
  
             createDefault 
        
       emptyJarListIsOK 
       * override any of the 
values for a property in a driver template, including: 
          
     name 
              
 description 
              
 value 
  
             visible 
          
     example 
              
 required 
              
 customPropertyDescriptor 
              
 category 
       * remove a property from a driver 
template 

The 
reasons this change is compelling is that an adopter (say Sybase for example) 
could override the template for the Sybase ASA enablement contribution to 
include a plug-in wrapped path to a particular jar file and indicate that the 
template should have a default driver definition created at startup if it 
doesn't already exist. This would ensure that a driver was ready to go for the 
Sybase ASA product right out of the box and the user wouldn't have to do any 
further configuration of the driver, simply create a new Sybase ASA profile and 
they're off to the races. 

We would like to deliver this for DTP 1.5 unless there are any 
objections. 

Thanks for your time. 

--Fitz 

Brian Fitzpatrick
Senior Software Engineer/DTP 
Committer
Sybase, Inc._______________________________________________
dtp-pmc mailing 
list
dtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dtp-pmc