Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 24280

Summary:	"New Project" wizard setting name and getting project
Product:	[Eclipse Project] Platform	Reporter:	Michael Valenta <Michael.Valenta>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Kevin_McGuire, Tod_Creasey
Version:	2.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:
Bug Depends on:
Bug Blocks:	25077

Description Michael Valenta

2002-10-01 15:06:13 EDT

We (CVS) need to create projects using the "New Project" wizard. We currently 
do this by running the NewProjectAction. We need to be able to prime the name 
of the project but there is currently no API for this. Also, we need to know 
the project that was created and we do this by listening for the project 
creation delta. It would be cleaner to be able to invoke the wizard directly 
through API and get the project as a result.

Comment 1 Tod Creasey

2002-10-22 08:43:46 EDT

This is a good idea but will have to wait until we can make breaking API 
changes (i.e. 3.0). Here is what needs to be done

1) Priming with a name. We would need to propagate the name from the 
NewProjectAction, to the NewWizard, to an INewWizard and then to the first 
page. As there is no way for the page to look back as far as the NewWizard we 
would have to add a setDefaultName method to INewWizard

2) Returning a value. Both INewWizard and IWizardPage will need API to get a 
result.

Comment 2 Kevin McGuire

2002-10-22 14:50:06 EDT

>>As there is no way for the page to look back as far as the NewWizard 

I don't know the wizard framework well, but:

I seem to recall that this is a common problem with wizards - there is no real 
shared model to transfer values between the pages. Perhaps if they could all 
see the same lookup table, then one page could prime the value there and 
others could look for it.  You could use a convention of qualified names for 
the keys to prevent accidental collision.  This could mean that generic 
wizards could still act as intermediaries without having to have API specific 
to the values that others care about (in this case, the project name).  

With this approach there may even be a way of doing it without breaking 
changes.

Comment 3 Tod Creasey

2002-10-22 15:03:23 EDT

The problem is also about getting all of the other wizards to conform to this -
 a breaking API change is likely the only way to get other wizard contributors 
to satisfy this behaviour.

Comment 4 Tod Creasey

2004-10-22 10:12:48 EDT

We would need PMC approval for this sort of change. I am going to mark WONTFIX 
until this gets approval.

Comment 5 Michael Valenta

2004-10-22 10:26:03 EDT

Tod, sorry to nitpick here but if approval for this is being sought from the 
PMC then this should be left open and made part of the 3.1 plan. If approval 
is not being sought (and never will be if the bug is cloised), it should be 
closed as WONTFIX with a description indicating why (i.e. affects too many 
clients and is only required because there is no means to configure projects 
checked out from a repository).

This request was only made because repository providers need a means of 
configuring projects that have been checked out from the repository. I'm OK 
with this bug being closed since it does not really address the main issue. I 
think the broader issue still needs to be addressed (see bug 36959 and bug 
26224)

Comment 6 Tod Creasey

2004-10-22 10:39:31 EDT

I closed it as WONTFIX as the UI Team does not currently intend to present 
this for consideration to the PMC. Should another team do so and it gets PMC 
approval we could reopen it then.