I tried doing this a few years ago. I don't think that much has changed since then unless you are using .net.
IMHO packages are a better solution as you can pass objects between modules. Doing this with dll's is rather difficult, but you could probably get around it by using interfaces. There are several free and commercial toolkits. Remobjects.com have hydra, tmssoftware.com has one, and there is a free framework in the jvcl. All of these will allow loading of packages at runtime etc. Regards Sean ----------------------------- Sean Cross Systems Development CRM PO Box 230 Napier Phone: 06 835 5868 Mobile: 027 276 6439 Email: [EMAIL PROTECTED] Disclaimer: "The information contained in this document is confidential to the addressee(s) and may be legally privileged. Any view or opinions expressed are those of the author and may not be those of CRM. No guarantee or representation is made that this communication is free of errors, viruses or interference. If you have received this e-mail message in error please delete it and notify me. Thank you." > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, 29 March 2006 12:54 a.m. > To: Borland's Delphi Discussion List > Subject: Re: Modular Program > > Most serious Delphi manuals give info on DLL programming even > old ones (D4 or D5) should do; you need to figure out how to > launch a DLL from a calling .exe in the Delphi IDE (for > debugging), then its fairly similar to ordinary .exe development; > > ----- Original Message ----- > From: "David Duffy" <[EMAIL PROTECTED]> > To: "Borland's Delphi Discussion List" <[email protected]> > Sent: Tuesday, March 28, 2006 1:28 PM > Subject: Re: Modular Program > > > > Ralph D. Wilson II wrote: > > > David, > > > > > > IMHO, you need to check out DLL's. I have used them in > the past to > provide > > > both extensibility and improved (i.e. easier) > maintenance. You can > specify > > > the DLL extension (e.g. I usually use ".twg" for mine ;-) so that > > > your > main > > > form can locate and load any and all of the DLL's associated with > > > your app. (For an app that is composed of various > > > "subapplications", I > usually > > > have a small MainMenu form that identifies any available ".twg" > > > DLL's > and > > > queries them for their menu names, images, etc., and adds that > information > > > to the menu and task bar . . . as you create them and get them > > > working, they automatically appear in the menu.) > > > > Thanks Ralph. (and others) It looks like DLL's are the way to go. > > I just tried a simple example I found on the web but that didn't > > include a forms in the DLL. Still have to figure how to do that bit. > > I assume you can only run and debug the DLL by running the main > > application that calls it? Just getting my head around it all. :-) > > David... > > > > -- > > ___________________________________________ > > David Duffy Audio Visual Devices P/L > > Unit 8, 10 Hook St, Capalaba 4157 Australia > > Ph: +61 7 38235717 Fax: +61 7 38234717 > > New Web: www.audiovisualdevices.com.au > > ___________________________________________ > > > > _______________________________________________ > > Delphi mailing list -> [email protected] > > http://www.elists.org/mailman/listinfo/delphi > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.1.385 / Virus Database: 268.3.1/292 - Release Date: > > 24/03/2006 > > > > _______________________________________________ > Delphi mailing list -> [email protected] > http://www.elists.org/mailman/listinfo/delphi > > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
