Flowcode

Flowcode is a Microsoft Windows-based development environment commercially produced by Matrix TSL for programming embedded devices based on PIC, AVR (including Arduino) and ARM technologies using graphical programming styles (such as flowcharts) and imperative programming styles (through C and Pseudocode). It is currently in its eighth revision.

Flowcode
Flowcode 8 Screenshot
Developer(s)Matrix TSL
Stable release
8.0.0.6 / 23 May 2018 (2018-05-23)
Written inC++
Operating systemMicrosoft Windows
Available inEnglish, French, German, Spanish
TypeMicrocontroller, RPi programming
LicenseProprietary EULA
Websitewww.matrixtsl.com/flowcode/

Flowcode is dedicated to simplifying complex functionality such as Bluetooth, Mobile Phones Communications, USB communications etc. by using pre-developed dedicated component libraries of functions. This is achieved by dragging virtual representations of hardware onto a visual panel, providing access to associated libraries. Flowcode is therefore ideal for speeding up software development times and allowing those with little programming experience to get started and help with projects. This makes it appropriate for the formal teaching of principles of programming microcontrollers [1]..

Flowcode allows the user to develop and view their program using four different visual modes. These are the Flowchart view, the Blocks view (a graphical programming paradigm inspired by Blockly), the C code view and the Pseudocode view.

Flowcode also has compatibility with Solidworks.[2]

There is a large and helpful online community based at the Matrix user forums.[3] There is also a dedicated Wiki.[4]

Notes

  1. Pearson, "Unit 6: Micro-controllers - BTEC National Engineering additional FAQs ", Pearson, 06/06/2018
  2. Dassault Systèmes, "Flowcode | SOLIDWORKS", Solidworks, 31/05/2018
  3. Matrix TSL, "Matrix user forums", Matrix user forums, 31/05/2018
  4. Matrix TSL, "Flowcode Help", Flowcode Wiki, 31/05/2018
gollark: Very expensive, and probably going to overheat if you do anything intensive on it.
gollark: All the software will need recompiling, or they'll have to use emulation, which will be very slow.
gollark: There is probably *something* you can use, and probably browser-based development environments, but it won't be very good, most likely.
gollark: You probably can do it, but I don't know how.
gollark: Oh. Hmm. Chrome OS is really pretty terrible for programming-type things, because it is locked down and not much of a "general purpose" thing.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.