QText

Allow multi-level bullet-lists/numbered-lists without needing to resort to HTML: (My mail client uses Markdown, and allows 2-level-deep lists; I don't know if that's a custom enhancement or if Markdown supports it.)

Of course, it's a little more perlious in Querki because when generating QText it's easy to accidentally have extra whitespace.

Ampersand does not parse correctly: The heart of the recipe is: put an ampersand in a Chart Label for a Rating. Display the Summary for that Rating inside of the Instance Edit View of the Review Model that incorporates it.

As a Querki programmer, I can enhance QText more easily: This is the motivating story to rewrite the QText parser from scratch, probably in FastParse.

Can't use plain numbers as HTML attributes: The specific case where this came up was for tables: you can't say <td colspan=4> -- it doesn't pass the whitelisting in BaseParsers.scala::xmlAttrVal

Explicitly divs interact poorly with auto-paragraphs: Take the following QText:

<div class="myClass">


Foo

</div>

Does this work as expected? No, because the lines containing the div tags themselves get automatically wrapped in paragraphs, so you get a < /div> at the end of the first line, nicely foiling it.

Horizontal Rule is too faint to see on some monitors: Dad reports that he can barely see the standard horizontal rule on one of his monitors, and only with squinting on another. We should probably tweak the CSS to make it a bit darker.

I can easily link to sections on my page: This is a pretty common feature nowadays: when I hover over a header, a link icon appears next to it, and I can click that to get the URL to that link.

I should be able to create hyperlinks that jump to elsewhere on a page (like hypertext anchors): Long pages really want to have tables of contents. However, Querki's URL system hijacks the normal use of #, making that impossible. The underlying details don't matter - it could selectively suppress Querki's normal use of # for navigation, or it could be something that doesn't interact with the normal HTML anchoring system at all - but something to allow anchors would be useful for long pages.

I should be able to insert comments in my QText: Both line-oriented comments with //, and block-oriented /* ... */ comments.

I should be able to insert Tabs into my QText: Not actually clear that this is possible, but it's worth investigating.

It is unreasonably hard to combine QText paragraphs with divs: Since we are interpreting paragraphs as div's, things can easily get auto-closed when you don't want it when trying to use div's explicitly for layout, to apply classes.

Mismatched XML causes mysterious-sounding errors: Because we sometimes do XML parsing of the Wikitext, mismatched HTML tags can cause loud and hard-to-understand failures. For example, put a simple <br> tag (not XHTML-styled) into an _edit control to see this happen.

Multiple styles in a span-styled style clause don't work: When I create a div-type {{ clause, I can use multiple styles, space-separated. That doesn't seem to be working for span-style clauses.

Putting markup inside a link doesn't work: That is, if I try to boldface some text inside of a _QLButton, I get raw HTML instead.

QText should support emoji: This needs to be fleshed out, but at this point emoji are a reality that we should incorporate. At the very least, they are essential in conversations, and we might as well just build them into QText more generally.

Remove setext-style headers from QText: Inherited from Markdown, if you put a line of dashes or equals under another line, the previous line becomes a header. This sucks in Querki -- remove it.

Underscores in variable names go to italics: Eric pointed out that, on this page, the underscores in $_1 and $_2 were italicizing. I fixed the symptom, but it should happen in the first place.

Using a Large Text Property inline produces surprising effects: Embedding a Large Text Property in the middle of a line can screw up QText operators at the beginning of the value.

Would be helpful to indent QText div markers: When you have deeply-nested QText class expressions, it can get hard to visually parse what's going on.

"label" should be whitelisted: Currently it isn't legal, but it is helpful for building forms with the Bootstrap stuff.

_showLink is over-escaping its contents: I have a Property containing [[Visible Game Items -> Qualify Game Items By Type]] - [[_showLink(Update Summary)]]. When Update Summary has characters that need to be HTML-escaped in it, they display as the full HTML-escaped string, which makes it really hard to skim. If I eliminate the _showLink call, Update Summary displays correctly.

A space after a class name screws up the QText:

Collection-accepting Text Literals don't work correctly with an empty context: If I say something -> *""blah blah ____ blah blah"", and something is empty, I expect it to show "blah blah blah blah". But currently, it shows nothing.

I can suppress line breaks entirely in a chunk of text: This is a request for "!+noLines", which would be sort of a super-powered version of !+rawLines. It would suppress not only paragraphs, but linebreaks as well. It would serve as a rough but functional workaround for the difficulties of specifying divs in QText.

I should be able to compare Tags and Parsed Text to a Text Literal: Eric noted that he tried some obvious _equals expressions, and they didn't work. That's because we don't have the appropriate type coercion yet.

I should be able to define an anchor tag that opens a new tab: Basically, Eric would like a whitelist for the common target="_blank" construct. That's reasonably safe, and indeed likely to become the default, so it seems fine.

I should be able to indent HTML tags in QText arbitrarily: This is the motivating story for scrapping the four-space codeLine that we inherited from Markdown.

I should be able to specify that an HTML element is disabled: Currently, there is no way (even if you are building raw XML) to show a disabled button.