Customization Options
Different types of customization are possible in Objective Edit:
• Using standard functions— Add code to standard functions to modify the appearance of the editor.
• Subclassing & Overriding—To add new features, you can derive from almost all main classes and override virtual functions. (Normally you will not derive from SECEditLangConfig.)
• Changing the .ini file—If you want to implement colorizing for a new language, change the .ini file.
• Changing Settings at Runtime—Modify keywords and color settings using public accessors to protected data containers.
• Using custom resources—Create and use customized resources (such as bitmaps or new .ini files for non-supported languages, such as Java).
• Source Code Modification—Additional flexibility is possible if you venture to change the source code directly. Keep in mind, however, that modifying source code is not supported by Rogue Wave because it may lead to problems if you later want to upgrade to newer versions of Objective Edit. If you think that your modifications should be included in the future versions of Objective Edit, please send them to us. We will be glad to consider incorporating them into Objective Edit.
Except for the last technique on this list (source code modification), examples of each of these techniques are discussed in this chapter, as listed in Table 4.
Table 4 – Customization Techniques Demonstrated in this Chapter
Examples in this Chapter | Use
Standard Functions | Subclass & Override | Change .ini file | Use
Custom Resources | Modify Source Code |
| X | | | | |
| X | | | | |
| | | X | | |
| | | X | | |
| | X | | | |
| X | | | | |
| | X | | | |
| | X | | | |
| X | | | | |
| | | | X | |
| | X | | | |
| X | | | | |
| | X | | | |
| | X | | | |
| X | | | | |
| | X | | | |
| X | | | | |
| X | | | | |