ORDnance
bar.gif
Author: Mark Thom & Roy Souther

ProjectX

4/12/04 - Most of the progress completed to date has been documented. To convey a progressive outline of how the software works, it's best to read the documentation in the following order.
Documentation/Description Filename
ORDnance Pre-development Functional Specification
 		ORDnance_Pre-Development_Functional_Specification.sxw
ORDnance Component Diagram
 		ORDnance_Component_Diagram.sxd
ORDnance Report Compiler Components
 		ORDnance_module_components.sxd
ORDnance API Definition
 		ORDnance_API_Definition.sxw
ORDnance Dialog Storyboard
 		ORDnance_dialog_drawing.sxw
ORDnance Dialog Details
 		ORDnance_dialog_details.sxw
ORDnance Dialog Information
 		ORDnance_dialog_info.sxw
ORDnance Content Packaging
ORDnance_packaging.sxw
ORDnance XPCOM Notes / Class Structure
 		ORDnance_xpcom.sxw

3/08/04 - We'd like to add two new features to the PHP report compiler: one to embed and retrieve graphics to and from text format and another to create report arguments from the command line. Preferably the second feature will be implemented from the wrapper script down. Arguments will be passed to the wrapper and then to the compiler, which will make additions to the comment block at the appropriate parsing period. Different flags should be used to indicate argument placements for each block (something in the order of "--arg -h [element] [argument]" for header, "--arg -b [element] [argument]" for body).

2/25/04 - The XPIDL files for a few interface implementations have been completed. The interface implementations derive from two existing DOM interfaces, nsIDOMNode will be used to preserve component-side variables while polymorphically applying themselves to the DOM content model.

2/23/04 - The interface has been designed and implemented using XUL. The XUL files are available in the content directory and the storyboard is available in the doc directory.

2/17/04 - We've decided to implement the GUI as a XUL-based XPCOM component. This affords us a great deal of flexibility and control, not to mention the backing of a user friendly WYSIWYG environment.

2/10/04 - A few early GUI considerations have been posted to the docs directory on CVS. These considerations include a Mozilla editor component, a forked version of GINF (GINF Is Not Frontpage, a GtkHtml based WYSIWYG editor) or creating a GtkHtml application from scratch. Keep in mind that this choice will be mostly influenced by ease of use and software ubiquity - eg. Mozilla is readily available on most flavors of Linux.

2/5/04 - An early version of the PHP parser has been completed. Currently the parser only supports a few of the more pertinent features of the pseudo-code API. Because we still haven't determined whether format settings will be specified by means of the WYSIWYG component or the pseudo-code, they are not yet supported in the parser and may never be.