Re: [Bodington-developers] Spring again

[Alistair Y. <ali...@sm...>]

> But shouldn't the "page which gives information" be a tool? as you  
> might
> want it to be permission and hierarchy aware?
nothing's concrete just now, just poking around trying to avoid yet  
another method in Facility and also avoiding tools. The ability to  
have a chat "control page" isn't bod specific so doing it as a tool  
is a waste.
The MyModules could be a tool but the demand for it didn't give any  
time to navigate the bone crushing blackness of bod tools ;) and it's  
not restricted - you have the right to view your modules anywhere in  
bod. Interfaces were mentioned then but were poo-pooed in favour of  
spring, which was coming. Now it's here, tools are back in fashion 8-0

> polluting the application with the
> interface.
that's a bit harsh. How else could one do it without doing a tool?  
The only advantage of a tool is the restrictions you can place on it.  
Something like chat isn't suited to a tool as the user can just say  
"sod it", leave bod and use their chat client to do the same thing.  
Why don't they just use their client in the first place? Ask those  
who produce requirements ;)

> Facility (and subclass)
but templates can only use one class. So you can't add functionality  
to a template that already uses Facility without putting that  
functionality into Facility.

> Tool: A Bodington tool that can be deployed somewhere in the tree of
> resources and is aware of permissions and possibly the hierarchy.
but requires an onerous overhead of database insertion. You can't  
distribute bod tools as they require the database to be modified. If  
you just wanted public functionality you could just add a <plugin>  
call to a template and supply the jar in the distro. Facility would  
use the bod plugin interface to load and call it.

The goal of a plugin was a self contained unit of functionality that  
could be called from a template. Unfortunately, as templates are  
restricted to one class, all plugin hooks have to go into Facility.  
That's where the interface came from. So Facility could be shipped  
with a plugin method that just loaded and called the desired plugin,  
defined by the template at run-time.

Of course, if restrictions are required then a tool would be better  
although that means merge problems and database modifications and  
leads to site specific code in bod. Unless you do what we have to do  
and remove all our functionality before committing to bod head. Now  
that's a waste of everyone's time.

Alistair


On 11 Jul 2006, at 15:16, Matthew Buckett wrote:

> Sean Mehan wrote:
>> need to differentiate here between the client which connects to the
>> external server and the page which gives information on which of your
>> pals is online and chattable.
>
> But shouldn't the "page which gives information" be a tool? as you  
> might
> want it to be permission and hierarchy aware?
>
>> The chat server is being made aware of bod groups, so your groups  
>> turn
>> into roster groups in chat-space, and you have the ability to  
>> create a
>> chat room as you do a forum for the discussion tool.
>
> Ok so from our current discussion I have a glossary of:
>
> Plugin: A way of linking code into an application without having the
> application explicitly depend on the code. Don't you need an interface
> todo this, you get the application to depend on the interface not the
> implementation. But you still end up polluting the application with  
> the
> interface.
>
> Bodington already has plugins in BuildingSession (and subclasses) and
> Facility (and subclass) can be replaced at runtime with different
> implementations.
>
> Tool: A Bodington tool that can be deployed somewhere in the tree of
> resources and is aware of permissions and possibly the hierarchy.
>
> -- 
>   -- Matthew Buckett, VLE Developer
>   -- Learning Technologies Group, Oxford University Computing Services
>   -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers