1. Main Screen Templates

Review of the main types of screens. This is a review of the concept the screen more than the content of the screen. The content of the screens are being discussed in the pages 2 - 7.

1. Gateway Dashboard Screen

1. General branding and content

This is already implemented. We do need to find a way that makes this easily adaptable through a configuration file

ToDo :

Domain Description Work Estimate Tracking
Technical Make branding and content easily configurable 8 hours Implemented
Technical Make real pages also internationalizable 16 hours Implemented
    Total: 24 hours

2. Create an account

Allows you to create a new account. How is this handled inside different institutions?

ToDo :

Domain Description Work Estimate Tracking
Design Make screen that allows you to create an account 5 hours Designed (click here to download)
Technical Implement screen 8 hours Implemented
    Total: 13 hours

3. Need help

Brings up the help pages, zoomed into the requested area. This needs more investigation
on how different institutions handle help and support pages right now. We might drop this
for now.

4. Login form

Main login. Has been implemented.

5. Forgot your username or password

Allows you to retrieve your password if you have forgotten it. This isn't available in
current Sakai and is probably highly institution dependant. Needs more investigation.
Will be dropped for now.

6. Footer

General footer that needs to be highly customizable for each institution.

ToDo :

Domain Description Work Estimate Tracking
Technical Make footer highly customizable 4 hours Implemented
    Total: 4 hours




2. Dashboard Screen

The idea is that a personal dashboard has got the institution branding, as sites can
have their own branding.

1. My Dashboard header

Header for your dashboard page. Probably should be customizable for each institution.

ToDo :

Domain Description Work Estimate Tracking
Technical Make it customizable 8 hours Implemented
    Total: 8 hours

2. Username

Shows first name and last name in stead of user login

ToDo :

Domain Description Work Estimate Tracking
Technical Implement 10 min Implemented
    Total: 10 min

3. Preferences

Preferences itself is a link which links to main Preferences page. The icon next to it
is a dropdown menu which allows you to deep link into the Preferences pages (into a certain
area).

ToDo :

Domain Description Work Estimate Tracking
Design Rename to My Preferences and make screen + HTML for dropdown 3 hours
Technical Implement 1 hour Implemented
    Total: 4 hours

4. Help

Brings up the main Sakai help pages.

ToDo :

Domain Description Work Estimate Tracking
Technical Implement 10 min Implemented
    Total: 10 min

5-6-7. DashBoard widgets

5 and 6 have already been fully designed, 7 is just a placeholder. Whether a widget
is a DashBoard widget or a Site widget can be configured, as can the default dashboard
layout.

ToDo :

Domain Description Work Estimate Tracking
Design Have a look at possible useful new widgets and review MyCamTools widgets 9 hours
Technical Make a widget dashboard only/site only 1 hour Implemented
    Total: 10 hours

8. Add Widgets + Edit Look & Feel

Buttons that will make it possible to change your personal dashboard. More info later.




3. Site Home Page Screen

1. Back to My Dashboard

Allows you to go back to your personal dashboard.

2. Preferences

Same as 2.3. We'd like to be here as a concept. For now it will only allow you to
change your preferences sakai-wide, but in the future you might be able to set your
preferences for a specific site.

ToDo :

Domain Description Work Estimate Tracking
Design Preferences page needs note that changes are global 15 min Implemented
    Total: 15 min

Note: Implemented by renaming Preferences to My Preferences

3. Site Settings

The link itself takes you to the Site Settings main page. The dropdown next to it
allows you to deep link into a section of the Site Settings page.

ToDo :

Domain Description Work Estimate
Design Design dropdown + HTML 1 hour
Technical Implement 1 hour
    Total: 2 hours

4. Site title bar

This should be customizable using the Edit Look & Feel button (See later).

5-6-7. Sidebar

Sidebar which contains tabs that allow you to go into different dashboard layout
(= organizational structure). Add Page will become Add Tab.

Reminder for Nico: Drag and drop widgets from tab to tab (if there is time)

ToDo :

Domain Description Work Estimate
Design Make extra screens and interaction design for adding tabs, removing tabs, reordering tabs and investigate whether the minimize button is useful at all 8 hours
Technical Implementation 24 hours
    Total: 32 hours

8-9. Placeholder widgets

These widgets are only placeholders. We might look into a restyling of the Cambridge
Recent Activity widget as a replacement of the Updates and Announcements widget.

