client server version of timekpr
I have 2 computers and 2 kids and they are not allways on the same pc. So I thought if timekpr was a client-server program than the server could run e.g. on a NAS and no matter on which pc they log in, they always would use only their share.
I know changing a program to this concept is not done easily.
I really like it
- Not started
- Needs approval
- Series goal:
- Milestone target:
- Started by
- Completed by
I was thinking about the same problem and think that a peer-to-peer version of this (now it's own blueprint) would be easier to implement and would also avoid problems should the server/cable go away.