This is a brief summary of what Jocundmail is and what it is about.
Jocundmail's main goal is to cater to everyone. It should uncover as many or as few settings as a user wishes to deal with. It should be slim if a user wants a slim client and it should provide extensive utilities should a user desire them.
All of that is nice and all, but how will it work?
Jocundmail's code will strive to have fine granularity object orientation. This will allow small modifications to be made at any level in the code. What does this mean in terms of work programming? It means that documentation is paramount as well as writing readable code. The goal would be for someone new to jocundmail to be able to jump into the middle of the code and understand what is going on by reading the comments of the hierarchy from the top down to their level.
The program is divided into two essential pieces. There is a background daemon style process that processes your mail for you, doing the hardwork of talking to the server and storing the mail. The backend is meant to run all the time, and as such should probably be fairly lightweight if possible.
The frontend piece is the piece you open up to browse your mail. It is essentially a graphical interface to the backend. A fronted can manage/edit settings, read mail and write mail. Whether the frontend be a java swing app or a webserver app, is irrelavent to the backend, both will be treated exactly the same.
More to come as I write it down...
Last Modified: 06/18/2007 23:37:24.
