Summary

This chapter has shown how you may use editors in a Series 60 application to enter, edit and view numerous data types, in various formats. It has also described how input restrictions can be enforced, and how access to extended character sets can be configured.

Editors can be created statically (using a resource file) or dynamically (using API construction) and may exist as stand-alone UI components . However, more typically they are used as part of a dialog, or form ”in which case they are usually constructed and owned as part of that control.

The first example application, PlainTextEditor , showed you how to create and use a plain text editor, applying attributes that made it into an editor suitable for the insertion of URLs. The second example application, RichTextEditor , showed you how to use a rich text editor and how to apply complex character formatting, also giving an overview of paragraph formatting, or "styles." The third example, NumericEditor , showed you how to use numeric editors and, in particular, how to configure them for entry of integer, or fixed-point, data.

Additionally, this chapter gave you direction on how to create and use secret editors ”in other words, editors that hide their input values, and also multi-field numeric editors (MFNEs). These provide specialized entry for specific numeric data types, such as times, dates and IP addresses.

Further information on these and other editor controls can be found in the SDK documentation.