HiWhen developing libraries it may be a good idea to understand what a Arduino library stands for.

In Arduino there is no difference between your sketch code and library code. All code is treated as standard code and linked as if it is one big program.The only exception to the rule is the Arduino library code (the one you always need and use via arduino.h) which is actually build like a library.The reason for this is that linking in a C library has the advantage of code optimizations (you don't need it you don't get it => smaller sketch).However if you link in a library you need it; so code optimization is not (really) needed.Best regardsJantje

Do not PM me a question unless you are prepared to pay for consultancy.Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

I normally use emacs for my IDE and screen for my serial monitor. If you're not using a build system of some type, you can then tell the arduino IDE, via preferences, that you're using an external editor. You can edit your file in your editor/IDE of choice and then hit the verify button, whereby it will reload and compile the file in the arduino IDE.

tell the arduino IDE, via preferences, that you're using an external editor.

I find that this works really well, actually. It's one of those really simple-to-implement "compromises" that looks a lot better in practice than when described; essentially it turns the Arduino IDE into a one-click compile/upload engine, and lets all the editing happen elsewhere.

Well if we start mentioning product ...I like my eclipse plugin. But I'm probably biased It is just that it provides me a single environment where I can easily do sketch and libraries compile and upload with nice features like bug marks, outline and jumps.

Best regardsJantje

Do not PM me a question unless you are prepared to pay for consultancy.Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

tell the arduino IDE, via preferences, that you're using an external editor.

I find that this works really well, actually. It's one of those really simple-to-implement "compromises" that looks a lot better in practice than when described; essentially it turns the Arduino IDE into a one-click compile/upload engine, and lets all the editing happen elsewhere.

Have you tried using daemon mode? A lot of emacians don't know about daemon mode. Use, "emacs --daemon" to start it up. Then use "emacsclient -n -c -a <alternate editor>". So for example, I use, "emacsclient -n -c -a nano". I then create an alias, in my case, "edit", for the emacsclient line. Then I can type, "edit <file>", and an emacs frame instantly pops up with <file>. The cool things is, emacs is now running as a server so all buffers you have previously opened/created are now accessible within your new frame. And, should I type, "edit" and had not previously started emacs, it will go ahead and edit the file via the specified alternate editor; in my case, nano.

And if you're on linux, you can use the following to pull things together.

Wow, really cool! Unfortunately I'm not into emacs (I'm of the vim church :-) ) I obtain a (somewhat) similar result on ssh-administered machines with tmux (or screen). That emacs daemon mode seems more powerful, though. I wonder if vi has one too (or anything close) ?

Wow, really cool! Unfortunately I'm not into emacs (I'm of the vim church :-) ) I obtain a (somewhat) similar result on ssh-administered machines with tmux (or screen). That emacs daemon mode seems more powerful, though. I wonder if vi has one too (or anything close) ?

I've not heard of such a feature for vim. Doesn't mean it doesn't exist.

Of course, you can also try VIP, VIM, or VIPER mode for emacs. Emacs nicely emulates a lot of vi/vim features and key bindings, allowing all but the most hard core vim user to find a home within emacs. I still use vi from time to time, normally as root. If I think about it, I'll use nano as root but muscle memory is vi for that quick edit. And that's one of the nice things about daemon mode is that its so fast, its comparable to using vi for that fast edit.

I will say, once you get used to daemon mode, you won't want to go back to your other work flows.