Tiny update of the LAF project. This 22.214.171.124 version sligtly improves the Image Spinner feature by consuming less memory. a new IMAGE_SPINNER_SET_KEEP_SIZE method
can be used not to keep the original image size if you don't intend to save them later in the database.
Even though this component has be created to behave like an image carousel, it is not designed to handle hundreds of images and/or megabytes. If you intend to load it with a large amount of
images, think to increase the JRE memory by updating your launching HTML file (probably the /forms/server/basejpi.htm):
You can display multiple images in the same component like a carousel, add images to the spinner from the client machine (JAR or file system), the Internet, and the
database. You can also populate it by Drag&Dropping files from you file system, then save the new loaded images to the database.
I receive sometimes requests by users that are interested by some features of the Forms Look and Feel tool, but don't want to install the whole stuff : .pll,
.css, database packages, ...
Even though you need the PLL and the CSS to easilly paint the canvases and the blocks, this is not absolutly required. The PLL itself uses the methods stored in the laf_xxx JAR file.
100% of the Java Bean's methods can be used without the PLL.
So, if you need some features of the LAF like Pushbuttons, fun buttons, carousel, Text Items with HTML or CLOB content, ... just put the laf_xxx jar in your /forms/java folder, add it to your
archive tags, and that's all. Use the methods directly via the Set_Custom_Property() Forms built-in.
The DrawLAF Java Bean can, now, start external commands, then get the result back.
It allows the developer to start external commands, then after get the result or the error.
A new method has been added to the DrawLAF Java Bean : SET_EXT_PROG.
Result text or error message is transmitted to the bean through new Custom Item Event added to the DrawLAF When-Custom-Item-Event trigger.
The event name is EXT_MSGSTND for a correct result or EXT_MSGERROR for an error message. The text itself is transmitted line by line and asynchronously via the EXT_MSGTEXT event.
I have just updated the good old
Multirecord PJC. It can, now, handle buttons. The only standard way to personalize an object in a multi-record table block is to use the Set_Item_Instance_Property()
Unfortunately, the list of properties you can alter is very limited, reason why I created the multi-record PJC.
The properties you can set
to the multi-record button are:
- background color
- foreground color
- icon - enable - visible
A few months ago, I delivered the Forms Magnifier tool, capable of adjusting the Forms elements size and location at runtime, whatever the
screen size is. This tool allows the application to fit any screen resolution in an heterogeneous PC pool.
Today, I deliver its little brother called Forms Resizer. This one is “lighter” in a way that there is no Java Bean nor PL/SQL library added to the application. It
just takes a source (.FMB) file in entry, then generate another one with every object size and location adjusted to a new given resolution. At the same time, you can also set the properties of
the main Forms objects in a one shot.
So Forms Magnifier addresses the problem : "In our company, we have PCs with different screen size and we want the Forms Application to use the maximum
resolution size for each of them" while Forms Resizer addresses another problem : "we have designed a Forms Application for 800x600 screen resolution, and we want to have it, now, for a
1024x800 new resolution, and we also want to take benefit of the conversion to change many Forms properties in my modules".
If you get at least, one of these problems, have a try of the trial versions that come along.