The Raisonance
Integrated Development Environment (RIDE) is a fully featured Integrated
Development Environment (IDE) that provides seamless integration and easy
access to all the development tools. From editing to compiling, linking,
debugging and back to the start, with a Simulator, ICE, Rom Monitor or other
debugging tools, RIDE conveniently manages all aspects of the Embedded Systems
development with a single user interface.
Multi-file Editor
RIDE is based on a fast multi-document editor designed to
meet the specific needs of programming. The various methods, menus, commands,
and shortcuts are all fully compliant with the Microsoft® specifications
for Windows 2000, XP and NT. Classic commands, such as string search and block
action are integrated. Advanced features such as Matching Delimiter (parenthesis,
brackets), Grep (multi-file search), Indenter and the customizable color-highlighting feature are
integrated as well.
Project Manager
The project manager creates links between the various files
that includes a project and the tools necessary to create that project. A
project is dedicated to a particular target: 8051, XA, ST7, STR7, ST6, ST5
or other microcontrollers. Tree-structured projects ease the management of
the most complex applications (bank switching, flash, multi-processor, multi-module...).

The Message Window and the On-line Help
The message window displays all warning, error, and progress
messages generated during the processing of files associated with each project.
Clicking on an error string in the message window automatically positions
the cursor at the point of that error in the source code window.

The Script Language
Most RIDE commands can be run from a script file. Scripts
are written in a C-like language, and are interpreted at execution time. With
the script language, most repetitive tasks can be done automatically thus
speeding up operations and reducing the probability of errors. Scripts are
very useful for Hardware Testing (board, emulator) and to initialize the system
to a known status, but can also be conveniently used for other tasks such
as creating very complex breakpoints or redirecting some output to a file
to run a 'batch' debug session.
Context Saving
When a project is closed, the whole associated context is
saved (open file list, window size and position etc..). Settings associated
with the debugger are also saves such as breakpoints, watches etc. |