here's my preference:
1. Ease of use.
2. Run-time extensibility.
3. Speed.
I think that's the priority list I'm using to direct my activities.
+1. Speed can come later. Premature optimisation is the root of all evil and
all that.
James
[[ cc:'d to the list ]]
I'm having problems trying to access to cvs, we are using a proxy that
almost never works :(
Hmmm... Then tarballs work best for you, right?
I'll see if I can't get nightly snapshots auto-building for ya. Might
be a few days, though.
James-- You have
Well kids, I'm unplugging for the night.
I think the Java Semantic Module is Done. I've included ease-of-use
features.
Tomorrow, I'll work on examples and end-user documentation (as opposed
to simply the nearly-complete JavaDocs).
Now's the time to start banging on it, and let me know what
Hi,
I am very interested in making a workflow engine (as I'm sure others on this
list are interested in doing) and I wanted to know if anything has started
in earnest based on drools?
I've a couple commercial packages that look really neat:
http://www.dralasoft.com/products/workflow/index.html
