And what do you mean by "scheduler" component - I can think of at
least 3 very different definitions. You also give no indication of
what you expect the software to do, and what you expect to code. For
instance, ILOG make a very good Gantt tool (
http://www.ilog.com/
products/ganttnet/), which can be used to model most types of schedule
data - it is fast and highly extensible. However, your own code must
drive the model to tell it how to behave. It isn't cheap, but (for a
previous project) after comparing about 10 products it was the clear
winner. Sometimes you get what you pay for.
But the first thing I did was to write down a: what I *needed* it to
do, and b: what I *wanted* it to do, so that I could sensibly test and
compare the products.
Marc
