Zitat von Michael Van Canneyt <michael@freepascal.org>:

>
>
> On Thu, 8 May 2008, Mattias Gaertner wrote:
>
> > > > > At worst, I just need methods to be inherited from a base form
> > > > > and appears to be working, but I was curious as to the "Visual"
> > > > > part of VFI at design time or if that will be planned?
> > > >
> > > > AFAIK there are two things missing:
> > > > - Easy creating descendant forms via 'New ...' dialog
> > >
> > > But this is the essence of VFI ?
> > > Without this, how can one say that VFI works ?
> >
> > Oh, come on. This is too simple.
> > You can already create easily any kind of inherited component. Just
> > close the designer form and change the ancestor in the source.
>
> I didn't know that this "works", hence my question :-)

Can't Delphi do the same?


> > The only
> > missing thing is a dialog, that do this in on step.
> > I already wondered why you didn't provide a dialog yourself. You wrote
> > the project templates, so I know you are skilled.
>
> Thank  you for the confidence...
>
> The point was simply that I didn't know the above works.
> I always wondered what exactly you meant with "VFI works" :)

Well, the complex parts work and for the rest there are simple workarounds.
Although the last missing feature (inheriting changes in real time) is quite
complex, so don't expect a solution soon.
The next complex part will be nested components (e.g. frames). Of course you can
already create/inherit frames. Paul implemented editing frames. I will do the
nesting.


> > Anyway, here is "the essence":
> > I found a nice patch for this in bug 1287. I simplified and extended it
> > and now you can inherit forms, datamodules, frames and custom component
> > classes via the new dialog.
>
> Great news, I'll test it ASAP :-)
>
> > Lazarians are spoiled.
>
> I know this since a long time, even without VFI :-)

Sure. You are responsible for this too.


> Now we need to convince the rest of the world of this :-)

Mattias



