Madrid Implementers Workshop - Applications

From wiki.gpii
Revision as of 14:05, 11 September 2013 by CStrobbe (talk | contribs) (ReadWrite Gold & SpeechStream (TextHelp): category added)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Linux/Gnome (Emergya)

Short description of you application (1 paragraph or so):

How are settings stored for your application? (eg. XML):

How is your application launched/killed? (eg. commands, location of .exe, etc):

How can one detect whether application is installed? (eg. registry lookup):

Java phone (CERTH)

Short description of you application (1 paragraph or so):

How are settings stored for your application? (eg. XML):

How is your application launched/killed? (eg. commands, location of .exe, etc):

How can one detect whether application is installed? (eg. registry lookup):

Smart Phone (Vodaphone)

Short description of you application (1 paragraph or so):

How are settings stored for your application? (eg. XML):

How is your application launched/killed? (eg. commands, location of .exe, etc):

How can one detect whether application is installed? (eg. registry lookup):

MS Surface (SILO)

Short description of you application (1 paragraph or so):

SOCIABLE is an application running on tablet PCs and on the MS PixelSense platform that integrates, deploys and operates an innovative ICT-enabled on-line service for assessing and accordingly reinforcing the mental state of the elderly through pleasant gaming activities for cognitive training.

How are settings stored for your application? (eg. XML):

Sociable must be installed in path: C:\Sociable The settings reside on a file entitled as "Configuration.xml". This file exists under the root path (C:\Sociable). This file adopts the following structure:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  
(User Identification)
  <user> </user> (The ID of the User in Sociable Database)
  <expert>1</expert> (Ignore this - It will be removed)
  <careCenter>1</careCenter> (Ignore this - It will be removed)
  
(Accessibility)
  <textToSpeech> </textToSpeech> (true, false)
  <font> </font> (monospace, proportional)
  <fontSize> </fontSize> (absolute name of font)
  <theme> </theme> (dark, light)

(Informative Attributes)
  <soundVolume> </soundVolume> (low, medium, high)
  <magnifier> </magnifier> (true, false)
  <highContrast> </highContrast> (true, false)
  
</configuration>


How is your application launched/killed? (eg. commands, location of .exe, etc):

Sociable launches from an .exe file entitled as "Cloud4All.exe", which also exists under the root path(C:\Sociable)

How can one detect whether application is installed? (eg. registry lookup):

You can detect that the application is properly installed by searching for the existence of the folder "Sociable" in path: "C:\". Sociable does not write in registry.

Sample Social Networkng App [BD]

Short description of you application (1 paragraph or so):

How are settings stored for your application? (eg. XML):

How is your application launched/killed? (eg. commands, location of .exe, etc):

How can one detect whether application is installed? (eg. registry lookup):


SuperNova (Enlogic): Nikos Demou

Short description of your application (1 paragraph or so):

Supernova is a screen reading and magnification software for Windows for people with visual impairements (blind or low vision).

How are settings stored for your application? (eg. XML):

The settings are strored in binary files under the Settings directory. We're developing a custom application (snconf.exe) which is responsible to change Supernova settings

How is your application launched/killed? (eg. commands, location of .exe, etc):

The application is launched by running "snconf.exe /s". It is killed by calling "snconf.exe /k".

How can one detect whether application is installed? (eg. registry lookup):

Check for the existance of this registry entry: HKEY_LOCAL_MACHINE\Software\enLogic\snconf

Mobile Access (Code Factory)

Short description of you application (1 paragraph or so):

Mobile Accessibility is an app which makes Android devices accessible for blind users. It consists on 2 main components: Suite of 12 accessbile apps with simplified UI + Screen Reader which implements native Accessibility API features.

How are settings stored for your application? (eg. XML):

Mobile Accessibility stores settings through native SharedPreferences mechanism present in Android API.

Visit http://developer.android.com/reference/android/content/SharedPreferences.html for more information.

How is your application launched/killed? (eg. commands, location of .exe, etc):

MA suite of apps is registered as Home Screen for Android devices, so once installed and selected as default Home Screen by the user, it is always ON and pressing the pyshical Home Key will go to the main MA screen.

