[lazarus] ToDo dialog

Mattias Gaertner nc-gaertnma at netcologne.de
Fri Nov 28 12:55:04 EST 2003

On Fri, 28 Nov 2003 10:08:26 -0600  Bob Wingard <bwingard at gt.rr.com> wrote:

> > 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 ....?

Not enough? ;)
Ok, here some more: Files in a directory, with or without sub directories,
include file filter, exclude filter (see publish project dialog), ...

I don't expect you to implement all this. For find identifier we need only
All project units, and a package plus all depending packages/projects.

> > 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.

Don't use the IDE manager units (main, mainbar, (base)debugmanager,
(base)pkgmanager, uniteditor, formeditor, customformeditor). If you require
information from them, either add some parameters or define some hooks. The
codetoolmanager unit can be used. 
All others can be used.

> > 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.

Yes, please rename 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? 

Not this weekend.

> 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.

Fantastic. Sounds like x-mas is coming :)
My idea is you can define a list of rules to search for files. When the
search is executed, it will create a TStrings of absolute filenames. (and
relative filenames for virtual files, but this is another story). Then this
list will be given to the codetools to search all references.

The dialog does not need to be a complete rule editor. Just the most common
tasks. I can give you more details, but I guess you know how to write
frontends. :)  


More information about the Lazarus mailing list