× 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.



Just a few ideas I think would make the LPEX editor in WDSC 5 even better.

1)  Service Pack 1 finally makes the editor do a good job with CL source. 
One thing I always hated about SEU, that LPEX makes even worse, is the way 
it formats commands that were prompted.  LPEX makes it worse because it 
does this to all source you edit, even if you do not prompt it.  I would 
like to see this automatic "style" configurable.  Ideally there would be 
some pre-determined choices, such as the style proposed by News/400 many 
years ago.

By the way, I believe you can turn off that "automatic formatting" but on 
releases prior to SP1 this had some negative side effects, such as letting 
source go way past the boundaries.  I have not tried it again with SP1.  I 
still think the automatic formatting could be controllable in terms of 
style.

2)  Templates.  Could support for small templates like what the Java 
editor provides be provided?  This could be a really cool feature, 
especially if it could work half as nice as it does in the Java editor.

3)  Intelligent RPG prompt.  Flex/EDIT added this years and years ago.  I 
do not know why IBM has never adopted it.  There is a very small and 
finite number of op-codes.  Why can't the prompter adapt itself to the 
current opcode?  In other words, if Factor 2 is not valid do not show it. 
If I am doing a CHAIN, only show the valid indicators, and put intelligent 
text like ERR or FND above them.

Thanks.

Mark





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.