Bug 433676 - PDT Extension Discovery wizard
Summary: PDT Extension Discovery wizard
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: PDT (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PHP UI CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-28 11:58 EDT by Kaloyan Raev CLA
Modified: 2020-05-14 10:16 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kaloyan Raev CLA 2014-04-28 11:58:33 EDT
I am opening this bug following the discussion [1] in the pdt-dev mailing list.

As we have recently resurrected the Eclipse PHP EPP package we should provide a way to promote existing PDT extensions plugins developed outside of the Eclipse Foundation. 

Ideally, there should be a wizard that presents a categorized list of available extensions that can be installed via a button click on the current IDE. We started collecting the existing PDT extensions on a wiki page. [2]

The discovery wizard may use the MPC API and may be similar to other similar wizards like the Mylyn Connector Discovery wizard [3]. A recent improvement in MPC is that the API is declared as public. [4]

[1] https://dev.eclipse.org/mhonarc/lists/pdt-dev/msg02554.html
[2] https://wiki.eclipse.org/PDT/Extensions
[3] https://wiki.eclipse.org/Mylyn/Discovery
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=432803
Comment 1 Dawid Pakula CLA 2014-09-28 16:19:26 EDT
We should decide what is better:
 a) Collect only MarketPlace urls/ids and read all required informations from MPC API
 b) Prepare discovery wizard similar to Mylyn. This will allow to register extension without Marketplace record.

Should we move this function to separate plugin/feature?
Comment 2 Kaloyan Raev CLA 2014-09-29 02:42:51 EDT
IMHO, the wizard should have the following capabilities:
1. Display title, description and icon for each extension
2. Show only extensions that are compatible with the current Eclipse version (some extension may be late with supporting latest Eclipse)
3. Organize the extensions in categories
4. Extensions are added to the list following a well-defined process with the agreement of PDT committers - this is to avoid abusing the extensions wizard.

I am sure that approach b) fulfills all of the above. I have my doubts that this is completely possible with approach a), but we could research this.

Whatever approach we choose, this should be implemented in a separate plugin.