From: bv (bjvest_at_post.cybercity.dk)
Date: Fri Mar 03 2006 - 22:11:28 CET
From: bv <bjvest@post.cybercity.dk> Message-ID: <19bb.4408b100@www.taskjuggler.org> Date: Fri, 3 Mar 2006 22:11:28 +0100 (CET) Subject: [taskjuggler-devel] Optimized XML file format v2
I've been playing around with the Taskjuggler XML file format v2. It looks promising. Use of XML as both input and output format makes it easier to have Taskjuggler interoperate with other tools, for example. I've seen a time registration system that supports export of time registrations in XML, for example. Would be nice to have Taskjuggler work smoothly with such a tool.
I consider Taskjugglers modular structure a real strength; one can in principle use the GUI, the command line form, a separate XML editor, or similar according to ones own preferences. In principle, at least. Use of the XML format as input format is IMO only a feasible option if the XML format is relatively simple.
Unfortunately, the current use of the XML format (v2) makes it somewhat difficult (or at least tedious) to write an input file manually in the v2 XML format. For example, dates are provided in both human readable and machine-readable forms, but only the machine-readable form is used when task-juggler reads in the XML file. Use of the machine-readable form seems like a showstopper for the use of the XML format as input file. Also, several inherited task attributes are dublicated, projectId is copied in everywhere.
I would argue that it is possible for example to devise some reasonable default values for the various attrbutes and element values so that most of the redundancy/complexity in the XML input/output file is removed. If noone objects, I'd like to implement a few of such optimizations - keeping backwards compatibility in mind, of course.
Comments?
-- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Fri Mar 03 2006 - 22:11:31 CET