We've made use of some extensions to MediaWiki to present data sourced from Seaside. It may of interest to others. Our in-house wiki is used for documentation and reference material. We run Seaside for a simple issue tracking system and as a patch server for client sites. The wiki presents data from these two Seaside apps. <div>
<br></div><div>The web services extension is <a href="http://www.mediawiki.org/wiki/Extension:Webservice">http://www.mediawiki.org/wiki/Extension:Webservice</a> </div><div>We also use an iframe extension <a href="http://www.mediawiki.org/wiki/Extension:Website_in_iFrame">http://www.mediawiki.org/wiki/Extension:Website_in_iFrame</a></div>
<div><br></div><div>For issue tracking, the wiki has a sidebar, generated by a webservice call, with each person's name and a count of issues in various life cycle stages. Each sidebar entry links to a wiki page with another webservice call which shows a list of the person's issues.</div>
<div><br></div><div>The sidebar entry looks like this: {{#webservice:<a href="http://our.seaside.server.com:7777/Issues?wiki=sidebar|">our.seaside.server.com:7777/Issues?wiki=sidebar|</a> %//div%}}</div><div>Seaside answers... (html text: aString)</div>
<div><br></div><div>* To Do </div><div>** ToDo bob|Bob (2, 7, 1, 0) </div><div>** ToDo john|John (6, 0, 5, 0) </div><div>** ToDo paul|Paul (0, 9, 8, 21) </div><div><br></div><div>...which links each entry to a page like: </div>
<div><br></div><div><div><a href="http://our.wiki.server.com/wiki/index.php/ToDo_bob">http://our.wiki.server.com/wiki/index.php/ToDo_bob</a> </div></div><div><br></div><div>...which contains... </div><div><br></div><div>{{#webservice:<a href="http://our.seaside.server.com:7777/Issues?wiki=user:Bob|">our.seaside.server.com:7777/Issues?wiki=user:Bob|</a> %//div%}}</div>
<div><br></div><div>...which answers a wiki formatted table with links... </div><div><br></div><div><div>==Active Issues assigned to Bob ==</div><div>{|</div><div>! ID</div><div>! System</div><div>! Client</div><div>! Title</div>
<div>! Stage</div><div>! Text</div><div>! P.</div><div>! Assigned</div><div>! Date</div><div>! Type</div><div>|-</div><div>| [<a href="http://our.seaside.server.com:7777/Issues?issue=1105">http://our.seaside.server.com:7777/Issues?issue=1105</a> 1105] || ToolCASE || CS || Add Code Critic to daily SUnit tests || [[image:Blueplay.png]] current || '' investigating '' || C || Bob || 2010-09-21 || Technical</div>
<div>|-</div><div>| [<a href="http://our.seaside.server.com:7777/Issues?issue=1118">http://our.seaside.server.com:7777/Issues?issue=1118</a> 1118] || BID || CS || change notice on the project profile || [[image:Blueplay.png]] current || '' coding report spec '' || C || Bob || 2010-09-24 || Modification</div>
<div>|}</div></div><div><br></div><div>You can paste the string into a wiki page and see how it looks. The first cell on each row links back to our issue tracking Seaside app. </div><div>We use a similar technique for displaying lists of patches and client patch status information.</div>
<div><br></div><div>We also use this technique to display graphs, using the <a href="http://chart.apis.google.com/chart">http://chart.apis.google.com/chart</a> and the mediawiki iframe extension. In this case, the Seaside app answers a string that the wiki interprets as an iframe extension call. So, the wiki code looks like... </div>
<div><br></div><div>{{#webservice:<a href="http://our.seaside.server.com:7777/Issues?wikichart|">our.seaside.server.com:7777/Issues?wikichart|</a> %//div%}}</div><div><br></div><div>...which answers something like... </div>
<div><br></div><div><div><websiteFrame></div><div>website=<a href="http://chart.apis.google.com/chart?&cht=bvo&chs=800x350&chg=0,10,4,0&chtt=Test+summary&chts=19293D,20&chbh=40,50&chco=AABAD7,4F81BD,40699C&chdl=TEST1|TEST2|TEST3&chd=t:80,65,39,35,37,37,46,62|64,38,24,18,23,13,18,31|50,10,19,12,18,8,12,21&chds=0,80&chxt=x,y&chxl=0:|Feb">http://chart.apis.google.com/chart?&cht=bvo&chs=800x350&chg=0,10,4,0&chtt=Test+summary&chts=19293D,20&chbh=40,50&chco=AABAD7,4F81BD,40699C&chdl=TEST1|TEST2|TEST3&chd=t:80,65,39,35,37,37,46,62|64,38,24,18,23,13,18,31|50,10,19,12,18,8,12,21&chds=0,80&chxt=x,y&chxl=0:|Feb</a> 2010|Mar 2010|Apr 2010|May 2010|Jun 2010|Jul 2010|Aug 2010|Sep 2010|1:|0|8|16|24|32|40|48|56|64|72|80</div>
<div>name=Test summary</div><div>align=middle</div><div>height=380</div><div>width=800</div><div>border=0</div><div>scroll=no</div><div>longdescription=chart</div><div></websiteFrame></div></div><div><br></div><div>
So we're wrapping the google chart in the iframe, not our Seaside app. </div><div><br></div><div>We end up seamlessly combining static wiki content with dynamic Seaside content.</div><div><br></div><div>Hope the idea is of use to someone,</div>
<div>Bob Nemec</div><div><br></div><div><br></div>