Difference between revisions of "Tutorials/Your First Egg (for uGFX badges)"

From Badge team
Jump to navigation Jump to search
Line 19: Line 19:
 
Your badge comes with a set of MicroPython libraries that contain functions allowing you to access its hardware. The first lines you must put in your '''__init__.py''' file simply tell MicroPython that your egg will need to use two of them. The '''badge''' library contains low-level badge-specific functions, and the ''''ugfx''' library contains functions relating to the display and keys of the user interface. Type the following into your file:
 
Your badge comes with a set of MicroPython libraries that contain functions allowing you to access its hardware. The first lines you must put in your '''__init__.py''' file simply tell MicroPython that your egg will need to use two of them. The '''badge''' library contains low-level badge-specific functions, and the ''''ugfx''' library contains functions relating to the display and keys of the user interface. Type the following into your file:
  
<nowiki>
+
<code>
 
import badge
 
import badge
import ugfx</nowiki>
+
import ugfx
 +
</code>

Revision as of 12:35, 1 March 2019

Introduction

One of the aims of the badge.team project is to ensure that as many people as possible can develop software for the platform. This ensures that badges and other hardware running our firmware are more likely to have a life beyond the event for which they were created. The problem with many event badges has been that the learning curve for new developers is too steep and the acceptance process for new software too difficult. When detailed knowledge of a toolchain is required to write code and each addition must wait to be built into a fresh badge firmware update, most would-be developers go away and enjoy the event instead. With an online app store we refer to as the hatchery and MicroPython apps we refer to as eggs, publishing new software for badges running our firmware is a much simpler process.

Not everybody is immediately familiar with a new platform though, so to help with your first badge egg we've produced this tutorial. The aim here is not to teach you Python, but to introduce you to the structure of an extremely basic badge.team egg as well as get you going with the user interface. We'll be following the time-honoured tradition of introducing you to badge programming with a Hello World egg.

Compatibility

The software here has been tested on both the SHA2017 and Hacker Hotel 2019 badges.

Your First Egg

__init__.py

The first thing the firmware does when it tries to run an egg is look for a file named __init__.py, and run it. Some eggs also have other files, but at its simplest all the code for an egg can be contained within this one file.

So the first thing you should do is take an empty new directory, and create a file called __init__.py within it using your favourite text editor.

Libraries

Your badge comes with a set of MicroPython libraries that contain functions allowing you to access its hardware. The first lines you must put in your __init__.py file simply tell MicroPython that your egg will need to use two of them. The badge library contains low-level badge-specific functions, and the 'ugfx library contains functions relating to the display and keys of the user interface. Type the following into your file:

import badge import ugfx