Community
Participate
Working Groups
Created attachment 81700 [details] the exported plugins Attached 2 plugins with some enhancements to make the creation of a new jdbc connection much easier and intuitive to the user. In order see the code working you just need to add the jdbc drivers in the relevant folders. In addition, the code provides a double click action on tables in order to edit them (acts like the right click->edit action)
My team would be willing to continue working on this code with DTP
Created attachment 81701 [details] RSD for the added features The requirements and specification document includes the list of chnages/enhacements included in the attached plugins
Hi there... Where would I find the com.zend.license & com.zend.license.ui plug-ins so I can take a look at this? Thanks. --Fitz
Created attachment 82616 [details] The plugins without the license requirements In the attachment you can file the plugins modified so that they don't require a license
you can get the org.eclipse.php.ui plugin (which is a dependency of com.zend.php.datatools.ui) from http://download.eclipse.org/tools/pdt/downloads/
Hi there... I've had some time to take a look at your proposed contributions and have a few concerns and comments... I think the way you streamlined the process in the wizard and property pages is fine. My concern here is that if there are custom pages available for a particular driver/DBMS/profile, you're not allowing the user access to that updated functionality by boiling the interface down to URL, user name, and password. If extenders provide their own profile wizards or categories, they're going to want access to them in the DSE. My biggest concern with this approach is that it's not additive, it changes the look and feel of the DSE by removing/changing categories and then overrides the base JDBC profile wizard. Since the DSE is used in a variety of contexts, this may not be the best approach. We are working on adding some functionality for filters that would allow extenders and users to add their own filters to customize the view. For example, if you wanted to hide the ODA categories, you could add a filter to the DSE that would do that. Or if you wanted to only see tables and stored procedures, you could filter out all the other assorted object types in the SQL model to minimize the clutter in the view. Another possibility is having a custom Common Navigator that brings in the DSE content and actions and providing the ability for you to override the look and feel in your own viewer at that point. We have done some refactoring for 1.6 to move the DSE content and action providers as much as possible into connectivity.ui to allow other viewers to pull in that functionality without having to bring in the entire DSE. So though I think you have some great ideas, I think we need to look at how they can get integrated in an additive fashion. If this functionality is being used extensively in the PHP, maybe a customized DSE view would make more sense. But I think that some of the changes you're suggesting could definitely be worked in as alternatives for adopters/extenders to use if they see the benefits. --Fitz
One of my big concerns is that the wizard appears to bypass the connection profile type selection wizard page. This means that adopters cannot contribute new connection profile wizards to create SQL connections. However, there are several features of the wizard that would be very useful for DTP including but no limited to: 1) Providing a default connection profile name. 2) Providing a mechanism for populating the jar list at runtime. 3) Pre-populating driver instances in the wizard. I'm not sure if it is appropriate to populate them in DTP or just provide a mechanism for adopters to do this. See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=202641
we opened 2 separate bugs for the features that are not connected to the "quick connection" feature. (see "depends on" bugs)
Assigning to Brian, since he will drive the Connectivity usability effort in 1.6.
Have addressed what we can for Ganymede
