Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Active Client 2.0"

(New page: {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} right A new variant of the Higgins selector being developed for Higgins 1.1. We're just ...)
 
(Planned Functionality)
Line 12: Line 12:
 
===Planned Functionality===
 
===Planned Functionality===
 
* Traditional IMI selector functionality
 
* Traditional IMI selector functionality
 +
* Selector can (optionally) be associated with [[Authentication Service 1.1]] and thereby gain the access tokens necessary to use other selector-related web services including:
 +
** [[Attribute Service 1.1]]
 +
** [[CardSync Service 1.1]]
  
 
===Compatibility===
 
===Compatibility===

Revision as of 21:05, 25 October 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

A new variant of the Higgins selector being developed for Higgins 1.1. We're just getting started on this page, so it is mostly just a template at present.

Introduction

This selector is a C++ client that uses the Qt GUI environment and is designed to run on Windows.

End-User Perspective

For an introduction to Information Cards and Selectors visit http://informationcard.net

Planned Functionality

Compatibility

Card types/protocols:

  • Supports managed and personal IMI information cards
  • Supports managed OpenID information cards
  • Supports managed and personal Higgins relationship cards

Browsers:

  • Firefox 3.0+
  • IE 6+

Operating systems (and what should be in the OS!):

  • Windows XP, Vista, and Windows 7
  • Higgins Selector Switch

Setup

<how do you install it?>

Deployer Perspective

<This section exists only if the solution can be deployed independently, e.g. STS. In the event that the solution consists of executables that run in more than one process, then these "sub-systems" should link to separate pages that adhere to the following structure (for example, see here>

<links to one or more pages to describe...>

<..prerequisites>

Download

<..how to obtain the .WAR, .jar, etc.>

Deploying

<..how to deploy a complete working solution>

Configuration

<..configuration files, options, etc.>

Developer Perspective

<links to one or more pages to describe...>

Architecture

<..component diagram>

<..[flow diagrams]>

<..list of components used>

Building

<..how to get the source>

<..how to build executables (jars, wars, exes, etc)>

See Also

Back to the top