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

List:       kde-pim
Subject:    Re: [Kde-pim] Re: KPilot: yow to experiment
From:       David Bishop <david () bishop ! dhs ! org>
Date:       2001-09-24 6:15:10
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Second, I have a mock-up of the conduit dialog up.  There are a couple of
> problems: one, I was thinking we would inherit from KDialogBase again, but
> we'll need to add a couple custom buttons (add and remove, to be specific).
> Can you do that?  Or rather, because I'm sure you can, anyone know how? 
> And problem two is an implementation thing.  I notice in the old code for
> the conduit config, it has some code like: setDragEnabled(true); and
> setItemsMovable(false); in the setupWidget class.  Well, I can't find the
> equivilant selections in designer, for QListView or KListView (the old code
> uses K*, but Adriaan previously asked that I stick to Q* for the designer
> generated stuff).  Am I missing something? As near as I can tell, that's
> what enables you to drag from one RootItem to another (i.e., from available
> to active).  The ui file is at
> http://bishop.dhs.org/~david/conduitConfig_base.ui.  If someone (who isn't
> using qt-designer3.0! :-) can tell me what I'm doing wrong, that would be
> wonderful.

First off, anyone who replies to their own email *twice* should be shot.  
Second, this needs to be extremely quick, because my wife is about to kill 
me.  I thought about it some more, and want to rework the conduit config 
dialog completely.  One thing that bugs me is that it doesn't "fit" with the 
rest of kpilot.  I.e., drap and drop is nice, but everywhere else we use 
checkboxes and drop down lists.  Why change?  In that spirit, I (literally) 
took less than five minutes and whipped up a skeleton of how I envision the 
new conduit dialog to look like.  As a side benefit, we can add individual 
tooltips to each conduit, something we can't do while using a (Q|K)ListView.  
Let me know what you guys think, and I'll finish it tomorrow.  Oh, and we 
could also inherit from KDialogBase without adding extra buttons, and 
probably reuse code from the kpilot config.  Code reuse rocks!

Okay, screenshot at http://bishop.dhs.org/~david/blah.png  Yes, it's ugly but 
it should get the point across.  Well, g'night.  I gotta work in the morning 
:-(

Oh, and the code if anyone wants it, is at 
http://bishop.dhs.org/~david/conduitConfig_base2.ui  Please note it will 
change drastically in the morning.

D.A.Bishop
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7rs9uKEJ4huP2XBERApmtAKCQTGF8sqYII5WPsV2XIz+0558tdACgwNuP
nkaWrzWJZBSSen8Re7eoDys=
=QKzp
-----END PGP SIGNATURE-----
_______________________________________________
Kde-pim mailing list
Kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim

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