[Building Sakai] how to future-proof Sakai 2 tools?

[Nate Angell]

How about locating it as a child of the main Building Sakai wiki page? There seem to be quite a few such general guidelines there:
http://wiki.sakaiproject.org/display/SAKDEV/Building+Sakai+%28a.k.a.+sakai-dev%29#BuildingSakai%28a.k.a.sakai-dev%29-DeveloperDocumentation

Cheers!

On Mar 9, 2010, at 9:18 AM, Adam Marshall wrote:

> I'm happy to paste in the text that Christian sent me and add nuggets of wisdom as and when I come across them. 
> 
> I'm not a big confluence user nor very involved with sakai 3 (which is v bad but there's no time) - could somebody suggest where I should create my page then I'll do it? I've had a look and can't see anywhere obvious.
> 
> And congratulations to Nate for being the first person to suggest I put my money where my mouth is so-to-speak! ;)
> 
> adam 
> 
> | -----Original Message-----
> | From: nate.angell at rsmart.com [mailto:nate.angell at rsmart.com]
> | Sent: 09 March 2010 17:06
> | To: Adam Marshall
> | Cc: Christian Vuerings; sakai-dev at collab.sakaiproject.org
> | Subject: Re: [Building Sakai] how to future-proof Sakai 2 tools?
> | 
> | Great suggestion Adam! As a community member, where will you start
> | this wiki page? ;)
> | 
> | The product council would love to be able to point Sakai 2 tool
> | developers toward it so they might take such future-proofing into
> | account.
> | 
> | On Mar 9, 2010, at 2:05 AM, Adam Marshall
> | <adam.marshall at oucs.ox.ac.uk> wrote:
> | 
> | > would the community be prepared to start a confluence page on this
> | > topic?
> | >
> | > I think the question will be raised more and more as we speed
> | forward.
> | >
> | > Adam
> | >
> | > | -----Original Message-----
> | > | From: Christian Vuerings [mailto:vueringschristian at gmail.com]
> | > | Sent: 08 March 2010 22:32
> | > | To: Adam Marshall
> | > | Cc: sakai-dev at collab.sakaiproject.org
> | > | Subject: Re: [Building Sakai] how to future-proof Sakai 2 tools?
> | > |
> | > | Adam,
> | > |
> | > |
> | > | AFAIK we don't really have guidelines for that at the moment.
> | > |
> | > | But maybe the following pointers/hints could help:
> | > |
> | > | If you include the tool in an iframe (that's how we are currently
> | > doing
> | > | it)
> | > |  - Don't load the CSS from the parent frame dynamically.
> | > |    We currently have an issue standing open for that. [1]
> | > |  - This is probably standard in every Sakai2 tool, but make sure
> | you
> | > | call the setMainFrameHeight function on loading the tool (for
> | > resizing
> | > | the iframe height)
> | > |
> | > | If you want to access the data in Sakai3:
> | > |  - Make your tool accessible via REST calls and supports JSON (XML
> | > | could work as well but it will be a bit slower). (e.g. [2])
> | > |    This would enable you to create a native Sakai3 widget that
> | > accesses
> | > | the Sakai2 REST services.
> | > |
> | > | IMO most of the current tools should already work within Sakai3
> | > since
> | > | we are just using iframes to load them.
> | > |
> | > |
> | > | Christian
> | > |
> | > | [1] http://jira.sakaiproject.org/browse/SAKIII-94
> | > | [2] http://sakai3-nightly.uits.indiana.edu:8080/sakai-hybrid/sites
> | > |
> | > |
> | > | On 8 Mar 2010, at 17:33, Adam Marshall wrote:
> | > |
> | > | > Are there guidelines on how to write a Sakai 2 tool so it will
> | fit
> | > | with Sakai 3?
> | > | >
> | > | > Adam
> | > | > _______________________________________________
> | > | > 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"
> | >
> | > _______________________________________________
> | > 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"