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
Hello once again ! Few days after releasing TracGViz 1.3.3 the new version TracGViz 1.3.4 is out there. This package (plugin) provides components so that Trac may be integrated with Google Visualization API and other technologies provided by Google (e.g. iGoogle gadgets). This means that it 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. Therefore : - It allows to feed data managed by Trac to widgets based on Google Visualization API. - It allows to embed iGoogle Gadgets in wiki pages using WikiFormatting. This is essentially a bug fix release so this time the focus has been given to fix serious bugs present in TracGViz 1.3.3 (especially some related to VersionControlRPC using Hg, and all the data source depending on it). I apologize if this caused any trouble. Therefore it is very important to upgrade to this version. I am sure that it will be much more useful. In case something wrong's been detected please create a ticket [1]_ including all the relevant information. Coming soon ============== - Support for GViz API QL - Functional tests - reStructuredText encoder - Perhaps there are no data sources left, but if you find one, will be included ;o) - More docs & tutorials ... - more ... see CHANGES and TODO files for details ;) What's new in version 1.3.4 --------------------------- - New ! `GVizQuickJumpEntries` offers data about interesting places in the repository (a.k.a. `quick jump entries`). This includes tags and branches, for instance. The data is provided by VersionControlRPC. - Bug fixed: When using Hg backend, the code in version 1.3.3 in order to list revisions (VCS RPC) entered infinite loop (under certain conditions apparently related to branching or version numbers). This doesnt happen anymore. - Bug fixed: Formerly all revisions were included in the revision log if only individual revisions were requested. Now the result sets include just the information for the particular changesets supplied in `rev` parameter. Tested with both `hg` and `svn`. - Bug fixed: Exception with message `Invalid list index` was raised when using Subversion backend when requesting the log for individual revisions. This works OK now for both `hg` and `svn`. - Bug fixed: Wrong default value for `fmt` parameter in `GVizChangesetDetails`. Now it's OK. - Bug fixed: Formerly undocumented column in `GVizTimelineFilters` provider now contains appropriate description. - WikiFormatting may be used to document the data sources. It may be included in the documentation written for parameters, columns, and the data source itself. - Bug fixed: Documentation for providers having dynamic schemas was not previously rendered. This has been fixed and a new property has been added in docs to highlight whether the data source returns always the same columns or if they can vary depending upon run-time conditions. - Milestones may be filtered by name by providing a UNIX pattern in `filter_by` parameter. - UNIX filename patterns are compiled using REs for better performance. - Bug fixed: Now VCS RPC retrieves all changesets when using Hg backend. The implementation doesn't guess anymore the revision order and retrieves all that information directly from the underlying VCS connector in use. The former algorithm was weak because it only considered the first parent of a given revision. Therefore many others (especially all those in different branches) were missing from the result set. - Individual revisions (and not just intervals like before) may be selected in `GVizChangesets` (i.e. to obtain the revision log). - Bug fixed: As a consequence of the changes introduced in version 1.3.3 (especially in ReportRPC and VersionControlRPC) together with `bug #[email protected]`_ in XmlRpcPlugin, made impossible to render the main displaying documentation about the different RPC handlers. Both docstrings have been modified and everything is back to normal right now. .. _bug #[email protected]: http://trac-hacks.org/ticket/5586 Acknowledgements ====================== - Trac devs - Google devs Keep up the good work ! 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.4 @ PyPI (http://pypi.python.org/pypi/TracGViz/1.3.4) .. [4] Direct download link (http://pypi.python.org/packages/2.5/T/TracGViz/TracGViz-1.3.4-py2.5.egg) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
