From: Matthew B. <mat...@ou...> - 2006-07-11 13:43:00
|
Alistair Young wrote: >> Plugin in what sense? > added functionality, like our MyModules, which has to go in Facility > just now. Also, different "views" of users. Chat view for instance. > Who's online, start a chat with them >> Not a tool in the bodingtno sense that can be deployed at multiple >> URLs? > no, that's a good point. Plugins aren't bod specific. They're an > easier way to customise a bod. e.g. ox can't use our MyModules and > Chat so rather than endlessly removing from merges, just do them as > plugins. Ok so plugins aren't tools. Although I'd argue that chat should be a tool rather than a plugin as it makes sense that you could have multiple chat tools in a bod. >> Spring App? > well he'd rather do it as a spring app, then he can run it somewhere > else. So he needs your bs_spring stuff in our head. Maybe it can't be > a plugin as it might need to be added to bod at multiple urls. But what is the application exposing? and API? a set of web pages? a Web Service? -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |