Roxen.git / server / modules / examples / common_api.pike

version» Context lines:

Roxen.git/server/modules/examples/common_api.pike:1:   inherit "module";   // All roxen modules must inherit module.pike + #include <roxen.h> + // include roxen.h for locale specific stuff    - constant cvs_version = "$Id: common_api.pike,v 1.3 2000/08/25 17:44:18 jhs Exp $"; + // Some defines for the translation system + // + //<locale-token project="mod_common_api">LOCALE</locale-token> + #define LOCALE(X,Y) _DEF_LOCALE("mod_common_api",X,Y) + // end of the locale related stuff +  + constant cvs_version="$Id: common_api.pike,v 1.4 2000/11/24 16:50:37 per Exp $";   //! This string (filtered to remove some ugly cvs id markup) shows up in   //! the roxen administration interface when handling module parameters in   //! developer mode (configured under "User Settings" below the Admin tab).   //! It will also serve as the basis for extracting version information of   //! the file in the inherit tree. Optional, but convenient, especially if   //! you use cvs for version control of your code.    - constant module_name = "Tamaroxchi"; + LocaleString module_name_locale = LOCALE(0,"Tamaroxchi");   //! The name that will show up in the module listings when adding modules   //! or viewing the modules of a virtual server. Keep it fairly informative   //! and unique, since this is the only means for identification of your   //! module in the most brief add module view mode.      constant module_type = MODULE_ZERO;   //! Module type (see server/etc/include/module.h). May be bitwise ored   //! (|) for hybrid modules. Hybrid modules must implement the required   //! API functions for all of the module types they are hybrids of.    - constant module_doc = "This module does nothing, but its inlined " -  "documentation gets imported into the roxen " -  "programmer manual. You really don't want to " -  "add this module to your virtual server, promise!"; + LocaleString module_doc_locale = LOCALE(0,"This module does nothing, but its " +  "inlined documentation gets imported " +  "into the roxen programmer manual. " +  "You really don't want to add this " +  "module to your virtual server, promise!");   //! The documentation string that will end up in the administration   //! interface view of the module just below the module name. Also shows   //! up in the more verbose add module views.      constant module_unique = 1;   //! 0 to allow multiple instances of the module per virtual server,   //! 1 to allow at most one.      constant thread_safe = 0;   //! Tell Roxen that this module is thread safe. That is, there is no
Roxen.git/server/modules/examples/common_api.pike:67:   //! administration settings page; convenient for triggering module   //! actions like flushing caches and the like.   //!   //! The indices of the returned mapping are the action descriptions that will   //! show up on each button (e g "flush cache"), and the corresponding values   //! are the callbacks for each button respectively. These functions may take   //! an optional RequestID argument, where this id object refers to the id   //! object in the admin interface sent with the request used to invoke the   //! action by the administrator.   { -  return ([ "Scratch me!" : scratch_me ]); +  return ([ LOCALE(0,"Scratch me!") : scratch_me ]);   }      void scratch_me()   // No, this is not a common API function. :-)   {    if(itching)    {    itching = 0; -  report_notice("Aah, that's good.\n"); +  report_notice(LOCALE(0,"Aah, that's good.\n"));    } else -  report_warning("Ouch!\n"); +  report_warning(LOCALE(0,"Ouch!\n"));   }    - string info( Configuration|void conf ) + LocaleString info( Configuration conf )   //! Implementing this function in your module is optional.   //!   //! When present, it returns a string that describes the module. - //! When absent, Roxen will use element <ref>module_doc</ref>. Unlike - //! module_doc, though, this information is only shown when the module + //! When absent, Roxen will use element <ref>module_doc_locale</ref>. Unlike + //! module_doc_locale, though, this information is only shown when the module   //! is present in a virtual server, so it won't show up when adding   //! modules to a server.   {    string mp = query_internal_location(); -  return "This string overrides the documentation string given in " -  "module_doc, but only once the module is added to a server. " -  "The module's internal mountpoint is found at <tt>" + -  mp + "</tt>."; +  +  return sprintf(LOCALE(0,"This string overrides the documentation string " +  "given in module_doc[_locale], but only once the " +  "module is added to a server. The module's internal " +  "mountpoint is found at <tt>%s</tt>"), mp );   }    - string|void check_variable(string variable, mixed set_to) + LocaleString check_variable(string variable, mixed set_to)   //! Custom checks of configuration variable validities. (optional)   //!   //! Check admin interface variables for sanity.   //!   //! "variable" is the name of the variable we're checking,   //! "set_to" is the value being tested. A return value of zero (0)   //! means all was OK, a string is used as an error message that the   //! administrator will be prompted with when given a second shot at   //! getting it right.   {    // find out what variable we're checking...    if(variable=="variable1")    {    // find out if it's a value we'll accept... if so, then just return.    if(set_to=="whatevervalueweaccept") -  return; +  return 0;    else // if it's not, return an error message. -  return "Sorry, we don't accept that value...\n"; +  return LOCALE(0,"Sorry, we don't accept that value.")+"\n";    }   }      void start(int occasion, Configuration conf)   //! Set up shop / perform some action when saving variables. (optional)   //!   //! If occasion is 0, we're being called when starting up the module,   //! to perform whatever actions necessary before we are able to service   //! requests. This call is received when the virtual server the module   //! belongs to gets initialized, just after the module is successfully   //! added by the administrator or when reloading the module.   //!   //! This method is also called with occasion set to 2 whenever the   //! configuration is saved, as in when some module variable has changed   //! and the administrator clicked "save" in the admin interface. This   //! also happens just before calling <ref>stop()</ref> upon reloading   //! the module.   { -  report_notice("Wow, I feel good!\n"); +  report_notice(LOCALE(0,"Wow, I feel good!")+"\n");   }      void stop()   //! Close down shop. (optional)   //!   //! Tidy up before the module is terminated. This method is called   //! when the administrator drops the module, reloads the module or   //! when the server is being shut down.   { -  report_notice("'Guess that's what I get for all this itching. *sigh*\n"); +  report_notice(LOCALE(0,"Guess that's what I get for all this itching. *sigh*")+"\n");   }      string status()   //! Tells some run-time status, statistics or similar to the curious   //! administrator. Implementing this function is optional.   //!   //! Returns a string of HTML that will be put in the admin interface   //! on the module's settings page just below the   //! <ref to=>documentation string</ref>.   {    string how_much;    itching += !random(3);       switch(itching)    { -  case 0: return "Feelin' fine."; -  case 1: how_much = "a bit."; break; -  case 2: how_much = "noticeably."; break; -  case 3: how_much = "quite a bit."; break; -  case 4: how_much = "really much."; break; -  case 5: how_much = "a lot."; break; -  case 6: how_much = "unbearably!"; break; -  default: how_much = "more than any sane person could stand!"; +  case 0: return LOCALE(0,"Feelin' fine."); +  case 1: how_much = LOCALE(0,"a bit"); break; +  case 2: how_much = LOCALE(0,"noticeably"); break; +  case 3: how_much = LOCALE(0,"quite a bit"); break; +  case 4: how_much = LOCALE(0,"really much"); break; +  case 5: how_much = LOCALE(0,"a lot"); break; +  case 6: how_much = LOCALE(0,"unbearably"); break; +  default: how_much = LOCALE(0,"more than any sane person could stand");    } -  return sprintf("I'm itching %s Please scratch me!", how_much); +  return sprintf(LOCALE(0,"I'm itching %s. Please scratch me!"), how_much);   }    - mapping|int|Stdio.File|void find_internal(string file, RequestID id) + mapping|int|Stdio.File find_internal(string file, RequestID id)   //! Internal magic location. May return a result mapping,   //! -1 for a directory indicator, an open file descriptor   //! or 0, signifying file not found / request not handled.   //! Similar to the MODULE_LOCATION <ref>find_file()</ref>   //! in most respects, except that the mountpoint is defined   //! by the virtual server, and mostly used for background   //! things where a URL doesn't show too much, such as when   //! generating background images and the like. To get the   //! internal mountpoint below which find_internal will handle   //! requests, use <ref>query_internal_location()</ref>.   {    return Roxen.http_string_answer(status());   }