[Building Sakai] 2.7 Release Discussion - Basic LTI Portlet

[csev]

Stephen - that is the SimpleLTI portlet source - here is the Basic LTI  
portlet:

https://source.sakaiproject.org/contrib/csev/trunk/basiclti/

I have not yet made a tag for Basic LTI - the trunk is currently in  
good shape.   There are no known errors, I have tested it a lot, it  
has no known spurious debugging messages.  If you find problems let me  
know.

It is designed to run along side of SimpleLTI in your system in case  
you have already done SimpleLTI integrations over the past year and  
need to keep them running while we transition to Basic LTI.  It also  
supports the "virtual tool" concept like the SimpleLTI portlet.

I will write documentation as you suggest:

(a) How to install, configure properties, and use the Basic LTI portlet

(b) How to write a Basic LTI tool (including source code samples)

My other "to do" is internationalization which should be easy since  
there is a very small amount of code.

For the SimpleLTI portlet - trunk is fine - but this tag is probably  
safer - I think this is what UM is running in production (Matt??)

https://source.sakaiproject.org/contrib/sakai-portlets/tags/release-0.1/

I did some refactor and cleanup in SimpleLTI code after that tag based  
on my approach and experience adding SimpleLTI to Melete - but we  
never put my new SimpleLTI trunk into production at UM because there  
were no bugs fixed and no functionality changed.  The nice thing is  
that the cleaner approach is what I started with to build BasicLTI.

/Chuck

On Jul 20, 2009, at 8:44 AM, Stephen Marquard wrote:

> Hi Chuck,
>
> Is there a recommended stable branch for running in production with  
> 2-6-x? We currently have
>
> https://source.sakaiproject.org/contrib/sakai-portlets/trunk/
>
> in our externals - is that the latest & greatest BasicLTI code?
>
> Secondly where would new adopters start with code examples of  
> various BasicLTI clients (e.g. php, perl, etc.)?
>
> It seems to me we'd be targetting two purposes for this, (a) use  
> this tool to bring in someone else's external tools (on App Engine,  
> etc.), or (b) use this tool to write your own integrations (like  
> LinkTool).
>
> In both cases really good, simple documentation seems important.
>
> Cheers
> Stephen
>
>
>
>
> Stephen Marquard, Learning Technologies Co-ordinator
> Centre for Educational Technology, University of Cape Town
> http://www.cet.uct.ac.za
> Email/IM/XMPP: stephen.marquard at uct.ac.za
> Phone: +27-21-650-5037 Cell: +27-83-500-5290
>>>> csev <csev at umich.edu> 7/20/2009 4:01 AM >>>
> Clay,
>
> I have some functionality I would like to add to 2.7 and am happy to
> be a guinea-pig for the new process for new functionality.
>
> I would like to add a BasicLTI Portlet to 2.7 - This is an evolution
> of the SimpleLTI portlet which has been in production at UM for a
> year.  BasicLTI is going to be an approved IMS spec so I figure it
> makes sense to update the portlet and then get it into Trunk and in
> the release.
>
> ...
>
> Where do I start?
>
> /Chuck
>
>
>
>
>