Folks, In my response here to a performance issue https://groups.google.com/d/msg/tiddlywiki/Y1SMtIen5ww/Nn9kggVFCAAJ
I was wondering if the fact Tiddlywiki always refreshes everything is not forcing everything through one process? Whilst this may be needed as a rule, where has being a few question raise and refresh suppression I was wondering if there is an opportunity to allow some processes to be moved into their own thread, perhaps leaving a splash screen equivalent behind while the process runs? Could we wrap a section of wiki text in a widget that does this, knowing full well that unless intermediate results outside the process is not a dependency, the process is independent and only rendered when complete? - This would allow interaction to return to the user quicker - It provides for large dataset cases - We could even hide the process behind a refresh button, or previous results. Why - This could extend tiddlywiki into larger datasets and more efficient processing, and higher interactivity. Regards Tones/Tony -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/31bc987c-29d8-4ad2-9fc3-2c7410cf06f4o%40googlegroups.com.
