Re: Forms 5.0 Standards!!!

After developing quite a number of forms over the last year, this is where I tend to put code and why:

1. Library. If the code is likely to be used by a whole bunch of forms, I always put it into a library (*.pll). This allows me to reuse it and not have to reinvent the wheel for every form.
2. Named form-level trigger. This is a great place to put code because it is the only way to have code in the form kicked off from a menu. Nearly all of the menu items call a form-level named trigger.
3. Form-level procedures/functions/packages. Usually this type of thing is taken care of by step #1... but there are usually 1-2 that I can't fit in there (ie too form-specific).
4. last, I put a small amt. of code into the actual item triggers on the form (ie when_button_pressed, etc.).

I've found that code reuse is very high using this method, and it's easier to debug.

-jay

In article <77gges$6b4$1_at_nnrp1.dejanews.com>,   plprasad_at_my-dejanews.com wrote:
> Hello,
>
> I am involved in a process of setting standards for developers
> in forms 5.0. One of my collegue says it is better to have a
> package at "form level" and have all the trigger code as
> procedures and functions in that package and call them from
> the triggers.
>
> I personally felt this is not the best way, but I need some
> good reasons to support my choice. First of all I would like
> to know
>
> 1. Is it good to have forms package and have all the procedures
> in it and call them from triggers.
>
> 2. Are there any advantages of writing trigger text at the
> trigger level instead of having the forms Packages.
>
> Please give pros and cons in both the cases.
>
> Thanks in Advance,
> Prasad
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Wed Jan 13 1999 - 18:57:00 CET