I think we need to define "workflow". When we are talking about adding workflow to a package, it means using the workflow package to manage the processes. This can all be done behind the scenes. It allows the developer to quickly build a process and the forms to perform that process. It does not mean adding unecessary complexity to an otherwise easy to use application. Or hopefully not, anyway.
I suggest everyone who can get the chance checks out the acs-workflow packages documentation. It if very clear and I think it should be the model for documentation for other packages. Compare it to the documentation for other packages and you will understand what I mean.
I don't want to take over control of ETP either :). I just need certain features for an application I am using and I want to see what would be useful to others also.
