DokuWiki

It's better when it's simple

User Tools

Site Tools


plugin:components

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
plugin:components [2018-05-29 23:03] – [Installation] Klap-inplugin:components [2018-10-13 18:56] (current) – new download url (from GitHub) Aleksandr
Line 2: Line 2:
  
 ---- plugin ---- ---- plugin ----
-description: Defines some easy interfaces for AJAX function handlers and action handlers/renderers.+description: Defines some easy interfaces for AJAX function handlers and action handlers/renderers
 author     : jma  author     : jma 
 email      : junlingm@gmail.com  email      : junlingm@gmail.com 
Line 13: Line 13:
 tags       : action, ajax tags       : action, ajax
  
-downloadurl: http://rsv.math.uvic.ca/components.zip+downloadurl: https://github.com/roverrobot/components/zipball/master
 bugtracker : https://github.com/roverrobot/components/issues bugtracker : https://github.com/roverrobot/components/issues
 sourcerepo : https://github.com/roverrobot/components sourcerepo : https://github.com/roverrobot/components
Line 27: Line 27:
 ===== Examples/Usage ===== ===== Examples/Usage =====
  
-=====New action handlers/renderers==+===== New action handlers/renderers ===== 
 All new action handlers should be put under your plugin's //commands// folder, with a php script name identical to your command name. For example, if you want to implement an example_action action for your plugin named example, you need to put commands/example.php under your plugin folder. This defines an action example.example_action. Your script should as lead extend the Doku_Action class, which defines a handler, and its handle class can return an action name to change the processing to the action that you returned. If you do not change to another action, you must define a renderer for this action by extending the Doku_Action_Renderer class. Its xhtml() function's standard output is the action rendering output. All new action handlers should be put under your plugin's //commands// folder, with a php script name identical to your command name. For example, if you want to implement an example_action action for your plugin named example, you need to put commands/example.php under your plugin folder. This defines an action example.example_action. Your script should as lead extend the Doku_Action class, which defines a handler, and its handle class can return an action name to change the processing to the action that you returned. If you do not change to another action, you must define a renderer for this action by extending the Doku_Action_Renderer class. Its xhtml() function's standard output is the action rendering output.
  
-See the commands/example.php in this source repo. To see this in action, add a link to ?do=components.example&tag=pre to your page.+See the commands/example.php in this source repo. To see this in action, add a link to ''%%?do=components.example&tag=pre%%'' to your page. 
 + 
 +===== AJAX function call handler =====
  
-=====AJAX function call handler== 
 All new AJAX function call should extend the Doku_AJAX class, and be put in your plugin's //ajax// folder, with a name identical to your AJAX function. For example, if you want to implement a function example_call in your plugin named example, you should name the script ajax/example.php. This defines an AJAX function call named example.example_call. The caller should pass in a data object that contains All new AJAX function call should extend the Doku_AJAX class, and be put in your plugin's //ajax// folder, with a name identical to your AJAX function. For example, if you want to implement a function example_call in your plugin named example, you should name the script ajax/example.php. This defines an AJAX function call named example.example_call. The caller should pass in a data object that contains
  
Line 46: Line 48:
 Your ajax handler class should implement the call($parmas) function, which returns a PHP array/string/number/bool, this return value is automatically encoded as JSON and sent to the client. The $params argument is an array holding the passed in parameters. To specify the parameters, the constructor should call the parent's constructor with two parameters, the first is an array of required parameters, keys are the parameter names, and values are the parameter types. The second is an optional parameter array in the same format. For example, Your ajax handler class should implement the call($parmas) function, which returns a PHP array/string/number/bool, this return value is automatically encoded as JSON and sent to the client. The $params argument is an array holding the passed in parameters. To specify the parameters, the constructor should call the parent's constructor with two parameters, the first is an array of required parameters, keys are the parameter names, and values are the parameter types. The second is an optional parameter array in the same format. For example,
  
-<code>+<code php>
 public function __construct() { public function __construct() {
     parent::__construct(     parent::__construct(
Line 54: Line 56:
 </code> </code>
  
-See the ajax/example.php and script.js for an example. To see the example in action, put <slice from="1" to="5"/> in your wiki to see aslice of the first 5 characters in your raw wiki text. +See the ajax/example.php and script.js for an example. To see the example in action, put ''%%<slice from="1" to="5"/>%%'' in your wiki to see aslice of the first 5 characters in your raw wiki text.  
 ===== Development ===== ===== Development =====
  
plugin/components.txt · Last modified: 2018-10-13 18:56 by Aleksandr

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki