Missing DSGNINTF.DCU file in Delphi 5 Standard
Helmuth Adolph
I've got a third party component which works perfectly under Delph
2/3/4.
It uses DSGNINTF.DCU, this DCU is not in the LIB-directory, there is
only a DSGNINTF.INT file. According to the Delphi help the class
TComponentEditor should be in this DCU.
Is this file forgotten to store on the CD or is it only availlable
in the professional version ?
Thanks for helping
--
Helmuth J.H. Adolph
-------------------------------------------
e-mail: helmuth...@europe.de
web: http://www.hp.europe.de/prodelphi
-------------------------------------------
Jeff Overcash (TeamB)
versions that come with source code the pas file is included. Your only option
is to compile with packages as the code is in the VCL50.bpl package. The other
otion is to propely design the component. All the design time code should be in
a design time package. This would include any code that needs dsgnintf. All
your runtime code should be in its own package and the design time package
should use this run time package.
This is covered in the readme.txt file. D6 will probably remove the pas file
totally and only ship with the int file and might move the compiled code into a
design time IDE package so it will not be possible to distribute this non
redistributable code.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Learning is finding out what you already know. Doing is demonstrating that you
know it. Teaching is reminding others that they know it as well as you. We are
all leaners, doers, teachers. (R Bach)
Ilya Andreev AKA Andre
compile it.
>D6 will probably remove the pas file
> totally and only ship with the int file and might move the compiled code
into a
> design time IDE package so it will not be possible to distribute this non
> redistributable code.
Why? They thinking, nobody using it in run-time applications :) ?
with best regards,
Ilya Andreev AKA Andre,
Diamond Tools Team, Memphis, TN
www.islamov.com/diamond/
Jeff Overcash (TeamB) <over...@onramp.net> wrote in message
news:383B12E7...@onramp.net...
J. Peter Mugaas
<ilya_a...@geocities.com> wrote:
>[snip]
> Why? They thinking, nobody using it in run-time applications :) ?
>
From what I understand, it was only for providing Experts and Property
editors. Unfortunately, a few component authors where using it to
make property editors which are in the same unit as the component
itself meaning that you could not compile your program without it and
the design-time information was actually linked into the .EXE if you
use the component. Thus, many users could unwittingly wind up
redistributing part of the dsgnintf code in their .EXE's.
Legal issues a aside, a more practical reason for developing a
property editor in a different unit than the VCL component code is
that the design information is not needed and only adds bloat to the
.EXE.
-- Support the anti-Spam amendment - Join at http://www.cauce.org/
J. Peter Mugaas E-Mail: oma0...@mail.wvnet.edu
http://wvnvm.wvnet.edu/~oma00215/ ICQ Number: 14297043
Finger for PGP Key
Ilya Andreev AKA Andre
Damn, Delphi 5 Professional is not including VCL sources.
--
with best regards,
Ilya Andreev AKA Andre,
Diamond Tools, Memphis, TN
www.islamov.com/diamond/
Ilya Andreev AKA Andre <ilya_a...@geocities.com> wrote in message
news:81f52j$2h...@forums.borland.com...
> No, you still have DSGNINTF.pas in Delphi5/Source/ToolsApi and you can
> compile it.
>
> >D6 will probably remove the pas file
> > totally and only ship with the int file and might move the compiled code
> into a
> > design time IDE package so it will not be possible to distribute this
non
> > redistributable code.
>
> Why? They thinking, nobody using it in run-time applications :) ?
>
>
Jeff Overcash (TeamB)
Ilya Andreev AKA Andre wrote:
>
> No, you still have DSGNINTF.pas in Delphi5/Source/ToolsApi and you can
> compile it.
>
The question was about Delphi 5 Standard. Standard has never shipped with
source code.
> >D6 will probably remove the pas file
> > totally and only ship with the int file and might move the compiled code
> into a
> > design time IDE package so it will not be possible to distribute this non
> > redistributable code.
>
> Why? They thinking, nobody using it in run-time applications :) ?
>
It they are they are using it illeagally. Borland is giving component writers
some time to make the shift. It can be done over 2 versions. The reason is
simply that Borland hit a major problem in D4 that could not be addressed
without changing dsgnintf. Because of the fact the people have been incorrectly
using it Borland had to delay the fix to D5 or else break working code in D4.
The decisiobn was made to force component writers to properly design their
packages from now on. Once DsgnIntf is accessable only in package form,
Borland's hands are much freeer to fix certian IDE issues.
One thing you nmeed to remember is that this is supposed to be a design time
only unit. But people were incorrectly bloating their packages by putting the
component and property editors ni the runtime package. Correctly designed all
that code should be in a design time package and only runtime code in the
redistributable run time package.
> with best regards,
>
> Ilya Andreev AKA Andre,
> Diamond Tools Team, Memphis, TN
> www.islamov.com/diamond/
>
Ilya Andreev AKA Andre
> > compile it.
> >
>
> The question was about Delphi 5 Standard. Standard has never shipped with
> source code.
Yes, I'm understood it 2 minutes after my first message :)
> It they are they are using it illeagally. Borland is giving component
writers
> some time to make the shift. It can be done over 2 versions. The reason
is
> simply that Borland hit a major problem in D4 that could not be addressed
> without changing dsgnintf. Because of the fact the people have been
incorrectly
> using it Borland had to delay the fix to D5 or else break working code in
D4.
> The decisiobn was made to force component writers to properly design their
> packages from now on. Once DsgnIntf is accessable only in package form,
> Borland's hands are much freeer to fix certian IDE issues.
Ok, can you explain me this situation? We have our report writer (unique
report writer, for
character-based reports, with full visual designer, user-frendly,
drag&drop etc).
And I'm using my object inspector for edit properties of report elements.
It's very useful and easy.
What should I do now? Re-write all designer? Make some hacks for access to
RTTI without dsgnintf.pas?
I can do it, of cause. But I don't want. I was hope, that Inprise will ship
more source codes (for property editors,
component editors, some tools etc. But, what we can see now? They start to
ship less source codes!
Of cause, now I can watch Decision Cube sources - that is really nice! <g>
with best regards,
Ilya Andreev AKA Andre
Diamond Tools, Memphis, TN
www.islamov.com/diamond
Jeff Overcash (TeamB) <over...@onramp.net> wrote in message
news:383B255B...@onramp.net...
Jeff Overcash (TeamB)
Ilya Andreev AKA Andre wrote:
>
>
> Ok, can you explain me this situation? We have our report writer (unique
> report writer, for
> character-based reports, with full visual designer, user-frendly,
> drag&drop etc).
>
> And I'm using my object inspector for edit properties of report elements.
> It's very useful and easy.
> What should I do now? Re-write all designer?
If you were using DsgnIntf (in runtime packages) in the past you were clearly in
violation of your license agreement. The fact that Borland was not actively
enforcing this does not change the fact that you were or that they can't in the
future. DsgnIntf has never been a part of the redistributable list.
If you need an Object Inspector like component there are several in the market.
Look at the DreamCompany's (www.dream-com.com) as a replacement if you need one
(although DsgnIntf never exposed the OI anyways so not having access to DsgnIntf
at runtime wouldn't change that fact at all).
> Make some hacks for access to RTTI without dsgnintf.pas?
RTTI routines are in typinfo.pas, not dsgnintf.pas. DsgnIntf only has
procedures and classes required to interact with the IDE.
> I can do it, of cause. But I don't want. I was hope, that Inprise will ship
> more source codes (for property editors,
> component editors, some tools etc. But, what we can see now? They start to
> ship less source codes!
> Of cause, now I can watch Decision Cube sources - that is really nice! <g>
>
If you do not take advantage of the D5 to D6 time to re work your packages to
come into compliance with the license agreement you will probalby have major
problems when D6 ships if you have a lot of work to do. Borland did this to
better be able to serve all their customers. Being able to fix IDE bugs is
important to everyone, and having DsgnIntf being misused by component writers
was affecting this ability.
> with best regards,
>
> Ilya Andreev AKA Andre
> Diamond Tools, Memphis, TN
> www.islamov.com/diamond
>
Helmuth Adolph
yes, the prices are rising and rising. In my company we bought the
professional version only because of the VCL-sources, not to give
them away or to modify, only for understanding. Now we need to
buy the enterprise edition with a lot of features we don't need
at all, each release we have to pay more. We are already thinking
of not upgrading to Delphi 5 and to keep Delphi 3. We didn't make
the step to Delphi 4 because of the price.
Greetings -
Helmuth Adolph
-------------------------------------------
e-mail: helmuth...@europe.de
web: http://www.hp.europe.de/prodelphi
-------------------------------------------
Ilya Andreev AKA Andre schrieb:
>
> Damn, Delphi 5 Professional is not including VCL sources.
>
> --
> with best regards,
>
> Ilya Andreev AKA Andre,
> Diamond Tools, Memphis, TN
> www.islamov.com/diamond/
>
> Ilya Andreev AKA Andre <ilya_a...@geocities.com> wrote in message
> news:81f52j$2h...@forums.borland.com...
> > No, you still have DSGNINTF.pas in Delphi5/Source/ToolsApi and you can
> > compile it.
> >
> > >D6 will probably remove the pas file
> > > totally and only ship with the int file and might move the compiled code
> > into a
> > > design time IDE package so it will not be possible to distribute this
> non
> > > redistributable code.
> >
> > Why? They thinking, nobody using it in run-time applications :) ?
> >
> >
> > with best regards,
> >
> > Ilya Andreev AKA Andre,
> > Diamond Tools Team, Memphis, TN
> > www.islamov.com/diamond/
> >
> >
> >
> > Jeff Overcash (TeamB) <over...@onramp.net> wrote in message
> > news:383B12E7...@onramp.net...
> > > DsgnIntf is not a redistributable. The DCU is no longer shipping. In
> the
> > > versions that come with source code the pas file is included. Your only
> > option
> > > is to compile with packages as the code is in the VCL50.bpl package.
> The
> > other
> > > otion is to propely design the component. All the design time code
> should
> > be in
> > > a design time package. This would include any code that needs dsgnintf.
> > All
> > > your runtime code should be in its own package and the design time
> package
> > > should use this run time package.
> > >
> > > This is covered in the readme.txt file. D6 will probably remove the pas
> > file
> > > totally and only ship with the int file and might move the compiled code
> > into a
> > > design time IDE package so it will not be possible to distribute this
> non
> > > redistributable code.
> > >
> > > Helmuth Adolph wrote:
> > > >
> > > > Hi,
> > > > I've got a third party component which works perfectly under Delph
> > > > 2/3/4.
> > > > It uses DSGNINTF.DCU, this DCU is not in the LIB-directory, there is
> > > > only a DSGNINTF.INT file. According to the Delphi help the class
> > > > TComponentEditor should be in this DCU.
> > > >
> > > > Is this file forgotten to store on the CD or is it only availlable
> > > > in the professional version ?
> > > >
> > > > Thanks for helping
> > > >
> > > > --
> > > >
> > > > Helmuth J.H. Adolph
> > > >
> > > > -------------------------------------------
> > > >
> > > > e-mail: helmuth...@europe.de
> > > > web: http://www.hp.europe.de/prodelphi
> > > >
> > > > -------------------------------------------
> > >
Helmuth Adolph
TComponentEditor. As the author didn't port it to Delphi 5, I now can
completely rewrite my program. That means either to write an own
component that does the same or to look for a component on the market.
It took me days to find that one among many others and to test them
to find one that suits for my application and which has no bugs.
I'm so thankful that I now have to do a lot of, in principle, useless
work instead of doing new things.
Helmuth J.H. Adolph
-------------------------------------------
e-mail: helmuth...@europe.de
web: http://www.hp.europe.de/prodelphi
-------------------------------------------
"Jeff Overcash (TeamB)" schrieb:
Jeff Overcash (TeamB)
contrary to what Ilya says. As a matter of fact it comes with more source than
D3 since most of the component editors are included and they weren't with D3.
Prices have not gone up since D2. D3 Pro cost the same as D5 Pro. The only
addition is a middle upgrade tier for Enterprise level for Pro users. Other
than that the pricing is the same as before.
Helmuth Adolph wrote:
>
> Hi,
> yes, the prices are rising and rising. In my company we bought the
> professional version only because of the VCL-sources, not to give
> them away or to modify, only for understanding. Now we need to
> buy the enterprise edition with a lot of features we don't need
> at all, each release we have to pay more. We are already thinking
> of not upgrading to Delphi 5 and to keep Delphi 3. We didn't make
> the step to Delphi 4 because of the price.
>
> Greetings -
> Helmuth Adolph
DuncanMcC
> DsgnIntf is not a redistributable. The DCU is no longer shipping. In the
> versions that come with source code the pas file is included. Your only option
> is to compile with packages as the code is in the VCL50.bpl package. The other
> otion is to propely design the component. All the design time code should be in
> a design time package. This would include any code that needs dsgnintf. All
> your runtime code should be in its own package and the design time package
> should use this run time package.
>
> This is covered in the readme.txt file. D6 will probably remove the pas file
> totally and only ship with the int file and might move the compiled code into a
> design time IDE package so it will not be possible to distribute this non
> redistributable code.
Jeff, there are a number of components around that use property editors
etc. The declaration (in the USES clause) must be there, in order that
the property editor can be correctly defined.
So um... what is the *best* way of dealing with this? - in terms of
component distribution.
--
Regards Duncan
(remove nosmeggingspam to reply email)
DuncanMcC
>
>
> Ilya Andreev AKA Andre wrote:
> >
> >
> > Ok, can you explain me this situation? We have our report writer (unique
> > report writer, for
> > character-based reports, with full visual designer, user-frendly,
> > drag&drop etc).
> >
> > And I'm using my object inspector for edit properties of report elements.
> > It's very useful and easy.
> > What should I do now? Re-write all designer?
>
> If you were using DsgnIntf (in runtime packages) in the past you were clearly in
> violation of your license agreement. The fact that Borland was not actively
> enforcing this does not change the fact that you were or that they can't in the
> future. DsgnIntf has never been a part of the redistributable list.
Hey um... lets stick to the main point here - the main problem is
components that use property editors - or experts - that type of thing.
It's not about end-user executables - at least not to me. What we're
talking about is shipping to other developers (components) - that have a
property editor. Now that's needed at design time. So can the "other"
developer just compile with packages and work?
DuncanMcC
says...
> The component I got has a property editor which inherits somehow from
> TComponentEditor. As the author didn't port it to Delphi 5, I now can
> completely rewrite my program. That means either to write an own
> component that does the same or to look for a component on the market.
> It took me days to find that one among many others and to test them
> to find one that suits for my application and which has no bugs.
> I'm so thankful that I now have to do a lot of, in principle, useless
> work instead of doing new things.
Can you not get the source code for the component you've bought? That's,
surely, you easiest option.
Jeff Overcash (TeamB)
etc into a design time package. That design time package can use DsgnIntf.
That package should require VCL50 which is where DsgnIntf's code resides. Since
VCL50.bpl is on all Delphi machines the end recipiant already has a copy. When
the editors are improperly placed into runtime packages at compile time DsgnIntf
must be compiled into the exe eventhough this is effectively dead code (it only
has meaning running in the IDE).
Just properly segregate the runtime code from the design time code by using both
run time and design time packages and this problem goes away.
DuncanMcC wrote:
>
>
> Jeff, there are a number of components around that use property editors
> etc. The declaration (in the USES clause) must be there, in order that
> the property editor can be correctly defined.
>
> So um... what is the *best* way of dealing with this? - in terms of
> component distribution.
>
> --
> Regards Duncan
> (remove nosmeggingspam to reply email)
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Live never to be ashamed if anything you do or say is published around the world
- even if what is published is not true. (R Bach)
DuncanMcC
> Split all the design tiem code, property editors, component editors, experts,
> etc into a design time package. That design time package can use DsgnIntf.
> That package should require VCL50 which is where DsgnIntf's code resides. Since
> VCL50.bpl is on all Delphi machines the end recipiant already has a copy. When
> the editors are improperly placed into runtime packages at compile time DsgnIntf
> must be compiled into the exe eventhough this is effectively dead code (it only
> has meaning running in the IDE).
>
> Just properly segregate the runtime code from the design time code by using both
> run time and design time packages and this problem goes away.
Yep - got it all figured now - taa for the reply.