TracGViz 1.2.2

The meaning of the different columns in the table returned by GViz data sources as well as the default labels can be documented using gviz_col. This function is compliant with annotations as defined by PEP 3107.

Data sources’ documentation can be included in wiki pages using GVizDataSource macro.

Docstrings have changed a little.

Bug fixed: Until now, if no protocol handler was enabled then the project environment became broken, because of a ValueError exception being raised. This is annoying and therefore has been fixed. Now if a URL having gviz prefix is accessed and there’s no protocol handler available, a Not Found (404) HTTP response is returned to the caller with message Unable to find any protocol handler.

The gviz_api module (version 1.0.0) is redistributed in this package. This has been made to fall back to this implementation if no other has been previously installed.

From this version on, the work is licensed under the Apache License. See COPYRIGHT and NOTICE for details.

Babel is no longer a dependency.

Full TracLinks expansion in iGoogleGadget macro parameters.

iGoogle gadgets logo included as image resource. Borders template updated.

Bug fixed: Until now, if an underlying RPC handler was disabled then environment initialization failed since an annoying ValueError was raised. That won’t happen anymore. Now, once a method is requested on the corresponding GViz data source provider, a GViz error response is returned to the caller containing an explanatory message.

Added support to display iGoogle gadgets using WikiFormatting extensions (i.e. iGoogleGadget macro).

Added support to upload and host custom image-based gadget borders inside the project environment.

Bug fixed : All requests handled by IGVizDataProvider implementors not having tq and tqx parameters (e.g. http://myserver.com/project_name/gviz/ticket/status) now output the correct data. Previously when accessing these URLs the HTTP response body was an HTML error page.

Support has been added to implement Google Visualization API data sources by reusing existing Trac XML RPC components.

Some (but not all) data sources for Trac ticket system are provided. They are based on the following Trac XML-RPC providers (listed hereafter by namespace): ticket.milestone, ticket.severity, ticket.type, ticket.resolution, ticket.priority, ticket.component, ticket.version, ticket.status.

An architecture is available so as to provide a project’s data in the format specified in Google Visualization API protocol specification (version 0.5) api.TracGVizSystem.

Multiple protocol handlers (e.g. for different versions, and protocol evolution) are allowed by implementing the interface api.IGVizProtocolHandler. There is native support for version 0.5 of Google Visualization API protocol through GViz_0_5.

It is possible to register new data sources by implementing the interface api.IGVizDataProvider

A pluggable architecture is at hand to retrieve table contents in multiple formats by merely implementing api.IGVizTableEncoder interface. The following formats are supported : JSON (class stdfmt.GVizJsonEncoder), HTML (class stdfmt.GVizHtmlEncoder), CSV (class stdfmt.GVizCSVEncoder).

The exception conditions mentioned in Google Visualization API protocol specification (version 0.5) have been identified.