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

List:       kde-usability
Subject:    Re: list of usability-related aKademy discussion
From:       Benjamin Meyer <ben () meyerhome ! net>
Date:       2004-07-26 16:25:01
Message-ID: 200407261225.04323.ben () meyerhome ! net
[Download RAW message or body]

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

On Monday 26 July 2004 9:37 am, Aaron J. Seigo wrote:
> On Monday 26 July 2004 05:13, Benjamin Meyer wrote:
> > > we'll be writing code there as well. just as you, Benjamin and others
> > > have. or did you first write and pass a long formal document here
> > > before writing code? did you get everyone and their dog to help you
> > > write that code? no, you discussed it with various people and got to
> > > the business of writing code. and that's the way it should work.
> >
> > I very much wrote the doc first and then made the app.
>
> how man other developers not on this list vetted it? i wasn't around for
> the last couple months, so this is a serious question ;-)
>
> and.... how would i find it were i to hear about it on IRC? e.g. a URL?
>
> i ask simply because these are the questions i expect to get asked ;-)

Well I am hardly the case you are looking for.  My doc/app are simply things I 
put together on my own.  Now the doc in kdebase/kcontrol/TODO and the code in 
kdenonbeta/kcontrol4/ from what I understand have been discussed over and 
over.  I didn't want to jump into the middle of the conversation without 
bringing something to the table. 

> > I could just write
> > a xml file for my current doc that fits in the current kde3 kcontrol, but
> > also wanted to present another idea for how kcontrol could look.  There
> > are really two parts to kcontrol.  Where things go and what they look
> > like (the data and the presentation).
>
> ... and what guidelines the individual panels follow. that affects how the
> "where things go" works out.

Yes, that is very important also.

> the presentation, in my mind, also includes not just looks but interaction:
> search, help, navigation (which has to scale up and out) ....
>
> anything to add to the above quick snips?
>
> > > 	points of conversation you are interested in seeing addressed and/or
> > > want to be involved in
> >
> > To help make the two doc describing the categories and presentation.
>
> noted =)
>
> and hopefully we'll be able to get to more than just docs. any code in
> particular you'd like to have discussed / picked over? any points in your
> doc that you see as particularly salient / finished? embryonic and in need
> of fleshing out?



Well when it comes time to code and cvs opens up again I am all for helping 
out especially in the KConfigXT conversion as I know that intimately along 
with general work.  As much as I would love it my doc might not be the best 
starting place.  Frans Englich listed several docs that should probably be 
the bases (Maybe someone should start flashing it out in kdebase/kcontrol?) 
as they have been rehashed over and over here.

- From the TODO list alone a lot of the kcontrol modules seem to be headed for 
merging as there is a bunch of duplication all over, that will be some effort 
right there.

A few things in my doc that I think should be in the final one are statements 
of what modules goes in a section and why and what modules don't go in a 
module and why.  Also the breaking up of "Appearance & Themes and Desktop" 
better, but that might have already been in the TODO, need to double check 
that one.

- -Benjamin Meyer

- -- 
aka icefox
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBBTBg1rZ3LTw38vIRAk4uAKCixXLGUX+LLtsJpJwPrVH65lV2twCfUBM8
bJdE+3e3Dnvi6s5d2FSDwao=
=+/fV
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]