Nic Wise asked:
> > From: Nic Wise [mailto:[EMAIL PROTECTED]]
> > >From what I've heard, IBO has a few fundermental problems too.
> >
> > I'd wondered about that. Nobody's been willing to tell me IBO's
> > shortcomings. :-)
>
> Paul or Max, care to comment?
Never being one to shy away from giving an opinion I'll give one now 8-)
IBO's main issues are to do with the fundimental design decisions that
Jason Wharton made during the development. Paul and I were helping with
the debugging during these stages, and Paul has some talks with Jason at
one of the US BorCon's.
Jason's environment is 100MB ethernet local area networks. So IBO is
subtly tilted towards a high bandwith environment, and some of the trade
offs in the code do cause some pain when dealing with modem links for
example.
Apart from that the main issues that people have is Jason's insistence on
replacing all the standard data-aware controls with his own vesions (where
has you heard that before 8-) that he has designed to work well with SQL
backends . It too a long time (and a large code dump from Profax) before
Jason got into doing TDataset stuff, and this caused more mutterings
amongst the natives.
So if you do IBO you're buying into Jason's controls, component design
ideas and connectivity design. Some of it is good, but some rubs people
the wrong way. And Jason's insistence that he's Open Source by using his
"trustware license" is also adds a rather odd twist to the saga, and not a
few flame wars 8-)
With the birth of IBX the data-aware linking, native Delphi control people
are happy, but soon find that IBX needs a lot more development effort into
it to make it have the equivalent functionality as IBO.
Cheers, Max.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
