Changes between Version 7 and Version 8 of Obsolete/WorkInProgress/3rdparty guidelines


Ignore:
Timestamp:
Jun 4, 2011 10:03:01 PM (8 years ago)
Author:
scottmc
Comment:

removed hard coded paths, replaced with find_directory() constants.

Legend:

Unmodified
Added
Removed
Modified
  • Obsolete/WorkInProgress/3rdparty guidelines

    v7 v8  
    55= What rules should software follow =
    66 * It should work on the latest stable release of Haiku
    7  * It should work on gcc2 hybrid - other flavours of Haiku may be ignored
    8  * configuration files should go in home/config/settings; and the path should be obtained by the appropriate functions & constants, not hardcoded - use find_directory() ([http://ports.haiku-files.org/wiki/FindDirectory Examples for porting]).
    9  * The app must not write anything to the hard disk except in its own directory (/boot/app/appName, or whatever the user installed it), the configuration directories (home/config/settings, common/), unless the user explicitly asks for it (a save dialog is a good example). <-- This makes little sense, as an application usually won't have the rights to write anything into its own directory. It may write to the user's cache, data, or settings directory, though, and that's pretty much it (axeld).
     7 * It should work on gcc2 hybrid - other flavors of Haiku may be ignored
     8 * configuration files should go in B_USER_SETTINGS_DIRECTORY; and the path should be obtained by the appropriate functions & constants, not hardcoded - use find_directory() ([http://ports.haiku-files.org/wiki/FindDirectory Examples for porting]).
     9 * The app must not write anything to the hard disk except in its own directory (B_APPS_DIRECTORY/AppName, or whatever the user installed it), the configuration directories (B_USER_SETTINGS_DIRECTORY, B_COMMON_SETTINGS_DIRECTORY), unless the user explicitly asks for it (a save dialog is a good example). <-- This makes little sense, as an application usually won't have the rights to write anything into its own directory. It may write to the user's cache, data, or settings directory, though, and that's pretty much it (axeld).
    1010
    1111 * HIG compliance (e.g. sentence casing, colour scheme, vector icons): it's better if your application fits in the look&feel of the whole system.