Documentation gap for Prefs Framework, and UIO confusion

Hung, Jonathan jhung at
Thu Mar 7 15:50:54 UTC 2019

Thanks Alan. What you described makes sense. Something like that should make its way into the UIO documentation. I'll make a Jira for it and copy your text as an example.

In the meantime, what would the strategy be for situations where someone wants the features they see in the Prefs Framework (i.e. self-voicing and syllabification, etc.) and wants that "out of the box" experience of integration?

- Jon.

Jonathan Hung, Inclusive Designer
Email: jhung at
OCAD University
Inclusive Design Research Centre

From: Harnum, Alan
Sent: March 7, 2019 10:17:26 AM
To: Hung, Jonathan; Fluid Work
Subject: Re: Documentation gap for Prefs Framework, and UIO confusion

Hi Jon,

Thank you for starting this conversation, as I agree the distinction is not clear; however, I don’t think they are essentially the same in a number of senses. I recognize that some of this distinction might be at the level of “only meaningful to developers”, but that is a meaningful distinction for certain audiences. It’s definitely a meaningful distinction at the level of codebase architecture.

I’m going to quote some of an email I sent to some of the CAST partners in July, as I explained my take on the situation there:


Briefly, I want to highlight a distinction between two pieces of the Fluid Project’s Infusion JS framework:

User Interface Options (UIO) is a “standard” component for providing a UI for end users to customize the appearance and behavior of websites. This is what’s described in the documentation at and, what we typically use on our own sites, and what we recommend for use by others if they don’t have specific needs.

The Preferences Framework is an underlying piece of the Infusion framework that UIO is built with – the framework is designed to support a wide variety of approaches to building preferences editors, of which UIO is one possible manifestation. It’s described in detail at and corresponding sections.

So particularly when working with integration with other code (especially code also wanting to expose controls to the user to customize a website), there are options beyond “out of the box” use of UIO that can still draw on the Fluid’s Projects codebase. These have a higher complexity than UIO, but I wanted to make sure to highlight the distinction above.


The PF/UIO relationship is something like the one between D3.js (a generalized data-driven document framework, which has powerful usage for building data visualizations but also many other applications) and C3.js, Plotly, NVD3, etc (various chart generation libraries built on top of D3.js) – it is quite meaningful if you’re a developer making choices about how to build something.

From: fluid-work <fluid-work-bounces at> on behalf of "Hung, Jonathan" <jhung at>
Date: Thursday, March 7, 2019 at 9:55 AM
To: Fluid Work <fluid-work at>
Subject: Documentation gap for Prefs Framework, and UIO confusion

Hi everyone,

I spend a fair amount of time working with partners about integrating our tools into their projects, namely UI Options. Ideally I would like to be able to point our partners to a single demo, and a single guide so they can get up and running as quickly as possible. I can do that with UIO, but not Prefs Framework currently:

  1.  UI Options a nice user-friendly guide on how to set up UI Options here<>. The Prefs Framework does not have a similar guide.
  2.  It's never really explained in the documentation what the differences are between the Prefs Framework and UIO, and why someone would choose one over the other.
  3.  Is there a reason to maintain the distinction between Prefs Framework and UIO?

To me the core issue is that Prefs Framework and UIO are essentially the same, but currently there is a disparity in the documentation between these two entities. Would it make sense to:

  *   convert the UIO documentation to be Prefs Framework centric
  *   stop using the term "UIO", and focus on the "Prefs Framework"
  *   explain how Prefs Framework can tailored to your needs by either taking away features you don't need, or adding features you want

For now I will continue to point partners to UIO because it's a friendlier path, but ideally I would like a strategy for getting them to use Prefs Framework instead.

- Jon.

Jonathan Hung, Inclusive Designer
Email: jhung at
OCAD University
Inclusive Design Research Centre

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list