I am pleased to announce that Liam Devine is joining our humble little project. Liam has been contributing ideas, patches, and encouraging Twitter posts for quite some time, and most recently doing a smashing job adding Visual Studio 2010 support, with unit tests and everything! Considering all that, it seemed only fitting to give him the keys to the place. Meaning full rights to the repository and the trackers, so feel free to pester him with your feature requests (just kidding—use the trackers!).
While Liam will be coordinating with me, he's got free rein to work on whatever he sees fit. Presumably that means improving the VS2010 support in the short term, and where it goes from there...well, I don't know. I guess that's kind of the point. But now that I'm no longer the bottleneck for all of his improvements I can focus my scarce time on finally getting 4.3 out the door, and then finishing up the new usages feature for 4.4.
But enough about me. Welcome aboard, and keep up the good work!
Share
Cool. Any news on adding support to VS to specify the folder grouping in the projects? iirc starkos suggested something like:
files { group.name = "code/includes", "includes/**.h" }
files { group.name = "code/source", "src/**.cpp" }
which generates a vcproj with a folder heirarchy core->includes and core->source
No, no progress, as the license change and move to BitBucket has been sucking up all the air. I've got to finish getting 4.3 out the door, and complete the usages work that is already underway, and then this is next on my list (unless someone else can get to it first).
I can try to write a patch... whats the best way to embed the group.name part into the files table?
I don't have a good suggestions on storing it, and there might be a better syntax for creating the groups anyway. If you decide to tackle it, feel free to suggest an approach.
Note that I introduced a new way to handle the source files in the Xcode action, using the tree functions instead of walksources(). This approach is far more flexible; it was my intention to refactor the other actions to use it too.
While we (you, me , whoever) are in there, it might be possible to tick off a few of these (certainly the first one):