Disclaimer: This message has been sent to multiple lists in spite of
keeping users and tech authors informed about the new features
available. I apologize if you receive multiple copies of this message
I'm so excited to announce the latest release (1.3.1) of TracGviz
plugin. This package (plugin) puts together three great platforms
(Trac, iGoogle gadgets, and Google Visualization API) by providing
components so that Trac be able to use widgets and related
technologies provided by Google. This means that
- It allows to feed data managed by Trac to widgets based on Google
Visualisation API.
- It allows embedding iGoogle Gadgets in wiki pages using WikiFormatting.
This time the focus has been given to :
- include many (useful) data sources relying on core Trac components,
- integrate the plugin with Trac Permissions system
- ease the task of editing (using WikiFormatting) the wiki pages full
of gadgets
(especially Google Visualization Gadgets).
I am sure that this version will be much more useful. In case
something wrong's been detected please create a ticket [1]_ including
all the relevant information.
What's new in version 1.3.1
-----------------------------
- Assertions concerning permissions are supported, but not directly.
They are delegated to the underlying layers on top of which the data
sources have been implemented (e.g. XML-RPC handlers).
- GadgetLinksDispatcher has been renamed. Now it is known as
LinksTreeDispatcher. It supports multiple root namespaces
(i.e. so far `gadgets`, and `gviz`) as well as the former hierarchy
of links.
- IGadgetTracLinksResolver now is known as ITracLinksItem interface.
From now on its `get_link_resolvers` method *has to* return the
name of the root namespace (e.g. `gviz`).
- New ! TracLinks expressions for Google Apps Reporting Visualization
API have been implemented. It may be necessary to be logged in to
the Google Apps control panel in order to access the data.
Syntax ->
`gviz:google:apps:<report_key>@<report_date>:<domain>[?tq=<query>]`
- New ! It is possible to make reference to Google Spreadsheets using
TracLinks expressions starting with `gviz:google:sheet:` prefix.
They also support `range` attribute -to select only specific cells-
and `headers` option -in order to specify how many rows are header
rows-. Syntax ->
`gviz:google:sheet:<sheet_id>[:<top_cell>-<bottom_cell>][?headers=<number>]`
- New ! It is possible to make reference to Google's standard
visualizations using TracLinks expressions starting with
`gadget:google:modules:` prefix. Syntax ->
`gadget:google:modules:<chart_name>`
- TracLinks expansion for custom arguments in iGoogleGadget macro is
not a dream anymore. You can enclose TracLinks expressions in
brackets and assign such values to custom arguments. In such cases
the macro will perform the expansion looking for the target URL.
Hence the first expression shown below can be written now as shown
in the second example. Both of them will embed in the wiki page a
motion chart displaying the data found in cells B3-G17 inside
Google Spreadsheet number 1234.
[[iGoogleGadget(url=http://www.google.com/ig/modules/motionchart.xml,
_table_query_url=http://spreadsheets.google.com/tq?range=B3%3AG17&key=1234,
_table_query_refresh_interval=5)]]
[[iGoogleGadget(url=gadget:google:modules:motionchart,
_table_query_url=[gviz:google:sheet:1234:B3-G17],
_table_query_refresh_interval=5)]]
- All links to third-party sites resulting from expanding a
TracLinks expression are rendered in wiki pages with the well-know
icon `[]->`.
- Instances of GVizXMLRPCAdapter now can implement the method
`xmlrpc_namespace`. It is similar to the former `gviz_namespace`
method, but returns the XML-RPC namespace. This way multiple data
sources can be implemented using the services provided by a single
XML-RPC component.
- New ! GVizSearchFiltersProvider now allows to list all search
filters installed in a Trac environment.
- New ! It is possible to document the parameters accepted by a data
source using `gviz_param` decorator.
- GVizProviderList macro now displays the parameters accepted by
data providers.
- Now it is much easier to handle unicode, date & time and values
returned by the different data sources. From now on there is no
need to convert instances of xmlrpclib.DateTime in to instances of
datetime.date*
- New ! GVizSearchProvider now gives access to search results
returned by Trac built-in search engine. You can specify a query
string and control the search filters (e.g. `wiki`, `ticket`,
`milestone`, `pydoc`) in use.
- New ! You can get the names of the actions that can be performed on
a given ticket using `ticket/actions` data source.
- New ! You can get all the meta-data describing ticket fields by
accessing `ticket/fields` data source.
- New ! GVizTicketChangeLog provides a detailed changelog in order
to know the modifications made to different tickets. The data
source is available at `ticket/log`.
- New ! GVizTicketAttachments provides detailed information about the
files attached to different tickets. The data source is available
at `ticket/attachments`.
- New ! GVizTimelineFilters provides detailed information about the
different filters offered by those sources contributing to the
timeline. The data source is available at `timeline/filters`.
- New ! GVizTimelineEvents provides detailed information about the
timed events reported by those sources contributing to the
timeline. It supports time slicing, and filtering. The data source
is available at `timeline/log`.
- GVizMilestoneProvider has been enhanced. Formerly it just offered
the milestone name, due and completed time, plus its description.
Now it also contains some statistics on groups of tickets like
those displayed in the roadmap views. This includes the amount of
work that's been done, the units used to measure the indicators,
percent of the whole work that's been already done, the number of
active and closed tickets, and the percent they represent with
respect to the total number of tickets.
- New ! GVizWikiPages provides detailed information about the wiki
pages found in the Trac environment. It supports multiple features,
being timed filters, page selection and multiple versions, just a
few of them. The data source is available at `wiki/index`.
- New ! GVizWikiAttachments provides detailed information about the
files attached to wiki pages found in the Trac environment.
The data source is available at `wiki/attachments`.
- The right MIME type (i.e. `application/json`) is sent back to the
client in the HTTP response when JSON is requested. This
is consistent with RFC xxx.
What's new in version 1.2.3
-----------------------------
- Minor changes ... bah!
What's new in version 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``.
Pending issues
=============
- The timeline provider doesnt provide all the timed events related to
tickets (especially attachments), since that's not supported by the underlying
components. This is opposite to the similar behavior of Wiki
timeline provider
- which includes the attachments modifications - so it is very
possible that a
solution could be given.
- The ticket changes provider is not accurate enough since it seems that adding
attachments is not action doesnt update some ticket fields .
All this has been asked in `trac-users` group some time ago, but still
there's no reply. Once a solution be at hand, the plugin will be
updated ASAP in order to «fill the gap».
Useful links
===============
.. [1] Report an issue
(https://opensvn.csie.org/traccgi/swlcu/newticket?component=plugin_trac_gviz)
.. [2] Trac integration with Google Visualization API
(https://opensvn.csie.org/traccgi/swlcu/wiki/En/Devel/TracGViz)
.. [3] TracGViz 1.3.1 @ PyPI
(http://pypi.python.org/pypi?:action=search&term=TracGViz&submit=search)
.. [4] Direct download link
(http://pypi.python.org/packages/2.5/T/TracGViz/TracGViz-1.3.1-py2.5.egg#md5=2684a25ff10d1a91c0eccbaedce2dae5)
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Un mundo hermoso gracias al producto Z: The World of Goo -
http://feedproxy.google.com/~r/simelo-es/~3/5Rlq3bHsnHQ/un-mundo-increiblemente-hermoso-gracias_12.html
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
