× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Re[2]: "extract" command enhancement (subfiles and BIFs)
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Wed, 22 Sep 1999 10:18:19 -0700

You've put it very well. My pet peeve about display files, just not
subfiles, is the magic (key) words necessary to program displays and the
indicators that make code hard to maintain unless you document it in a very
disciplined way.  Consider a flat screen with a bunch of input capable
fields where you have to do programmatic error checking. If you want to
position the cursor to the errors, you can use up a lot of indicators real
fast.

If you try to build screens that make a business task easy to do, I think
you often find that you need to do some things that are unique to the
particular situation.  Particularly if the end users have a voice in the
design process. <g>
 

> -----Original Message-----
> From: pcunnane@learningco.com [mailto:pcunnane@learningco.com]
> Sent: Wednesday, September 22, 1999 6:46 AM
> To: RPG400-L
> Subject: Re[2]: "extract" command enhancement (subfiles and BIFs)
> 
> 
>      John,
>      
>      My own personal problem with subfiles is how difficult 
> it is to code 
>      one that encapsulates all the nice list functionality.  
> For example, 
>      if you want "Position to:" functionality, you need 
> SFLPAG=SFLSIZ.  If 
>      you want to be able to select multiple records on 
> different pages, and 
>      page back and forth at will without losing these selections, you 
>      either code SFLSIZ>SFLPAG, or handle it manually.  And 
> don't get me 
>      started on reliably positioning the list, and 
> positioning the cursor 
>      in the list.
>      
>      I agree with you that it is cheapest to code the same 
> subfile code 
>      every time, but my experience is that this doesn't 
> always provide an 
>      optimal solution to the business problem.  It may be 
> just a personal 
>      quirk, but I think that the look-and-feel of a program 
> is important - 
>      especially if (as in my last job) the programs were for sale.
>      
>      I've said it before - if UIM were easier to code, it would have 
>      answered a lot of my prayers.  It handles all the boring 
> stuff like 
>      actually displaying the data and managing user input, 
> leaving the 
>      business logic to the programmer.
>      
>      As to KISS, I wholeheartedly agree, but not at the expense of 
>      functionality.
>      
>      ____________
>      Paul Cunnane
>      The Learning Company
> 
> 
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.