Board index » cppbuilder » Design time vs run time packages

Design time vs run time packages

Hi all,

We are finally migrating to BCB6, (Yay) I have to upgrade someone elses
components (Boo). The problem is that it uses a Property editor. I can make
the component build fine, but when it is used in an application it won't
link (if build with runtime packages is not checked).

So my question, can I statically link to the property editors?

And if not, I have read on the news groups that this component should
actually be in 2 packages, one a runtime one with just the application
code, and one a designtime one that extends the runtime component to add
property editor stuff. Is this correct and are there any good references or
guides on how to do this? My 2 BCB books are pretty scant on details for
this sort of thing.

Thanks
Simon

 

Re:Design time vs run time packages


Quote
"Simon" <macneall@iinetdotnetdotau> wrote in message

news:Xns928254BEBE08Cwooohooo@207.105.83.65...

Quote
> So my question, can I statically link to the property editors?

No, and in fact you're explicitally not allowed to in BCB6.  All property
editors must reside in separate designtime packages specifically so that
they won't be linked into the runtime project itself.

Components need to be segregated into separate runtime and designtime
packages, where the runtime package contains the component code itself only,
and the designtime package contains everything else that the IDE itself
needs in order to work the component (editors, pallete icons, registrations,
etc).

If you can't separate the code correctly, then you're going to find it
difficult to use that component.

Start with the original package, and just comment out the design editor
header file(s).  Then try to compile.  Everything that fails to compile,
move to a separate package.  Then move the Register() function over as well,
and any icons and such as well.  Everything that is left over should be just
the component code itself.

Quote
> And if not, I have read on the news groups that this
> component should actually be in 2 packages, one a
> runtime one with just the application code, and one a
> designtime one that extends the runtime component
> to add property editor stuff.

Correct.

Gambit

Re:Design time vs run time packages


"Remy Lebeau [TeamB]" <gambi...@yahoo.com> wrote in
news:3d79513d$1@newsgroups.borland.com:

Quote

> No, and in fact you're explicitally not allowed to in BCB6.  All
> property editors must reside in separate designtime packages
> specifically so that they won't be linked into the runtime project
> itself.

{*word*81}.

Thanks Remi, I guess this is what I will be looking forward to at work on
Monday.

Simon

Re:Design time vs run time packages


"Remy Lebeau [TeamB]" <gambi...@yahoo.com> wrote in
news:3d79513d$1@newsgroups.borland.com:

Quote
> Start with the original package, and just comment out the design
> editor header file(s).  Then try to compile.  Everything that fails to
> compile, move to a separate package.  Then move the Register()
> function over as well, and any icons and such as well.  Everything
> that is left over should be just the component code itself.

I've done all this, and in builder 6, the application still requires the
design time component for linking. Are there any examples of this on the
web so I can try and see what is going wrong?

Thanks
Simon

Re:Design time vs run time packages


That most likely means that either the run-time package is still trying to
use something from the design-time package that it shouldn't be using, or
else the main application's project is configured to include the design-time
package into the project, which it shouldn't be doing.

Gambit

Quote
"Simon" <macneall@iinetdotnetdotau> wrote in message

news:Xns9287DBB359164wooohooo@207.105.83.65...
Quote
> I've done all this, and in builder 6, the application still
> requires the design time component for linking.

Other Threads