[Time-table-devl] Tasks

[graeme f. <fos...@gm...>]

Hi,

We are now six, with Vl Merenkov joining us.
So I thought that I should list a few of the tasks that need to be tackled.
What is there at the moment is the screens (mostly) to enter the data
necessary to start work on the timetable, but not yet the creation of the
timetable.

Configuration manager
Installation scripts from source
Package manager bundled
Log in, log out and splash screen
Windows compile
Windows Installation
Database interface
Creation of the timetable

Before I explain what I am doing I think I need to say a little about the
code. The Source code is divided into seven folder, I'll briefly talk about
the DataClasses, ItemClasses, ModelClasses and Persistence directories.

   - DataClasses  - This directory holds all the classes that mirror the
   tables in the database
   - ItemClasses  - This directory holds all the classes item classes,
   this is a Qt concept that acts as a container for the dataclasses
   - ModelClasses  - This directory holds all the classes model classes,
   again this is a Qt concept and is used to keep all GUI views of the data
   synchronised
   - Persistence  - This directory holds all the classes that access the
   database.

I am currently working on a rework of the database interface. This involves
the classes in the Persistence folders. I know that it was a botch job that
I did, I just didn't realise how bad it was! Anyway the idea is that when I
have completed it these classes will act as a single path to the database a=
t
to the data that is currently held in program data structures. Whilst I
might not implement it at the moment I want to enable it to support
multi-user updates. So if two users are modifying the system it will be
reflected on the system it is very hard to get this right 100% of the time
but I'd settle for a solution that will work most of the time, but like I
said I'll probably not implement that this time around but I do want the
rework that I'm doing to be able to support it seamlessly.

I'm currently changing sql.cpp and this has had a big knock on effect with
the classes in the DataClass folder. Mainly because I was cheating and
getting the data from the database directly this will all change and the ai=
m
is to get all SQL commands out of the code that doesn't reside in the
Persistence folder with just function names in the classes that reside in
the DataClass directory.

Anyway the list of tasks is far from complete but I'd suggest that we
discuss how best to allocate the work. As I said some of the jobs are bigge=
r
or more complex that others. I've not tried to rank them, nor have I
included everything so if there is something missing that interests you
please mention it and we can look into it.

cheers,

graeme.