I've drawn up a JIRA summarising the immediate motivations we might have for such a system (our upcoming
UIOptions refactoring work), a potential syntax, and some other use cases for it at
http://issues.fluidproject.org/browse/FLUID-4873
As a "potted summary", the proposal is to support this very tiny subset of the CSS selector syntax (almost
the same as that supported within the Fluid Renderer system for "cutpoints") for what we might call "IoCSS"
selectors which are capable of making downward assertions about the matching of a component or group of
components below a component tree root:
* - matches any component - universal selector
E - matches any component holding a context name of E - special support for the string "that" as in current
IoC context matching
E#myid - matches any component with a context name of E with id equal to myid
And the following two descendent rules:
E F - Matches any F element that is a descendant of an E element.
E > F - Matches any F element that is a direct child of an E element
Please supply comments, suggestions, questions, and improvements - if we have some time at today's community
meeting we could also discuss this a bit -
Cheers,
A
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
