crickscore-cvs Mailing List for crickscore
Status: Planning
Brought to you by:
stevemac
Menu
▾
▴
crickscore-cvs — Commit logs form the CVS repository
You can subscribe to this list here.
| 2004 |
Jan
(9) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: <ste...@us...> - 2004-01-12 11:13:49
|
Update of /cvsroot/crickscore/documents/uml In directory sc8-pr-cvs1:/tmp/cvs-serv14223 Added Files: ActorDiagram.png PlayerManagement.png ScoringMgmt.png SystemAdministration.png UML_Model.zuml Log Message: Initial version of some UML diagrams. --- NEW FILE: ActorDiagram.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: PlayerManagement.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: ScoringMgmt.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: SystemAdministration.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: UML_Model.zuml --- (This appears to be a binary file; contents omitted.) |
|
From: <ste...@us...> - 2004-01-12 11:08:58
|
Update of /cvsroot/crickscore/documents/uml In directory sc8-pr-cvs1:/tmp/cvs-serv13723/uml Log Message: Directory /cvsroot/crickscore/documents/uml added to the repository |
|
From: <ste...@us...> - 2004-01-11 21:41:01
|
Update of /cvsroot/crickscore/documents In directory sc8-pr-cvs1:/tmp/cvs-serv12337 Added Files: Licencing_Discussion.html Log Message: Initial Revision --- NEW FILE: Licencing_Discussion.html --- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <title>Licencing Discussion</title> </head> <body> <h1>Licencing Discussion</h1> <h2>Licencing Concerns</h2> I would like to keep the option of using the crickscore engine in a commercial product open. The system will be built in a modular way, with the data access maintained by the open source core. To maintain the activity of the project it may be nessicary for 3rd partys to create commercial addons to the standard core to enable active customisations for each installation. We need to find an open source licence that enables the project to allow the core to be utalised in a commercial fashion, without their source needing to be released. I would not encourage this splintering of the code base, but it is somthing that I don't want to completely outlaw. If 3rd partys want to create custom front ends, or custom plugins for the system, then they should be able to. I would hope that if any commercial success comes from re-using the the crickscore core, then they will contribute either time or resources back to the core to enable it to be come stronger and in turn assist them more.<br> <h2>Licencing Options</h2> This is somthing that i'm not sure about. There are things like the GPL, LGPL, Apache, etc... Source forge has a good list of them.<br> <h2>Licencing Comparison</h2> I would like to fill this section in with discussions of each possible open source licence. These may be 3rd party discussions, and if so should be linked to the source and not copied into this document. If someone actually reads the licence and offers their own opinion on it then the content is most welcome in this document.<br> <br> </body> </html> |
|
From: <ste...@us...> - 2004-01-11 11:25:39
|
Update of /cvsroot/crickscore/documents/architecture In directory sc8-pr-cvs1:/tmp/cvs-serv17008 Added Files: System_Architecture.html Log Message: Initial Revision --- NEW FILE: System_Architecture.html --- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <title>System Architecture</title> </head> <body> <h1>Architecture Discussion</h1> The purpose of this is to outline what I think the architecture of the application should be.<br> This is in no way final, as with everything that is ever created in relation to <b>crickscore</b>.<br> <br> I think that I'll structure this document on the layers of an application that I can think of. <h2>Database</h2> I am open for discussion on this point, as to whether its a java or other (c++) application. I assume that we will want it to be a open source. Once we decide on which one to use, we should code the system to work specifically <h2>Data/Persistance Layer</h2> We need an automated object-table mapping module. I would like this to be a simple system to configure and modify. The major option that I can think of at the moment is <span style="font-weight: bold;">Hibernate</span>. This section probably requires a bit more review.<br> <h2>Business Layer</h2> I think that we should use an existing web application framework to handle the processing of the requests, security, authentication, authorsiation, etc.. There are many of these frameworks around, and I am going to spend some time investigating them and I will add new documents based around each of these frameworks. These frameworks are things like Struts and Torque.<br> <h2>Presentation Layer</h2> This layer will be dependent on the web framework provided, but I assume it will be a JSPish type of front end. We need to create a system to cache items used often on the UI. The Presentation layer will have plugins aswell, so the system needs to support dynamical content generation, based on the availble plugins that are registered.<br> <h2>Client Layer</h2> The client system should be any modern browser. We should maintain compatiblity with as many old browsers as possible, but this should not limit any development options that we want to persue. I think that we should be able to use the most modern features of current browsers (DHTML, Javascript, etc).<br> <h2>Development Approach</h2> I think that we should define a core of the application that handles all generic rules about the game of cricket and generic rules about reporting and statistic generation. This core should manage storing the data in the database and allow access of this information to any plugin or addition to the system. I think that each of these modules/plugins should be developed and as a separate module. The initial modules I can think of would be outdoor scoring system, indoor scoring system, outdoor statistic generation, indoor statistic generation.<br> <br> There should be an way upload a set of data to the core and have it insert it into the database. I expect that this upload file will be an XML file, in which the format will be defined at a later date.<br> <h2>General Architecture Discussion</h2> <h3>Plugin System</h3> Many sections of the system should be managed by runtime addition of plugins. Each plugin should extend a base type (ie. Report, Statistic) and should be instantiated and initalised via either a configuration file or a user initated process. When the plugins are initatated, they should be able to register themselves availbile for use by the system. Different types of plugins would work in different ways, some would re-act to certain events, others would wait to be invoked by the user, others may just run at specific times.<br> <h3>Listener Usage</h3> Each of the Business objects should allow listeners to register with either the class or an instance. Each BO should allow multiple different events to be watched. This is to facilitate the ability for unrelated objects to add themselves to listen to events generated. Plugins will utalise this listerner/producer pattern extensivly, this is to facilitate the loosly coupled design principal.<br> <h3>Inheritance Structure</h3> There will be enties in the system like Game, Innings, Over, Ball, etc.. These classes should be abstract base classes, allowing for implementations for each item based on the type of game and rules that exist. When the user says that a new game is to be started, the system will check what game plugins are loaded, offer these types for the user to select from and then based on that selection from the user instansicate the Game object. This game object will then drive what actions are done to start the game (how many players, who they are, etc). Once the game has been started this specific instance then manages creating innings objects of the same type, then overs and balls. The base classes define the attributes that each of these objects contain, but the sub-classes provide the logic of how the different entities work (like how many players in a game, balls in an over, possible ball options, etc.<br> </body> </html> |
|
From: <ste...@us...> - 2004-01-11 11:24:51
|
Update of /cvsroot/crickscore/documents/architecture In directory sc8-pr-cvs1:/tmp/cvs-serv16865/architecture Log Message: Directory /cvsroot/crickscore/documents/architecture added to the repository |
|
From: <ste...@us...> - 2004-01-11 11:20:33
|
Update of /cvsroot/crickscore/documents In directory sc8-pr-cvs1:/tmp/cvs-serv16166 Removed Files: XWin.log cvs002120 Log Message: removed as unnessicary import --- XWin.log DELETED --- --- cvs002120 DELETED --- |
|
From: <ste...@us...> - 2004-01-06 21:58:50
|
Update of /cvsroot/crickscore/CVSROOT
In directory sc8-pr-cvs1:/tmp/cvs-serv17164
Modified Files:
loginfo
Log Message:
Updated loginfo again.
Index: loginfo
===================================================================
RCS file: /cvsroot/crickscore/CVSROOT/loginfo,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** loginfo 6 Jan 2004 21:55:59 -0000 1.3
--- loginfo 6 Jan 2004 21:58:47 -0000 1.4
***************
*** 26,27 ****
--- 26,28 ----
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
DEFAULT /cvsroot/sitedocs/CVSROOT/cvstools/syncmail %{sVv} cri...@li...
+
|
|
From: Steve M. <st...@wh...> - 2004-01-06 12:00:32
|
Just testing again. -------------------------------- Steve Mactaggart Systems Architect Golftime International 12 Strathalbyn St Kew East 3102 Victoria, Australia PH: (03) 9859 5394 FAX: (03) 9859 5655 WEB: http://www.golftime.com.au MAIL: st...@go... |
|
From: Steve M. <st...@wh...> - 2004-01-06 09:33:37
|
-------------------------------- Steve Mactaggart Systems Architect Golftime International 12 Strathalbyn St Kew East 3102 Victoria, Australia PH: (03) 9859 5394 FAX: (03) 9859 5655 WEB: http://www.golftime.com.au MAIL: st...@go... |
