The image below is a real screenshot of the latest Turbo Delphi Explorer, the free “limited” version of Turbo Delphi Professional. No any kind of image manipulations is occured. Yes, installing custom components on Turbo Delphi Explorer is very possible, and IMHO it is also legal (speaking of law). 🙂
After I found that Turbo Delphi can be installed without any dependencies to .Net framework libraries here (since Turbo Delphi actually is BDS 2006 with single personality), I also found that the custom or third party component installation limitation is not truly true! Borland should have said “can’t add additional packages” instead of “components”. 🙂
No, there’s no illegal action requires to overcome this limitation. No cracking, no hacking, I even didn’t change any single bit of the original files. I suspicious that DevCo actually provided this trick intentionally and let us found it. It’s very hard to believe that they forgot to disable this trick.
To have your third-party or custom component installed, is very simple and straight-forward. All you need to do is these 3 steps…
- Declare your component within dclusr.dpk (within /lib folder of your Turbo Delphi installation) which is a Delphi’s default package to store custom components.
- Compile the package, and Delphi will produce the package library (.bpl extension) in BPL output directory, of course if the compilation is success.
- Install the package library (dclusr.bpl) through Install Packages menu item, as usual. Yes, Delphi will accept to install this package! 🙂
Viola… your custom component(s) is already on the Tool Palette. 🙂 Yes, we will be tiered to one-single component package for ALL of our custom components, the dclusr package. I think this is the true limitation of Turbo Delphi Explorer. *this must be Nick‘s idea* 🙂 But, for me personally, this is more than enough! 😀
So… enjoy the free Turbo Delphi Explorer! 🙂
I never meant this trick would discourage people from purchasing the Turbo Delphi Professional edition. This solution would help if we only use couple of custom components, or for component testing purpose. Besides, it’ll be difficult to manage large number of components within a single package. This trick available is more because the generousity of Borland/DevCo since actually they already knew this “hole” from the testing stage but still let it open. For more convenience solution, please purchase the Turbo Delphi Professional edition. 🙂