Turbo Delphi explorer: installing own components via dclusr.dpk
Max Pyatnitsky
conf. that it is POSSIBLE to install your OWN components via dclusr.dpk.
Just open dclusr.dpk from lib\ subdir and add your components.
Max Pyatnitsky
Thomas Mueller
Max Pyatnitsky wrote:
Hm, yes that's possible. Interesting. I wonder how the IDE distinguishes
between dclusr and any other package...
MfG
twm
Eric Grange
However, rather than locking out dclusr.dpk completely in the next TurboDelphi
Explorer, but it might be interesting to allow installation of 1 or 2 custom
components via dclusr.dpk (no more than 1 or 2), so that people can experiment
with custom components and be enticed.
Eric
Serge Dosyukov (Dragon Soft)
So, if someone to learn how to create custom components then this is the
only way to approach the task.
Now, this is a backdoor and I am sure that at some point we would see 3rd
party which will parse this dpk and install their own components... ;o)
"Max Pyatnitsky" <mp...@gfk-usm.com.ua> wrote in message
news:450032d0$1...@newsgroups.borland.com...
Clinton R. Johnson
> Now, this is a backdoor and I am sure that at some point we would see
> 3rd party which will parse this dpk and install their own
> components... ;o)
I'm a little surprised that this one works, as most packages have to be
specially signed (check out the package resources) to work in the
explorer ide. I wonder if they sign that package.
It has been forever since I worked with that particular package as it
always seemed a little kludgy to me (I write a lot of custom
components), I'd completely forgotten it was there.
Ralf Mimoun
> Now, this is a backdoor and I am sure that at some point we would see
> 3rd party which will parse this dpk and install their own
> components... ;o)
There are many, most of the single-component stuff can be added easily in
dclusr. But I will never invest my limited lifetime to press DevExpress,
RBuilder or DBISAM in dclusr :-)
If you ask me, it's great that you can download small nice components eg.
from Torry and use them with Explorer. You get a feeling how components are
working and how they can help you. But for any real world project, UI heavy?
Not really :-)
Ralf
David Cameron
"Max Pyatnitsky" <mp...@gfk-usm.com.ua> wrote in message
news:450032d0$1...@newsgroups.borland.com...
Thanks, nice one Max :)
Thomas Mueller
"Serge Dosyukov \(Dragon Soft\)" <serge [AT] dragonsoftru [DoT] com> wrote:
> dclusr.dpk is common package where *custom* components are placed in...
> So, if someone to learn how to create custom components then this is the
> only way to approach the task.
> Now, this is a backdoor and I am sure that at some point we would see 3rd
> party which will parse this dpk and install their own components... ;o)
No, I doubt that. If somebody really wants to get around this limitation,
there are other, much simpler ways. Simpler in this case not meaning it
does not need any effort, but that through other manipulations it is
possible to just load any existing package.
MfG
twm
Tom van der Vlugt
I've just COPIED all the dclusr*.* bytes from <turbo delphi>\lib to my own working directory on my data partition and I put two simple derived button objects to it and it works! This means that the Explore Edition is somewhat capable to install your own components for designtime.
Renaming all the dclusr*.* stuff to happy*.* presents the "This version of turbo Delphi isn't licensed to install 3rd party components!". So it seems that dclusr is fixed to do the work right now.
This means that it is possible to create a HUGE package. This means to look out for making mistakes or your library will get hosed.
David Cameron
"Tom van der Vlugt" <t.v...@quicknet.nl> wrote in message
news:45008476$1...@newsgroups.borland.com...
Maybe something to do with package registration and file naming?
I can't remember the details of how package registration is actually
implemented.
Maybe it uses entries in the Windows registry (not sure)?
geor...@gmail.com
Probably it's not a new for gurus :-) but I've just read on one
delphi-related
conf. that it is POSSIBLE to install your OWN components via
dclusr.dpk.
Just open dclusr.dpk from lib\ subdir and add your components.
Max you are great.
You boosted Turbo Delphi Explorer Edition to another dimension.
Personally i think Borland did this on purpose to help hobbyists :)
When you make such a nice product like Developer studio, you rarely do
these kind
of mistakes :)
Borland forever :)
Thanks again Max, it worked
Serge Dosyukov (Dragon Soft)
Tom van der Vlugt
"David Cameron" <nom...@tome.thanks> wrote:
>Maybe something to do with package registration and file naming?
>
>I can't remember the details of how package registration is >actually implemented.
>
>Maybe it uses entries in the Windows registry (not sure)?
>
Don't rename anything of the files beginning with dclusr, since
you will see a 'This version isn't licensed for installing 3rd
components!' upon installing the package.
If you open your dclusr.dpk project, you'll get an empty project
without anything. Just create a component from the menu and derive
it from a TButton as example. It will be inserted into your
package project. Open this new file and look at the procedure
called register. Happily the Windows-registry ISN'T touched
anywhere. Registering a component merely modified the component
palette in Delphi. You can also specify a palette and if this
doesn't exist yet, it will be created for you.
Tom
Tom van der Vlugt
"Serge Dosyukov \(Dragon Soft\)" <serge [AT] dragonsoftru [DoT] com> wrote:
>
I hope this need not to violate the license.
Limiting inserting new components only using dclusr seems also a
good limitation, since you still cannot install components using
the easy way. Firstly absolute beginners still want to use the
GIVEN Borland palettes for creating nice forms.
dclusr is perfect for your OWN components and can be a real
headache for inserting 3rd party ones.
Tom
Chester
Serge Dosyukov (Dragon Soft)
As soon as it was mentioned that limitation of "limited" edition is "one
personality" and "no 3rd party components", I thought That it will last 5
minutes. - And this is what happened. ;o)
but lets look at the past history moments:
* Turbo Pascal/Borland Pascal/Delphi was one of the most popular product
lines in many countries... because of piracy ;o)
People would not spend time on cracking "worthless" products, but rather
one they like.
* Delphi was lost for education and newcommers because of the price. When
question comes to money you will invest in something which will give you a
good return in the future. With popularity, population, presentation and
features shrinking for Delphi line over the years you would not invest into
it no matter how good product might be...
* with pression from the Open Source community it is hard to compete just
because of the name, you have to give people a good toy first (and this is
what many OS projects are today) and then when people are ready they would
spend money on something more serious. It is finaly realized by ex-Borland
and many others.
* we need to bring the fun back into our life (by exploring Delphi, by
having fun with it). This will make product better. Happy customers who has
fun are better then one who are dead locked on coding - in the past
Pascal/Delphi community was one of the most adventures and proactive. We did
lost it. Hopefully we could get this back.
Dave Jewell
news:45005549$1...@newsgroups.borland.com...
> I'm a little surprised that this one works, as most packages have to be
> specially signed (check out the package resources) to work in the
> explorer ide. I wonder if they sign that package.
Yes, they do. I get the impression you've already found the RCDATA resource
called BORLAND_SIG. If this resource isn't present in the package, then the
IDE will not allow you to use components from the package. If you create
yourself a new DCLUSR100 package as described by Max, the IDE will
automatically add a BORLAND_SIG resource to the package. It will then be
accepted by the IDE as ok.
As an experiment, you might like to try what I just did: build a working
DCLUSR100 package file, exit the IDE and then delete the BORLAND_SIG
resource from the package. Now launch the IDE again and it will accept the
package at startup - no error messages. HOWEVER, as soon as you create a
design-time form and try using a component from the package, you will then
get the unlicensed error we all know and love.
It would be interesting to try adding an existing BORLAND_SIG resource to a
third-party assembly. However, I suspect the 'sig' contains other info such
as an encrypted form of the package size, file/date, etc, for validation.
Dave
rodrigo
rodrigo
Has anybody try to install kbmmemtable for example?
I've tried but I can't compile due errors like [Pascal Fatal Error]
DSDesign.pas(18): F2063 Could not compile used unit 'DsnDBCst.pas'
new...@gmail.com
portuguese-Brazil. Coming soon translate to english.
NewZeek