I attempted a better support for Scratch in Stretch by leaving untouched the basic Scratch, and calling it appropriately. This way, if the RaspberryPi Foundation changes something with Scratch 1.4, we will be kept up to date.
Simplification means we only use the following files now, on Stretch only - Jessie is not affected.
Scratch_Start.py
scratch_direct (which is a bash file, without the .sh for some reason)
install_scratch_start.sh (at setup time)
Plus the appropriate robot scratch driver, which resides in the robot repo.
Scratch_Start.py is a standalone but can also be loaded up as a library (it is not system wide). When loaded as a library, it can be used to launch both the robot scratch driver and Scratch. A filename parameter can be used to open up a specific Scratch program (ie, by double-clicking on it)
Caveat: to double-click a .sb file, the association has to be done manually when creating an image.
I attempted a better support for Scratch in Stretch by leaving untouched the basic Scratch, and calling it appropriately. This way, if the RaspberryPi Foundation changes something with Scratch 1.4, we will be kept up to date.
Simplification means we only use the following files now, on Stretch only - Jessie is not affected. Scratch_Start.py
scratch_direct (which is a bash file, without the .sh for some reason) install_scratch_start.sh (at setup time) Plus the appropriate robot scratch driver, which resides in the robot repo.
Scratch_Start.py is a standalone but can also be loaded up as a library (it is not system wide). When loaded as a library, it can be used to launch both the robot scratch driver and Scratch. A filename parameter can be used to open up a specific Scratch program (ie, by double-clicking on it)
Caveat: to double-click a .sb file, the association has to be done manually when creating an image.
This PR contains https://github.com/DexterInd/Raspbian_For_Robots/pull/174 which needs to be merged first.