Hi David, You could stick with the "all-in-one" application and have switches for turning modules on or off. Or you could have a plug-in architecture for your modules, and there's a couple of options if you go down that path as well. I'm currently reworking the plug-in framework for one of our applications to switch from packages to plain vanilla DLLs. The key to this is that I've spec'd out an API for the interface between the DLLs and executable. Hope this helps.
Regards, Darren -- Darren Ferguson Senior Software Engineer Clinical Software Division Medtel Australia Adelaide, South Australia -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Duffy Sent: Monday, 27 March 2006 9:48 PM To: [email protected] Subject: Modular Program Hi, I'm thinking of writing a new application to use in my business that would encompass accounting, ordering, inventory, sales, etc. The last one I wrote was all one exe file but I've been thinking of something that had modules that could be added or updated or even removed at some time after the original compilation. Does anyone have any pointers on how programs like Mozilla Firefox and Thunderbird use extensions as this may be one way of achieving what I want to do. Am I on the right track even? David... _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
