This updates the theme picker to include brews tagged as themes owned by
the user.
Some supporting functions were updated. User themes are loaded on /edit
and added to the request.
This consolidates the style/theme endpoint to a singular method, adds
interpretation of static themes, and allow parent theme recursion.
I am not 100% sure this will order styles correctly.
This has been implemented three different ways to allow for comparison
and discussion
- /api/css/:id : This returns the style frontmatter of the referenced
document as a text/css document.
/api/theme/:id : This returns an object with the reference'd object's
theme and style frontmatter.
/api/csstheme/:id : This returns the stylye frontmatter of the
referenced document as a text/css document and adds the theme as an
@import ( if not using the legacy renderer )
Discovered that classes ( and possibly other splits could end up with an
empty/null member that still gets joined so I added a trim to the end of
all the joins in processStyleTags.
Added tests that SHOULD test for bloc-level and inline-span moustaches
with added attributes ( a=b )
Wraps with quotes ( a="b and c" )
Still does not work on Mustache Divs. UNsure where the failure is at the
moment. Even regressed "a:b and c" pattern on those.
This should match more economically and in line with marked
recomendations as well as not allow whitespace ( \s ) at the beginning
or end of a sub or superscript mark. Additionally, a failure in having
mixed sub and supers on the same line was corrected.
Uses ^^ for superscript and ^^^ subscript as wrappers in the same
pattern as italics and bold ( * and **, respectively)
Adds editor hot-keys and sytax highlighting. (CTRL-6/CTRL-7)
Exact values may not be ideal. Short of the suggestted overloading of ~,
I didn't see a better option for the delimiter.
This adds the ability to include attribute values for any element that
can be altered by a moustache.
Form:
```
{attribute=value}
example:
 {position:absolute,bottom:20px,left:130px,width:220px,a=b and c,g=h}
```
In order to permit spaces, the pattern matches for moustache code had to
remove the space character as a delimiter. I believe I have adequate
compensated.
This should solve #1488
David Bolack
