Platforms, Syscalls, and Objects
As explained in the previous topic, Tibbo BASIC and C are "pure" languages — they only provide the language constructs, but not the input/output facilities.
All input/output facilities are defined in platforms. Each type of a Tibbo programmable device is represented by a platform describing its capabilities — memory capacity, available features, and so on.
 You have to select a platform for every Tibbo IDE (TIDE) project you create. This is done in the Project Settings dialog (File > Project Settings).
You have to select a platform for every Tibbo IDE (TIDE) project you create. This is done in the Project Settings dialog (File > Project Settings).
Each platform provides a set of syscalls and a set of objects.
Syscalls ("system calls") form a well-developed API with convenient calls for string handling, encryption, and other handy functions.
Objects package large chunks of device functionality. Available objects are so sophisticated that many of your programs will end up containing nothing but the "glue code" tying objects together.
Here is a little taste of what's available:
|  adc. object ADC |  beep. object Buzzer |  bt. object Bluetooth |  button. object Main button |  fd. object Flash disk | 
|  io. object Digital I/O |  kp. object Keypad |  lcd. object LCD/OLED |  net. object Ethernet |  pat. object Status LEDs | 
|  ppp. object PPP |  pppoe. object PPPoE |  romfile. object Fixed data |  rtc. object Real-time clock |  ser. object Serial ports | 
|  sock. object Sockets |  ssi. object I²C and SPI |  stor. object EEPROM |  sys. object System control |  wln. object Wi-Fi | 
For additional information, see Platforms and Objects.