On Sat, 5 Nov 2005, Mattias Gaertner wrote:
> On Sat, 05 Nov 2005 12:32:22 +0000
> Colin Western <[EMAIL PROTECTED]> wrote:
>
> > Mattias Gaertner wrote:
> >
> > >On Sat, 05 Nov 2005 11:33:47 +0000
> > >Colin Western <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > >>To improve this I need the lfm files for the
> > >>super class form, but I am not sure how to get hold of them.
> > >>
> > >>
> > >
> > >1. The IDE must find the uses clause in the unit.
> > >2. Find all these units.
> > >3. read the lfm files to find the right one.
> > > if ambigious: warn programmer
> > >4. do that recursively
> > > check for cycle
> > >
> > >The main problem is here: the IDE must be able to load forms, even if
> > >there are errors in source. That's why parsing the unit should be
> > >minimized. I will try to help you with these points.
> > >
> > >Then you got the LFM files. Next step is to feed them into TReader.
> > >
> > >
> >
> > Can't you just use the same logic for ctrl-clicking on a type name to
> > get the source file for the form? Or am I missing something?
>
> Yes, some parts will be used.
> But if we would use exactly the same functions, then the form will not load
> on the slightest syntax error and this can abort loading the whole project.
> Very unpleasant. The IDE should be fault tolerant and be able to work with
> source under development.
> Delphi does it similar.
Delphi only looks in the current project and in the repository.
That is a very limited search.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
