ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Header Creator

by Harryman ALL

This script is aimed to make writing arduino libraries less painful by creating the header file and keywords.txt file automatically from your library.

Details

  • 2013.11.25.23.54.15
  • github.​com
  • github.​com
  • 11 years ago
  • 42 minutes ago
  • 11 years ago

Installs

  • Total 2K
  • Win 1K
  • Mac 406
  • Linux 429
Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31 Jan 30 Jan 29 Jan 28 Jan 27 Jan 26 Jan 25 Jan 24 Jan 23 Jan 22 Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Arduino-header-keyword-creator

The purpose of this script to make writing arduino libraries less painful by creating the header file and keywords.txt file automatically from your library. It will pull Top comments, includes, functions along with their adjacent comments, and variables with types*(see instructions)

This is the first python script and Sublime Text plugin I've made so the code is a bit of a mess.

This is available through Package Control

I haven't tested it on ST3 but it does work on ST2 for windows. I'm pretty sure this will bug out and not work Linux because of different path separators.

Instructions

  • .cpp file must use explicit { }
  • Private functions & variables must start with and underscore(_) i.e. _privar
  • the variable type are pulled from the exsisting .h file
  • just to be on the safe side you should make copy of your exsisting header file, just incase
  • if there is no exsisting .h file you will have to manually enter the datatype
  • Copies comments directly from the top
  • Copies comments from driectly above or on the same line as the function or above it
  • creates keywords.txt with all of the public functions and libname
  • All references in the library should look like the file name YOURLIB.cpp YOURLIB will be used to parse the file and find functions etc. include your YOURLIB.h before any other includes
  • Use library https://github.com/Harryman/simple-buttons-arduino as an example of what the formatting looks like if you are still unsure how it works

If you find utility or vaule in it please return the favor via bitcoin: 17E66DJ5hEx6wSFxnSvYM7jgXY2PYBVrth

Or if you just want to donate to my beer fund: 151sgJ4z2tNGzVFJHGyBAd8H4F4RT62ebQ