| 28 | | |
| 29 | | == Other wild ideas |
| 30 | | |
| 31 | | === Mozilla / Firefox / Thunderbird Extensions |
| 32 | | |
| 33 | | Being able to conveniently access tickets in a Firefox and/or Thunderbird extension would be kinda cool. -- DanielLundin |
| 34 | | |
| 35 | | '''Answer''': Use the [https://addons.mozilla.org/en-US/firefox/addon/sage Sage RSS sidebar] and you have everything in your sidebar that you want. |
| 36 | | |
| 37 | | === Timeline and Reports output in alternate formats |
| 38 | | |
| 39 | | Having options (through URL arguments presumably) to render [http://blogs.law.harvard.edu/tech/rss RSS], [http://www.ietf.org/rfc/rfc2445.txt iCal] and XML versions of the timeline and reports, rather than the default HTML/web page output, could be quite useful, and open some interesting possibilities. -- DanielLundin |
| 40 | | |
| 41 | | Actually, the Timeline (and, I think, reports as well) already have an RSS version. |
| 42 | | |
| 43 | | I was inspired by a simple chart tool as well. You take a Timeline RSS feed, transform it with my xsl which creates the chart data which you can then render in a web page. |
| 44 | | |
| 45 | | === Rst for everything |
| 46 | | |
| 47 | | Add a configuration option to use [WikiRestructuredText reStructuredText] as default markup for all pages, tickets and commit messages. This would mean a rewrite of all the default wiki pages to reStructuredText, probably some changes to the special pages such as RecentChanges and a lot of small stuff here and there. Also change the default role for reStructuredText to be Trac, so that wiki links could simply be written as: |
| 48 | | |
| 49 | | {{{ |
| 50 | | A link to `SandBox`, ticket `#1`, changeset `[1]` and report `{1}`. Or even as `[wiki:SandBox the sand box]` |
| 51 | | }}} |
| 52 | | |
| 53 | | === Eclipse Integration |
| 54 | | |
| 55 | | Anyone fancy implementing a plug-in for [http://www.eclipse.org Eclipse]? There's currently an [http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/bugs-plugin/index.html effort] going on to provide [https://www.bugzilla.org/ Bugzilla] integration, apparently extensible to other issue tracking systems. Such an effort would probably depend on us getting some kind of web-service layer working. |
| 56 | | |
| 57 | | '''Answer''': The [http://wiki.eclipse.org/Mylyn/SOC/2006/Trac_Connector Trac Connector] for Mylyn does exactly this. See also [th:MylynTracConnector]. |
| 58 | | |
| 59 | | === Continuous Integration |
| 60 | | |
| 61 | | Provide integration with [http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix Continuous Integration tools]. |
| 62 | | |
| 63 | | '''Answer''': A well tested CI tool is [http://trac.buildbot.net/ Buildbot] and integrated with Trac as [th:TracBuildbotIntegration] and [th:BuildbotPlugin]. Also see [PluginList#ContinuousIntegration other CI tool plugins]. Christopher Lenz's [http://bitten.cmlenz.net/ Bitten] plugin has been discontinued. |
| 64 | | |
| 65 | | === RPC Interface |
| 66 | | |
| 67 | | Via SOAP or XML-RPC (recommended for utter simplicity!), export the user interface functions to allow integration with proprietary Intranets and so forth. This would also allow some developers to write for example an [wikipedia:AJAX] interface to Trac. |
| 68 | | |
| 69 | | In particular, the ability to retrieve reports would make a lovely addition to my Intranet homepage. :) -- [http://botanicus.net/dw/ DavidWilson] |
| 70 | | |
| 71 | | Related Tickets: #217, #250. |
| 72 | | |
| 73 | | '''Answer''': The [th:XmlRpcPlugin XML-RPC plugin] at trac-hacks does exactly this. |
| 74 | | |
| 75 | | === SVN Edition |
| 76 | | |
| 77 | | Currently, the only way to put a new revision from/to svn is with a check out and commit. Why not provide online integration, and this form I can edit source from repository without download and upload the code, only with an embedded text editor and a couple of buttons. |
| 78 | | |
| 79 | | '''Answer''': #2956: Upload files to the repository -- cboos |
| 80 | | |
| 81 | | |
