| Application Directory |
Article Index for Application |
Website Links For Application |
Information AboutApplication Directory |
| CATEGORIES ABOUT APPLICATION DIRECTORY | |
| source code | |
|
Joining various files in this manner allows tools for manipulating applications to be merged with tools for manipulating the File System . FIXED CONTENTS In order to support user interaction with application directories, several files have special status. Application binaries Launching an application directory causes the included file ''AppRun'' (ROX Desktop) or ''!Run'' (RISC OS) to be launched. On RISC OS this is generally an Obey file (a RISC OS command script) which allocates memory and loads OS extension modules and Shared Libraries before executing the application binary. Under the ROX Desktop, it is not uncommon for it to be a Shell Script that will launch the correct system binary if available or compile a suitable binary from source otherwise. Help files and icons Both RISC OS and the ROX Desktop allow the user to view help files associated with an application directory without launching the application. RISC OS relies on a file in the directory named ''!Help'' in a proprietary format, while the ROX Desktop looks for HTML format help files in a ''Help'' directory. Similarly, custom icons for the Application Directory may be contained within it - either ''.DirIcon'' (in PNG format) or ''AppIcon.xpm'' under the ROX Desktop, or ''!Sprites'' and optionally ''!Sprites22'' under RISC OS. !Boot RISC OS application directories may contain a file named ''!Boot'' which is executed by the OS when the bundle is first discovered by the OS, allowing an application to do tasks such as register supported filetypes, or load different icons such as ASprites (icons with an alpha channel for RISC OS Select) or 5Sprites (icons with a RISC OS 5 appearance). ''!Boot'' files are the most popular propagation Vector for such RISC OS Virus es as exist. This feature is not duplicated by the ROX Desktop. EXTERNAL LINKS |
|
|