very good your docs are always neat. 

when you get time maybe you would do a user guide for the visual studio plugin

Very good.

The new debug stuff in visual micro uses c++ injection. If we can work a way for make files to provide this feature then we have a complete winner!

I look forward to your valuable feedback and ideas when the debug tools are released for visual studio.

yes that would be good. let's have an xml file that allows make files to be registered with nice names. I can add an interface to allow new ones to be added by users but initially we could just have a pre-defined list. can you try thyem out in vs?

I'm working on the next release of embedXcode. I plan to integrate an automatic documenting feature. 

After having reviewed HeaderDoc, doxygen and appledoc, I picked doxygen. 

Integration with Xcode is the main challenge. The idea is to select a specific target to build the documentation, obtain a PDF and integrate a codeset Xcode could use. 

There's still a lot of work to do. 

Stay tuned 

Please find the new release of embedXcode with the implementation of the self-documentation.

embedXcode • Jun 14, 2012 release 13
Installation Guide • Jun 14, 2012 release 9

Just add to your code and launch the Document target:



A help document is generated and closely integrated in Xcode. 

Quick Help provides details on documented functions:



As always, learn more and download from here.

Hi,

First of all, congratulations for this nice and working Arduino plug-in for a standard IDE. I haven't been lucky with other plug-ins for Eclipse, NetBeans, ...

Now, an interesting enhancement would be including other platforms. For example, the Microchip PIC32 based chipKIT UNO32 brings 32-bits at 80 MHz and has a Processing-based IDE called MPIDE —for multiple platform IDE— which handles both AVR / Arduino and Microchip / chipKIT platforms / boards. 

Because I own a chipKIT UNO32, I no longer use the Arduino IDE because MPIDE can manage both.



C / C++ language is the same, expect the tool-chains, avr- for Arduino, pic32- for chipKIT.

Here's a comparison between both IDEs, including build and upload and directories and files. 

Best regards,

Great.

I did some research work available is this public folder.

Good luck!

Rei Vilo,

your link don't work anymore. Could you repost it. I just courious about compariosion IDE<> MPIDE...

Regarsd...

Mladen Bruck
Hercegovina

I found your makefiles when searching the web. You really know your stuff!! 

Your makefile system has to be the neatest and most flexible arduino compiler on the planet!

1)
Now that vm has the ability to store project properties it would be useful to allow users to override the base compiler settings on a project by project basis. Also t optionally provide outputs for avr sim + symbols etc. as per your make file examples.

I would appreciate hearing what project options you think others will find useful so enable or change the compiler functionality.

2)
On another note, the next version of vm implements your suggestion of including arduino help and examples from a while back. Thanks for the suggestion! 

The new help/examples system has been implemented in an "explorer" type window view, filtered by platform. This is the first step towards your other suggestion of supporting additional platforms such as chipKit

1)
Good idea about the option to open the serial. The debug tool does it but it makes sense for std projects to be able to do it.

2)
Yes I am going to add the default sketchbook folder property to vm to avoid the need to set in the arduino ide.

I think it's best to write the change back to the arduino ide preferences in an attempt to avoid user confusion and questions such as"Why doesn't my sketch compile in vm but it does in arduino?"

Makefiles/Multi-platform

3) It might be possible to use the makfile in visual studio. I thought it might be difficult with the debug stuff but it turned out that the debug system just uses the standard arduino compile. 

When we first started discussing a multi platform make file I mentioned the need for a common format to register new platforms. This will provide the ability for users to add their own platforms to the standard list. There is no reason why a makefile is not automatically generated from an xml based platform list.

So, for me, the first job is for us to agree a standard platforms reg file, then it's a simple bit of c# for me and/or makefile magic for you to convert the xml (or ano format) into makefiles. 

Or we just write out a small platform sepcific makefile (like your first level makefiles) for each registered platform. I guess we could read the makefile back into some sort of configuration dialog for users, allowing the platform to be maintained?