How
much time do you have and how big is your budget ...?
The
article/series is a reasonable starting point, it is a case of horses for
courses (how big is your app - the documented one would be suitable
for small applications, and maybe medium size ones IMO)? It does not talk
about transactions at all (eg across objects)
There
is quite a bit of info available, but most is in books. I suggest you do a lot
of reading before attempting anything.
The
EJB spec is another example for Business Objects (this has some interesting
features and does cover transactions in detail).- Smalltalk is
regarded as the most mature OO language and there is a lot of info in this
arena.
Have a
read of the Design Patterns book by Gamma et al, etc
Almost
any framework is better than none, as it can be manipulated and extended
overtime.
Personally I favour a OO framework, and I like several (most) aspects of
the EJB/Java application server concept.
Beware
that for a single project a OO framework could easily consume 40%-60% of
the budget/time of the project, so reuse really does become a necessity in
most cases.
Myles.
-----Original Message-----
From: James Low [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 9 August 2001 11:13 a.m.
To: Multiple recipients of list delphi
Subject: [DUG]: Business Objects/ Best Delphi PractiseDoes anyone have a reference to, or pearls of wisdom on best practise for Delphi Business app design. For example, how to best separate UI/DB and Business Logic (Datamodules vs Db access classes (see the link)) and smart approaches to building class hierarchies that promote code re-use and easy scaling/ modification.Maybe you have some guidelines you follow/ or a set of standards/ reference book that might enlighten me. Seems to be little on the net.FYI, here is an article that got me thinking: http://www.howtodothings.com/showarticle.asp?article=157TIA
