Re: TActionList and datamodules
- From: Andrea Raimondi <rainaple@xxxxxx>
- Date: Sat, 30 Apr 2005 00:41:04 +0200
David Farrell-Garcia wrote:
Not at all. Your TAction can simiply call a public method on your data module. For even better separation you can move your business logic to a 3rd layer and just do your data layer on he datamodule. But either way you can keep the real logic away from your prensentation layer.
Mmmmh... looks like my target is blurry :-)
Ok, let's see if I can explain better what I'm thinking of.
I usually have this kind of structure for database applications:
1) GUI 2) Logical datamodules 3) Database datamodule 4) Reporting
This means that each section has its own module set. This makes things much easier when it comes to mantain the applications.
Now, you're suggesting that part of what composes the logical datamodules be placed on the GUI, from my point of view - and that
breaks the separation imho.
Cheers,
Andrew .
- References:
- TActionList and datamodules
- From: Andrea Raimondi
- Re: TActionList and datamodules
- From: David Farrell-Garcia
- TActionList and datamodules
- Prev by Date: Re: Windows 32 with VMWare 64bits
- Next by Date: Re: Wanted: 64bit Delphi
- Previous by thread: Re: TActionList and datamodules
- Next by thread: Windows 32 with VMWare 64bits
- Index(es):
Relevant Pages
|