Ferreteria/v0.5/dropin: Difference between revisions
< Ferreteria | v0.5
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 23: | Line 23: | ||
* '''cDropinLink''' | * '''cDropinLink''' | ||
** '''cDropinAction''' | ** '''cDropinAction''' | ||
* '''value\cDropin''' | |||
==Index File== | ==Index File== | ||
By convention, the index file is named <code>index.dropin.php</code>; this name can be changed via the global settings object. The index file's primary task is to define the <code>$arDropin</code> array, with the following elements: | By convention, the index file is named <code>index.dropin.php</code>; this name can be changed via the global settings object. The index file's primary task is to define the <code>$arDropin</code> array, with the following elements: | ||
Line 30: | Line 31: | ||
* '''date''': release date, in YYYY-MM-DD format | * '''date''': release date, in YYYY-MM-DD format | ||
* '''URL''': full URL to documentation | * '''URL''': full URL to documentation | ||
* '''db.spec''': name of class for database spec (must descend from cDatabaseSpec) | |||
** If omitted, uses the site's default db spec. | |||
** if NULL, Tabloid class is constructed without a db. | |||
* '''section''': array which defines how the dropin will be listed in the dropins bar | * '''section''': array which defines how the dropin will be listed in the dropins bar | ||
** '''title''': what to display at the top of the section | ** '''title''': what to display at the top of the section |
Revision as of 16:51, 8 November 2021
A dropin is a collection of code-files which can be included in a Ferreteria project by simply being "dropped in" to the appropriate folder (as designated by the local configuration). Each dropin must have an index file which tells Ferreteria what classes, actions, files, etc. are involved.
Process
loading/display
(ctDropInManager)
looks through each subfolder within the dropins folder.- For each folder found,
(ctDropInManager)->CheckFolder()
checks for an index file. - If the index file is found, it creates a
crcDropIndex
object and calls(crcDropIndex)->ProcessIndex()
->ProcessIndex()
loads the$arDropin
data into acrcDropIndex
object, which more or less encapsulates it.
URL interpretation
- in fcArrayLink:
- GetLinkURL() calls GetLinkArray()
- GetLinkArray() calls GetLinkArray_figured()
- GetLinkArray_figured() calls cDropinLink→GetLinkArray_self()
- in cDropinLink:
- OnEventAfter() calls PageEvent(); Render() calls AddPageRendering();
- PageEvent(), AddPageRendering(), and GetLinkArray_self() each call MakeActionObject() to get the table or record to act on.
- MakeActionObject() looks up a record or table object from the URL, and returns the result.
Classes
loading/display
These classes make heavy use of the ClassLoader system.
- csDropinManager: static class which runs the whole process; analogous (but not related) to csLoader
- cDropIndex: manages index to dropin library; descends from caLibrary
URL interpretation
- cDropinLink
- cDropinAction
- value\cDropin
Index File
By convention, the index file is named index.dropin.php
; this name can be changed via the global settings object. The index file's primary task is to define the $arDropin
array, with the following elements:
- name: the name of the dropin
- descr: one-line description
- version: version number
- date: release date, in YYYY-MM-DD format
- URL: full URL to documentation
- db.spec: name of class for database spec (must descend from cDatabaseSpec)
- If omitted, uses the site's default db spec.
- if NULL, Tabloid class is constructed without a db.
- section: array which defines how the dropin will be listed in the dropins bar
- title: what to display at the top of the section
- popup: (optional) text to appear when mouse hovers over the dropin name
- actions: array of items to appear within the section
- array[<item key>]: indexed array of information for a single actionable item
- class: name of action class to invoke
- text: text to display in section listing
- summary: one-line description of item (used for hover-over text but may appear in other places)
- perms: permits required in order to invoke this item. If user lacks permission, item will not be displayed.
- array[<item key>]: indexed array of information for a single actionable item
- classes: array of files and the classes they contain
- array[<relative filespec>]: collection array of classes available in the given code-file