Posted by Hafed | Posted in Forms, oracle, PJCs/Javabeans | Posted on 16-01-2009
As I was finalizing the technical note for another gauge bean, it hit me that I wasted quite some time designing the visual part of the bean. In Oracle Forms, you create the bean on the canvas, assign it a height and width and then set up the implementation class.
Now, in order to customize it, you would have to follow the bean’s developer recommendations and use the set_custom_property built-in in order to modify the bean properties. However, this implies that as a developer, you would have to compile and run the module each time in order to see the result.
In my case, it requires a number of iterations and that bothers me quite a bit. That’s where I suddenly realized that when I designed MouliForms, I created a class that was basically a clone of the Oracle Forms property palette editor ( Remember F4 !!).
I asked myself whether I can extend the same concept to Forms javabeans and here what I think should come out in a few days (hopefully not weeks):
I guess that should do it and could be very useful.
Similar Posts:
- A Dashboard styled Oracle Forms bean
- Google Static Map javabean with Forms 10g: new improvements
- File Selection Dialog with Oracle Forms 10g (10.1.2): replacing some of webutil functionalities
- Gauge with thermometer style display- Javabean for Oracle Forms 9i-10g
- Generating FormsDoc and FMB module compare functionality
There also exists a white paper on OTN about “How Do I Debug Oracle9i Forms Developer Pluggable Java Components”:
http://www.oracle.com/technology/products/forms/htdocs/howto_debug_pjc.html
that would be a good complement to your entry ;D
Francois
Hi Francois,
Yes that’s a good one. In my case, I was thinking about providing a developer about a nice way to set the bean properties using a property editor similar to Forms property palette, especially setting up font properties and color properties from font and color swatch selectors.