File Handling; Saving; File Naming; Using File Name Extensions - Nokia COMMUNICATOR 9210 Interface Manual

16. FILE HANDLING

16.1 Saving

There is a global default folder that can be changed in the Control Panel. Applications will refer to this global
-
default folder.
Note the following:
-
When performing 'save as' for an unnamed document, the global default folder is always used
-
When performing 'save as' for an already named document, a current folder is proposed
-
If a file with the same name exists, the new file is renamed with a sequential number in parenthesis, e.g.
-
<newfilename (n)>, where n={2,3,4,...}
Applications that save files should remember the folder that files are saved to, and suggest this folder as the
-
default for the next saving action.
Support flexibility: different people organise things in different ways (sort by date, file type, project, customer,
-
etc.).
Ask the user for the name once and only once.
-

16.2 File naming

EPOC file names are case-sensitive at a UI level, and retain the capital letters they were given when created, but the
filing system does not distinguish between upper and lower case. It is therefore not possible to have two files of the
same name in the same folder, even if they are in a different case: for example, 'Document' and 'DOCUMENT.'

16.3 Using file name extensions

File extensions are not used except where required to differentiate files of the same name. Do not show file name
extensions to the user when it is not necessary!

16.4 Folders

The user should be able to use the device without using the file manager. File/folder creation and deletion across
applications is possible within application menus or common dialogs.

16.5 Protect user data

The users' data is important – they have invested significant time and effort to input the data, and trust you to
respect this. Be very careful not to inadvertently delete any user data.
The two approaches are outlined below. Only one of the two approaches should be used:
Undo: an 'Undo' option should be provided wherever deletions are routine, and providing a dialog would prove
-
excessively irritating to the user. For example, 'undo' is provided in text editors – we would not want to ask for
confirmation on deleting individual characters.
Confirmation: confirmation should be requested whenever the deletion is extreme and irreversible. The
-
confirmation dialog should contain as much relevant information as possible (and no unnecessary information).
Examples of confirmations:
Calendar delete entry
-
File deleting
-
Copyright © Nokia Mobile Phones 2000. All rights reserved.
63 (71)