On 12/2/06, Dean Zobec <[EMAIL PROTECTED]> wrote:
see with an accounting program is the fact that at lower level it has to couple with different laws and forms of taxation, so the greatest work is to build a flexible system that can be easily adopted to the single
This is where a good dose of design patterns come into play. I better dust of my Gang-of-Four book. Oh and for those interested, try the "Head First Design Patterns" book. Very different style, but excellent.
You are right however, oop is the way to go and build a strong framework of business classes, combined with an OPF and a good solution to link the business classes to the UI. I've seen a lot of bad code written in Delphi, no tests and validations that were mixed directly with the UI code, completely unmaintainable.
Yeah, I once had to maintain the Capacity Planning section of that UK accounting package. It has been through the hands of quite a few developers over the years and each developer seems to have decided to apply their own style of coding. I was quite surprised to find a section actually using OOP and it was a breeze to extend compared to the rest of the system. -- Graeme Geldenhuys Location: S 34° 03.168' E018° 49.342' http://tinyurl.com/y6lc26 There's no place like 127.0.0.1 _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
