[Building Sakai] Removing standalone modes for sections/gradebook

[Neal Caidin]

Wow, that’s too bad that it didn’t take off. A standalone gradebook sounds kind of cool. All it needs is LTI and you could have something there.

— Neal



Neal Caidin
Sakai Community Coordinator
neal.caidin at apereo.org
Skype: nealkdin
Twitter: ncaidin









On Nov 12, 2013, at 8:35 PM, Jon Gorrono <jpgorrono at ucdavis.edu> wrote:

> I followed the trail from SAK-23907 to here... and as one of the few remaining survivors who have run Standalone in the past (but not in production): +1 for removal :)
> 
> For the Wikipedia page about it: the Standalone Gradebook was created first, IIRC. And, IMO it had about 3X the coolness quotient, with graphing and such.... I think it even had some UI components with text at 45 degree angles for better graph readability, or some such craziness... it worked.
> 
> 
> On Thu, Nov 7, 2013 at 11:47 AM, Matthew Jones <matthew at longsight.com> wrote:
> 2 issues are considered blockers for the release of Sakai 10
> 
> https://jira.sakaiproject.org/browse/SAK-23918
> https://jira.sakaiproject.org/browse/SAK-23917
> 
> These are both related to sections and gradebook depending on impl's that have been moved into edu-services. The cross between edu-services and these tools isn't completely clean and much of it is continued support for the a feature called "standalone". I've never ran this feature, only read about it in some of the old docs. Nobody on the release call was running these tools "standalone". The documentation on this mode is over 7 years old and it seemed to imply you did need some parts of Sakai to get it to run. The release team call suggestion is to just remove standalone capability from these tools in Sakai 10. This would simplify the code in these tools and remove these dependencies. 
> 
> However, before I committed this I wanted to a check to verify nobody outside of the call was using this mode and would miss it. If so would they consider supporting the work to fix this dependency problem and test this mode. The alternative I could think of would probably be profiles specific for the standalone mode which would only compile these standalone classes and include these dependencies when specifically enabled. 
> 
> Obviously they would remain in versions of Sakai 2.9 and earlier.
> 
> I plan to commit the removal of these next week if there is no dissenting opinion. I've done this locally for sections and it seems to work fine, gradebook looks like a little more involved.
> 
> Thanks!
> 
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of "unsubscribe"
> 
> 
> 
> -- 
> Jon Gorrono
> PGP Key: 0x5434509D - http{pgp.mit.edu:11371/pks/lookup?search=0x5434509D&op=index}
> http{middleware.ucdavis.edu}
> _______________________________________________
> sakai-dev mailing list
> 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 with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131113/42c7b5a6/attachment.html