FreeRadiantBunny Agent Classes List

icon

The Free Radiant Bunny software exists to help aid people who are growing food with a permaculture design method. To achieve this we design. At the core of our design is a set of classes which model the abstract problem domain. You heard right!

There is a set of classes, call them "agent classes" and let each of these classes be accessed by the user, thus representing a kind of view upon the data of the database. More importantly perhaps, each of these classes is represented by a database table. Enter multiple perspectives.

At one level, the whole purpose of the classes (and its implied API) is to ask the database management system to CRUD upon the database.

So, this is our first truism, that each Agent Classes should have a corresponding database table. This design guideline is a way of specifying some code for the database, creating a concept that says an Agent Class is associated with a php file, and the names only differ by the capitalization of the letters. The matching is important because a given class file is an API to its corresponding database table.

That certain traits are common upon all Agent Classes means that there is a class library of parent classes that each Agent Classes inherits to different degrees. A very plain starter class from the library is the scrubber class, allowing some basic functions for the agent such as accessing the database and filtering input. The scrubber class is an empirical conduit of data moving inward and outward.

In addition, the text description of each class is stored with its own file on the file system. This creates a link between database table and software class and computer file. In this way each agent class has 3 aspects, each with its own context inside out networked computers.

List of FreeRadiantBunny Agent Classes

The agent classes are listed in the table below. As of database schema 1.6, there are 111 tables in the database. Speaking SQL then one might say: select count(*) from information_schema.tables where table_schema = 'public';

The list below also serves as a menu to the agent class documentation. Click on the name (or id) and you will go to the documentation for that given agent class.

This is a list of the Agent Classes.

Here is a simple list of the table_name for the tables associated with the version 1.6 Agent Classes of FreeRadiantBunny:

accounts
agricultural_types
albums
applications
asset_types
blog_posts
book_clips
books
budget_accounts
budgets
builds
business_plan_texts
calendars
categories
classes
colors
customers
databases
designers
design_instances
design_order_items
design_orders
designs
documentations
domain_measurements
domains
email_addresses
events
field_tests
goal_statements
guest_passes
harvests
host_applications
host_databases
host_email_addresses
hosts
hyperlink_reasons
hyperlinks
hyperlink_tags
images
indiegoals
invoice_lines
invoices
journals
kernel_theories
kernel_theory_sets
keywords
land_beds
land_city_states
land_farmers
lands
land_traits
land_width_lengths
location_workdates
machines
maxonomies
moneymakers
object_images
observations
payments
permaculture_topics
pickup_details
pickup_plants
pickups
plant_aliases
plant_attributes
plant_categories
plant_families
plant_histories
plant_history_events
plant_list_plants
plant_lists
plants
plant_units
postings
potentials
prices
processes
process_flows
products
projects
reasons
scene_elements
searches
seed_packets
shares
shifts
soil_areas
soil_tests
songs
spacings
stakeholders
storages
styles
suppliers
tags
tenperdays
tickets
timecards
tools
units
usernames
varieties
visits
webmasters
webpage_maxonomies
webpage_moneymakers
webpages
webpage_tags
yields
zachmans

See Agent Classes associated with FreeRadiantBunny database schema 1.2

Related Information

From here, there are two ways in which you could go: larger scope or smaller scope.

icon

Larger Scope: Check out the Directories

To go larger scope, you could check out the over-all design of the files in the application, of which the agent class files (described on this page) are just a part. To understand that larger scope, check out the directories.

Said another way: this page described just one type of file in the application. To learn more about all of the files in the application, visit the directories.


icon

Smaller Scope: Check out the Subsystems

To go smaller scope, you could check out the subsystems. Instead of viewing all of the Agent Classes, view a subset of the Agent Classes as selected by designer-assigned "subsystem" categorization.

This small scope was developed based upon the divide and conquere tactic. To aid the person learning the Agent Classes, the classes have been grouped. The agents have been categorized into subsystems based upon the natural qualities of the classes and how they work together. The subsystem categorizaing aims to aid the learning of the classes by making it easier to mentally manage a large list of agent classes. So, if you are aiming to learn the Agent Classes list, you could visit subsystems.

Or, if you wanted to jump that step, you could go directly to one of the subsystems. Check out the subsystems and dive right into learning about a particular subsystem. The most important tables in the database contain the projects and goal_statements data. Using the Motivation Model as a design theory, tables for business_plant_texts and processes round out the core data of an initiative. Then the processes are brought to action with the scene_elements table.To learn about these classes, visit the Motivational Model Subsystem.



freeradiantbunny.org home