\nI visited Cambridge this week to see what was up with the new Sling + Sakai (Slikai) work that Ian is working on. I figured that one way or another I would find a way to hack in IMS Simple Learning Tools Interoperability into it – after all I hack LTI into pretty much anything else. One day I will write a FORTRAN version of Simple LTI :).<\/p>\n
\nI figured that in two days I would be a little pressed for time. Day one started out with Ian explaining Sling for about an hour and giving me some hello world stuff. It took me a while to hack each piece together. I started this morning knowning nothing about Sling and now this evening I have my first working application in Sling\/Sakai.<\/p>\n
\nSitting 3 feet away from Ian meant I was never stuck for too long – I was just slow. But by the end of the first day, I am pretty much done – the code is checked in here:<\/p>\n
\nhttps:\/\/source.sakaiproject.org\/contrib\/csev\/trunk\/sling\/<\/p>\n
\nAll in all I am pretty impressed with Sling. Many important decisions are already made – most of the APIs we think of as “kernel” are in place. There is lots of value to be added – mostly in terms of “helper” APIs to lock down “Sakai conventions” within Sling and keep us from hard-coding convention too widely scattered throughout the code.<\/p>\n
\nThere is lots to do – so much more to do – but Sling feels like a great starting point. Performance is always something to worry about – but I am confident that Ian worries about performance even more than I do – so I expect that whatever we run into is solvable.<\/p>\n
\nIt was great fun to see this at an early state and to talk issues over with Ian and I look forward to the progress over the next few months and hope that we see some nice shiny stuff by the conference.<\/p>\n
\nThe README is below if you want to replicate my experiences.<\/p>\n
<\/p>\n
\nHacking Sakai K2 Sling Adding IMS Simple LTI As a Resource Type\nHere are my rough notes on playing with Sakai 3 \/ Sling and\ngetting IMS LTI to work in Sling as a resource type.\nNote: I have NO Idea how long these URLs will work -- Chuck\nMany thanks to Ian Boston who walked me through all of this\nat Caret.\nReferences:\nhttp:\/\/groups.google.com\/group\/sakai-kernel\nhttp:\/\/incubator.apache.org\/sling\/site\/discover-sling-in-15-minutes.html\nhttp:\/\/cwiki.apache.org\/SLING\/using-slinginclude-in-jsp.html\nCheck out my example code (including this README) from here:\nhttps:\/\/source.sakaiproject.org\/contrib\/csev\/trunk\/\nFor the rest of this document ~\/dev\/csev\/trunk\/sling\/ is where\nI checked out this source.\nMake some directory to run your Sakai3\/Sling instance - DO NOT\nuse the same directory as this source.\nGo to that other directory\nDownload the Sling+Sakai bundle from Ian:\ncurl -O http:\/\/www2.caret.cam.ac.uk\/%7Eieb\/k2binary-snapshot\/sakai-k2-0.1-SNAPSHOT-binary.tar.gz\ntar xfz sakai-k2-0.1-SNAPSHOT-binary.tar.gz\ncd sakai-k2-0.1-SNAPSHOT-binary\/\n.\/startup.sh\nKeep this terminal window - it is your console - useful for debugging.\nIn your browser go here:\nhttp:\/\/localhost:8080\/index.html (main sling launch pad)\nhttp:\/\/localhost:8080\/system\/console\/bundles (what stuff is installed\nIf it looks OK and you see \"Apache Felix Web Management Console\nBundles\" and a long list of \"Active\" things all is well.\nStart a new window and come back here. We need to poke a pom\ninto your repo (there may be a slicker way to do this - but\nwhatever...).\ncd ~\/dev\/csev\/trunk\/sling\/ (or wherever)\ncp m2-repo-patch.tgz ~\/.m2\ncd ~\/.m2\ntar xfvz m2-repo-patch.tgz\nrm m2-repo-patch.tgz\nCome back here and then\ncd ~\/dev\/csev\/trunk\/sling\/ (or wherever)\ncd imsltibundle\/\nmvn -Predeploy clean install\nIf you get this message then the tar above mis-fired:\n[INFO] Failed to resolve artifact.\nGroupId: org.sakaiproject.kernel\nArtifactId: base\nVersion: 0.1-SNAPSHOT\nIf it starts downloading a zillion files - it is almost\na sure sign of success.\nIf you get this message:\n[INFO] [sling:install {execution: install-bundle}]\n[INFO] Installing Bundle org.imsglobal.simplelti(\/Users\/csev\/dev\n\/csev\/trunk\/sling\/imsltibundle\n\/target\/org.imsglobal.simplelti-0.1-SNAPSHOT.jar) to\nhttp:\/\/localhost:8080\/system\/console via POST\n[INFO] Bundle installed\n[INFO] BUILD SUCCESSFUL\nDo a small jig or pump your fist in the air.\nGo back to the following URL\nhttp:\/\/localhost:8080\/system\/console\/bundles\nPress refresh and look for IMS. If you find and\nentry titles \"IMS Global Learning: SimpleLTI\" and it\nsays \"Active\" - you are so in good shape.\nYou are now 85% complete!\nJust for yucks, use Finder | Go | Connect to Server\nUse http:\/\/localhost:8080\/\nAnd admin\/admin as id and pw\nIf all goes well - you should see your repo in the finder!\nYou can also find your repo under\n\/Volumes\/localhost\nYou can edit files wither place and look at the structures.\nLook at the apps folder (it is empty) and notice there is no\ncourses folder - all that is about to change.\nCome back here:\ncd ~\/dev\/csev\/trunk\/sling\/ (or wherever)\nsh doit.sh\nThis will put a bunch of files into the repository\nin clever places:\n(1) Install a resource handler in apps\/ims\/simplelti\n(2) Make a \/courses and \/courses\/SI301 and put an LTI\nplacement called wiscrowd in SI301\nThis should finish and tell you what to do next.\nLogin with admin admin at\nhttp:\/\/localhost:8080\/login.htm\nNavigate to\nhttp:\/\/localhost:8080\/courses\/SI301\/wiscrowd.html\nIf all goes well you will see the Wisdom of Crowds\nprogram showing the user and course info from\nSling.\nTry going to\nhttp:\/\/localhost:8080\/courses\/SI301\/wiscrowd.html\nIn another browser without logging in - you will\nbe a student.\nYou can change all kinds of values in doit.sh\nand re-run to play with different LTI urls and\ncourse titles, etc etc.\nHave fun. I did.\n<\/pre>\n","protected":false},"excerpt":{"rendered":"I visited Cambridge this week to see what was up with the new Sling + Sakai (Slikai) work that Ian is working on. I figured that one way or another I would find a way to hack in IMS Simple Learning Tools Interoperability into it – after all I hack LTI into pretty much anything […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-625","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/625","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/comments?post=625"}],"version-history":[{"count":1,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/625\/revisions"}],"predecessor-version":[{"id":2748,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/posts\/625\/revisions\/2748"}],"wp:attachment":[{"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/media?parent=625"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/categories?post=625"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dr-chuck.com\/csev-blog\/wp-json\/wp\/v2\/tags?post=625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}