[lazarus] ToDo dialog

[Bob Wingard]

On Fri, 2003-11-28 at 04:59, Mattias Gaertner wrote:
> On Thu, 27 Nov 2003 18:53:21 -0600  Bob Wingard <bwingard at gt.rr.com> wrote:
> 
> > Mattias,
> > 
> >[...]
> > I am glad you guys had this conversation because I was looking into ways
> > to determine the unit search path for the find Identifier function that
> > Mattias outlined and this little exercise has helped a bunch.
> 
> The unit search path for a directory can be retrieved with 
> 
> UnitPath:=CodeToolBoss.GetUnitPathForDirectory(Dir);
> 
> Same for include and src path:
> 
> IncPath:=CodeToolBoss.GetIncludePathForDirectory(Dir);
> SrcPath:=CodeToolBoss.GetSrcPathForDirectory(Dir);
> 
> The combined Src Path plus Unit Path is
> 
> SearchPath:=MergeSearchPaths(SrcPath,UnitPath);
> 
  This is why the exercise was good for me, got me looking at the
CodeToolBoss.
> 
> About "Find In Files":
> The user should be able to specify the search rules for the files. For
> example: all open files, all files in a search path, all project files, all
> files of a package, all required packages, all depending packages, ... or
> any combination.
  Fill in the ....?

> The task to gather all needed paths and to finally create the file list,
> should be separate from the Find In Files dialog. Maybe in an unit of its
> own. I need this also for some other tasks. Even separate from the LCL, so
> we can provide some command line tools.
> 
  What parts of the LCL and Lazarus can I have dependencies on. I am
thinking about project files used unit searches etc.

> I suggest to define a class TSearchFileRules for this.
> 
 ok, I started something like this in SearchResultView.pp I could move
the TLazSearch class to a separate file, rename and extend it.

> Can you do that?
 yes.
> If you think, that's much more work, than you wanted to do, I can do that. I
> have to implement some of the package part anyway.

 No I do not think its more work than I wanted to do, just a matter of
time. How quickly do you need it? I think your time would be better
spent working on the core of lazarus, it does not take a deep
understanding of the structure of the lcl or lazarus to do most of the
little things that I have been doing. It is a good way to be useful
while learning about the core though. 

You seem to have a good idea of what you want, send me an outline and I
will work to implement it.

> 
> 
> Mattias
> 
> _________________________________________________________________
>      To unsubscribe: mail lazarus-request at miraclec.com with
>                 "unsubscribe" as the Subject
>    archives at http://www.lazarus.freepascal.org/mailarchives