Actual *coding* finally started this week, now that we believe we have
found the best possible design of the program using threads.
In short we now have:
The Tessa executable, which holds what would be the "GUI module".
This executable then executes a script that actually is the core of
Tessa. This script will load plugins (including the network
plugin(s) ), and pass relevant events on up to the GUI (which is
sitting in a separate thread).
I (Nick: MattJ, SVN: MWild1) (have the base GUI working, and
responding to events (ok, I only coded in 1 event so far...
ContactStatusChanged :) ). I also have the execution of the core Lua
script implemented.
Cory (Nick: groovebot, SVN: mooshoofasa) has been helping out with the
Code::Blocks project files, to try and get a setup that works in as
many distributions as possible. This is important if we are going to
make it easy for people to join the project as testers/developers.
Thanks Cory!
Next job is to merge the code I have already written for the core (all
Lua) with the new GUI events interface. It shouldn't be too hard.
I have also set up a guide to installing the latest SVN version of
Tessa, so you can keep up with development: http://code.google.com/p/tessa/wiki/InstallingFromSVN
If have any problems, join us at the te...@conference.jabber.org MUC.
On the same note, I currently have SVN commit notifications feeding
into the MUC via a bot...
Who would prefer them posted to this list? Who would want them sent
directly via Jabber? and who would rather they stayed in the MUC? Bear
in mind that there could be up to a dozen commits in a day (I tend to
commit at nearly every working stage).
Thanks also to Paul (nick: Thorns, SVN: brokenthorn) for the offer of
a website, which I am sure I will get around to configuring soon :)
Thanks again to everyone involved! (That includes Niek, an endless
stream of feature ideas, and Waqas, currently at a programming
competition, who helped me develop the new design of Tessa)