VoyForums
[ Show ]
Support VoyForums
[ Shrink ]
VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, [10] ]

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Date Posted: 21:37:56 06/08/00 Thu
Author: Michel
Subject: Re: Envision Components
In reply to: Homer 's message, "Re: Envision Components" on 00:20:20 06/07/00 Wed


I will consider creating "wrapper" components to get the best of "both" worlds. From my experience I really prefer creating non-visual components are run-time and not in forms. By dropping things on a form, it not only consumes more memory, but also increased the size of the EXE, and increases the time it takes to load forms.

I am working on a large Delphi project (more than 500000 lines of code) and have migrated from Delphi 1 to 4. With DFM files there can be problems across delphi versions, especially if you need to go back to a version. When components are created at run time, the migration is much smoother, as there are not any design time dependencies.

Best regards,

Michel
> I agree with your memory conservation philosophy,
> however components don't really assure a memory
> thrifty program. After all, one can .Create virually
> any component at runtime. The availability of
> components make it easier for prototyping. Not only
> that, they help programmers who are unfamiliar with a
> complex topic (like imaging) to become familiar. Look
> at the plethora of components available to VB
> programmers, then look at their numbers, and the
> popularity of VB. I for one, vote for components if
> for no other reason than it might bring us a few more
> Delphi users which helps assure the life of the
> product we all love.
> >
> > Hi Shane,
> >
> > As Bill mentionned there is only one component. This
> > is on purpose. I may later add components which will
> > wrap the functionality of the objects, such as
> > TDibGraphicPrinter, TScanner, and the transform
> > classes.
> >
> > I think that creating objects when you need them and
> > deleting them when they are no longer in use,
> > encourages good programming. There is a section in
> the
> > help file called "RAD Abuse ?" which explains my
> > thoughts on this.
> >
> > Best regards,
> >
> > Michel
> >
> >
> >
> > > I have gotten the Envision package installed into C
> > > Builder 5! Where are all the components for the
> > > package? All I see is ImageScrollBox. Where are all
> > > the other components (Scanning / Printing /
> > > manipulation)?? I was figuring there would be
> > > TEnvisionImage component at least.
> > >
> > > Thanks,
> > >
> > > Shane

[ Next Thread | Previous Thread | Next Message | Previous Message ]
[ Contact Forum Admin ]

Forum timezone: GMT-5
VF Version: 3.00b, ConfDB:
Before posting please read our privacy policy.
VoyForums(tm) is a Free Service from Voyager Info-Systems.
Copyright © 1998-2019 Voyager Info-Systems. All Rights Reserved.