Re: Easy components feature for Delphi


Very good feature indeed. I was thinking of something like that
for a long time. This can now be done in VS.Net, btw (e.g.
for typed datasets).

To make this type of feature, you'd need to be able to compile
a component (unit) into some dll/bpl (at least temporarily) and
load that module. You will also need to reload it every time
you change that unit (or avoid using design-time features).

Then the next step would be to create a separate section in
component palette with all the components that you implicitly
or explicitly use + your local components. This will make it easier
to locate components as normally you only use a small portion
of all in current application. Allow to pre-select components you
intend to use when starting application. Avoid loading any libraries
not related to those selected components - improve startup time without
uninstalling packages (e.g. I never use IW components or ActiveX or
internet (rarely) or IB\ADO\BDE... this list could get really long
- why would I want to load packages. However, I don't want to
un-install them either).

Michael

William Egge wrote:
I like the ease of use of components, and at times I would like to have components "just" for a particular application. I don't want to create these components though because it is too time consuming and sometimes a big headache. So what I would like is the ability to create a component for an application but do so with very little setup overhead.

Here is a way I envision it would work:

I am building my app and decide I would like to have a non-visual component (not to exlude visual ones), so I create a new pas unit and code my new component. I would not have to go through a lengthly install, I would not have to create a package, and at best no install at all. I would simply be able to drop this component on a form and start using it.

I imagine this component could show up in some "local components" toolbar or something.

Also, thinking ahead, if it were this easy then 3rd party components would be as easy as adding the 3rd party unit to your uses clause. This would also solve the huge list of components problem.


-Bill


.

Relevant Pages

  • Re: Big SUSE News
    ... > YAST and SUSE does, the good integration and easiness of the things and ... > ADD to that the good things that APT does, ... that is not a feature of the ... the distro packages and third-party packages developed with the original ...
    (alt.os.linux.suse)
  • Re: making deborphan obsolete?
    ... If I use synaptic (or apt-get) to install an application A a required ... I'm wondering why a similar feature does not exist for removing packages ...
    (Ubuntu)
  • Re: Using pre-built packages with portmanager
    ... The port trees themselves are synchronized; ... The packages generated on the different ... including their dependencies. ... most people that would want to use such a feature, ...
    (freebsd-questions)
  • Re: Fedora Extras is extra
    ... > Yum does not have either) although the configuration if Apt's pinning ... I've used APT to upgrade packages, and I've read about this "pinning" ... feature before; what is this "pinning"? ...
    (Fedora)