RAPTOR is a flowchart-based programming environment, designed specifically to help students visualize their algorithms and avoid syntactic baggage. RAPTOR programs are created visually and executed visually by tracing the execution through the flowchart. Required syntax is kept to a minimum. Students prefer using flowcharts to express their algorithms, and are more successful creating algorithms using RAPTOR than using a traditional language or writing flowcharts without RAPTOR.
Are you interested in running RAPTOR on Chromebooks, iPads, or just in a browser? Check out the pre-release here!. This is NOT fully tested. Send feedback via
A Multiplatform version of RAPTOR is now available for Windows, Mac and Linux built on top of [Avalonia]! See the downloads section below. Uses fonts from Noto Sans CJK for internationalization. Key differences:
Figure 1 RAPTOR for Windows
Figure 2 RAPTOR Avalonia
Papers on RAPTOR application:
RAPTOR referenced in following books or publications:
![]() |
![]() |
![]() |
Three hours into my crisis, I realized that simple header corruption was reversible. A skilled forensic analyst could theoretically repair a JPEG header by guessing the correct values. I needed a nuclear option.
Sitting across from him at the corner table of Joe’s—his favorite—felt like standing at the rim of an argument. He talked about a new volunteer pipeline, about a fundraising gala that had gone better than expected. He showed me a photo on his phone of a child who’d received a scholarship. He didn’t look like the kind of person who would be dangerous to anyone; he looked like the kind of person you trusted to water your plants while you were away.
While it might buy you a night of sleep, "corrupting" your files is a high-risk strategy:
Due to my new situation, I have learned that data is not truth. Data is a story. And sometimes, to prevent a false story from ruining your life, you have to introduce a little static. You have to scramble the ending. You have to corrupt the file.
Three hours into my crisis, I realized that simple header corruption was reversible. A skilled forensic analyst could theoretically repair a JPEG header by guessing the correct values. I needed a nuclear option.
Sitting across from him at the corner table of Joe’s—his favorite—felt like standing at the rim of an argument. He talked about a new volunteer pipeline, about a fundraising gala that had gone better than expected. He showed me a photo on his phone of a child who’d received a scholarship. He didn’t look like the kind of person who would be dangerous to anyone; he looked like the kind of person you trusted to water your plants while you were away.
While it might buy you a night of sleep, "corrupting" your files is a high-risk strategy:
Due to my new situation, I have learned that data is not truth. Data is a story. And sometimes, to prevent a false story from ruining your life, you have to introduce a little static. You have to scramble the ending. You have to corrupt the file.
Do you want more older versions? Check out older versions of RAPTOR here
Did you know RAPTOR has modes? By default, you start in Novice mode. Novice mode has a single global namespace for variables. Intermediate mode allows you to create procedures that have their own scope (introducing the notion of parameter passing and supports recursion). Object-Oriented mode is new (in the Summer 2009 version)
RAPTOR is freely distributed as a service to the CS education community. RAPTOR was originally developed by and for the US Air Force Academy, but its use has spread and RAPTOR is now used for CS education in over 30 countries on at least 4 continents. Martin Carlisle is the primary maintainer, and is a professor at Texas A&M University.
Below handouts are by Elizabeth Drake, edited from Appendix D of her book, Prelude to Programming: Concepts and Design, 5th Edition, by Elizabeth Drake and Stewart Venit, Addison-Wesley, 2011. Linked here with author's permission.
Comments, suggestions, and bug reports are welcome. If you have a comment, suggestion or bug report, send an email to .
David Cox has put together a user forum at http://raptorflowchart.freeforums.org. This provides a place for users to exchange ideas, how tos, etc. Note however, that feedback for the author should be sent by email rather than posting on this forum.
Randy Bower has some YouTube tutorials at http://www.youtube.com/user/RandallBower. You can also search YouTube for "RAPTOR flowchart".
The UML designer is based on NClass, an open-source UML Class Designer. NClass is licensed under the GNU General Public License. The rest of RAPTOR, by US Air Force policy, is public domain. Source is found here. RAPTOR is written in a combination of A# and C#. Unfortunately, I don't have the time to provide support on compilation issues