tutos-devel Mailing List for TUTOS

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I want to discuss different issues so please excuse the length of this 
email. I apologize if any of this is incoherent; it is late and I 
should be in bed.

> First thing I'd like to develop would be a TUTOS "platform" set of
> services that various presentation layers could be based upon but some
> of this projects direction may be based on prior work by the Didactylus
> team.
The core of the Didactylus project is a j2ee server application, that 
will run with the reference implementation from sun, that has a message 
driven layer. I didn't write it but at the time that we halted 
development it was finished. The only further coding to this group 
would be to fix/add any additional message types needed for the 
communication. This is a very simple task. The j2ee application manages 
all access to the database in order to synchronize database selects and 
updates.

> To that end, Matt would you be willing share the source code... ... If 
> so could you email it to me (zip file should be fine I have a large 
> inbox).
Would it be possible to commit this to the SF cvs? This would be much 
easier and make the code readily accessible (the small portion that 
actually works). If that is a problem I will  send a .bz2 or .zip.

> I promise to give full credit where it's due...
Team members put their names in the class files so any additional 
authors should append their names.

> ...and not change any code unless required...
The team tried to comment the code as time permitted so I hope these 
prove useful for someone not acquainted with the Didactylus project.  
You will find that certain portions of the code will need to be 
rewritten or even scrapped. This applies primarily to the database and 
GUI/Swing portions of the project. I will discuss the to do list where 
the Didactylus team stopped.

The Didactylus Project consisted of four components:
1. Database Controller
1.1 Algorithms Subsystem
2. J2EE Messaging System/Controller
3. Java/Swing Client

1. The Database Controller is responsible for pulling data from the 
database and then putting it in the appropriate object. Most of the 
time this involves receiving a request from the client, processing the 
request, and then returning the appropriate response.
1.1 The algorithms Subsystem is instantiated by the database 
controller. Algorithms is responsible for generating the gantt chart 
and telling the database controller if an update is allowed. It also 
tells the database the objects that are to be updated. For instance if 
the user updates a Task, any SubTask will have its time automatically 
updated.
2. The J2EE Messaging System controls the passing of messages from the 
Database Controller to the Client(s).
3. The easiest to explain is the Java/Swing Client. This is the client 
program sends and receives requests and responses from the J2EE 
Messaging System.

Current Status:
	At the moment Didactylus will only authenticate users and display the 
main window (auth success/auth failed). There are several windows and 
working menu items. But they do not communicate with the database.

Documentation:
	I will post all of the documentation we created while working on 
Didactylus. This includes a setup guide for Eclipse (eclipse.org) and 
instructions on how to get Didactylus to run. Where should I post this 
information? Do you have a site or should I post if on mine? It matters 
not to me.

To Do:
	- create remaining database object classes and their JUnit test classes
	- implement the help system
	- get the gui working/cleaned. (We had noone experienced with Swing)
	- debug the algorithms code to ensure it works as we ran out of time 
to test it.
	- implement a memory manager for the db to increase object retrieval 
time and overall performance
	- update Didactylus to use current database version.
	- debug debug debug
	- create an installer for the entire system/better installation 
instructions

To Fix:
	- Comments need to be JavaDoc compliant.
	- develop a set of coding standards and follow them. make all of the 
existing code match this standard
	- remove the non functioning Swing files (some people wrote garbage 
that never worked and will confuse any sane person)
	- get database to read SQL connection info from a file. define the 
format for this file

There are many other things that need fixed and added to the To Do 
list; I only added the items that stood out most in my mind. Again the 
biggest areas that need work are the client and database. I worked on 
the database team so I know what needs to be done to get it in full 
running order. The GUI is what worries me most.

I would advise this order of attack: (if you decide to use our code)
Database
Swing/GUI
Algorithms
J2EE

I have attached some of the Documentation created during this project. 
Email me with any questions that you have.
1. Running_Didactylus.html is the setup manual

2. TeamResponsbilities.html shows the responsibilites and roles of each 
group.

3. ProjectDescription.html is a brief description of TUTOS and 
Microsoft's project management software and what some of their 
pros/cons.

4. SystemSpecification.pdf is a short document I wrote detailing our 
project and its components at a high level.

I hope some of this helps and I have more information to post when I 
have more time. If someone wants to discuss this in real time my aim 
screen name is terminalnine.

- Matt

Attachments:

2000	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (16)	Nov	Dec
2001	Jan	Feb	Mar	Apr	May (2)	Jun	Jul (10)	Aug (4)	Sep	Oct (4)	Nov (1)	Dec (7)
2002	Jan (1)	Feb (8)	Mar (7)	Apr (20)	May (1)	Jun (5)	Jul (27)	Aug (18)	Sep (55)	Oct (13)	Nov (27)	Dec (20)
2003	Jan (23)	Feb (40)	Mar (20)	Apr (10)	May (12)	Jun (8)	Jul (11)	Aug (7)	Sep (3)	Oct (2)	Nov (1)	Dec
2004	Jan (2)	Feb (34)	Mar (10)	Apr (11)	May (5)	Jun (6)	Jul (12)	Aug (7)	Sep (16)	Oct (25)	Nov (8)	Dec (2)
2005	Jan (17)	Feb (2)	Mar	Apr (5)	May (5)	Jun (8)	Jul	Aug	Sep	Oct	Nov	Dec
2007	Jan	Feb (2)	Mar (1)	Apr (1)	May	Jun (2)	Jul	Aug	Sep	Oct	Nov	Dec
2010	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2011	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2014	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

S	M	T	W	T	F	S
1	2	3	4	5	6	7
8 (1)	9 (5)	10	11 (2)	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30

tutos-devel Mailing List for TUTOS

Projects / CRM / PLM / Calendar / Tasks / SCRUM / Test / Inventory

tutos-devel — Developers