Re: [BCB3] Adding Custom Components to the Palette

[Roberto Artigas Jr <ascend@netten.net>]

> Rick Malik wrote:
> The IDE enhancements are fine with me, but this component
> palette stuff is a total error. I've got a ton of components without source
> codes, and a ton of delphi components, and not one of them will work.

This is a fact of life when it comes to development environments. 
Specially when Borland seems to be merging the internal code for DELPHI
and CBC.

I do not like it either. I have to redo all my components. And retest
everything.

I also buy components and libraries with source. Since I have been BADLY
BIT 
when I did not do that in other environments. So I am in better shape
that most.

> You guys all seem very happy with this upgrade. What gives?

Most of us are not as deep into projects as you are.
So we are looking for advancement in features and ease of use.
You seem to have been up front in the "bleeding" edge.
Been there, done that. Sometimes it is NOT very pleasant.

> No offense intended. The whole thing boils down to this. I've got three
> heavy project on the fire. I'm using third party components, and some of my
> modules are 20-30 pages long. "and I ain't start'in over". 

Don't blame you. No offense taken. That **IS** the correct decision. 
Finish in what you got. Then take you projects and upgrade if necessary. 
That is the reason that in the real world, most new handy dandy wiz bang 
environments, do not get inplemented for a while. 
There is conversion and retraining costs. Facts of life. 
New things have to be proven. They are never bug free out of the box.

> I'm glad that I
> put version 3 on a separate partition on the HD, and if I can't get this
> switched over, I'll be finishing these in version 1 through the spring.

SMART MAN!!! This is someone with some experience under his belt.
Either experiece, or his brain was ON when he got his upgrade.

> Maybe by then "Someone" will rewrite some 300+ components to work in
> version 3. 

By end of spring? Two months away? HEHEHEHEHE! But maybe I am being too
pesimistic.
Let see what reality brings about.

> BTW - I do buy the components when they're not free, but w/o
> sources. I never planned on having to change a word or two in them, so most
> of them were half price.

I buy components. But never without source. Same with libraries.
This is for my own environment. I make the decisions there.

When other people control the enviroment (as in contracts or employment)
you might not have a choice. But you can ask for policy changes.

Been where you are. Not pleasant. There is always some insane deadline.
And then you run into a limitation with some third party software.
This response might bring some insight to the *NOT CODED HERE* (do now
want it)
behavior of most large companies in the real world. 
Only time they yield to a library (or component), is when they have
no choice. Too labor intensive to do it themselves. Economies of scale.
And most of the time they purchase sources. It is a control issue.
Having control over your own means of production.

I can sometimes find a solution or workaround if I get into a limitation
whith someone else's code. I can also create my own as a derivative.
But I need to have the source available to do that.
So a long time ago, I made a decision for my personal buying habits.

> Rick Malik
> rmfci@pacbell.net

Roberto Artigas
ascend@netten.net