Deactivating the default preference whick makes MA to be the main home scren would mean to "Clear Defaults" under Settings > apps > Mobile Accessibility.

MA Screen Reader can be activated under Settings > Accessibility on the native Android UI.

Doing changes on such native settings programmatically would need Root privileges and maybe also using non-documented techniques.

How can one detect whether application is installed? (eg. registry lookup):

Look in the device for an app with package name including "es.codefactory.android.app.ma".

Allan eC (Omnitor)

Short description of you application (1 paragraph or so):

How are settings stored for your application? (eg. XML):

How is your application launched/killed? (eg. commands, location of .exe, etc):

How can one detect whether application is installed? (eg. registry lookup):


Maavis (Open Directive)

Short description of you application:

Maavis is a Windows program that provides very simple access to media and communications. It is designed for use by people with dementia or very low digital literacy. Maavis it not so much an end user ready program as a tool for facilitators to setup up an end user experience; for example it can be configured by simply adding media files into folders. In order that Maavis can be tested 'out of the box' a basic configuration, complete with sample media is provided in the installer. it is expected that this will be tested.

How are settings stored for your application? (eg. XML):

The settings that are alterable by GPII are store in a JSON formatted file called userconfig.json. An example is

{
"userType:" "touch, 
"theme": "colour, 
"speakTitles": "yes, 
"showLabels": "yes, 
"showImages": "yes, 
"useSkype": "no, 
"scanMode": "AUTO1SWITCHAUTOSTART, 
"scanRate": "2500, 
"speakLabels": "no, 
"selectionsSetSize": "2x3, 
"passwordItems": "images, 
"passwordSetSize": "4x3, 
"splashTime": 2 , 
"name": "Default"
}

Maavis also support multiple users,that may have their own media sets. However when run by the GPII the default user settings are used (these are those used when a user is not specified explicitly to Maavis). This settings file can be found as <MaavisPortable>\MaavisMedia\Users\Default\userconfig.json

How is your application launched/killed?:

The Maavis installer creates a "MaavisPortable" folder on the desktop by default. Maavis is run as the default user by executing "MaavisPortable.cmd" in that folder. This is how the GPII runs it. Note Firefox must not already be running. Maavis may be exited by "ALT+Q" key combination or by killing the Firefox process using task manager or the "taskkill" command (the later is how GPII kills it)

How can one detect whether application is installed?:

The easiest way is to look for the MaavisPortable folder on the desktop. Maavis is a portable app and so is not installed in the conventional sense of updating the registry etc. However for GPII to locate it an Environment Variable MAAVIS_HOME is set by the 'installer'. Thus this can be used to see if Maavis was ever installed, but is there no guarantee it has not been subsequently deleted.

Logging in GPII users

Maavis has been tested using the 3 current login methods; browse to a URL, USB listener and NFC listener. Details are provided on the Maavis developer setup page.

ReadWrite Gold & SpeechStream (TextHelp)

Short description of your application (1 paragraph or so)
BrowseAloud Plus (a customisation of SpeechStream) is a JavaScript application which provides text-to-speech facilities for web pages and implements a small sub-set of the features currently available in Read&Write (dual-colour highlighting, continuous reading). The features of the product will be extended in the coming months to include more of the existing Read&Write features (speech control, language tools, reading aids and so on).

How are settings stored for your application? (eg. XML):
Our original expectations were that settings would be stored in a SQL Server database and pushed/pulled via AJAX and JSON.

How is your application launched/killed? (eg. commands, location of .exe, etc):
The application is launched in one of two ways: by end users creating and invoking a bookmarklet within their browsers or by website owners embedding a snippet of custom JavaScript which draws a button to trigger the application. There's currently no mechanism to kill it, but the application only lives within the current page - so navigating to a different page/website will remove it from the current context.

How can one detect whether application is installed? (eg. registry lookup):
BrowseAloud Plus doesn't install anything locally. When invoked, it simply retrieves JavaScript from our servers and inserts it into the current web page.