what is needed it nost a DFM-> LDM converter, but a Broken LFM repair wizard, to allow fixing broken LFM's, such as have been converted from DFM(since obviously they are not perfectly compatible). DFM can already be "Converted" so to speak, but the result is usually a broken LFM, because of the various differences in components properties or missing components etc.

If you wish to help with this that would be great.

If not, database could definitely use some love, especially debugging and fixing things, which I would suggest first, and then adding in the DBLookup* components.

Also as mentioned in past threads, there are many things needed in the underlying FCL DB framework that are either broken, or simply unimplemented, or in a few cases which need reworking, both in the base db, and in the various db interfaces.

Any help in any DB area would be greatly appreciated.

Andrew

PS is there a list somewhere that name all the people involved with the project.

Actually I think this isn't a bad idea. A list of active developers and what they are working on...

I know it's dynamic and that's part of what this list is for, but if I knew say, Andrew was working on the GTK2 stuff, I might be inclined to mail him something I think I might have figured out but wouldn't want to bother the whole list with.

And then there's people like me who aren't really working on Lazarus itself (though I do sometimes send patches in) but do other component and app development.

-Tony

Right.
Some details:
The codetools can already check a LFM source and search for all missing identifiers. (Type checking is not yet implemented). See checklfmdlg.pas. This unit also contains a form, that should become a wizard. That means, if the codetools find some errors, the wizard should popup, list all the errors and present the user some rules to automatically fix the errors. The first rule is for example: Delete missing properties. Other rules can be of the form: Replace X with Y.
The wizard should then fix the lfm file. That means it applies the fixes and checks again. The codetools already return a LFMTree structure, so you don't need to parse the LFM file.

Mattias

I will also like to get more involved and be a helping hand to Lazarus. Just Two things
I do not have very mush time. But I will put the time I have to good use.

and secondly. I have never before worked with CSV. I know other versioning tools but not CSV. I am a Delphi developer. But I will need some help to get started with making changes to code without messing up the code with CSV. If anyone want to take the Thread Of-line Please feel free to do so.

I would love to help out in the FCL and LCL and any other coding area. Thank.

PS is there a list somewhere that name all the people involved with the project.

Jr." wrote

If there's a need for another set of hands on either the Linux or Windows side of the house (preferably Linux) I'd love to help out with the project.

:)

We need helping hands. Where do you want to help: Debugger, Source Editor, Form Editing, Databases, Components, Controls, Help/Docs, Doc Editor, gtk interface, win32 interface, ... ?
Also see Roadmap.

Mattias

All:

I've been subscribed to the [lazarus] list for quite some time, kind of lurking around. I've been wanting to get involved with the project for quite some time (about 2 or 3 years, IIRC), however there was always something else that came up in my life to absorb all of my free time (like moving, new children, etc.)

I've finally found myself in a position to <gasp> have some free time that I'd like to contribute to a worthwhile cause, and I certainly think that Lazarus is worthwhile!

As a Pascal/Delphi (among other languages) developer since 1986, I'd be very interested in contributing to the project in whatever capacity I can.

If there's a need for another set of hands on either the Linux or Windows side of the house (preferably Linux) I'd love to help out with the project.

Sincerely,

Anthony Downey
Logical Information Services, Inc.
PO Box 73
Palmyra, PA 17078
http://www.logicalinfo.com/

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.2.2 (GNU/Linux)

mQENAzoXLtAAAAEIAOLW8B7lRTIV2ErBGTe9xNPNWQv5FpFBXWBSTbhHftUHu5J/ tl+MBdwRPijovvFbbGspGYRbmYPGJawKTXK/PqSsVCTnlVO1h9MC28+XLOFXUtiY 1KjXd8kSHEmYDAOT1yHI4eF8wWhaN8Acoojxst4Gbkqg6rekRZm19mH+zlHI/rEJ QIg8wXlV3G8owWPfsHlUVlKGvnXmTO1XRxERsgtbDtKN0ovMO/3++EBh2hJRgteX bJbueJZr/xUIZ+YqkveObH+rceiIQKKb7OQjirC8vUWWBYzNGIX0rjICVJ81rjnc zisDWMDgpldvtVZt/o+I9pJ9b0XmscKDGdZeoIMABRG0MEFudGhvbnkgSC4gRG93 bmV5LCBKci4gPGFkb3duZXlAbG9naWNhbGluZm8uY29tPokBFQMFEDoXLtCxwoMZ 1l6ggwEBHL8H/1ZMKdm65LrbIlev3FAnlq3UXgSC6+hc4lMVExEMPY7sHYb5uYvE YHDZ//AYpc9l5q3Qi+2LI//x5+zjScs7y+TmM9ryGqFRxRwujAM9vf5GaC2yHYVF Rc16Q8XHSyqMkTl4sBJ1xVoIM+KSqvW/OyC9TXpSaNIlEt+qgsV0vner8sSxLvht TmyuCsCialR2trlLQunUmbXNQgyuok648V3Gz1q1+cF9A+mUfLq1hcRmyHi5Jnw0 mIZ8YICISBTXX8huZZxq87glbB39Zv9qNInTKqYairbq5s30uzKvUYsHWZPPiQ1w 7GBLrJIURms3BuUhanmJHS7mua3/gWlbpLw=
=kOUV
-----END PGP PUBLIC KEY BLOCK-----

I'd be glad to help in any area, although I'd prefer Database, Components, Editor, and Interface. I notice that you have a need for a DFM-LFM converter. Would that be a good starting point?

TD

IMO:
1. Either you know from the list who is working on what.
2. If not, then you are either a newbie, or it was never mentioned on the list.
Ergo: write to the list, if you don't know. Others will have the same questions.

And then there's people like me who aren't really working on Lazarus itself (though I do sometimes send patches in) but do other component and app development.

I think, a list of contributors would be useful. Anyone, who wants to be listed, please mail.

Mattias

> > PS is there a list somewhere that name all the people > > involved with the project. > > Actually I think this isn't a bad idea. A list of active

developers and

on the

list. Ergo: write to the list, if you don't know. Others will have

the same

questions.

> And then there's people like me who aren't really working

on Lazarus

> itself (though I do sometimes send patches in) but do other

component

> and app development. I think, a list of contributors would be useful. Anyone, who

wants to be

listed, please mail.

Well we tried this once and it just didn't work. The bottom line is that it depends on the individuals doing the work report what they are working on when they are done, etc. etc. Nobody would. I tried to keep such a list but it was always VERY outdated and of little use. As Mattias suggested it is better to just keep up with the list to know who is working on what.

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

___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com.

And I suggest to create a list of what was done by whom. Such a list can't get outdated and is easy to maintain.

Mattias

I have a ghost writer ;)

Mattias

Please list me. Currently I'm looking at some of the database stuff.

Thanks.

TD