RE: RE: RE: Context Menu

> From: Alberto Amigoni
> 
> You don't need to change the JSP every time, joe.
> 
> In the last post i talk about capturing the clik or dblclick event and
> recognize the field that generate it, and this code
> does'nt need to be embedded in each JSP, using DHTML from
ClientScrpit/usr
>  you can add functionality "dynamically",
> on the client side, and the javascript library are downloaded only one
> time...

This only works if the field name stays the same on every page and you
are going to do the same thing on the field every time.  This is a very
bad assumption.


> Think at Date, or Numeric, or Currency.. but even think at hyperlink
from
> Customer fields (can we assume that all CDCUST or CUSTID fields are
> customers ?)...

NO!  You can NOT make that sort of assumption! CDCUST might be a
customer, but it might be "Washington DC, US Treasury".  Customer fields
might also include CUST1, CUST2, and CUST3, and CUSTOMER1, and CUS1.
Not only that, but I might want to do something different with a
customer on one screen than on another.  Dates especially might be in
different formats on different screens!

Sure, you can make some assumptions about your screens, but the vast
majority of systems do not have screens that follow standards throughout
their application.  And every exception must be manually coded every
time.  (Not to mention you have to be pretty good at JavaScript.)

With PSC/400, you define a simple database record: Program, field,
event, action.  From that point on, every conversion of that program
will add the appropriate code.

Joe