EldoS Components Pack for Delphi and C++Builder.
- Installation
- Migration from ElPack 2.x
- Release notes
- Licensing and purchase
- Disclaimer
- Contact information
- Credits
First run the included executable file named "ElPack.exe" and install the pack contents to your hard drive. Then follow the instructions to install the package in your development tool (either Delphi or C++ Builder).
If you are upgrading from the previous version of ElPack, please, see the list of changes first. Due to the filenames changes, your projects might require little modifications before they can be compiled with new version of ElPack.
To install ElPack, different sets of packages for different development tools (Delphi and C++Builder) are provided.
Each set consists of 8 packages:
- elpackXY.?pk - ElPack run-time package
- dclelpXY.?pk - ElPack design-time package
- elpkdbXY.?pk - ElPack DB-aware controls run-time package (Evaluation and Registered Professional package only)
- dceldbXY.?pk - ElPack DB-aware controls design-time package (Evaluation and Registered Professional package only)
- elpproXY.?pk - ElPack Professional run-time package (Evaluation and Registered Professional package only)
- dcelppXY.?pk - ElPack Professional controls design-time package (Evaluation and Registered Professional package only)
- elmlgnXY.?pk - EldoS *ML Generator package (Registered Professional package only)
- elmltgXY.?pk - EldoS ElTree *ML Generator package (Registered Professional package only)
Where
X stands for the development tool (D - Delphi, B - C++Builder), and
Y stands for the version of the development tool (3, 4, 5, 6 for Delphi and C++Builder).
These packages are pre-built for easier installation.
By default ElPack setup builds and installs all packages and help files automatically. If automatic operation fails for any reason, you will be informed that you need to use the instructions below to install ElPack.
Supposing you have installed ElPack to the <somedir> folder, you will find all necessary files in <somedir>\Code\Source folder.
Pre-built packages are elpackD3.dpl, elpkdbD3.dpl, elpproD3.dpl (run-time packages) and dclelpD3.dpl, dceldbD3.dpl, dcelppD3.dpl (design-time packages).
- Copy or move <somedir>\Code\elpackD3.dpl, <somedir>\Code\elpkdbD3.dpl and <somedir>\Code\elpproD3.dpl into your Windows System folder.
- Choose Components\Installed Packages from Delphi IDE main menu.
- Add <somedir>\Code\dclelpD3.dpl to the list (using Add button).
- Add <somedir>\Code\dceldbD3.dpl to the list (using Add button).
- Add <somedir>\Code\dcelppD3.dpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as Delphi IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "DPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackD4.bpl, elpkdbD4.bpl, elpproD4.bpl (run-time packages) and dclelpD4.bpl, dceldbD4.bpl, dcelppD4.bpl (design-time packages).
- Copy or move <somedir>\Code\elpackD4.bpl, <somedir>\Code\elpproD4.bpl and <somedir>\Code\elpkdbD4.bpl into your Windows System folder.
- Choose Components\Installed Packages from Delphi IDE main menu.
- Add <somedir>\Code\dclelpD4.bpl to the list (using Add button).
- Add <somedir>\Code\dceldbD4.bpl to the list (using Add button).
- Add <somedir>\Code\dcelppD4.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as Delphi IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackD5.bpl, elpkdbD5.bpl, elpproD5.bpl (run-time packages) and dclelpD5.bpl, dceldbD5.bpl, dcelppD5.bpl (design-time packages).
- Copy or move <somedir>\Code\elpackD5.bpl, <somedir>\Code\elpproD5.bpl and <somedir>\Source\elpkdbD5.bpl into your Windows System folder.
- Choose Components\Installed Packages from Delphi IDE main menu.
- Add <somedir>\Code\dclelpD5.bpl to the list (using Add button).
- Add <somedir>\Code\dceldbD5.bpl to the list (using Add button).
- Add <somedir>\Code\dcelppD5.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as Delphi IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackD6.bpl, elpkdbD6.bpl, elpproD6.bpl (run-time packages) and dclelpD6.bpl, dceldbD6.bpl, dcelppD6.bpl (design-time packages).
- Copy or move <somedir>\Code\elpackD6.bpl, <somedir>\Code\elpproD6.bpl and <somedir>\Code\elpkdbD6.bpl into your Windows System folder.
- Choose Components\Installed Packages from Delphi IDE main menu.
- Add <somedir>\Code\Source\dclelpD6.bpl to the list (using Add button).
- Add <somedir>\Code\Source\dceldbD6.bpl to the list (using Add button).
- Add <somedir>\Code\Source\dcelppD6.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as Delphi IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackD6.bpl (run-time package) and dclelpD6.bpl (design-time package).
- Copy or move <somedir>\Code\elpackD6.bplinto your Windows System folder.
- Choose Components\Installed Packages from Delphi IDE main menu.
- Add <somedir>\Code\Source\dclelpD6.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as Delphi IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackB3.bpl, elpkdbB3.bpl, elpproB3.bpl (run-time packages) and dclelpB3.bpl, dceldbB3.bpl, dcelppB3.bpl (design-time packages).
If you get the message about missing *.lib file (dclstd35.lib, for example), copy <BCB folder>\Lib\dclstd35.bpi to <BCB folder>\Lib\dclstd35.lib.
- Copy or move <somedir>\Code\elpackB3.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\Source\dclelpB3.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as C++Builder IDE default library path.
- Copy or move <somedir>\Code\elpkdbB3.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dceldbB3.bpl to the list (using Add button).
- Copy or move <somedir>\Code\Source\elpproB3.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dcelppB3.bpl to the list (using Add button).
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Please see the note for C++Builder (all versions) below.
Pre-built packages are elpackB4.bpl, elpkdbB4.bpl, elpproB4.bpl (run-time packages) and dclelpB4.bpl, dceldbB4.bpl, dcelppB4.bpl (design-time packages).
If you get the message about missing *.lib file (dclstd40.lib, for example), copy <BCB folder>\Lib\dclstd40.bpi to <BCB folder>\Lib\dclstd40.lib.
- Copy or move <somedir>\Code\Source\elpackB4.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dclelpB4.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as C++Builder IDE default library path.
- Copy or move <somedir>\Code\elpkdbB4.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dceldbB4.bpl to the list (using Add button).
- Copy or move <somedir>\Code\elpproB4.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dcelppB4.bpl to the list (using Add button).
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Please see the note for C++Builder (all versions) below.
Pre-built packages are elpackB5.bpl, elpkdbB5.bpl, elpproB5.bpl (run-time packages) and dclelpB5.bpl, dceldbB5.bpl, dcelppB5.bpl (design-time packages).
If you get the message about missing *.lib file (dclstd50.lib, for example), copy <BCB folder>\Lib\dclstd50.bpi to <BCB folder>\Lib\dclstd50.lib.
- Copy or move <somedir>\Code\elpackB5.bpl, <somedir>\Code\elpproB5.bpl and <somedir>\Code\elpkdbB5.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dclelpB5.bpl to the list (using Add button).
- Add <somedir>\Code\dceldbB5.bpl to the list (using Add button).
- Add <somedir>\Code\dcelppB5.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as C++Builder IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Pre-built packages are elpackB6.bpl, elpkdbB6.bpl, elpproB6.bpl (run-time packages) and dclelpB6.bpl, dceldbB6.bpl, dcelppB6.bpl (design-time packages).
If you get the message about missing *.lib file (dclstd.lib, for example), copy <BCB folder>\Lib\dclstd.bpi to <BCB folder>\Lib\dclstd.lib.
- Copy or move <somedir>\Code\elpackB6.bpl, <somedir>\Code\elpproB6.bpl and <somedir>\Code\elpkdbB6.bpl into your Windows System folder.
- Choose Components\Installed Packages from C++Builder IDE main menu.
- Add <somedir>\Code\dclelpB6.bpl to the list (using Add button).
- Add <somedir>\Code\dceldbB6.bpl to the list (using Add button).
- Add <somedir>\Code\dcelppB6.bpl to the list (using Add button).
- Add <somedir>\Code\Source folder to the list of library folders in your project or as C++Builder IDE default library path.
If you are getting the error "Can't load package ", be sure that run-time packages are visible in the system path, i.e. they can be loaded as libraries. By default, ElPack setup copies run-time packages to the folder specified in "BPL directory" in Delphi. If this folder is not in the Path environment variable, OS will not be able to find run-time packages needed by design-time packages. In this case you will need to manually copy run-time packages to the Windows System folder.
Notes for C++Builder users:
-
If you get an error "unknown identifier: _di_IDropTarget" or something similar, it might be caused by the declaration missing from VCL. To solve the problem add the following three lines as first lines of any .cpp file of your project that refers to ElDragDrop or ElTree modules:
#include <sysdefs.h>
DECLARE_DINTERFACE_TYPE(IEnumFORMATETC)
DECLARE_DINTERFACE_TYPE(IDropSource)
C++Builder developers simply forgot to declare these two interfaces in VCL source code.
-
Unfortunately, Delphi compiler in C++Builder is unable to produce the libraries (elpackBY.lib, elpkdbBY.lib, elpproBY.lib) required to link the application with evaluation version of ElPack. To create those files you need to open the appropriate .BPK file and compile it. If all paths are set correctly, the package will be rebuilt and you will get .LIB files.
Help files installation is described below.
To install ElPack, different sets of packages for different development tools (Delphi and C++Builder) are provided.
Each set consists of 8 packages:
- elpackXY.?pk - ElPack run-time package
- dclelpXY.?pk - ElPack design-time package
- elpkdbXY.?pk - ElPack DB-aware controls run-time package (Professional package only, VCL only)
- dceldbXY.?pk - ElPack DB-aware controls design-time package (Professional package only, VCL only)
- elpproXY.?pk - ElPack Professional run-time package (Professional package only, VCL only)
- dcelppXY.?pk - ElPack Professional controls design-time package (Professional package only, VCL only)
- elmlgnXY.?pk - EldoS *ML Generator package (Professional package only, VCL only)
- elmltgXY.?pk - EldoS ElTree *ML Generator package (Professional package only, VCL only)
Where
X stands for the development tool (D - Delphi, B - C++Builder, C - Delpi/CLX), and
Y stands for the version of the development tool (3, 4, 5, 6 for Delphi and C++Builder).
Pre-built packages and units are not included to reduce distribution size. During installation ElPack Setup attempts to build and install all packages except packages for C++Builder 3 and C++Builder 4 automatically. If Setup fails or you need packages for C++Builder 3 and C++Builder 4, you will need to build the packages manually.
- Tune-up global paths in your development tool.
You have to set
- the output paths to the folder, where the packages are located. Usually you will need to add two folders to the path -- one folder with run-time packages, and one folder with design-time packages.
- source path (or include and library paths for C++Builder) to the folder, where code files are located. Usually you will need to add two folders to the path -- one folder with run-time code, and one folder with design-time code).
Paths are set in Menu->Tools->Environment options. Environment Options dialog appears. Find Library or Directories tab in the page control and you will find paths configuration page.
If you installed ElPack to c:\eldos\elpack, then source paths will be c:\eldos\elpack\code\source and c:\eldos\elpack\code\design. You select output path yourself, but usually this is the path that is set as DPL/BPL output directory.
- (C++Builder 3 only). Go to the LIB subfolder of the C++Builder 3 base folder.
There dclstd35.lib file might exist. If it doesn't exist, copy the file named dclstd35.bpi to the dclstd35.lib. This is need to compile projects that will use ElPack, and sometimes needed even to make ElPack packages.
(C++Builder 4 only). Go to the LIB subfolder of the C++Builder 4 base folder. There can dclstd40.lib file exist. If it doesn't exist, copy the file named dclstd40.bpi to the dclstd40.lib. This is need to compile projects that will use ElPack, and sometimes needed even to make ElPack packages.
- Open elpackXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Compile the opened package (press Compile Package button in Delphi or Make in C++Builder).
- Copy the compiled package (elpackXY.?pl) to your Windows system folder.
- Open dclelpXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Install the opened package. In Delphi you will need just to press Install Package button. In C++Builder you have to "Make" the package first, then select Component\Installed packages and add the package you've just compiled, to the list of loaded packages.
- (Professional package only) Open elpkdbXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Compile the opened package (press Compile Package button in Delphi or Make in C++Builder).
- Copy the compiled package (elpkdbXY.?pl) to your Windows system folder.
- (Professional package only) Open dceldbXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Install the opened package. In Delphi you will need just to press Install Package button. In C++Builder you have to "Make" the package first, then select Component\Installed packages and add the package you've just compiled, to the list of loaded packages.
- (Professional package only) Open elpproXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Compile the opened package (press Compile Package button in Delphi or Make in C++Builder).
- Copy the compiled package (elpkdbXY.?pl) to your Windows system folder.
- (Professional package only) Open dcelppXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Install the opened package. In Delphi you will need just to press Install Package button. In C++Builder you have to "Make" the package first, then select Component\Installed packages and add the package you've just compiled, to the list of loaded packages.
- (Professional package only) Open elmlgnXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Install the opened package. In Delphi you will need just to press Install Package button. In C++Builder you have to "Make" the package first, then select Component\Installed packages and add the package you've just compiled, to the list of loaded packages.
- (Professional package only) Open elmltgXY.?pk package (see the explanation above to find out the right name).
- Repeat step 1 for the package private paths. To set the package's paths, use Options button in Delphi and Project\Properties menu for C++Builder.
- Install the opened package. In Delphi you will need just to press Install Package button. In C++Builder you have to "Make" the package first, then select Component\Installed packages and add the package you've just compiled, to the list of loaded packages.
- (C++Builder only, all versions)
If you get the message about missing *.lib file (pkg_name.lib, for example), copy <BCB folder>\Lib\pkg_name.bpi to <BCB folder>\Lib\pkg_name.lib.
If you get an error "unknown identifier: _di_IDropTarget" or something similar, it might be caused by the declaration missing from VCL. To solve the problem add the following three lines as first lines of any .cpp file of your project that refers to ElDragDrop or ElTree modules:
#include <sysdefs.h>
DECLARE_DINTERFACE_TYPE(IEnumFORMATETC)
DECLARE_DINTERFACE_TYPE(IDropSource)
C++Builder developers simply forgot to declare these two interfaces in VCL source code.
Since ElPack 3.10 help files are available as a separate package and are not included into code installation. You can get the help files from the site
Help files are integrated to Delphi or C++Builder help system during ElPack Help Files installation (ElPack Help Files is what you download from the above link). If you need to re-install your development tool, you will have to add ElPack help files to help system manually. To do this
- Delphi 3:
- Delphi 4:
- Delphi 5:
- Delphi 6 (both VCL and CLX):
- C++Builder 3:
- C++Builder 4:
- C++Builder 5:
- C++Builder 6:
Several important changes have happened in ElPack 3.0 comparing to ElPack 2.80. First of all, ElDice component have been removed.
Then, TElColorCombo component has been completely rewritten. Due to this fact you will given an error message when trying to open forms that contain ElColorCombo. When you are notified that some property is missing from the combo box control, press "Ignore" button.
Some properties of different components (TElCheckBox, TElRadioButton, TElTree, TElPopupButton, TElGraphicButton and others) have been removed or renamed. So when you open the forms that contain these components, you will be notified that the property is missng and asked what to do (Ignore, Cancel, Ignore All). Choose Ignore or Ignore All.
TElFlat* components have been renamed to TElAdvanced*. To solve the problem with existing forms you need to use ElpConvert utility. The utility is installed to Tools folder. Use this utility as follows - start the application with the given parameters in every folder where your project files are located.
elpconvert *.dfm
elpconvert *.pas
What this tool does is open dfm and pas files and replace every occurence of "TElFlatListBox", "TElFlatComboBox", "TElFlatMemo" and "TElFlatEdit" to their "TElAdvanced" analogues.
By default most visual components operate with Unicode strings. This might lead to problems while compiling some old projects that use event handlers with string parameters. You will need to manually change declarations of those event handlers. To turn off Unicode change {$DEFINE ELPACK_UNICODE} in ElPack.inc to {.$DEFINE ELPACK_UNICODE}.
ElTree 3.0 contains completely new, ultimately flexible and powerful inplace editing scheme. Of course, this scheme is completely incompatible with previous inplace editing. If you want to stay with old editing scheme, change {$DEFINE VER3_EDITORS} in ElPack.inc to {.$DEFINE VER3_EDITORS}.
No release notes for now.
Licensing terms are described in license.txt.
ElPack is available in different packages and under different licenses.
To compare package contents please see packages.html.
To order some package please use order.html
IN NO EVENT SHALL ELPACK LIBRARY AUTHORS, OR ANY OTHER PARTY WHO MAY HAVE DISTRIBUTED THE SOFTWARE AS PERMITTED, BE LIABLE FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER PRODUCTS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
ElPack is the product of EldoS.
The official ElPack homepage is http://www.eldos.org/elpack/elpack.html
You can send bug-reports and suggestions by e-mail to the authors to elpack@eldos.org
Special thanks to Akzhan Abdulin (http://www.akzhan.midi.ru/devcorner/), who initiated XP themes support and made lots of improvements to existing components.
Some components were made by Alex Shovkoplyas for his Net Vampire Download manager project at http://www.netvampire.com.
(c) Copyright, 1998-2002 EldoS