How does one make use of the ToDo dialog in Lazarus?

I never used it in Delphi (was added after D4?) and can't find any docs on it.

Thanks,

Tony

Hi Tony

ToDo list it isn't an Delphi component but an Expert (there is full with other good things)
See : http://www.gexperts.org/ (i dont know if work with D4)

Olivier

Mattias,

Changes the jump to code function in todolist.pp, does a better search of the unit path before calling OnOpenFile. It attempts to pass an absolute path to the file to be opened.

Testing shows that the todo parser is having trouble with single line comments. I have not looked into it but if you have a //#todoxxx comment somewhere in one of your project files the parser will add duplicate todo entries with incorrect line numbers.

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.

Bob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: zip00048.zip
Type: application/octet-stream
Size: 1330 bytes
Desc: "todolist112703.zip"
Url : http://localhost/pipermail/lazarus/attachments/20031127/58396abc/zip00048.obj

Ah - it's a # symbol, not percent.

I did this, it populated the list. I double clicked one expecting to jump to the code and got "Not implemented" at which point it locked in and endless loop requiring that I kill X to get control of the PC back.

Oh well...

-Tony

The ToDo List was implemented by Olivier GUILBAUD. See todolist.pp for details.

Mattias

It seems Mattias started this, but hasn't quite finished it yet :-)

Michael.

Tony Maro wrote

How does one make use of the ToDo dialog in Lazarus?

One adds items. The items are saved in the project file as comments, like this:

{%TODO The todo text}
{%TODO Some more todo text}

The dialog essentially just manages these comments.

Michael.

Mattias,
Implements the TODO list jump to code function. Diff picked up a couple of small changes I made to to frmSearch, Had a stray label on the form, I killed it, and I changed the color to clBtnFace because it looked BAD on win32.

Bob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: zip00047.zip
Type: application/octet-stream
Size: 4766 bytes
Desc: "todolist.zip"
Url : http://localhost/pipermail/lazarus/attachments/20031126/e4924a6b/zip00047.obj

Doesn't work for me. I tried manually adding a TODO line as described in the project file, and hit refresh in the todo dialog. No effect. I also can't see a way to add a todo from the todo dialog. Is this implemented yet?

Thanks,
Tony

This is why the exercise was good for me, got me looking at the CodeToolBoss.

Fill in the ....?

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.

You don't sleep do you?;)

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);

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

I suggest to define a class TSearchFileRules for this.

Can you do that?
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.

Mattias

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.

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.

Not this weekend.

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

Mattias