okay, I've gotten most the work before v1.0 done, I'm mostly doing bug/annoyance smashing. Here is a build directly from my computer. A Windows build is now up too.

v1.0 beta 2
_____________
Linux 64:
www.box.net/shared/eom1m2rxyy

Windows 32:
www.box.net/shared/aylon0xav2

Except the known bugs, no other bugs have been discovered, so beta2 is v1.0. v1.0 is a good starting place for this project in that it has all the basic functionality needed to start being useful. However, my original idea will hopefully be more realized in v2.0, which will add some features to help go from data to code and will have a back-end re-factor cleanup. Details are in the first post.

Great! Looking forward the v2.0. =)

Also I wanted to apologize for not having integrated the code you sent me. I completely forgot last week end as I was focused on the iPhone port. I'll do it during the week and keep you informed. =)

This is awesome. I love the simplicity (and needless to say, usefulness) of the whole thing.

One thing I've noticed: I have Pey installed in its own independant folder, outside of any orx project. When I use the file browser to select a path, the path that appears in the end is absolute. It would be very handy if the paths were instead relative to the emplacement of the .ini file that's being edited. Same goes for the default folder when the file browser opens.

Anyway, I really like where this is going. The lack of an undo function at this point is perharps the only major drawback of editing ini files with Pey. I shall try it out when making improvements on DragonCube and give you some more feedback : )

Thanks for the feedback, I haven't been working on this as much recently, as I've been gearing up for a possible Google Summer of Code(and another mystery project), but I have partial relative folder support. I believe if you put in your own relative folder path(relative to the exe) it will work fine, but I haven't yet changed the file selector to behave like such.

An undo function is something from the start I had wanted to implement, but since it requires a hook into an item changes, and some changes have no good hook for(dragging objects on the left, the only way to detect what happened is actually to look for "selection changed", I believe)so it's a little tricky, hence why it isn't there yet.

One cool thing is that these "distraction projects" I mentioned above(GSoC and mystery project), no matter which one succeeds(or both) the code will most likely be reused into Pey, which will yield some awesome features, so keep an eye out, as I have plans for Pey's future.

Great to see you found a GSoC project. What will it be then?

I'm really looking forward the next steps for Pey. I'm sure a lot of people will appreciate this tool.
Btw, do you want me to open a FTP account on orx's website for you so that you can easily publish things related to Pey?