Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Compile errors, project status, and so on

So many of you may or may not know but the keyfinder project was originally developed in Boreland Delphi using a language called pascal. As of right now I don't have a decent pascal IDE and the one I do have the code doesn't compile correctly. This is something I'd like to address in two ways; 1) Get it compiling again; 2) Reprogram Enchanted Keyfinder in a completely different language and one which is more open. This means I'll likely be leaving pascal behind in search of a more modern language to do this. Preferably one which supports sqlite3 databases because that's how Adobe stores its keys.

For the record, currently EKeyfinder is stable in the state that it is in. I have tested it many times over and it is more stable than it's predecessor Magical Jelly Bean Keyfinder. I was trying to compile it again to get it finally into its stable stage by fixing some of the HTML exporting. At any rate, please rest assured that I've not given up on this project just that it's taken me a while to get my gears rolling again on it.

Switching to a new language isn't impossible as we already have the necessary algorithms needed to decode the keys right in the Pascal source code. For instance I had previously converted the Adobe key decoder into JavaScript just for fun. See this link:

http://www.pages.drexel.edu/~sag47/adobe/

All of the devs on this project have kind of stalled mainly because everybody got too busy to work on it. I'm also considering moving the ekeyfinder project to github so that it will be easier for a wide variety of people to contribute. It's something to consider when I look at overhauling keyfinder in a new language. At any rate this is my news release so hopefully it didn't get you too down.

Posted by Sam Gleske 2012-10-09