Search results

Jump to: navigation, search
  • *See [[Installing the GPII]] or [[Setting Up Your Development Environment]] for installation on Linux and Windows. The [ ...All Project that is currently exploring and building many of the core components of the GPII (as can be seen below), links to other funded projects such as
    10 KB (1,504 words) - 17:47, 11 October 2017
  • ## Information about the device's characteristics and the user's working environment (with their permission) (from the '''Device Characteristics Reporter''') ## Resolving device, context, and environment-specific conditions for those settings
    16 KB (2,327 words) - 04:20, 22 August 2015
  • .../ GPII Github Organization] for more information about GPII development.'' ...would basically be a first working implementation of the architecture, the components will be simplified to various degrees, and some will even be implemented as
    10 KB (1,599 words) - 01:11, 14 August 2015
  • * It might make sense to build either components to or generic OS level SALHs that are able to handle: events from registry * Can we have native components without a node.js server/module (e.g. user listener)?
    4 KB (634 words) - 19:20, 26 June 2013
  • ...ble for (e.g., considering the user state, the user activity, the physical environment, etc.); *The ontology development will be based on an '''iterative and incremental approach''', keeping it si
    16 KB (2,208 words) - 17:27, 9 March 2015
  • ...ud-based service. The matching process between the user needs and the user environment can be performed by several approaches: rule-based approaches, statistical ...ed AT. The personalization framework is under development. Definitions and components can be changed or renamed.
    5 KB (644 words) - 20:09, 13 November 2015
  • = Getting Set Up For GPII Personalization Framework Development = ...-platform. It is written in JavaScript and deployed in the Node.js runtime environment, which is widely supported on Windows, Linux, Mac OS X, and even some mobil
    18 KB (2,679 words) - 18:06, 2 March 2017
  • = Areas of GPII needing research and development<br/> = #<span style="font-size:large">'''Development Environment/ WorkBench for Access Technologies and services'''</span>
    21 KB (3,311 words) - 19:08, 2 September 2012
  • *For development, generated profiles are sufficient. contexts of interaction are presented, so the user can test different components and parameters, and the system learns the user characteristics, from his im
    6 KB (857 words) - 17:09, 17 January 2014
  • a video resource and is deaf, hard of hearing, or is working in a noisy environment, SenseAble can match this need with any associated captions or sign languag ...with suitable OERs (Open Education Resources) through a set of embeddable components and services as part of the Fluid Infusion code solution [5].
    5 KB (668 words) - 18:15, 17 January 2014
  • ...the user, etc. The solution registry is held in a database (or in case of development, local testing or deployment with no internet - in a flat file). Like all o The solution metadata is used by several components of the GPII;
    18 KB (1,789 words) - 19:05, 15 September 2015
  • ...ere are many rough edges, but it provides a good start point for continued development. The Cloud4all framework team anticipates putting out regular stable releas ...r configurable deployment profiles (local or remote) of the core Cloud4all components
    4 KB (563 words) - 19:00, 26 June 2013
  • GNOME 3; GNOME 2 lives on in the [ MATE Desktop Environment], which also uses [ gsettings]. ...ers are well defined, and it is one of the most versatile environments for development purposes.
    9 KB (1,437 words) - 13:58, 28 April 2015
  • This page describes the QA testing process of the core components of the architecture. === A5: Launch in production and development mode (ie. use remote prefs server) ===
    10 KB (1,609 words) - 19:48, 14 June 2013
  • ...phase and for each prototype, in close collaboration with all the relevant development teams, in order to detail the '''goals''', the '''indicators''' and the ''' ...findings of this activity will be continuously fed back to the respective development teams. In this way, from each evaluation round, results both from the users
    24 KB (3,460 words) - 15:56, 15 March 2017
  • ...hard disk space (150 MB for the Architecture + 126 MB for Java SE Runtime Environment + 100 MB for rule-based MM + 2 MB for statistical MB + 50 MB for NVDA + 200 Java SE Runtime Environment (JRE)] 6 or higher (for the rule-based matchmaker).
    76 KB (11,259 words) - 19:56, 14 June 2013
  • ...e on Android. This is, necessarily, written in Javascript running on a V8 environment, in our case Node.js. === Can I still code my Accessiblity components in Java? ===
    4 KB (610 words) - 21:21, 30 June 2014
  • new or editing existing JSON configuration files that describe various components for specific GPII/Kettle deployment types. With the help of these configuration files, developers can configure which components are deployed and with what settings. Examples of such configurations includ
    18 KB (1,877 words) - 20:44, 16 March 2014
  • ...ility, modularity, and interoperability of the GPII project’s technology development efforts. This architecture is intended to reach across a variety of platfor * a set of interoperable components, service APIs, and data exchange formats
    83 KB (11,770 words) - 18:29, 23 August 2017
  • ...n Cloud4all/GPII are large and ambitious; we want to provide users with an environment that: ...the Cloud4all framework, which are being used throughout most of the other components including the Matchmakers. We need to ensure that any security/privacy/auth
    13 KB (2,134 words) - 13:34, 6 August 2013

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)