Cheers Jason, I might try this approach of ONE bpl with the others like 
VCL and RTL etc. in it.
I DID however just save having to include the 3.5mb TMS components pack 
which was good. Wanted one component SO I just created a new component 
from their source, and it gets included in the add-ins dpk file, but if I 
am going to use one BPL, then I can put it there.

Alos, when you say "compressed" is this via the UPX tool or just the 
winzip compression ?

Jeremy

-----Original Message-----
From: "Jason Coley" <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Tue, 3 Jun 2003 10:30:38 +1200
Subject: RE: [DUG]:  Modulizing Apps. with Packages

> I have been using a bpl approach on my latest version of my addins, it
> seem to be working well, I have a Delphi bpl, basically a package that
> I
> have created which includes all of the Delphi units and third party
> units which do not get updated frequently. A have another package which
> I use for shared forms, frames and code and also some third party
> components which do tend to be updated frequently. Then my main dlls, (
> I write Office adidns) which use the packages, I also have a web update
> component that uses the packages as well, so my main dlls are around
> 500
> k, my update exe which is about 100k and the packages.
> 
>  
> 
> Using this approach the Delphi package, which would rarely change, is
> about 2.1 Mb, (877kb compressed), the shared package 2Mb (688kb
> compressed) and main dlls around 500kb (100kb compressed). So the web
> update works quick and easy, the files are tiny to update, and seems to
> work really well. The trick with packages I found was that if a major
> change is made to a package then anything that uses that package must
> also be recompiled and checked to ensure it can find the new entry
> points etc, but that's just normal I guess.
> 
>  
> 
> It is great to be able to reuse the code as easily as you can with
> packages.
> 
>  
> 
> Regards
> 
>  
> 
> Jason Coley
> 
> Manawatu Software Solutions
> 
> email: [EMAIL PROTECTED]
> 
> web: http://www.software-solutions.co.nz
> 
>  
> 
>  
> 
>  
> 
> -----Original Message-----
> From: Jeremy Coulter [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 2 June 2003 5:03 p.m.
> To: Multiple recipients of list delphi
> Subject: [DUG]: Modulizing Apps. with Packages
> 
>  
> 
> Hi all. Yeah I know, its sad to be having a day off, but still thinking
> about work :-)
> 
>  
> 
> Anyway, I have finally got a project where I will or want to use
> packages to modulize the app.
> 
> I have already developed the first part based on an article in the
> Delphi Informant Mag.
> 
> The only thing I am kinda confused about is, to get the app. that looks
> for and loads the packages at runtime, I have to set the "Compile with
> Runtime Support", or whatever its called, switch in the project
> settings.
> 
> This means that I need to now supply the 6mb VCL packages and what ever
> else I use, like ADO, etc.
> 
> This is not going to be any good for this project as it has to go to
> over 100 places.
> 
>  
> 
> SO, can I do the above slightly differently so I can just distribute
> the
> EXE without have to also send out the runtime BPL's too?
> 
> Or am I better to use some 3rd party plugin tool?
> 
>  
> 
> Cheers,
> 
>  
> 
> Jeremy Coulter
> 
>  
> 
>  
> 
> -----------------------------------------------------------------------
> -
> 
> All email scanned with Nortons Antivurus 2002
> 
> -----------------------------------------------------------------------
> -
> 
>  
> 
> 

---------------------------------------------------------------------------
    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/

Reply via email to