[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Changed Open/Import Project Page
From: Aleix Pol <aleixpol () kde ! org>
Date: 2010-08-04 2:21:26
Message-ID: AANLkTimW8NVOk239bMObxE6m_sY76d_SCzH6s6jHpt6+ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, Aug 3, 2010 at 3:03 AM, Aleix Pol <aleixpol@kde.org> wrote:
>
>
> On Mon, Aug 2, 2010 at 11:06 PM, Andreas Pakulat <apaku@gmx.de> wrote:
>
>> On 02.08.10 21:23:45, Aleix Pol wrote:
>> > On Wed, Jul 14, 2010 at 3:56 PM, Aleix Pol <aleixpol@kde.org> wrote:
>> > > Yes, that's what I meant by finding a better solution
>> >
>> > So we don't like the first step I added and I was considering solutions.
>> > Since I have like a mental mess I'll put here the solutions I've thought
>> of
>> > so that we can discuss.
>> >
>> > - Separe the wizard into two menu entries open and import project for
>> > example. It's easy and straightforward, no code duplication but clutters
>> a
>> > little the menu. I like it, but I fear the name might not be verbose
>> enough.
>>
>> This is bad, there's a reason that its open/import project now. That
>> reason is that in kdev3 times users where always confused which one to
>> use when. IIRC the 'import' part is only kept there to cater for kdev3
>> users which are used to look for an import entry to get their project
>> into kdevelop (when it has no .kdev4 file).
>>
>> > - Put a Import project button in the same page as the KFileDialog that
>> shows
>> > the dialog. That would make the UI a little uglier but wouldn't
>> influence
>> > the rest that much. Also it would make the new feature very hard to see
>> and
>> > since it's very oriented to newcomers I don't really like it.
>>
>> I don't like that either, for the reasons you've already given.
>>
>> > - Have two KFileDialogs, one for the local case (with the select source
>> > widget in the same view) and another one on the next page in case it's a
>> > project that's just been checked out. I think this one might make the UI
>> a
>> > little complicated and probably duplicate some code but it would be the
>> best
>> > for current users.
>>
>> I guess you mean having the first page with the combobox and in case
>> 'local' is selected (don't have the exact string here right now) get the
>> file-selector below the combobox. On the other hand when selecting
>> git/svn/... one would get whats there right now, i.e. a separate page
>> with the actual file...
>>
> Yes.
>
>
>>
>> > What do you think? I think the best is to have the two menu entries but
>> I'd
>> > also like to know what do you think of my concerns on the other ones.
>>
>> I'd like to propose two more options:
>>
>> - have two menu entries, one for open/import project from disk, one for
>> open/import project from remote source (need to find better texts)
>> with separate dialog flows
>>
> What's the difference with my first option?
> Yes, we have to be very careful with the naming.
>
>
>> - Separate the "fetch" step from the "open/import" step, again by having
>> a separate menu entry, but automatically opening the open/import
>> dialog once the fetch is done. This would also make it easier to do
>> the whole thing asynchronously and showing progress of the
>> fetch-stuff. So there's a Project->Fetch Remote Project option which
>> has the first page of the import-wizard only, eventually a second one
>> if necessary. And then once the job doing the fetch (could be a
>> kio-copy, svn checkout, git clone, whatever) is finished it could
>> invoke the import wizard automatically.
>>
>
> I don't really see the advantage of having 2 wizards, it's not like we
> would work while the project is being loaded. Also, we can make the dialog
> not modal. Also, I think a new dialog popping up automatically would feel
> weird.
>
>
>>
>>
>> Andreas
>>
>> --
>> Your aim is high and to the right.
>>
>> --
>> KDevelop-devel mailing list
>> KDevelop-devel@kdevelop.org
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>>
>
>
Finally I added a new action. It doesn't look bad at all (besides that we
lack the icon).
If someone is interested, please take a look at the result and we can
discuss better naming and so on.
Tomorrow I'll come back with more messing up with the wizard :D
Aleix
[Attachment #5 (text/html)]
<div class="gmail_quote">On Tue, Aug 3, 2010 at 3:03 AM, Aleix Pol <span \
dir="ltr"><<a href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <br><br><div class="gmail_quote"><div><div></div><div \
class="h5">On Mon, Aug 2, 2010 at 11:06 PM, Andreas Pakulat <span dir="ltr"><<a \
href="mailto:apaku@gmx.de" target="_blank">apaku@gmx.de</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">
<div>On 02.08.10 21:23:45, Aleix Pol wrote:<br>
> On Wed, Jul 14, 2010 at 3:56 PM, Aleix Pol <<a href="mailto:aleixpol@kde.org" \
target="_blank">aleixpol@kde.org</a>> wrote:<br> </div><div>> > Yes, \
that's what I meant by finding a better solution<br> ><br>
> So we don't like the first step I added and I was considering solutions.<br>
> Since I have like a mental mess I'll put here the solutions I've thought \
of<br> > so that we can discuss.<br>
><br>
> - Separe the wizard into two menu entries open and import project for<br>
> example. It's easy and straightforward, no code duplication but clutters \
a<br> > little the menu. I like it, but I fear the name might not be verbose \
enough.<br> <br>
</div>This is bad, there's a reason that its open/import project now. That<br>
reason is that in kdev3 times users where always confused which one to<br>
use when. IIRC the 'import' part is only kept there to cater for kdev3<br>
users which are used to look for an import entry to get their project<br>
into kdevelop (when it has no .kdev4 file).<br>
<div><br>
> - Put a Import project button in the same page as the KFileDialog that shows<br>
> the dialog. That would make the UI a little uglier but wouldn't \
influence<br> > the rest that much. Also it would make the new feature very hard \
to see and<br> > since it's very oriented to newcomers I don't really like \
it.<br> <br>
</div>I don't like that either, for the reasons you've already given.<br>
<div><br>
> - Have two KFileDialogs, one for the local case (with the select source<br>
> widget in the same view) and another one on the next page in case it's a<br>
> project that's just been checked out. I think this one might make the UI \
a<br> > little complicated and probably duplicate some code but it would be the \
best<br> > for current users.<br>
<br>
</div>I guess you mean having the first page with the combobox and in case<br>
'local' is selected (don't have the exact string here right now) get \
the<br> file-selector below the combobox. On the other hand when selecting<br>
git/svn/... one would get whats there right now, i.e. a separate page<br>
with the actual file...<br></blockquote></div></div><div>Yes.</div><div \
class="im"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <div><br>
> What do you think? I think the best is to have the two menu entries but \
I'd<br> > also like to know what do you think of my concerns on the other \
ones.<br> <br>
</div>I'd like to propose two more options:<br>
<br>
- have two menu entries, one for open/import project from disk, one for<br>
open/import project from remote source (need to find better texts)<br>
with separate dialog flows<br></blockquote></div><div>What's the difference \
with my first option?</div><div>Yes, we have to be very careful with the \
naming.</div><div class="im"><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Separate the "fetch" step from the "open/import" step, again by \
having<br> a separate menu entry, but automatically opening the open/import<br>
dialog once the fetch is done. This would also make it easier to do<br>
the whole thing asynchronously and showing progress of the<br>
fetch-stuff. So there's a Project->Fetch Remote Project option which<br>
has the first page of the import-wizard only, eventually a second one<br>
if necessary. And then once the job doing the fetch (could be a<br>
kio-copy, svn checkout, git clone, whatever) is finished it could<br>
invoke the import wizard automatically.<br></blockquote><div> </div></div><div>I \
don't really see the advantage of having 2 wizards, it's not like we would \
work while the project is being loaded. Also, we can make the dialog not modal. \
Also, I think a new dialog popping up automatically would feel weird.</div> <div \
class="im"> <div> </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
<br>
Andreas<br>
<br>
--<br>
Your aim is high and to the right.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div>KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org" \
target="_blank">KDevelop-devel@kdevelop.org</a><br> <a \
href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div></div><br>
</blockquote></div><br><div>Finally I added a new action. It doesn't look bad at \
all (besides that we lack the icon).</div><div><br></div><div>If someone is \
interested, please take a look at the result and we can discuss better naming and so \
on.</div> <div><br></div><div>Tomorrow I'll come back with more messing up with \
the wizard :D</div><div><br></div><div>Aleix</div>
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic