The Moodle block (as written) runs on a heavily customized version of VCL 2.2.1, but the modifications are only necessary if either Moodle or VCL use Shibboleth authentication. Once version 2.3 is released, I will be updating the Moodle block, and I will write some detailed instructions for how the two may be integrated.
Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College [email protected]<mailto:[email protected]> On Jul 18, 2012, at 10:29 AM, Mike Kirgan wrote: This is something FIU would be interested too - as well as any Blackboard building blocks if anyone has developed any. --Mike Mike Kirgan Associate Director Division of IT Florida international University ________________________________________ From: Aaron Coburn [[email protected]<mailto:[email protected]>] Sent: Tuesday, July 17, 2012 5:03 PM To: <[email protected]<mailto:[email protected]>> Subject: Re: Moodle integration Block I have a Moodle (2.x) block that works with the VCL. Users can schedule, connect to and delete reservations. There were some necessary changes to get it working with Shibboleth-based authentication, and there are some local customizations in how we handle RDP connections, but I would be happy to share what we have. Aaron -- Aaron Coburn Systems Administrator and Programmer Academic Technology Services, Amherst College [email protected]<mailto:[email protected]><mailto:[email protected]> On Jul 17, 2012, at 4:58 PM, James O'Dell wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Everyone, It seems like VCL and Moodle would be a good fit. (Especially, if they were both configured for Shibboleth.) Just wondering, has anyone done any development work for a VCL block under Moodle 2? __Jim - -- Jim O'Dell Network Analyst California State University Fullerton Email: [email protected]<mailto:[email protected]><mailto:[email protected]> Phone: (657) 278-2256 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAF0eoACgkQREVHAOnXPYRIEQCguV2wFy0nFWmxAYj6ORztqP7D 35EAn11MMFu27VTLjNH6Mteq3i4lxtEL =qcCy -----END PGP SIGNATURE-----
