On Mon, 20 Feb 2006 17:39:04 -0300
"Alexsander Rosa" <[EMAIL PROTECTED]> wrote:

> 2006/2/18, Mattias Gaertner <[EMAIL PROTECTED]>:
> >
> > On Thu, 16 Feb 2006 10:22:17 -0300
> > Alexsander Rosa <[EMAIL PROTECTED]> wrote:
> >
> > > Maybe the tool could use the codetools for some complex source-code
> > > operations and TProject for generation of the lpi file - from
> > > *outside* the IDE.
> >
> > The codetools are no problem.
> > About TProject: I agree, that the converter needs a lot of the IDE. Too
> > much, to put it all into the IDEIntf.
> > What about this:
> >
> > We add a directory <lazarusdir>/converter.
> > Here we put all new IDE units, that converts Delphi things.
> > And we add <lazarusdir>/tools/delphiconverter/
> > Here we put the new standalone tool.
> 
> If you agree, I can setup this. Just send me a current version.
> 
> That's a good idea. Right now the current version is the one I sent, as I
> can't work on this on a daily basis. My next release will probably address
> some of the points you listed below.

Ok.

 
> I just had a short look at your project:
> > - The .dof file is ignored
> 
> 
> AFAIK the .dof file is like an INI with informations about the project;
> do you know which sections/keys should I use? 

Every key you can translate. :)


> I think [Directories] and
> [History*] are good candidates. My first thought was to start like the
> "Convert Files" tool I used to port from CLX to VCL; this tool is very
> simple, basically a fancy search-and-replace based on a dictionary.
> 
> With this talk we can get a smarter tool.
> 
> - You scan sub directories, but this will find too much and not enough.
> > Delphi projects define their parts via the uses section in the .dpr
> > file. For example:
> > uses MyUnit in '..\dir\MyUnit.pas';
> 
> 
> So it would be better to open a DPR file (instead of a directory) and scan
> it, using as "list of files" the files found after the "uses * in" piece
> of code? It would be easy to parse them and the list would be smaller.

Correct. And there are already codetools for that.

 
> This line means: MyUnit is part of the project and the directory '..\dir'
> > must be added to the unit path.
> >
> > - I like the idea, to first setup some values, then get an overview
> > (scan button), what will happen.
> 
> 
> One nice side effect is to get people that just heard about Lazarus giving
> it a try faster, or at least knowing before hand how hard it will be to
> port their projects. This could help them to know which kind of components
> they should avoid, and what is supported. For a first-time user it's hard
> to find out what works and what don't.

I guess, this tool is more for Delphians, than for first time users. 


Mattias

_________________________________________________________________
     To unsubscribe: mail [EMAIL PROTECTED] with
                "unsubscribe" as the Subject
   archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to