Another possibility would be to have an error log tiddler - this would be a 
temp tiddler - not saved, to stop it becoming large. All widgets and js 
macros could write to this tiddler, it could even be a 'virtual' tiddler, 
not stored in the store but connected to $tw - this would be for 
performance reasons.

On Thursday, January 18, 2018 at 7:20:09 PM UTC, Evan Balster wrote:
>
> Hey, all —
>
> I've been thinking recently about how TiddlyWiki could benefit from 
> something like the "errors and warnings" list provided by a compiler.  When 
> displayed or previewed, the tiddler would display a small "problems" badge 
> that could be expanded to display an accumulated list of any problems 
> detected in the course of parsing, execution and rendering.  This would 
> help with a number of situations where TiddlyWiki simply doesn't do what is 
> expected.
>
> At a baseline this could be a very simple listing of each error message, 
> paired with a line number indicating where the originating widget lies.  
> Some kind of "catcher" widget enclosing the tiddler could accumulate these 
> messages as they're generated.  Other widgets like transclude and macrocall 
> could catch and modify the messages to note any indirections in their 
> origin.  But bells and whistles aren't really necessary in the short term — 
> just a way to see the information in the first place.  Improvements can be 
> made gradually.
>
> I'm mainly thinking about this because it's becoming increasingly apparent 
> I need a better way to indicate various errors in formula computation, 
> which is often used to generate attribute values or placed inside SVGs 
> (making any error text output invisible).
>
>
> As a sidenote, this mechanism might be useful for implementing refresh 
> integrity checks.  When those diagnostics are active, any discrepancy in 
> the refresh could be noted as a critical error.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/959e6d06-b962-4be6-acab-7c9b8174ef1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to