Jupiter Portal

Owned by Former user (Deleted)
Last updated: Dec 29, 2006Version comment
2 min read

Overview

The Jupiter Portal is designed to be a simple Sakai portal that illustrates how such applications work for training purposes.

Features

Login

Jupiter, unlike Mercury requires that a user be logged in before access to tools is provided. A login link is provided that brings up a login form. Currently, no authentication is done on this id, so any id can be used.

Tool Registration and Display

After login, Jupiter displays the set of tools registered to it as links down the left side of the browser window. Only Jupiter tools are listed, as determined by a category setting in the Sakai tool registration file:

<category name="jupiter.tool" />
<category name="sakai.sample" />
<keyword name="dash-comp-mgr" />

A category string of "jupiter.tool" will cause the tool to appear in the Jupiter portal. Note that other category names may also appear. In this case, a category of "sakai.sample" will cause the tool to appear in the sample tools section of the Mercury portal.

Tool Content Display

Jupiter is designed to be completely free of iFrames. As such, Jupiter tools are required to render content in a <div> or as an HTML fragment. This content is shown in a table cell on the right part of the browser screen. Only one tools can be displayed at a time. No support is provided for the kind of pages supported by Charon.

Developing Tools for Jupiter

  1. Develop the tool as a regular Sakai tool using any presentation technology.
  2. Add a category name of "jupiter.tool" in the tool registration file.
  3. Make sure content renders as a fragment with no <HTML>, <HEAD>, or <BODY> tags.

Jupiter Code Analysis

TBD.