|
Blake said: The most important thing is to write modular code as is
stressed over and
over again by people on this list. Separate concerns by breaking your data
access logic and business rules into RPG service programs or what have
you. If architected properly, you can then re-use that logic any number of
ways, whether it be for a 5250, browser or fat-client application. I'm not
saying anything a lot of people on this list don't already know (and
better than myself), but maybe it will provide a starting point.
___________________________________________________________
In the end you summed it up right on the money. We all have had
different experiences with successes and failures of the various
technologies. For those that DO plan on testing the waters with
non-IBMi technologies, then the best insurance policy is to build for
the "just in case it doesn't work out" scenarios, and that is building
modular and building for change in the landscape.
I would put money on Google coming out with their own UI technology in
the next couple years that will put the others to shame (i.e.
Silverlight, Flex/Flash, JavaFX, etc). Google has the advantage of
watching on the side lines the current fiascos going on and the
advantage of a ginormous check book to write checks with when the time
is right. Look how short of a time it took them to become a contender
in the mobile phone OS market? Two, maybe three years?
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
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.