Re: RPG Productivity Versus Other Approaches

And in reality, Rory, the majority of the work for a typical WRKxxx is in two places:

1. Placing the fields on the display
2. Coding the application-specific business logic, typically advanced edits

If you're happy with how a code generator places the fields (which is usually the case with simple maintenance panels) then you really only need to concentrate on the edits.

On the other hand, most generated code on the i that I know of doesn't follow MVC, meaning that the maintenance program usually has both the editing code and the display file logic in the same program. From a generator standpoint, what's really needed is the ability to generate a standalone CRUD server. Then the CRUD server could be used by green screen programs, thin browser clients, web services, rich clients, portals, you name it. Even better if the generator could generate first passes of those as well.

Joe

Paul,

If you're using a tool like Synon, about 30 seconds. Otherwise, if you can cut 'n'
paste from some template code, maybe a couple of hours.

Rory (who is heavily biased in favor of tools like Synon)


From:"Paul Holm" <pholm@xxxxxxxxxxxxxxxxx>

We are working on a white paper which will compare RPG programming productivity flexibility with other approaches for i5 application development. I would be interested in feedback/insight on the following.


The #1 most used and needed programming task is development of a ?WORK WITH? screen. This typically in RPG is a subfile with a position to type prompt. You typically can input a search parameter(s) and get a list of records to work with. They are used everywhere and examples include: work with orders, work with products, work with employees, work with customers, etc.

Once you have a list of records then #2 most required task is file maintenance. (Edit, insert, delete one of the records in your list. )


Roughly how long does it take in RPG to create a new ?WORK WITH? and Data maintenance application from your experience?

Thanks, Paul Holm