.. contents:: Table of Contents
-ToscaWidgets itself has a few different configuration settings. Here's a few
+ToscaWidgets itself has a few different configuration settings. Here's a few
ways you can modify the way ToscaWidgets renders content.
-TurboGears supports both the 0.9.x branches of ToscaWidgets and the 2.x code.
+TW 0.9.9+ support resource variants. This allows the developers to point TW at a different
+run "debug" mode on your js files in development, but "minified" on production for speedups.
+You can set this variable in two ways. Add the following line to your .ini file as::
+Note that this only works if your js wrapper has actually been set up to have multiple variants.
+If the library does not have variants, this variable will be ignored.
+TurboGears supports both the 0.9.x branches of ToscaWidgets and the 2.x TW code.
ToscaWidgets is currently at a crossroads, with the 0.9.x branch being a very stable
codebase, and TW2 providing speed benefits, easier use, and a simpler, easier to debug
codebase. TW2 is currently in alpha, so it's up to you to determine it's level
entry, ToscaWidgets handles server requests that are directed directly to the widget
itself, bypassing the TG Controllers. On exit, TW middleware provides resource injection,
-automatically. Both TW 0.9.x and TW 2.x support this usage. There is more information
+automatically. Both TW 0.9.x and TW 2.x support this usage. There is more information
on [tw_middleware_] and [tw2_middleware_].
.. _tw_middleware: http://toscawidgets.org/documentation/ToscaWidgets/modules/resource_injector.html