[[Image(http://static.edgewall.org/gfx/madscientist.png)]]
= Wild Ideas =

=== Mozilla / Firefox / Thunderbird Extensions ===
Being able to conveniently access tickets in a Firefox and/or Thunderbird extension would be kinda cool. -- DanielLundin

Answer: Use the [http://sage.mozdev.org/ Sage RSS sidebar] and you have everything in your sidebar that you want.

=== Timeline and Reports output in alternate formats ===
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

Actually, the Timeline (and, I think, reports as well) already have an RSS version...

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.  here is the [http://www.piedcow.com/archives/2005/03/inspired_to_cre.html link].

=== RstForEverything ===
Add a configuration option to use 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:

{{{
A link to `SandBox`, ticket `#1`, changeset `[1]` and report `{1}`. Or even as `[wiki:SandBox the sand box]`
}}}

=== Eclipse Integration ===
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 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.

Answer: One way would be, like the hint above, to use an eclipse RSS reader to syndicate the ticket RSS from Trac. There is one at http://morphine.sourceforge.net/presence/projects/rss/

'''Answer''': The [http://wiki.eclipse.org/Mylyn/SOC/2006/Trac_Connector Trac Connector] for Mylyn does exactly this.

=== Continuous Integration ===

Why not provide integration with ''Continuous Integration'' tool's like those listed [http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix here].

Christopher Lenz's [http://bitten.cmlenz.net/ Bitten] plugin provides continuous integration features for Trac.

=== RPC Interface ===

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 crazy developers to write e.g. an [http://en.wikipedia.org/wiki/AJAX AJAX] interface to Trac.

In particular, the ability to retrieve reports would make a lovely addition to my Intranet homepage. :) -- [http://botanicus.net/dw/ DavidWilson]

Related Tickets: #217, #250.

'''Answer''': The [https://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC plugin] at trac-hacks does exactly this.''

=== SVN Edition ===

Currently, the only way to put a new revision from/to svn is with a check out and commit. Why no provide online integration, and this form I can edit source from repository without download and upload the code, only with an embebed text editor and a couple of buttons (''that would be #2956 -- cboos'')