Ferreteria/v0.5/dropin

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.

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
• 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.
• classes: array of files and the classes they contain
  • array[<relative filespec>]: collection array of classes available in the given code-file

Process

• (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 a crcDropIndex object, which more or less encapsulates it.