|
|
|
|
|
|
| Re: Filter into transaction screen [message #1716 is a reply to message #1715] |
Thu, 25 September 2008 19:34   |
AJM
Messages: 2367
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
I'm afraid so. The reason that I have separate search screens is historic. Many years ago in a different language I had space for search criteria at the top of a LIST1 screen, as shown in http://www.tonymarston.net/uniface/componenttemplates.html#l ist1, but then my users wanted the ability to have more selection criteria. When it began to use more and more space at the top of the list screen, which was dead space when it wasn't being used, they asked for the search criteria to be moved to a separate screen which then freed up the space on the list screen.
Having search criteria in its own screen is far more flexible, and having search criteria in two places is redundant.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
|
|
| Re: Filter into transaction screen [message #1718 is a reply to message #1717] |
Fri, 26 September 2008 13:27 |
AJM
Messages: 2367
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
No documentation should be necessary as a transaction pattern consists of only three things:
(1) A page controller which communicates with one or more objects then passes the result to an XSL stylesheet.
(2) An XSL stylesheet which contains the various zones which are to be filled in at runtime.
(3) A screen structure file which identifies which data goes in what zone.
Rather than make a brand new pattern would it not be easier to modify the existing LIST1 pattern to optionally show a search area at the top of the screen? This would enable the search area to be turned on or off at will without having to switch patterns.
The only limitations I would put on the search area are:
(1) It can ony be one line deep.
(2) It can only contain columns which appear in the columnar display.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
|
|
| Re: Filter into transaction screen [message #1720 is a reply to message #1719] |
Fri, 26 September 2008 14:09 |
AJM
Messages: 2367
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
If you look in the XSL stylesheet for the LIST1 pattern you will see that both the 'select' and 'show' areas in the navigation button area are optional. Also, the navigation area will not show any buttons if none have been supplied in the XML document. The 'message' and 'error' zones will also be ignored if there is nothing in the XML document.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
