Jason,

These are really great features to add to IBO. As far as more components,
whats the difference? Add an IB Services page tab, and be done with it. Most
serious developers have large or multiple monitors. Also, GExperts has an
option to add multi rows to the component pallette tabs. You can also "turn
off" page tabs when working on projects. If its an IBO project leave them
on. If its a non-database app, then turn them off.

IMHO, don't go nuts with adding components, but add as many as seems
necessary. Don't compromise ease of use or functionality for the sake of
reducing component count by one or two. IBO has a LOT of components, but it
also has a LOT of power.

Paul Gallagher

----- Original Message -----
From: Jason Wharton <jwharton@...>
To: <IBObjects@egroups.com>
Sent: Thursday, January 18, 2001 1:50 PM
Subject: Re: [IBO] The Services API... again.


> > what do you have against an entire palette page?
>
> Being that IBO nearly takes over the entire component palette already I am
> conscious of enlarging it yet again.
>
> > > Let's look at making a complete wrapper for them all called
> TIB_Services.
> >
> > As you wish, but what does a class called "TIB_Services" encapsulate, if
> > I may ask?
>
> All of the services that the API delivers. Backup, Restore, adding users,
> etc.
>
> If I really had my way, they would simply be methods tied to the session
> component and not even be surfaced through a visual component.
>
> > Having to use the backup & restore code when I only need a log file
> > dump. *This* I believe is overkill.
>
> I don't think there will be enough code there to worry about. Keep in
mind,
> our code is only simple wrapper specs. Since all of the code to actually
do
> the backup and restore is in the API you are already forced to have 99% of
> the extra baggage to start with.
>
> Regards,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
>
>
>
>