document.getElementById('_z').innerHTML=paramObject.tiddler don't work. I
see only final tiddler at the end. I think, TW5 block DOM modify.
The next problem - it is too slow. Node.js static cut works faster. May be
it will be better to save *all* $:\temp\ tiddlers in IndexDB?
how can we do it?
воскресенье, 27 декабря 2020 г. в 21:01:59 UTC+3, [email protected]:
> @siniy-kit yes the JavaScript approach can work if you modify a DIV
> directly with JavaScript.
> You would also need to do a bit of extra work in advance to count the
> total number of tiddlers to render.
>
> It would be good to implement this as a widget. I have some ideas as to
> how we could do that, but I wont have the time to look into it for a few
> weeks at least.
>
> On Sunday, December 27, 2020 at 5:24:21 PM UTC+1 Siniy-Kit wrote:
>
>> may be we can edit $:/plugins/tiddlywiki/jszip/startup.js and see
>> current tiddler rendered
>> $tw.rootWidget.addEventListener("tm-zip-render-file",function(event) {
>> var paramObject = event.paramObject || {}; console.log(paramObject);
>>
>> we can add counter i=i+1, an make new fixed div with this
>> infomration....
>> воскресенье, 27 декабря 2020 г. в 14:30:36 UTC+3, [email protected]:
>>
>>> @siniy-kit
>>>
>>> I do not think what is being suggested here will work. It is easy enough
>>> to calculate how many tiddlers there are to render, and where you are in
>>> the process. The issue is that the TiddlyWiki interface will not refresh
>>> until after all the actions have been executed. So any kind of progress
>>> indicator will not display or update once the zip process starts, until
>>> after it ends.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/tiddlywiki/949a80b4-5215-422b-9c44-da19430d5c30n%40googlegroups.com.
