OpenFrameworks: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==OpenFrameworks== |
==OpenFrameworks== |
||
[[File:openframeworks.jpg|left|thumb|400px|Accessing the camera via Processing and OpenCV]] |
|||
OpenFrameworks is the C++ equivalent to [[Processing]]. Unlike Processing it does not provide its own simplified IDE, but requires an installation of either XCode on Mac OS, Visual Studio or Code::Blocks on Windows, or Code::Blocks on Linux. XCode and Visual Studio have a rather steep learning curve for beginners. Code::Blocks is just a little more light weight, but still far away from being an IDE especially designed for teaching purposes. Definitely, none of them is suitable to teach children. |
|||
The XO-HS might be a target for OpenFrameworks though. |
|||
Installing OpenFrameworks is more complex than installing Processing. It does not interact with all of the XO’s hardware features out of the box. |
|||
Figure 10 shows OpenFrameworks and Code::Blocks on the XO-1.5: After the successful installation Code::Blocks can be found in the Applications > Programming menu (7-➊). The animations in the AdvancedGraphicsExample are running slowly(7-➋). OpenCVExample and MoviePlayerExample produce errors while trying to display a movie (7-➌). This seems to be related to the videos’ codec: Message: don’t know how to handle video x-h264. A solution to this problem has not been found yet, the MovieGrabberExample (7-➎) works though. Connecting to the XO’s camera obviously is not the problem. The AudioOutputExample worked (7-➍) but produced ugly clicks and pops. 7-➏ shows one of the event handling examples. Mouse, trackpad and keyboard events are recognized. So are the game keys. The keys to switch the screen’s direction, as well as the additional arrow keys next to it, are not. |
|||
==Installation== |
==Installation== |
||
Revision as of 21:05, 17 September 2010
OpenFrameworks
OpenFrameworks is the C++ equivalent to Processing. Unlike Processing it does not provide its own simplified IDE, but requires an installation of either XCode on Mac OS, Visual Studio or Code::Blocks on Windows, or Code::Blocks on Linux. XCode and Visual Studio have a rather steep learning curve for beginners. Code::Blocks is just a little more light weight, but still far away from being an IDE especially designed for teaching purposes. Definitely, none of them is suitable to teach children. The XO-HS might be a target for OpenFrameworks though. Installing OpenFrameworks is more complex than installing Processing. It does not interact with all of the XO’s hardware features out of the box. Figure 10 shows OpenFrameworks and Code::Blocks on the XO-1.5: After the successful installation Code::Blocks can be found in the Applications > Programming menu (7-➊). The animations in the AdvancedGraphicsExample are running slowly(7-➋). OpenCVExample and MoviePlayerExample produce errors while trying to display a movie (7-➌). This seems to be related to the videos’ codec: Message: don’t know how to handle video x-h264. A solution to this problem has not been found yet, the MovieGrabberExample (7-➎) works though. Connecting to the XO’s camera obviously is not the problem. The AudioOutputExample worked (7-➍) but produced ugly clicks and pops. 7-➏ shows one of the event handling examples. Mouse, trackpad and keyboard events are recognized. So are the game keys. The keys to switch the screen’s direction, as well as the additional arrow keys next to it, are not.