I would create 3 packages, a runtime only package for the common units, another runtime only package for the components and a design-time only package for the property editor stuff.
----- Original Message ----- From: Donovan J. Edye To: Multiple recipients of list delphi Sent: Wednesday, February 12, 2003 3:19 PM Subject: [DUG]: [Q] "Library Units" --> Run Time Package? G'Day, We have some common units for things like string handling etc. At present these are just seperate units in the file system. We also have our own components package which has runtime and design time flags set which uses these units. The unfortunate side effect is that if someone creates a new package that uses one of these common units then our main package is required. So to avoid this I was considering placing all our common units into a package that is a run-time package. Is this the best solution or is there another way? -- Donovan ---------------------------------------------------------------------- Donovan J. Edye [www.edye.wattle.id.au] Namadgi Systems [www.namsys.com.au] Voice: +61 2 6285-3460 Fax: +61 2 6285-3459 TVisualBasic = Class(None); Heard just before the 'Big Bang': "...Uh Oh...." ---------------------------------------------------------------------- GXExplorer [http://www.gxexplorer.org] Freeware Windows Explorer replacement. Also includes freeware delphi windows explorer components. ---------------------------------------------------------------------- --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
