Thursday 15 December 2005 20:47, Fred Marmond wrote:
Hi,
I've just compiled/install the full koffice project, and kplato doesn't
start. the app.start() returns false, that is all I can say :-/

I compile/run it on a x86-64, and other parts of koffice are working
fine.

Is the current svn broken?
Is it supposed to work?
May I enable debug logs (how?)

Thanks in advance

I don't have an answer to the above question, but I want to apologize for
the long delay for the moderator approval, I have been out of town for
some days.
Do you still see the above problems?

21 december 2005 13:10, fmdp wrote:
Hi,
it works fine with today's svn (it may have worked for few past
days too as I couldn't test it until now).
Good :)

I'll play with kplato now.
Is the actual state can be tested, or is it known to be so unstable
that bug reporting is not welcome for now?
Is there any place to report bugs/features requests?
No, you can test, I don't know of any crashes atm ;)
It's early days yet, what I try to cover for this first 0.x release is
basic project planning. In short you can define tasks, resources,
calendars and accounts, link tasks, assign resources to tasks and
schedule the project.
Finding out how to link tasks can be tricky, but if you in ganttview
point to a task, press LMB and drag to another task, you'll get a
link. Double clicking on a link will get you a link dialog. (I've
plans to find a better way, suggestions wellcome)

The ui is generally not much good, I think, but I didn't plan to do
anything about it until qt4. Now, qt4 seems a very long time off,
so
But suggestions are very wellcome anyway!

Bugs can be reported using the help menu as normal, or directly using
bugs.kde.org, but discussing on this list first maybe better until we
release.

Unfortunately (?:) I'm taking a real long Christmas holiday this year,
leaving tomorrow, not back until next year! (probably jan 3.)

So, Merry Christmas and a Happy New Year to you all!

Fred

Le Lundi 19 D 2005 22:53, Thomas Zander a *:
Thursday 15 December 2005 20:47, Fred Marmond wrote:
Hi,
I've just compiled/install the full koffice project, and kplato
doesn't start. the app.start() returns false, that is all I can
say :-/

I compile/run it on a x86-64, and other parts of koffice are
working fine.

Is the current svn broken?
Is it supposed to work?
May I enable debug logs (how?)

Thanks in advance

I don't have an answer to the above question, but I want to
apologize for the long delay for the moderator approval, I have
been out of town for some days.
Do you still see the above problems?

kplato mailing list
kplato (AT) kde (DOT) org

21 december 2005 14:17, fmdp wrote:
Hi Dag,

I play with kplato, and here are few comments:
problems:
- doesn't handle correctly the task duration when set more than one
working plage per day (set 13:0->15:0 and 20:0->23:59)=all tasks
are displayed as '1 day long' in the gantt
I don't know what you expected to see , but it should display the task
as starting 13:0 and ending 23:59. It doesn't show that no work is
going on from 15:0 to 20:0.
- can't set ressources calendar (poor workers that can't take
holidays! ;) ) - project calendar: when days are tagged 'non
worked', it doesn't alter the gantt
The gantt chart doesn't (atm) display non-working days as you have set
them in the calendar. It indicates "week-ends" as gray in accordance
with you locale settings (I think), but this only works "correctly"
when you have a 1 day scale.

wishes:
I'll come back to this, no resource leveling is implemented yet, it
will just overbook.
- a link to Karm, to help feeding kplato with real worked times on
tasks - can assign a ressource for a 'mother task', that will
assign this ressource to all children's taskes
- calculate the right start time when 'ASAP' is selected with
previous effort sum:
task1 (effort 2days) and task2 (effort 1d) assigned to Ressource1
and both start the 2005-12-21 in parrallel
task3 (start ASAP as task1 and task2 are finished)
Now, I see that task3 start only 2 days after task1, but Ressource1
can't work 3 days (task1+task2) in 2 days! So, I would guess that
task3 will start 'as soon as possible', that's to say 'as soon as
Ressource1 is free', so, when he will have done task1+task2 =3
days after the start of task1/task2 - add a TD set of tasks that
are not yet plannified. We know that we'll have to work on theses
tasks, and they are yet ready to be planned (we can annotate them,
estimate effort, )
- handle euros too (only dollars for now) (minor for now! ;) )
- a per ressource list of tasks, in a calendar (as

But it seems to be promising, and I hope I will be able to use it
'for real' soon! ;)
The gui is not too hard to use (I miss some things like double
click on task on gantt to edit it, or things like that) but I found
the way of linking them alone. I used Qt4 in an other project, and
yes, you are right to wait qt4 on kde to implement that sort of
things ;)

have nice holidays, and see you next year!
Thanks, the same to to you.

Fred

Le Mercredi 21 D 2005 13:44, Dag Andersen a *:
21 december 2005 13:10, fmdp wrote:
Hi,
it works fine with today's svn (it may have worked for few past
days too as I couldn't test it until now).

Good :)

I'll play with kplato now.
Is the actual state can be tested, or is it known to be so
unstable that bug reporting is not welcome for now?
Is there any place to report bugs/features requests?

