There are two main ways to customize the behavior of Widgy and existing widgets.
The first is through the
WidgySite is a centralized source of configuration for
a Widgy instance, much like Django’s
AdminSite. You can also configure each
widget’s behavior by subclassing it with a proxy.
- tracks installed widgets
- stores URLs
- provides authorization
- allows centralized overriding of compatibility between components
- accomodates for multiple instances of widgy
Proxying a Widget¶
Widgy uses a special subclass of
GenericForeignKey that supports
retrieving proxy models. Subclassing a model as a proxy is a lightweight method
for providing custom behavior for widgets that you don’t control.
A more in-depth tutorial on proxying widgets can be found at the
Proxy Widgy Model Tutorial.