🚀 go-pugleaf

It seems that Borland has not done a very good job of code automation (not
OLE) in JBuilder. But if you consider the relative complexity of the effort,
perhaps they are doing the best that is possible with Java as a relatively
young language (they seemed to do allright in C++ Builder though). When they
insert code for straight forward small stuff, they seem to accomplish it OK.
But when it comes to complex code generation, everything seems to fall
completely apart.

Have you done any queryDataSet stuff yet? The parser cannot handle complex
queries (joins?) either, so you end up hand coding a lot of database stuff.
You've got to love typing to work with this product (and Java in general for
that matter).

Bradford C. Miller <millerb235@spicedhamawayaol.com> wrote in message
news:39E615B4.FF02C243@spicedhamawayaol.com...
> Yes but therein lies my problem. I can look at the sample code, and all
> makes sense. but the IDE is not just code! Stuff gets put into the
> source code, other things are left out, (the JTable goes in but there is
> no TableModel put in, etc), and I'm left scratching my head. Plus the
> fact that all the documentation really appears to be Sun's more than
> Borland's, so I end up looking at source code that makes sense but how
> does that relate to the IDE...oh wait, that's where I started.
>
> Anyway, the struggle continues