Modifications

{{bloc-etroit|text=Adding a library to the IDE starts by creating an open source GitHub repository where your code will live. At minimum, this repository needs a <code>spark.json</code> file, some documentation, some example firmware files, and some Arduino/C++ files. The import and validation process is designed to be forgiving and easy to interpret, so don't be scared; the IDE will walk you through what is required to get your library set to go.}}

{{bloc-etroit|text=Adding a library to the IDE starts by creating an open source GitHub repository where your code will live. At minimum, this repository needs a <code>spark.json</code> file, some documentation, some example firmware files, and some Arduino/C++ files. The import and validation process is designed to be forgiving and easy to interpret, so don't be scared; the IDE will walk you through what is required to get your library set to go.}}

{{SPARKImage|Spark.IO-Build-60.png|800px}}

{{SPARKImage|Spark.IO-Build-60.png|640px}}

The easiest way to generate library boilerplate code is to follow the instructions on the [https://github.com/spark/uber-library-example/#getting-started getting started section] of the <code>uber-library-example</code> (''Spark GitHub, anglais''), a project designed to illustrate and document what a library is supposed to look like.

The easiest way to generate library boilerplate code is to follow the instructions on the [https://github.com/spark/uber-library-example/#getting-started getting started section] of the <code>uber-library-example</code> (''Spark GitHub, anglais''), a project designed to illustrate and document what a library is supposed to look like.

{{Spark.IO-Build-TRAILER}}

{{Spark.IO-Build-TRAILER}}