No, you can test, I don't know of any crashes atm ;)
It's early days yet, what I try to cover for this first 0.x
release is basic project planning. In short you can define tasks,
resources, calendars and accounts, link tasks, assign resources
to tasks and schedule the project.
Finding out how to link tasks can be tricky, but if you in
ganttview point to a task, press LMB and drag to another task,
you'll get a link. Double clicking on a link will get you a link
dialog. (I've plans to find a better way, suggestions wellcome)

The ui is generally not much good, I think, but I didn't plan to
do anything about it until qt4. Now, qt4 seems a very long time
off, so
But suggestions are very wellcome anyway!

Bugs can be reported using the help menu as normal, or directly
using bugs.kde.org, but discussing on this list first maybe
better until we release.

Unfortunately (?:) I'm taking a real long Christmas holiday this
year, leaving tomorrow, not back until next year! (probably jan
3.)

So, Merry Christmas and a Happy New Year to you all!

Fred

Le Lundi 19 D 2005 22:53, Thomas Zander a *:
Thursday 15 December 2005 20:47, Fred Marmond wrote:
Hi,
I've just compiled/install the full koffice project, and
kplato doesn't start. the app.start() returns false, that
is all I can say :-/

I compile/run it on a x86-64, and other parts of koffice
are working fine.

Is the current svn broken?
Is it supposed to work?
May I enable debug logs (how?)

Thanks in advance

I don't have an answer to the above question, but I want to
apologize for the long delay for the moderator approval, I
have been out of town for some days.
Do you still see the above problems?

kplato mailing list
kplato (AT) kde (DOT) org

21 december 2005 15:24, fmdp wrote:
Here is a testcase of the problem (see the .kplato attached)

standard working day is 8-16 + 17-20 (11h)
monday to friday are the same (each redefined, to be sure)
If I create a task of 33h, it sets it to 3 days (good) but only
display it in 2 days in the gantt
, think I fixed it, probably I was interrupted during implementation
because the functionality wasn't complete. I simplified the use of
the StandardWorktime thing (do you have a better name?). It's only
used when entering/showing estimates now. To define working hours you
have to use calendars. (The problem with setting calendar for
resources is also fixes.)

By the way, I just see an other strange thing:
open the file I attached.
edit one task (test2) and you'll see 'effort' of 2d 9h.
enter something in the Note area. click ok
Then, reedit the task, the hour area will be sub by 2! (2d 7h the
very next time, 2d 5h, and follows like this until 2d 1h)
Fixed. BTW, the duration/effort widget, do you you think it works ok?
Shaheed came up with this since we wanted a (simple) way to localize
it. It's still kind of prototype, atm it can't handle more than days,
it should at least handle weeks imo.

Fred

Le Mercredi 21 D 2005 14:55, Dag Andersen a *:
21 december 2005 14:17, fmdp wrote:
- doesn't handle correctly the task duration when set more than
one working plage per day (set 13:0->15:0 and 20:0->23:59)=>
all tasks are displayed as '1 day long' in the gantt

I don't know what you expected to see , but it should display the
task as starting 13:0 and ending 23:59. It doesn't show that no
work is going on from 15:0 to 20:0.

Torsdag 05 januar 2006 10:45, fmdp wrote:
Hi Dag,

I only updated kplato and it crashes at sometimes.
so, now, all koffice is updated & compiling and it takes long
time!!!
Tip: To run just kplato you need lib, kugar, kdgantt and servicetypes
(I think).

few answers to your questions, I'll report success/problems on the
execution when compilation will be finished (in few hours)

Le Mercredi 4 Janvier 2006 13:36, Dag Andersen a *:
, think I fixed it, probably I was interrupted during
implementation because the functionality wasn't complete. I
simplified the use of the StandardWorktime thing (do you have a
better name?). It's only used when entering/showing estimates
now. To define working hours you have to use calendars. (The
problem with setting calendar for resources is also fixes.)

As you are in calendars, could you implement something like that:
- a widget to define working day type (where we can say:
workingDayType1=8:0-12:0, workingDayType2=8:0-12:0 + 14:0-18:0
)
- in calendar, use those user-defined day types instead of
specifing working plages by hand for each
- multi-selection in calendar to set more than one day at once
I did for weekdays, use ctrl-LMB.
(Also for weeks actually, but I plan to remove weeks altogether as it
just complicates things)

It would be helpfull for those who have partial time working, or
are working on several project at a time.

Fixed. BTW, the duration/effort widget, do you you think it works
ok? Shaheed came up with this since we wanted a (simple) way to
localize it. It's still kind of prototype, atm it can't handle
more than days, it should at least handle weeks imo.

As a project leader, or even as a 'ressource', what I expect is:
If I have 2 tasks at the same time for a ressource, the duration
must take the effort into account:
taskA and taskB are both planned for ressource1 starting at 1rst
january and both takes 5 days of effort. So, both duration must be
10 days, as ressource1 will have to spend 2*5days.
So, taskA will be:
- starting at 1/01
- effort 5days
- duration 10days
- ressource usage 50%

But I must admit that this may be hard to implement, as tasks may
overlap at random times
I don't know how other do, but I think it would be very very very
usefull!!!

What is your opinion?
I have put off resource leveling till after this release, it's a bit
much before jan 12 ;)
Possibly if I have time I may make a simple preliminary solution to
overbooking, but that's as far as can go for now.

