Paul Clapham wrote:Yeah, that's what all the beginners say.
Paul Clapham wrote:XYLayout??? No, no, no, read the tutorial about Using Layout Managers. Laying out your components pixel by pixel looks good to beginners because things seem to work right, but you can only really pull it off if you already know how to use layout managers.
Let me move this post to the Swing forum where the real Swing experts hang out.
Paul Clapham wrote:Oh, okay, so "group box" is just an ordinary JPanel then.
Paul Clapham wrote:The phrase "group box" doesn't ring any bells with me. But if you want a form which can show a variety of panels depending on the context, then a CardLayout does that sort of thing.
I don't see why it's an extra burden to keep track of what should be visible; surely no matter what solution you use, you're going to have to say which panel is currently supposed to be visible?
Anyway here's a link to the tutorial: How to Use CardLayout.
Rob Brownsell wrote:
This is document was written back in 2000 (when it comes to Oracle forms, I don't think much has really moved on since then!) but I think the principals are the same
http://www.oracle.com/technetwork/developer-tools/forms/documentation/269054-130573.pdf
Rob Brownsell wrote:I'll try to explain as much as I can in this post but I believe the Oracle website has some information on this. Surely they haven't blocked that site! You need to add frmall.jar to your project, this will give you the forms classes you need (you should find it in your forms installation).
Rob Brownsell wrote:Hi there, when calling Java from Oracle forms or adding swing components, I've always used PJCs (pluggable Java components). This has the benefit of using the JVM being used by the client instead of having to use the one that comes with forms. This means you're not tied to the particular version of forms you are running. You have to update your formsweb.cfg to register your jar and put it in the java directory below forms. I know this is a bit different to what you were describing in your post but generally I've found this to be a reliable way to integrate Java into Oracle forms. There's quite a good resource on doing this sort of thing here:
http://forms.pjc.bean.over-blog.com/
One gotcha is if your implementation still uses JInitiator. If this is the case then all your PJCs must use Java 1.3. That's still the case where I work but we should be moving away from it soon (hopefully).
Rob Brownsell wrote:Hi there, when calling Java from Oracle forms or adding swing components, I've always used PJCs (pluggable Java components). This has the benefit of using the JVM being used by the client instead of having to use the one that comes with forms. This means you're not tied to the particular version of forms you are running. You have to update your formsweb.cfg to register your jar and put it in the java directory below forms. I know this is a bit different to what you were describing in your post but generally I've found this to be a reliable way to integrate Java into Oracle forms. There's quite a good resource on doing this sort of thing here:
http://forms.pjc.bean.over-blog.com/
One gotcha is if your implementation still uses JInitiator. If this is the case then all your PJCs must use Java 1.3. That's still the case where I work but we should be moving away from it soon (hopefully).