Article View: borland.public.jbuilder.java.language
Article #17136Re: Working with jdk1.2 workaround
From: flashback
Date: Sat, 12 Dec 1998 00:00
Date: Sat, 12 Dec 1998 00:00
70 lines
3504 bytes
3504 bytes
howdy folks, Vasudevan Srinivasan wrote: > Hi, > is anybody already doing serious stuff with jdk1.2 ? well, i'm working for a german insurance-company, and we've done a project for a special business called "car guarantee", it's a java-application (!) with about 200 classes. we started using jbuilder 1 c/s-edition but luckily did NOT use neither the db-wizard nor the gui-builder. we have to access a db2-database on an os390 and we wanted to use swing. the solution was, that we did the coding by hand, means we used ibm-drivers (db2java.zip) to access the database and did the gui-design by hand. we had to do so because jbuilder 1.x did not support swing in the way we needed it. we than switched to jbuilder 2.0 (2.01) and recognized that jbuilder was not able to parse the views (we used the mvc-model, even provided the jbinit-method) and went on coding the gui by hand. than jdk1.2 came out, with the new javax-path.... well, we used the change-swing-path-class provided by sun, changed all the import-statement, dropped the swingall.jar off the project, therefore put in the swing1.1beta3 (which contains the same paths as jdk1.2) to the project. for debugging-purposes we ran our source against borland's jdk1.1.6 and sun's swing 1.1beta3, and it worked....until now we did not encounter any side-effects. for production-purposes we compiled the source against the jdk1.2 and installed the jre1.2 on our customer's pc's (nt 4.), and everything seems fine so far, we do not have any problems with jdk1.2 being slow, and we see a lot of bugs (printing, hotkeys etc.) fixed. well, this is not what i call a solution, but it's a work-around. and what do we learn from this? *never* ever rely on all those wizards, neither gui-, database- or whatever but do the coding by hand - after a while of doing it you'll be able to do it as fast or even faster as doing it using the wizards. jbuilder has got a great source-editor, a great debugger and a great class-browser, and that's exactly what we use, but just forget about all those wizards.... the only code that works is the code you're writing yourself.... hope that this may help some of you folks..... regards from cologne, germany gregor > How does it look ? > I ran some sample applications bundled with it, both applets and > applications, and I still find the refresh/paint/invalidate problems > persisting and is slow too. and im using pentium II 300 with 64 mb ram > with win98. it does though have lot of cool stuff on it llike java2d etc > (as promised and expected), but the underlying problems havent gone off > altogether. is it only on my machine ? or others experience the same ? > > Thanks for ur views > Vasu -- the best is yet to come... http://www.netcologne.de/~nc-schneigr icq-# 14100227
Technical Details
Message-ID:
<367239C9.67D0DF82@netcologne.de>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<366D3F73.C84C9752@netrisk.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,9986923020abb520 X-Google-Attributes: gidf74b3,public From: flashback <flashback@netcologne.de> Subject: Re: Working with jdk1.2 workaround Date: 1998/12/12 Message-ID: <367239C9.67D0DF82@netcologne.de> X-Deja-AN: 421475409 Content-Transfer-Encoding: 7bit References: <366D3F73.C84C9752@netrisk.com> To: Vasudevan Srinivasan <vasudevan@netrisk.com> X-Accept-Language: de Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Reply-To: flashback@netcologne.de Newsgroups: borland.public.jbuilder.java.language