<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Il 07/09/2014 18:39, Juha Manninen ha
scritto:<br>
</div>
<blockquote
cite="mid:CAPN1EhD4w+1oKojdcr5apBJnd7rOWP2qEDMXfwjpLrN62_hccg@mail.gmail.com"
type="cite"><br>
On Sunday, September 7, 2014, Giuliano Colla <<a
moz-do-not-send="true"
href="mailto:giuliano.colla@fastwebnet.it">giuliano.colla@fastwebnet.it</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Having as a
guideline the way editortoolbar integrates in the IDE, and on
the source editor, it shouldn't be too hard to adapt it to
POChecker needs. But it's better to make one change at a time,
not to create some confusion...<br>
</blockquote>
<div><br>
</div>
<div>You maybe misunderstood. I don't want to integrate PoChecker
in the source editor.</div>
<div>It has its own window which is ok but it does not use the
potential offered by IDE integration anyhow. Typically we want
to check translations of a Lazarus project, right. The most
logical thing would be to offer translations belonging to the
current open project for checking.</div>
<div><br>
</div>
</blockquote>
<br>
I wasn't thinking about integrating the PoChecker in the source
Editor. I was thinking of obtaining the information we need from the
IDE, such as current project files, currently open files and such,
the same way as editortoolbar obtains them (i.e. via IdeIntf etc.).
It seems to me that we could have a set of choices similar to the
"Find in files" dialog: current project files, open files, and
directory.<br>
<br>
The {$IFDEF PoCheckerStandalone}, which is already there, can easily
provide the appropriate options only to the integrated version.<br>
<br>
Giuliano<br>
<br>
</body>
</html>