[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Usability help needed for KPilot
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2003-04-24 11:04:35
[Download RAW message or body]

On Thursday 24 April 2003 09:32, Reinhold Kainhofer wrote:
> On Thursday 24 April 2003 01:09, Adriaan de Groot wrote:
> > On Monday 21 April 2003 21:07, Adriaan de Groot wrote:
> > > Right. The idea is that this will eventually not be a dialog, but a
> > > page inside KPilot itself. See snapshot9.png (same address) for what I
> > > had in mind.
>
> Wow, cool. I really like that layout (maybe the items in the list need to
> be reordered, but that's a minor issue)...

Yes. And it needs better icons than I can draw with KIconEdit in 15 minutes.

> And it seems we get a calendar and a generic database viewer!!! And I
> thought you were busy playing with junior. (Or does she wake you up every
> few minutes so you cannot get sleep anyway, so you have plenty of time for
> KDE? )

I can code with her asleep on my tummy. I have pictures. The calendar thing 
doesn't do anything yet, but it's my intention to give some display to the 
records of the calendar. I doubt it will become anything sophisticated, since 
I don't want to have to do complicated drawing or anything. Consider it the 
"details" view of a single appointment. The DB generic thing was supposed to 
give hex dumps or basic DB information. Right now it just reports some 
timestamps, since it turns out there's no way to quickly retrieve "how many 
records does this database have?" Something we could add to 
PilotLocalDatabase, though.

> > http://www.cs.kun.nl/~adridg/snapshot1[4567].png
>
> They all look good. Although I'm not sure if the step with the description
> and the configure button is really needed (okay, it makes thing easier for
> us since we don't have to deal with the question when to apply the
> settings, whether to ask the user, and also the conduits don't have to be
> in memory all the time).

That step only applies to conduits without a ConduitConfigBase object return 
from their factory. Those conduits create (modal) dialogs only for 
configuration. I thoguht it was really weird to pop up a dialog just from 
selecting a list view item. Once I've added ConduitConfigBase returns from 
all the conduit factories, this page will become obsolete. Then everything 
will end up "swallowed".

I don't actually have the logic for querying-and-saving changed settings in a 
conduit when switching them, but that shouldn't be too hard to do.

> The question is, how do the users expect the configuration dialog to work?

Um, we've tried all kinds of stuff over the years. While noone has really 
complained, most of the attempts _felt_ clumsy. Aaron could do a whole 
history of KDE UI stuff with CVS log conduitConfigDialog.cc, I think.

> At least the setup dialog had an explicit minimum size set in the ui file,
> which caused a similar  behavior. I fixed that a few days ago in CVS. Maybe
> it's the same with your dialog? (Every now and then, I usually  select each
> container and check which options are set, and which are unnecessary, like
> the LayoutMargin and LayoutSpacing set to 11 and 6 which would be the
> default anyway...).

My version of designer doesn't seem to respect the form settings for margins; 
I've hand-edited some .ui files to deal with that. As for the fixed minimum 
size, that might have been me as well, trying to get the lower and right 
edges to show. I'll mucronulate a little with the sources and see if I can 
find where to put the resize() and adjustSize() calls.

-- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org>
     Key fingerprint = 934E 31AA 80A7 723F 54F9  50ED 76AC EE01 FEA2 A3FE
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]