Extending Toaster - Revision history

Ddalex: /* How to create a Toaster extension */

2014-06-25T14:34:12Z

How to create a Toaster extension

← Older revision		Revision as of 14:34, 25 June 2014
Line 37:		Line 37:
	* limit all patches touching your application only to your application; this will ease the rebase (see below)		* limit all patches touching your application only to your application; this will ease the rebase (see below)
	* when updating Toaster, use rebase (as opposed to merge) to move your applications' patches on top of a new Toaster version		* when updating Toaster, use rebase (as opposed to merge) to move your applications' patches on top of a new Toaster version
			* database management functions will be automatically enabled for your applications

Ddalex at 14:33, 25 June 2014

2014-06-25T14:33:07Z

@@ Line 13: / Line 13: @@
 * bldcontrol - application containing the code to start and control bitbake in managed mode
-== Requirements for extensibility ==
+== Features for extensibility ==
-== Toaster points - a proposal ==
+As a web application, the code is driven by HTTP requests. In order to use your handlers, Toaster will automatically redirect requests starting "{modulename}/" to the patterns listed in the "{modulename}/urls.py" file, where "{modulename}" is the name of the application you're creating.

Ddalex: /* Django extensibility model */

2014-06-25T14:10:42Z

Django extensibility model

← Older revision		Revision as of 14:10, 25 June 2014
Line 11:		Line 11:
	* toastergui - the Toaster frontend for build inspection		* toastergui - the Toaster frontend for build inspection
	* orm - a separate application just to hold the persistent object models		* orm - a separate application just to hold the persistent object models
			* bldcontrol - application containing the code to start and control bitbake in managed mode

	== Requirements for extensibility ==		== Requirements for extensibility ==

Ddalex at 15:56, 15 May 2014

2014-05-15T15:56:16Z

← Older revision		Revision as of 15:56, 15 May 2014
Line 1:		Line 1:
	In order to promote customizability of Toaster, we have here a set of guidelines on how to add functionality and customize the Toaster web interface.		In order to promote customizability of Toaster, we have here a set of guidelines on how to add functionality and customize the Toaster web interface.

	* Django extensibility model *		== Django extensibility model ==

	Django, per se, does not offer any extensibility / customization model. Being a framework for hosted application, it is assumed that the host will have complete access for modification. Because Django is not envisioned to be distributed / portable / reusable, there is no need to support insertion of 3rd party content after deployment, or to alter the user flows by 3rd party contributors. However, we can use Django modularization support to add custom extensibility capabilities to our distributable project.		Django, per se, does not offer any extensibility / customization model. Being a framework for hosted application, it is assumed that the host will have complete access for modification. Because Django is not envisioned to be distributed / portable / reusable, there is no need to support insertion of 3rd party content after deployment, or to alter the user flows by 3rd party contributors. However, we can use Django modularization support to add custom extensibility capabilities to our distributable project.
Line 13:		Line 13:


	* Requirements for extensibility *		== Requirements for extensibility ==



	* Toaster points - a proposal *		== Toaster points - a proposal ==

Ddalex: Created page with "In order to promote customizability of Toaster, we have here a set of guidelines on how to add functionality and customize the Toaster web interface. * Django extensibility mode..."

2014-05-15T15:55:41Z

Created page with "In order to promote customizability of Toaster, we have here a set of guidelines on how to add functionality and customize the Toaster web interface. * Django extensibility mode..."

New page

In order to promote customizability of Toaster, we have here a set of guidelines on how to add functionality and customize the Toaster web interface.

* Django extensibility model *

Django, per se, does not offer any extensibility / customization model. Being a framework for hosted application, it is assumed that the host will have complete access for modification. Because Django is not envisioned to be distributed / portable / reusable, there is no need to support insertion of 3rd party content after deployment, or to alter the user flows by 3rd party contributors. However, we can use Django modularization support to add custom extensibility capabilities to our distributable project.

A Django project supports a number of "applications", intended to allow developers to separate different scopes of a web site in different applications. For example, the custom admin interface for a web site should live in a different application than the normal user-facing site.

Toaster consists of a basic set of applications - we have:
* bldviewer - the "simple" web interface, for development purposes only
* toastergui - the Toaster frontend for build inspection
* orm - a separate application just to hold the persistent object models

* Requirements for extensibility *

* Toaster points - a proposal *