Geoff Worboys wrote:

> I would suggest that the "too complex" complaint that
> sometimes gets thrown at IBO has more to do with the
> number of properties on a given component than it has
> to do with the number of components.

With respect, Geoff, I don't agree. IBObjects, AsyncPro, and ABC Components
all through a massive number of new components onto my component, and I
found each and every one of them intimidating. The root of my concern is,
roughly, "120 new components? Where the !@# do I start?"

I have two suggestions to ease this, and both will take some work.

1. Instead of one massive install, make several "palettes" optional at
install time (much as Delphi itself does). Add a short Help screen
describing each of them. I don't see a need to allow the user to install
components one-by-one, but pallette-by-pallette makes sense.

2. Arrange a distribution license with GExperts (AFAIK, it is
freeware). Set up a single multi-tabbed palette for IBObjects
automatically.

> I do think that Jason's original idea of a
> simple TIB_Services component is probably sufficient.

My preference is "one component should do one thing" and, as such, is quite
the reverse of (say) isc_database_info(). I would prefer to see separate
components to add/delete users, backup/restore, perhaps another relating to
gfix and one to allow you to add files to a database.

Just my 2 cents,

Art Metz
AMetz@...