Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] [Import] Why proposing the New Project wizard instead of Import Projects wizard?

Hi all,

 

it was quite some time ago when I looked into this, but I seem to remember that this generic propagation of the project folder to the wizards was the issue preventing us from implementing something more smart (wizards can’t be parameterized generically).

 

Best regards,

Mathias

 

 

From: egit-dev-bounces@xxxxxxxxxxx [mailto:egit-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Donnerstag, 16. Oktober 2014 16:31
To: Matthias Sohn
Cc: egit-dev@xxxxxxxxxxx
Subject: Re: [egit-dev] [Import] Why proposing the New Project wizard instead of Import Projects wizard?

 

On 10/16/2014 04:22 PM, Matthias Sohn wrote:

this sounds good :-)


Glad you like it, but what sounds good to you? ;)
Adding another radio to use the Import wizards?

Also, do you have an idea about my second question? About a generic & backward-compatible way to propagate the Git repo directory to any New/Import wizard?

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


Back to the top