that'd be http://nagoya.apache.org/wiki/apachewiki.cgi?GumpPython Ah yes, forgot that, sorry.
no worries dude!
1) There is a TODO in the existing code to actually launch "cvs" or launch "ant" and capture their exit status and output. I could see the need for some sort of launcher class to do this, and an result class to capture status & a file reference for stdout/stderr (combined?) [Perhaps this launcher could have a "timeout" in it, that would zap a long running process & set another status.]
I like XP. Do the simplest thing you can do to get it working :D. Combining stdout and stderr is probably a good idea. So is a timeout (the gump bash scripts I run have a timeout).
2) We need (IMHO) to represent the results of operations per project -- those operations are "configure" (merge/whatever), "update" and "build" & I see the latter two having the output from above. I could see this having "project gump status = SUCCESS/FAIL/PREREQ MISSING/TIMEOUT/CONFIG ERROR.
good plan.
When I think of gump I think "batch builds" so I'd see this as one aggregating class per project (and a named array per pro, but I fear that'd impact use cases other prefer (simple re-testing, whatever). Any thoughts on this?
you mean one aggregating object per project, all of the same class, right? Again: just go for it.
3) Ok, so given that "result set" we need one or more presentations. I am eager to work with forrest (via xdocs) so I was thinking of creating some sort of simple XDoc class w/ Book/Tab/Page type sub-classes. Nothing fancy, just enough to serialize out some simple xdocs.
also a good idea.
Ought I create gump/xdocs for this (as opposed to xdocs)?
dunno. We can always move it later ;)
I would love input on what the xdocs tabs ought be.
I believe jakarta-gump/stylesheets contains or contained at one point some kind of stylesheet for publishing gump run results in xml; maybe you can learn from there
BTW: I see something for RSS, do we need multiple output presenters?
need? It would be nice, for sure :D
4) I see that GumpBase and gen.py xmlize are pretty useful XML to/from Object mechanisms. I assume they are not 100% generic
oh, I think they are :D. Sam's an xml wizard, 'member ;)
All feedback appreciated.
I'll find time to submit your patches, at least :D
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
