This page attempts to document the current (December 2007) state of development of TurboGears. Hover over component names to see a longer description. Select a TurboGears version to see what TG uses for each component (JavaScript is required). The components are colour coded based on stability. Hover over non-green components to see why they're not green.
[1] SQLAlchemy/Elixir can be used as an alternative
[2] Several alternative template engines can be used
[3] ToscaWidgets and ToscaWidgetsForms can be used instead.
[4] Other JavaScript libraries can be used, although some widgets depend on MochiKit
[7] Paginate is arguably a helper function, and webhelpers can be used.
[1] SQLObject can be used as an alternative
[2] Several alternative template engines can be used, some requiring a specific integration package, e.g. TurboKid
[3] ToscaWidgets and ToscaWidgetsForms can be used instead.
[4] Other JavaScript libraries can be used, although some widgets depend on MochiKit
[7] Paginate is arguably a helper function, and webhelpers can be used.
[1] SQLObject can be used as an alternative
[2] Several alternative template engines can be used, some requiring a specific integration package, e.g. TurboKid
[3] TG Widgets will be available as an alternative.
[4] Other JavaScript libraries can be used, although some widgets depend on MochiKit
[5] Routes can also be used.
[6] CherryPy 3 can also be used.
[7] Paginate is arguably a helper function, and webhelpers can be used.
The colour takes some consideration of the importance of the component in the framework, e.g. FastData could be red, but because it's non-critical is only amber. The colour does not consider functionality, e.g. deployment is green because although we're missing potential functionality, generally people seem to be able to deploy TG apps ok.