I need to rebuild a product currently developed with Oracle Forms in 15 modules, many of which are master-detail(-detail).

What is the best strategy?

a) Create one application for each Form module and use the mechanism Tutorial 29 to share the web session across multiple applications.

b) Create one very large application with all forms together, using the menu-bar (Tutorial 23) for navigation. How do other customers do this?

asked 26 Sep '14, 05:36

Jan%20Willem%20Vermeer's gravatar image

Jan Willem V...
accept rate: 0%

Hi Jan,

I don't really have much to add to Michiel's comment. I just want to underline that the performance of a Formspider application is not dependent on its size. This is by design. Formspider streams screens to the client. The user only consumes resources for the screens that he accesses. So a user might be using a 10000 screen app. If he accesses only 10 screens than this is not different than using a 10 screen app.

This helps Formspider developers worry about one less thing while building applications.

Kind Regards,


answered 29 Sep '14, 03:04

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
accept rate: 15%

Hi Jan-Willem,

I would strongly recommmend using option b. It will make things much easier when it comes to re-using datasources, LOV's end so on. In my experience in building a pretty large formspider application, the speed of the final application and the speed of development in the Forspider IDE do not get worse working with or running a large Formspider app.

Have fun buidling your app!

Best regars, Michiel A.


answered 28 Sep '14, 05:26

Michiel%20A's gravatar image

Michiel A
accept rate: 13%

Hi Yalim,

When i develop 1 application with many Datasources, Windows, Panels and Actions, there will be very long lists of objects in the left navigator of the IDE. That worries me. I pressume it would be wise to think about namegiving standards, so it is easy to find them back.

I expect to need the api_frame.addpanel and removepanel a lot and these procedures needs the name of the frame, cell and panel. First i thought the architecture was frames with panels, but during my tests i discovered that in fact the architecture is that 1) there is a FRAME, 2) on that frame there are CELLS and 3) PANELS can be put in any cell. The namegiving standards will (hopefully) prevent a complete chaos of frames, cells and panels.

Did you already develop such standards? Do you have screenshots of examples of applications with (for example) 10 windows, 20 panels or so?

Kind regards, Jan Willem


answered 29 Sep '14, 03:28

Jan%20Willem%20Vermeer's gravatar image

Jan Willem V...
accept rate: 0%

Hi Jan,

Many developers worry about this before they start working with Formspider. I don't know of anyone who worries about this after working with Formspider.

Using a naming convention will certainly help although it is not a prerequisite. What we do is to use a two three letter prefix in front of panels, indicating which logical module they belong to. For example, in the Formspider IDE (which is a Formspider application itself) panels (and other objects) related to version control are prefixed with SC (source control which was the original name for version control). We use the prefix in the search bars for UI objects. So if we want to work on SC we type the search bars SC%.

In Formspider, there is a very easy way to find the name of the UI Object you want to work on. Say there is a problem in a certain screen in the application but you have no idea which panels this screen uses. Simply run your application in debug mode, open that screen, press shift and ctrl buttons and hover your mouse over the components that you want to work on. The debugger window will display the names of these objects including the panel name they are on. So finding which part of the application you want to work on is really simple.

One more thing. I would NOT use the type of the object in the name of the object. In other words, I would never name panels deptPanel, empPanel empSearchPanel etc... ditto for actions, alerts etc...This gets old very quickly. The type of the object is very easy to infer from the context it is being used.


answered 29 Sep '14, 04:05

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
accept rate: 15%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 26 Sep '14, 05:36

Seen: 1,619 times

Last updated: 29 Sep '14, 04:05

© Copyright Gerger 2017