Package limn.themeeditor
Theme, so that an application's users
can build a palette instead of choosing from the fifteen that ship.
ThemeEditor is the whole of it for most callers: hand it a
palette, embed it, and listen for what comes out. Beside it sit the three pieces it is
made of, each usable on its own: ThemePreview, which paints a
palette that is not the process-wide one; ThemeAudit, which
measures a palette against WCAG rather than judging it; and
ThemeEditorFiles, the optional half that opens the platform's
file chooser.
Nothing depends on this module, and nothing may. Authoring a palette and
wearing one are different jobs: an application ships a Theme, and the screen that
built it has no business on the classpath of every application that draws a button. What
crosses the line between them is a value (a Theme, or the text
ThemeFormat writes it as), which is why a palette saved here can
be loaded by an application that has never heard of this package.
-
ClassDescriptionWhat is wrong with a palette, measured rather than judged.Which side of its bar a measurement came out on.One measurement that missed its bar.How much a finding matters.Which scale a finding was measured on, and how a number on it is written.The screen an application embeds so that its users can build a palette of their own: every tone of a
Themeon a colour well, a preview that shows all of them at once, and a legibility report that names the unreadable pair before anyone ships it.The theme editor as a program you run, rather than a screen you embed.Open and Save As for aThemeEditor, through the platform's own chooser.A miniature window, painted from a palette that is not the process-wide one.