|
>> I wished creating a plugin was similar to creating an lpexlet in CODE/400. I just wish it was as simple as doing it in CODE in Rexx!! I just went through Ian's article in iSeries mag on programming the jlpex editor. It took five source members and hundreds of lines of code to do what Rexx does in about 10 lines of code - including the dialog box! While I love the idea of being able to extend the editor, I _know_ I will do it far less often because all of the "this will be useful today" type programs that I can do with Rexx just aren't worth the effort of jumping through all the hoops. Unless I know that it represents a frequent use function, I am not going to go to the bother. I am trying very hard not to be a luddite, but I confess I do get ticked off when perfectly good functionality is removed in the name of progress - and the "progress" takes ten times longer to do anything! Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
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.