Albatross - Revision history

PeterHarding at 23:42, 27 August 2010

2010-08-27T23:42:47Z

← Older revision		Revision as of 09:42, 28 August 2010
Line 29:		Line 29:
	[[Category:Internet]]		[[Category:Internet]]
	[[Category:Python]]		[[Category:Python]]
			[[Category:Albatross]]

PeterHarding at 23:42, 27 August 2010

2010-08-27T23:42:18Z

← Older revision		Revision as of 09:42, 28 August 2010
Line 28:		Line 28:
	[[Category:SOFTWARE]]		[[Category:SOFTWARE]]
	[[Category:Internet]]		[[Category:Internet]]
			[[Category:Python]]

PeterHarding at 03:19, 25 January 2008

2008-01-25T03:19:35Z

PeterHarding at 03:19, 25 January 2008

2008-01-25T03:19:06Z

← Older revision		Revision as of 13:19, 25 January 2008
Line 13:		Line 13:
	* The ability to place Python code for each page in a dynamically loaded module, or to place each page in it's own class in a single mainline.		* The ability to place Python code for each page in a dynamically loaded module, or to place each page in it's own class in a single mainline.
	*Optional sessions, which can be either:		*Optional sessions, which can be either:
	o Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),		* Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),
	o Server-side sessions via a supplied TCP session server,		* Server-side sessions via a supplied TCP session server,
	o Server-side file based session store.		* Server-side file based session store.
	*Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.		*Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.
	*Over 120 pages of documentation including many installable samples.		*Over 120 pages of documentation including many installable samples.

	A primary design goal of Albatross is that it be small and easy to use and extend. The toolkit application functionality is defined by a collection of fine grained mixin classes. Eight different application types and four different execution contexts are prepackaged, allowing you to define your own drop in replacements for any of the ~~[[Python - mixin]] mixins to~~ alter any aspect of the toolkit semantics.		A primary design goal of Albatross is that it be small and easy to use and extend. The toolkit application functionality is defined by a collection of fine grained mixin (See [[Python - Mixin Classes]]) classes. Eight different application types and four different execution contexts are prepackaged, allowing you to define your own drop in replacements for any of the mixinsto alter any aspect of the toolkit semantics.

	Object Craft developed Albatross because there was nothing available with the same capabilities which they could use for consulting work. For this reason the toolkit is important to Object Craft and so is actively maintained and developed.		Object Craft developed Albatross because there was nothing available with the same capabilities which they could use for consulting work. For this reason the toolkit is important to Object Craft and so is actively maintained and developed.

PeterHarding at 03:17, 25 January 2008

2008-01-25T03:17:12Z

@@ Line 1: / Line 1: @@
-=References=
+=Albatross - a Toolkit for Stateful Web Applications=
-* http://www.object-craft.com.au/projects/albatross/
+Albatross is a small and flexible Python toolkit for developing highly stateful web applications. The toolkit has been designed to take a lot of the pain out of constructing intranet applications although you can also use Albatross for deploying publicly accessed web applications.
 [[Category:SOFTWARE]]
 [[Category:Internet]]

PeterHarding at 03:15, 25 January 2008

2008-01-25T03:15:28Z

← Older revision		Revision as of 13:15, 25 January 2008
Line 1:		Line 1:
	=References=		=References=

	* http://www.object-craft.com.au/albatross/		* http://www.object-craft.com.au/projects/albatross/

	[[Category:SOFTWARE]]		[[Category:SOFTWARE]]
	[[Category:Internet]]		[[Category:Internet]]

PeterHarding: New page: =References= * http://www.object-craft.com.au/albatross/ Category:SOFTWARE Category:Internet

2008-01-25T03:15:11Z

New page: =References= * http://www.object-craft.com.au/albatross/ Category:SOFTWARE Category:Internet

New page

=References=

* http://www.object-craft.com.au/albatross/

[[Category:SOFTWARE]]
[[Category:Internet]]

← Older revision		Revision as of 13:19, 25 January 2008
Line 5:		Line 5:

	In slightly less than 2600 lines of Python (according to pycount), you get the following:		In slightly less than 2600 lines of Python (according to pycount), you get the following:

	* An extensible HTML templating system similar to DTML that promotes separation of presentation and implementation for improved program maintainability. The templating system includes tags for:		* An extensible HTML templating system similar to DTML that promotes separation of presentation and implementation for improved program maintainability. The templating system includes tags for:
	o Conditional processing,		o Conditional processing,
	o Macro definition and expansion,		o Macro definition and expansion,
	o Sequence iteration and pagination,		o Sequence iteration and pagination,
	o Tree browsing,		o Tree browsing,
	o Lookup tables to translate Python values to arbitrary template text.		o Lookup tables to translate Python values to arbitrary template text.
	* The ability to place Python code for each page in a dynamically loaded module, or to place each page in it's own class in a single mainline.		* The ability to place Python code for each page in a dynamically loaded module, or to place each page in it's own class in a single mainline.
	*Optional sessions, which can be either:		*Optional sessions, which can be either:
	* Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),		o Browser based sessions via automatically generated hidden form fields (cryptographically signed to ensure integrity),
	* Server-side sessions via a supplied TCP session server,		o Server-side sessions via a supplied TCP session server,
	* Server-side file based session store.		o Server-side file based session store.
	*Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.		*Applications that can be deployed as either CGI programs or as mod_python module with minor changes to program mainline. Custom deployment can be achieved by developing your own Request class.
	*Over 120 pages of documentation including many installable samples.		*Over 120 pages of documentation including many installable samples.