new import wizard, discussing vcs interfaces

[Aleix Pol]

On Sun, May 23, 2010 at 7:09 PM, Aleix Pol <aleixpol at kde.org> wrote:

> On Sun, May 23, 2010 at 12:32 AM, Andreas Pakulat <apaku at gmx.de> wrote:
>
>> On 22.05.10 21:16:17, Aleix Pol wrote:
>> > On Sat, May 22, 2010 at 9:10 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>> >
>> > > On 22.05.10 19:21:35, Aleix Pol wrote:
>> > > > On Sat, May 22, 2010 at 6:13 PM, Andreas Pakulat <apaku at gmx.de>
>> wrote:
>> > > >
>> > > > > On 21.05.10 15:17:51, Aleix Pol wrote:
>> > > > > > So I moved the import wizard branch to some clone of mine. it
>> can be
>> > > > > found
>> > > > > > here: http://gitorious.org/~apol/kdevelop/apol-gsoc2010
>> > > > > >
>> > > > > > What we can find there is the new page in the import wizard with
>> some
>> > > > > > changes here and there to make it work. (git plugin doesn't work
>> with
>> > > > > that
>> > > > > > branch, without my local changes). That page is capable to help
>> the
>> > > user
>> > > > > > clone/checkout and go on with the importing process.
>> > > > >
>> > > > > Hmm, just had a look at it. I like the idea behind it but have a
>> couple
>> > > > > of comments regarding the actual looks:
>> > > > >
>> > > > > - Whats working-directory? This isn't quite clear.
>> > > > >
>> > > > The working directory is the directory where to the project is going
>> to
>> > > be
>> > > > checked out and the directory that's being shown in the next wizard
>> page.
>> > > >
>> > > >
>> > > > > - For local I think the lower-part should just show the
>> file-selector
>> > > > >  instead of having that at a separate page
>> > > > >
>> > > > Yes, but the thing is that others are going to need the next page
>> anyway
>> > > so
>> > > > I'd like local users to be able to just go ahead.
>> > >
>> > > Well, local users just need the second page and remote users shouldn't
>> > > need the second page at all right? After all if they can say where to
>> > > checkout the project to and where it comes from then we don't need to
>> > > ask them which file to open. We can just use the directory it was
>> > > checked out to.
>> > >
>> >
>> > Well, when you checkout you need the second page to select the project
>> file
>> > (if there's no project.kdev4 file).
>>
>> No you don't. At least normally you don't. If I checkout a project X
>> from some svn repo then the .kdev4, cmakelists.txt etc. will be the one
>> in the top-level. So all you need is give the appwizard the
>> <working-dir>/<projectname> and the wizard will figure out the rest
>> (it'll even propose a manager-plugin if there's no .kdev4 file)
>>
>> Andreas
>>
>> --
>> You love your home and want it to be beautiful.
>>
>> --
>> KDevelop-devel mailing list
>> KDevelop-devel at kdevelop.org
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>>
>
> Well, there's the case I check out kde edu to be able to import kalgebra,
> it's not possible if we cut the user here.
>

I think that for the moment I'll leave the UI as it is right now and if we
don't like the result in the end we can always optimize it a little for the
local projects but I'd rather merge and concentrate on the technical parts
now.

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100609/77c2df83/attachment.html>