Hi Justin, This is an excellent summary. A few quick questions inline…
On 2013-06-11, at 7:18 PM, Justin Obara <[email protected]> wrote: > Today several of the UI Options developers met to talk about the UIO API and > how to best implement it. A new focus for UIO will be configuration through a > schema. You can see more info about the schema and new API as they shape up > on the wiki. > > http://wiki.fluidproject.org/display/fluid/Schema+for+UIO+preferences > http://wiki.fluidproject.org/display/fluid/Proposal+-+New+UIO+API These example schemas conform to the JSON Schema spec, is that right? http://json-schema.org/latest/json-schema-core.html > First of all, any implementation of UI Options and/or UI Enhancer should > expect a schema to be provided. The schema will likely be a subset of or > derived from the one held by the GPII server. Can you elaborate on this point? Which GPII server? I'm assuming you mean the Common Terms Registry. Is there any part of this schema that you think isn't covered by the data structure of the common terms registry, or that isn't relevant to it? Having these concrete examples will be very helpful as we start to implement the CTR soon. Thanks for putting them together! > • move min/max out of the settings panels' models, into standard options > • write a starter schema ( for the settings in our starter grades ) > • update the "model relay" to be "schema aware". To source defaults > from the schema. > • source the values for max, min, and etc. from the schema when panels > are configured in UIO Are people working on these specific tasks now? If so, who? Colin --- Colin Clark http://fluidproject.org _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
