Until recently, the command-line interface of the trunk was basically
ignored due to other priorities. Configuration certainly has changed a
bit, but is obviously unfinished (Gradual move to Avalon Configuration,
inrtoduction of the Confihurable interface, work in progress). IMO it's
low priority
Jeremias Maerki wrote:
Until recently, the command-line interface of the trunk was basically
ignored due to other priorities. Configuration certainly has changed a
bit, but is obviously unfinished (Gradual move to Avalon Configuration,
inrtoduction of the Confihurable interface, work in progress).
From: Clay Leeds [EMAIL PROTECTED]
snip/
It may not be too much of a loss, but I won't be able to test the trunk
until either a CLI is implemented, or I learn to run Java applets...
It would be a loss. If you could spare time to test the trunk, you could
report back on which bits of layout
Chris Bowditch wrote:
It would be a loss. If you could spare time to test the trunk, you could
report back on which bits of layout need attention. A sort of gap
analysis
for basic FO documents would be really useful. This in turn would help
encourage development of the layout.
I have run
Hi crew:
1. In the maintenance branch, the -x command-line option appears to *only*
spit out the configuration information, then bail out. Is that the desired
behavior? If so, I should probably update the doc to reflect that.
2. In the trunk, the -x command-line option seems to be ignored. Also,
