Jeremy, Can we not provide an edit-text widget equivalent (or feature) that when invoked in currentTiddler allows editing the fields outside the refresh mechanism and defers refresh to when the tiddler is saved, closed etc...?
- Whilst I know there are technical issues that must be addressed I feel overcoming this will empower users to use tiddlers as forms much more easily. Creative design techniques are required here, all I can say is as an observer is its a barrier to tiddlywiki use. - The Draft mechanism was designed to solve a problem at the time and still has its place, but I can't help but feel it has this negative side effect. - Of course I now know, how to work around it, but despite doing it multiple times, I have still not being able to make a user friendly solution I can share with newbees. As raised before it is cognitively complex. - It seems to me that if tiddlywiki refreshes its tree by design, that surely we can provide a mechanism to defer it. Here is my hair brained idea, potentially ill informed speculation - Is it possible to get the current tiddler/input field to exist within the standard DOM even if we need a trigger to submit it to tiddlywikis DOM - Could this facilitate the introduction of more advanced html in tiddlers such as onclick in tiddlers or able to access script inserted with raw tags? - I imagine a way to have html that on "submit" can create a tiddler containing the results. - This would open tiddlywiki to leverage the considerable library of forms and pages available on the internet. Regards Tony On Tuesday, February 11, 2020 at 11:35:19 PM UTC+11, Jeremy Ruston wrote: > > Hi Mat > > On 11 Feb 2020, at 11:42, Mat <[email protected] <javascript:>> wrote: > > I'm hijacking the thread (since the question seems straightened out) with > a long shot but: The long time problem with refresh and therefore lost > focus when one is editing a maro tiddler... could this somehow be prevented > using importvariables…? > > > The long time problem with the refresh mechanism is that it doesn’t > maintain certain state when widgets are deleted and recreated as part of > the refresh cycle (selection status, focus, scroll positions, the state of > summary/detail widgets etc). > > Xavier’s specific problem here is that changing a global macro tiddler > causes the entire page template to be reconstructed, losing the focus > status. > > The lack of state preservation is a major flaw that I’d like to see fixed. > We have some proposals for partial solutions that work for some state in > some situations, but we really need a rethink that makes state preservation > just work. One possibility is adopting a more conventional virtual DOM > strategy for updating the DOM. > > Best wishes > > Jeremy. > > > -- 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/c69de94e-36a3-4f0f-a7d5-07085ec42568%40googlegroups.com.
