View Single Post
Old 10-28-2016, 01:41 PM   #7
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,361
Karma: 20212223
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
Quote:
Originally Posted by DiapDealer View Post
To tell the truth, I'd almost be in favor of removing the wellformedness check altogether. 1) People seem to want to rely on it for more than what it was intended for. And 2) The preview window tends to immediately inform someone (pink box) when entered/altered code is fatally incorrect anyway.
My .02: I use the pink box in the preview window as well. Although it would be really nice if you could replace the "wellformedness check" (F7) with the code used in the SanityChecker plugin.... or some other easy way to identify when a particular file fails the wellformedness check. I think one suggestion mentioned in a previous thread was to make the file name bold or red in the Book Browser so the user can easily see which file is causing the problem. Or maybe putting a selectable list of offending files down in the Validation Results window when you click F7...

Just some ideas.
Turtle91 is offline   Reply With Quote