How does EssModel deal with graphical layout of complex diagrams? I guess it is easy to create a messy diagram but a nice layout needs a complicated algorithm.
If you've downloaded the source, try reverse engine the project itself and see such nice layout (there are A LOT of classes but they all look nice, no overlapping occured).
Ok, I improved the Delphi converter so it replaces also the Kylix Q* unit names (removes the 'Q'). EssModel converts nicely now.
OK, it looks like I don't have to continue mine (it's not far yet anyway), continue yours and post it somewhere please (I have no domain, so I can't post it myself. If I have to, I'll use google code), I'll help from my earlier experience.
It is not fully automatic though, still there is much manual work with Windows / Kylix specific functions.
It's not that much. Only some metafile, SHBrowseForFolder function, external png handler, and omni_xml. I remove all metafile related things since LCL doesn't have cross platform capability yet (a Windows-only package is available in Lazarus-CCR, it uses Windows API). The SHBrowseForFolder can be replaced by TSelectDirectoryDialog. External png handler can be removed, and with the current capability of TBitmap, we can even support more image types. The quite difficult one probably omni_xml. Though we can use units from fcl-xml, the way it's used must be different. So we need to adapt it.
Recent
