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

List:       kplato
Subject:    Re: [kplato] Re: State of KPlato?
From:       Dag Andersen <danders () get2net ! dk>
Date:       2004-10-28 13:47:37
Message-ID: 200410281547.38256.danders () get2net ! dk
[Download RAW message or body]

On Onsdag 27 oktober 2004 16:14, Sidoine Mosiah PIERREL wrote:
> Le Mercredi 27 Octobre 2004 13:33, Dag Andersen a écrit :
> > I feel it is a bit early for documentation, the ui is still
> > volatile.
>
> Ok. A translation in French? :)) and Spanish... :)))
sure :)
>
> > Of non-coding stuff, the following comes to mind:
> > - Doc, see above.
> > - Icons.
> > - Testing to see what doesn't work as expected, and which
> > functions to put priority on.
> > - In general: good ideas, especially on ui.
It was something that slipped my mind that may be interesting. It's 
obvious KPlato shall be able to *plan* (on which I have focused so 
far), but equally important is the output reports like progress, 
budgets, cost, deviations, etc. So, getting a handle on what's 
needed/what should be offered as standard would be a good thing.
>
> I can learn to code. I did in antoher live but I don't like. So,
> before trying something that I don't like in my everyday life, I
> prefer to ask about others things.
You're wellcome :)
>
> I am not a good graphist so, sorry for the icons. But I will test
Seems we have something in common ;)
> expensively kplato and fill as many bugs reports as necessary.
Good.
>
(snip)
-- 
Mvh,
Dag Andersen
_______________________________________________
kplato mailing list
kplato@kde.org
https://mail.kde.org/mailman/listinfo/kplato

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