Syntax errors should be contained

(Incomplete Feature, Closed -> Fixed, Priority: Critical, Test Status: No automated tests yet , Reported By Justin du Coeur, )

QL, UX

Summary: Currently, if a page has a syntax error, it generally blows the entire page -- there's little context, and it gets really annoying. Really, the syntax error should be isolated to the current "level" -- in particular, a syntax error in a QL expression should only affect that expression, and not blow the page.

I suspect this is going to want to wait until we switch the QL parser to use FastParse, where I understand exactly how to do this. FastParse is optimized for this sort of thing.