Difference between revisions of "ACF mvc.lua reference"

From Alpine Linux
Jump to: navigation, search
(mvc.lua function reference)
(mvc.lua function reference)
Line 48: Line 48:
 
|}
 
|}
  
The returned table  has a .__index method that points to '''self''', so this table can
+
The returned table  has a .__index method that points to '''worker''', so this table can
 
inherit values from the parent table.
 
inherit values from the parent table.
  
Line 76: Line 76:
 
This allows, for instance, the application to set a default method that is available to all child controllers.  The reason the model looks to its parent worker table first is that controller methods are usually in the worker table, and models do not normally inherit from each other.
 
This allows, for instance, the application to set a default method that is available to all child controllers.  The reason the model looks to its parent worker table first is that controller methods are usually in the worker table, and models do not normally inherit from each other.
  
The ''new'' function will also call the ''mvc.on_load'' function, if it exists, to set up any necessary object state.  The calling code should be sure to call the ''destroy'' function when done with this object.
+
The calling code should be sure to call the ''destroy'' function when done with this object.
  
 
=== destroy ( self ) ===
 
=== destroy ( self ) ===
Line 86: Line 86:
 
The gateway for executing controller actions in a protected xpcall.
 
The gateway for executing controller actions in a protected xpcall.
  
# Checks if user has permission to access this controller/action by calling any existing ''worker.mvc.check_permission'' function
+
# If no controller specified, use default prefix/controller
## If no permission to action, redirects to default action
 
## If no permission to controller, redirects to default controller/action
 
 
# Creates a '''self:new ( prefix .. controller)''' mvc object
 
# Creates a '''self:new ( prefix .. controller)''' mvc object
 +
# If no action specified, use controller default_action
 
# runs any existing ''worker.mvc.pre_exec'' function
 
# runs any existing ''worker.mvc.pre_exec'' function
 
# runs the ''worker.'''action'''''
 
# runs the ''worker.'''action'''''
 
# runs any existing ''worker.mvc.post_exec'' function
 
# runs any existing ''worker.mvc.post_exec'' function
# sends the results of the ''worker.'''action''''' to the view_resolver
+
# gets the view function from ''view_resolver''
 
# calls ''destroy'' to destroy the mvc object
 
# calls ''destroy'' to destroy the mvc object
# and executes the view
+
# and executes the view with the results of the ''worker.'''action'''''
  
 
If an error occurs, an exception_handler function is run.  If possible, the exception handler of the new mvc object is run, otherwise ''self::exception_handler'' function handles the error.  If an exception occurs after creating the new mvc object, ''mvc.on_unload'' is guaranteed to run, but ''mvc.post_exec'' is not.
 
If an error occurs, an exception_handler function is run.  If possible, the exception handler of the new mvc object is run, otherwise ''self::exception_handler'' function handles the error.  If an exception occurs after creating the new mvc object, ''mvc.on_unload'' is guaranteed to run, but ''mvc.post_exec'' is not.
 
=== redirect ( self, action ) ===
 
 
Cause a redirect to the specified (or default) action. The actual redirection is defined in the application error handler. This function can be called by an action to redirect to another action rather than display it's own view.  Note: The controller post_exec function will not be called after redirect is called.
 
  
 
=== soft_require ( self, modname ) ===
 
=== soft_require ( self, modname ) ===

Revision as of 15:04, 15 May 2008

mvc.lua function reference

This lua module provides the basics for creating an mvc application. It is patterned loosely after the Ruby on Rails pattern - but much more simplistic.

The general pattern is to use the mvc new function to create a set of tables, and then use 'new within those tables to create sub "objects". By using metatable .__index methods, function references flow up through the parent tables. So the application is structured something like this:

ACF's MVC architecture dia source


new( self, modname )

Returns 3 values: an mvc table and 2 booleans ( true or false if the modname-controller and modname-model.lua were loaded)

The mvc table contains:


table used for comments .__index points to
conf configuration items only created if a conf table does not exist in a parent n/a
clientdata data sent from the client only created if a clientdata table does not exist in a parent n/a
worker the "controller" methods if modname is given, then modname-controller.lua module is loaded into this table. Otherwise, an empty table is returned. self (parent mvc object)
worker.mvc special methods run by the mvc dispatch function If the modname-controller.lua module does not initalize a .mvc table, an empty one is created self.mvc (parent mvc object's mvc table)
model the "model" methods if modname is given, then modname-model.lua module is loaded into this table. Otherwise, an empty table is returned. worker (this mvc object's worker table)

The returned table has a .__index method that points to worker, so this table can inherit values from the parent table.

If the modname-controller.lua contains a .mvc.on_load function, the function is run before new returns.

The .__index metamethods mean that this code will set up inheritance as shown in the diagram:

 require("mvc")
 MVC=mvc:new()
   APP=MVC:new()
    controller=APP:new()
      subcontroller=controller:new()

ACF's inheritance dia source

If you try to run subcontroller.model.somefunction(), and it does not exist, the inheritance will look for somefunction() in ...

  1. subcontroller.worker
  2. controller
  3. controller.worker
  4. APP
  5. APP.worker
  6. MVC
  7. MVC.worker


This allows, for instance, the application to set a default method that is available to all child controllers. The reason the model looks to its parent worker table first is that controller methods are usually in the worker table, and models do not normally inherit from each other.

The calling code should be sure to call the destroy function when done with this object.

destroy ( self )

Calls the mvc.on_unload function, if it exists, to close any resources opened by the object.

dispatch ( self, prefix, controller, action )

The gateway for executing controller actions in a protected xpcall.

  1. If no controller specified, use default prefix/controller
  2. Creates a self:new ( prefix .. controller) mvc object
  3. If no action specified, use controller default_action
  4. runs any existing worker.mvc.pre_exec function
  5. runs the worker.action
  6. runs any existing worker.mvc.post_exec function
  7. gets the view function from view_resolver
  8. calls destroy to destroy the mvc object
  9. and executes the view with the results of the worker.action

If an error occurs, an exception_handler function is run. If possible, the exception handler of the new mvc object is run, otherwise self::exception_handler function handles the error. If an exception occurs after creating the new mvc object, mvc.on_unload is guaranteed to run, but mvc.post_exec is not.

soft_require ( self, modname )

Looks for modname.lua in self.conf.appdir and returns the results of a require() If the modname does not exist, returns nil.

This function allows modules to be loaded without generating an exception if they do not exist.

basename ( string, suffix )

Lua implementation of basename.1 Returns string with any leading directory components removed. If specified, also remove a trailing suffix.

dirname ( string )

Lua implementation of dirname.1 Returns string with its trailing /component removed.

read_config ( self, modname )

Looks in various places for a modname.conf file and parses its contents into the self.conf table.

parse_path_info ( string )

Returns 3 strings: a prefix, controller, and action. Given a string in the format of a URI or pathspec, returns the basename as the action, the last component of the dirname as the controller, and the rest as the prefix. Missing components are returned as empty strings.

view_resolver (self )

Returns a function that prints "you do not have a view resolver". The application should provide a more robust view_resolver.

soft_traceback ( self, message )

If called with no arguments, returns a debug.traceback, otherwise returns "message".

exception_handler ( self, message )

Prints an error message. Called if the xpcall in dispatch has an error. This is the exception_handler of last resort. The application should provide a more robust exception handler.