(PS: You don't have to CC me, I'm on the list :)

Fred

Fred

Le Mercredi 21 D 2005 14:55, Dag Andersen a *:
21 december 2005 14:17, fmdp wrote:
- doesn't handle correctly the task duration when set more
than one working plage per day (set 13:0->15:0 and
20:0->23:59)=all tasks are displayed as '1 day long' in
the gantt

I don't know what you expected to see , but it should display
the task as starting 13:0 and ending 23:59. It doesn't show
that no work is going on from 15:0 to 20:0.

Torsdag 05 januar 2006 13:52, fmdp wrote:
Le Jeudi 5 Janvier 2006 12:26, Dag Andersen a *:
Tip: To run just kplato you need lib, kugar, kdgantt and
servicetypes (I think).

ok, I'll try, it will be faster

I did for weekdays, use ctrl-LMB.
(Also for weeks actually, but I plan to remove weeks altogether
as it just complicates things)

, it works.
(personal feeling: I find it hard to see as it is not painted fully
in the calendar. A manager/ressource may find usefull to have each
day really painted in bleu/red. It would help to see vacations,
overbooked days, )
hmmm, is this the calendar dialog you are talking about? There isn't
any overbooking info there?
The reason I didn't use full background color on each day is that you
can define both weekdays and single day and then you couldn't see if
you had defined a single day (eg. with different workhours).
TH I expect the calendar dia to change when we go to KDE4 (in a year
or so) as I want to use the localized holidays stuff from kde-pim,
so I haven't put a really serious effort into the calendars (lame
excuse)

What is your opinion?

I have put off resource leveling till after this release, it's a
bit much before jan 12 ;)
Possibly if I have time I may make a simple preliminary solution
to overbooking, but that's as far as can go for now.

:)

I just want to give a 'user' feedback/point of view I hope my
suggestions do not stress you, that's not the goal!
I'm too much busy in my own project to invest into kplato code I
limit my participation to ba a user
But I know that projects often need 'external feedbacks' I hope
mine helps
You are very, very wellcome indeed. Exhaustive testing of my own code
is the hardest thing, and I'm not an extensive user of PMs so there
are millions of viable ways to use them that I couldn't even dream
of.
--
By the way, a minor bug: in Standard Work Time, if you put 'hours
per day' to '0.0', it hard-crashes when you modify a task duration:
Doesn't supprize me, I actually thought of it, but obviously didn't
test it, thanks.
fred@joe kplato]$ kplato
koffice (lib kofficecore): kplatopart.desktop found.
koffice (lib kofficecore): kplatopart.desktop found.
koffice (lib kofficecore):
KoDocument::loadNativeFormat(
/ )
kplato: Loading took 0.001 seconds
kplato: [KMacroCommand*
(KPlato::Part*)]
QGDict::hashKeyString: Invalid null key
kplato: [void
(KPlato::Task&,
KPlato::StandardWorktime*)] daylength=0
kplato: [void
(KPlato::Task&,
KPlato::StandardWorktime*)] Effort: 1 00:00:00.0
KCrash: Application 'kplato' crashing

(PS: You don't have to CC me, I'm on the list :)

yeap, the traffic is not so heavy to notify you twice! ;)

Fred

kplato mailing list
kplato (AT) kde (DOT) org

Torsdag 05 januar 2006 15:45, fmdp wrote:
Le Jeudi 5 Janvier 2006 14:37, Dag Andersen a *:
hmmm, is this the calendar dialog you are talking about? There
isn't any overbooking info there?

In fact, I was thinking of some code of color related to the amount
of work for a day: white for 0hour, full-red for 24h/d and a melt
between. A manager may quickly see periods that are too much red,
and try to plan quiter days after.
In little companies, working time is often flexible, but managers
have to keep in mind that 'ressources' are not slaves! ;)
So, when I spoke about 'overbooking', it was in fact
'overtiming'

The reason I didn't use full background color on each day is that
you can define both weekdays and single day and then you couldn't
see if you had defined a single day (eg. with different
workhours).

Yeap, I understood that. I was only express my personnal feeling: I
prefer to see details on a calendar.

TH I expect the calendar dia to change when we go to KDE4 (in a
year or so) as I want to use the localized holidays stuff from
kde-pim, so I haven't put a really serious effort into the
calendars (lame excuse)

concentrate on the valuable parts of kplato instead of answer my
cosmetic remarks! ;)
So, you are fully right, and I think an interraction with other kde
parts are very very important (with karm in particular, it would
be a must!) Forget my color requests for now 8-/
Yes, and pim and rest of koffice

I let you work in peace from now until the next time!
I don't mind you testing, I can always shelf wishes for later :)
oops, last question: is there any place to be aware of commits?
It would help for testing (detecting problems asap makes correction
often easier).
Yes, kde-commits (AT) kde (DOT) org, see for
how to filter (else you get all commits for whole kde)

Fred

kplato mailing list
kplato (AT) kde (DOT) org