Eddie, I'm not sure if you know this, but there is such a guide at Jason's
website www.ibojects.com .

Jeff Kreider

> -----Original Message-----
> From: Eddie Bush [mailto:eddie@...]
> Sent: Tuesday, January 23, 2001 7:01 PM
> To: IBObjects@egroups.com
> Subject: Re: [IBO] Starting out. (Was:Re:The Services API - corrections)
>
>
> My greatest problem as a new user of IBO was which properties to set to
> acheive the behavior I wanted. I did rely on help for a big part of that,
> but also referred to the sample apps. I would rather find it in help if
> possible though, as I hate having to go run off and load some sample app.
> Yeah, it's not that hard, but I just don't like doing it.
>
> A GSG would, I think, be a good thing. It should be fairly comprehensive
> though. There should also by examples in it. Maybe walk the
> reader through
> building a few applications that would start from a bare minimum app (a
> single grid editing a very simple table) to maybe a master/detail and a
> master/detail/detail.
>
> Parts of the help file are very good reading, but parts of it are severely
> lacking. While I can go out and look at a sample app, and
> eventually deduce
> which properties had to be set to what in order to acheive the desired
> behavior, I would MUCH rather be able to find that in online help
> or a GSG.
>
> That's just my two cents ... since others are giving theirs :)
>
> So far as the number of components goes ... I honestly couldn't care less.
> It would be nice, I suppose if things were grouped into separate packages
> you could cut down on application size by only compiling in those packages
> you need, but that's not really a huge concern for me because even with
> everything that is compiled in my apps don't tend to be huge. Of
> course, I
> wouldn't want a single component that did everything -- that
> would be silly
> too.
> Personally, I feel Jason has done a good job designing IBO and also done a
> very good job at managing the amount of functional autonomy and functional
> cohesion that IBO has.
>
> The SINGLE LARGEST FACTOR for ME is DOCUMENTATION. I guess I'm
> just a book
> worm.
>
> ----- Original Message -----
> From: Aage Johansen <aagjohan@...>
> To: <IBObjects@egroups.com>
> Sent: Tuesday, January 23, 2001 11:48 AM
> Subject: [IBO] Starting out. (Was:Re:The Services API - corrections)
>
>
> > Art wrote:
> > -------------------
> > ...
> > 1. I usually read the marketing materials, not the help file.
> > 2. The IBO helpfile is NOT useful to someone starting out. Perhaps the
> > Getting Started Guide is. Perhaps the sample programs are. But NOT the
> > helpfile.
> > ...
> > -------------------
> >
> > I think that when your average user looks at IBO for the very first time
> he
> > (or she) needs something that shows how to get a simple app up
> an running
> > STEP-BY-STEP. Like: Put this component here, set those
> properties so and
> > so, then place that component and so on.
> >
> > If a new user struggles for a couple of hours (and don't succeed) in
> > setting up a master-detail relationship (and he found IBX to be simple),
> > IBO needs something to help those users.
> > Maybe GSG provides an answer, but will they spend the USD30? My
> guess: at
> > this point - hardly.
> > After the first app, I think the user won't mind having a few
> well filled
> > tabs with components to explore.
> >
> >
> > Regards,
> > Aage J.
> >
> >
> >
> >
> >
>
>
>
>
>