[Building Sakai] Forcing Resources to be installed on a site

[Jaques Smith]

Stephen,

That is exactly what I was looking for, the SiteAdvisor. It is in the link that Alan send too but I did not understand it there, was a little slow.

Thanks,
Jaques

-----Original Message-----
From: Stephen Marquard [mailto:stephen.marquard at uct.ac.za] 
Sent: 21 January 2011 09:30 AM
To: Steve Swinsburg; Jaques Smith; Alan Berg
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] Forcing Resources to be installed on a site

If you want to add the Resources tool when your own tool is selected in
Site Setup, you can do that (I believe) by implementing a SiteAdvisor
(either that or ContextObserver - one is called before a site is saved,
the other is called after it is updated).

Cheers
Stephen 
 

-- 
Stephen Marquard, Learning Technologies Co-ordinator
Centre for Educational Technology, University of Cape Town
http://www.cet.uct.ac.za
Email / IM (Jabber/XMPP): stephen.marquard at uct.ac.za
Phone: +27-21-650-5037 Cell: +27-83-500-5290 


>>> Jaques Smith <jaques at psybergate.co.za> 1/21/2011 9:25 AM >>> 
Thanks Alan & Steve,

Yes, that helps.

What about if I want to make some tools dependent on other tools. I can
manage that by doing Sakai administration and saying, if you install
this then install that and having a process around that. But can I make
it so that the tool will automatically manage that for the user?

I was hoping there is something like that already in Sakai but I
haven't found anything. So what I'll do is to do a check when the tool
start to see if all dependencies are satisfied and prompt the user to do
it, or ask the user if the tool can just set it up automatically, given
it is possible which in this case it is.

Thanks for the help,
Jaques

From: Steve Swinsburg [mailto:steve.swinsburg at gmail.com]
Sent: 20 January 2011 12:46 PM
To: Berg, Alan
Cc: Jaques Smith; sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] Forcing Resources to be installed on a
site

There is an XML config file you can set, as Alan linked to. You can
also create a set of 'template' sites and then create new sites based on
those templates. The new sites will take on the page and tool structure,
but not the users or content (although that is possible too), so it is
perfect for setting up and then cloning out to your new sites.

cheers,
Steve



On 20/01/2011, at 8:38 PM, Berg, Alan wrote:


Does this help?
http://www.unicon.net/node/1000

Alan

Alan Berg
QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg
________________________________
From:
sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org>
[sakai-dev-bounces at collab.sakaiproject.org] on behalf of Jaques Smith
[jaques at psybergate.co.za]
Sent: 20 January 2011 09:45
To:
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Subject: [Building Sakai] Forcing Resources to be installed on a site
Hi All,

We are busy building a tool for Sakai. The tool will need the Resource
tool in the site. How can I force the Resource tool to be installed?
Sakai 2.7

Thanks,
Jaques

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to
sakai-dev-unsubscribe at collab.sakaiproject.org<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org>
with a subject of "unsubscribe"




 

###
UNIVERSITY OF CAPE TOWN 

This e-mail is subject to the UCT ICT policies and e-mail disclaimer
published on our website at
http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from
+27 21 650 9111. This e-mail is intended only for the person(s) to whom
it is addressed. If the e-mail has reached you in error, please notify
the author. If you are not the intended recipient of the e-mail you may
not use, disclose, copy, redirect or print the content. If this e-mail
is not related to the business of UCT it is sent by the sender in the
sender's individual capacity.

###