dieterholz/rasppifx-template-project

Template for projects using both Pi4J and JavaFX

rasppifx-template-project's Issues

Translate README for non FHNW members

• README is in English
• All FHNW specifics are replaced

Move repo to Pi4J account

Title says it all

README completion

done

• Presentation Model Concept explained
• How to start a new application based on ExampleApp
• Debugging is explained
• How to implement TestCases
• all todos in README are done

Implement medium sized app

To verify the template in a more realistic scenario, a larger example app has to be implemented.

This should be done before the students use the template.

Idea: Theremin

https://www.youtube.com/watch?v=ZnTLZtZzrWU

Done

• LCD Display is used (I2C)
• Distance Sensor is used (CrowPi Component needs to be enhanced)
• Distance Sensor Component approved by Pascal
• Buzzer is used (PWM)
• GUI consists of TextField (-> LCD), Label (-> Distance), Slider (-> Buzzer)

Controller actions should be done in separate thread

Actions are triggered by UI elements.

To avoid UI blocking, all these actions should be done outside the UI-thread.

ConcurrentTaskQueue should do the job.

• new Controller-API designed and liked
• TestCases are green
• GUI never freezes even for long running actions
• action sequence is kept stable

Provide pure Pi4J MVC example

It's recommended to use MVC for applications with a PUI only. There is no need to have a GUI to use MVC

Done

• example runs on Pi
• example properly shutdowns GPIO
• README explains new example
• example is approved by Frank

Debug Run-Config

CrowPi-Tutorial contains a debug run config.

This should be copied.

Done

• You can debug the application running on RaspPi from your laptop

Improve ConcurrentTaskQueue

Currently both 'todo' and 'onDone' are executed in a separate thread.

For TestCases that's a problem.

The TestCase remains green even when an assert fails (when called inside 'onDone').

This is especially important for application specific Controller-Tests, using ControllerBase.runLater

Done

• Controller Tests turn 'red' if an assert fails or an exception is thrown
• Controller Tests turn 'green' if all asserts are OK