ToDo :

Domain Description Work Estimate
Design Look at Cambridge Recent Activity widget + restyle See 1.2.5-6-7




4. Tool Screen (Ex: Site Settings)

1. Tool title

Name of the tool and is also a link into the first tab.

ToDo :

Domain Description Work Estimate Tracking
Technical Implementation 1 hour Implemented
    Total: 1 hour

2. Help

Help brings up the general help pages, zoomed in to the section containing info
about the tool itself

ToDo :

Domain Description Work Estimate Tracking
Technical Implementation 2.5 hours Implemented
    Total: 2.5 hours

3. Close & Return

Brings you back to the page you came from.

ToDo :

Domain Description Work Estimate Tracking
Technical Implementation 2 hours Implemented
    Total: 2 hours

4-5. Task bar

The active tab showing the tab you are currently in (active tab) and the other tabs
show what else is available (inactive tabs).

6. Save & Undo Changes

Save saves your changes without bringing you back to the previous page. Undo Changes
brings the form back into the state it was in

ToDo :

Domain Description Work Estimate Tracking
Technical Extend SData framework to enable easier form processing 5 days Implemented
    Total: 40 hours




5. Lightbox Screen (Ex: Add Widgets)

1. Grey background

The lightbox puts a slightly transparent layer on top of the screen you were
working in. Clicking this should not close the lightbox overlay.

2. Widget title

This should in this case adjust itself to where it is

ToDo :

Domain Description Work Estimate Tracking
Technical Implement contextual title changes 4 hours Implemented
    Total: 4 hours

3. Help

General help pages zoomed in to where the help pages for this lightbox are

4. Close Window & Cancel

Closes the lightbox and doesn't save changes. Comes back at the bottom of the
lightbox.

ToDo :

Domain Description Work Estimate Tracking
Design Redesign this specific widget to remove the Close Window & Cancel in the bottom and make it Close Window at the top (because Add Widget/Remove Widget is already a confirmation step) 1 hour Implemented
    Total: 1 hour

5. Finished

Closes the lightbox




6. Widget

ToDo :

Domain Description Work Estimate Tracking
Technical Build system which allows to have multiple instances of a widget 40 hours Implemented
    Total: 40 hours

1. Minimize

Minimizes the widget so only the title bar is visible

2. Widget Title

3. Hover area

When the mouse cursor hovers the grey area, the cursor will change into a crosshair
and will be draggable

4. Menu

(Optional) menu that allows you to set settings, refresh, ...

ToDo :

Domain Description Work Estimate Tracking
Design Design screens to find out how a settings screen should look like 3 hours w/HTML
Technical Allow widgets to be configurable through this Settings menu 16 hours Implemented
    Total: 19 hours

5. Close

Removes the widget from the screen

6. Task bar

Widget specific

TOTAL HOURS = ~208 (5.2 person weeks)

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Aug 05

    Nathan Pearson says:

    Nico, Issue 1.6.4 I'm assuming this will only be a design for the pulldown menu...

    Nico,

    Issue 1.6.4 - I'm assuming this will only be a design for the pull-down menu, or did you want a screen for widget "settings"?

    Nathan

    1. Aug 05

      Nicolaas Matthijs says:

      I meant a design for the widget's settings itself, as we probably want this to b...

      I meant a design for the widget's settings itself, as we probably want this to be consistent over the widgets.

      1. Aug 05

        Nathan Pearson says:

        I'm a little unclear about the requirements for the settings screen. I can desig...

        I'm a little unclear about the requirements for the settings screen. I can design a pull-down menu and a shell screen for settings, but I think settings will probably be widget specific. For example, if it's an RSS feed or an announcement type widget, settings may ask how many items do you want to list. If it's a calendar widget, settings may ask if you want a month view, day view, etc.

        So I think we'll need to take this on a case by case basis with a few widgets before a standardized template emerges.

        But since we do have a few widgets that we plan to see in 2.6, maybe we should talk more about the type of settings each one should have (if they should have any). I'm assuming some widgets won't have setting at all.

        1. Aug 29

          Nicolaas Matthijs says:

          As these are the Main Screen Templates, I indeed meant a shell screen for settin...

          As these are the Main Screen Templates, I indeed meant a shell screen for settings, so that the screen itself is consistent throughout the widgets. The settings themselves are of course widget-specific.