What a nice post: three negative points out of three points. I guess you take the template and all the work behind for granted.
- The code-sense doesn't seem to work at all. I can start typing a libmaple or wirish function and xcode does nothing to autocomplete like it would in an Objective-C application.
As I already wrote many times, code sense isn't a 100% hit as Xcode changes the way it works with every new version and as Apple is over secretive about documenting its IDE internals. If you have special tips, please share them!
- I wasn't expecting all of those preprocessor declares inside of my project, AFTER I selected I want a Maple project. I also didn't expect my project to contain the make files for all of the boards, and config files for all of the boards.
embedXcode is aimed at providing a template for a large array of boards and platforms, hence the pre-processor statements. I use it to develop libraries I can share with different platforms. Now, feel free to tailor the template to your specific needs and keep only Maple.
I would like to see the ability to select a Maple project, and only contain code inside of the project for Maple boards. In addition, I don't like how MapleIDE is required. Could it be possible in a future revision to point embedXcode to the path where libmaple is installed (/usr/local/libmaple in my case).
I do like the way the Maple and other IDEs are required: this allows easy installation and maintenance. Once again, feel free to build your own template.
The whole template is available at GitHub and awaiting your contribution! You're welcome.