I see dropping modified tiddler as a bug.

I am intensively working with PBWorks at the moment (while preparing 
transfer to TW in future).
PBWorks gives you all indicators of the processes taking place. I know, for 
example, that saving finished when a URL with no "edit" appeared. Then, 
it's safe to close the window.
Another protection measures they have is a warning dialogue on closing page 
being edited, before the save button pressed.

I think, we have to learn best practices from other platforms, collect them 
within just one platform, and implement as soon as practical.
Sorry for being persistent with the simple idea:
our team performance depends on how quick particular topics are 
found/discovered for reuse.
Please let me know if this mechanism is already realised, and that's just 
me who can't see it.

Thank you,
Dmitry

On Saturday, 24 December 2016 10:17:50 UTC+13, Arlen Beiler wrote:
>
> I just had an idea. The way the NodeJS server currently works is 
> asynchronous. It syncs with the server and then returns to the browser. 
> Then the server syncs to the file system and returns. If there would have 
> been a time where you closed your draft, waited for the check mark to turn 
> grey, and then immediately exited, it is possible that the server could 
> have missed writing the files. Try to see if you can replicate it like 
> this. If so, that may be the problem. 
>
> The way I dealt with that was to hack tiddlywiki (forget how, but I think 
> involved some of the first code in boot.js or bootprefix.js) so that it 
> would save directly to the file system from the browser. 
>
> Here's a gist that I posted 
> https://gist.github.com/Arlen22/45f1a460c9e348fa50ad
>
> For electron you would set the data directory in index.html, then open 
> index.html in a new BrowserWindow. And your done. The file syncer actually 
> takes care of saving changes, so it should stay red until the file actually 
> gets saved.
>
> On Thu, Dec 22, 2016 at 9:51 AM, 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com <javascript:>> wrote:
>
>> Not necessarily a bug in TW per se. No one ever promised (that I know of) 
>> that it would work on Electron. Definitely no one promised that it would 
>> work with a custom version of Electron and if it's on a custom branch of 
>> TW5 that depends on sensing its platform  --- all bets are off.
>>
>> Just depending on small desktop web/file  servers (like node.js) has 
>> always been risky in my experience. The hardware and the software may not 
>> be robust enough in all situations. Usually, there are time lags. Your 
>> machine may prioritize your email or web browsing over the web server.  If 
>> you shut down your machine or server before a save has completed (which 
>> might happen if you have a 3 or 5 page tiddler) then the chances are even 
>> greater. The trick in that situation would be to either save your own copy 
>> of current work locally or to break the work into smaller chunks. The 
>> editing tools in TW5 make working with smaller chunks easier than before.
>>
>>  If you check the forum, you will see that reports of actual data loss 
>> are fairly rare. The file-based TW seems to save itself reliably.  To be an 
>> actual bug you would need to see a repeatable set of standard circumstances 
>> under which TW fails to save.
>>
>> Have fun,
>> Mark
>>
>>
>> On Thursday, December 22, 2016 at 4:30:15 AM UTC-8, Arlen Beiler wrote:
>>>
>>> Nevertheless, this is a bug. TiddlyWiki should never lose changes no 
>>> matter how big the Tiddler is. Thanks for the info, though. I hope we can 
>>> find any problems that are causing it. 
>>>
>>> I have frankly never just used the draft idea before, I always save the 
>>> Tiddler when I am done writing. And I would recommend doing that normally. 
>>> However, it seems you are supposed to be able to save a draft and come back 
>>> to it later.
>>>
>>> On Dec 12, 2016 14:24, "Bruno Loff" <bruno...@gmail.com> wrote:
>>>
>>>> Yes it was.
>>>>
>>>> On Monday, 12 December 2016 19:46:54 UTC+1, Mark S. wrote:
>>>>>
>>>>> But, was all that work -- 3 to 5 pages -- in a single tiddler?
>>>>>
>>>>> Mark
>>>>>
>>>>> On Monday, December 12, 2016 at 9:13:45 AM UTC-8, Bruno Loff wrote:
>>>>>>
>>>>>> Tiddlywiki was running on electron v1.4 on Arch Linux; the server 
>>>>>> side was running on electron's server (a node.js process), and the 
>>>>>> webpage 
>>>>>> was running on electron's chromium process. So all of it was localhost.
>>>>>>
>>>>>> I was working on a slightly modified fork (
>>>>>> https://github.com/bloff/TiddlyWiki5), that included a minimal 
>>>>>> change to detect when TW was running under electron.
>>>>>>
>>>>>> It also included various plugins that I wrote/modified to serve my 
>>>>>> purposes (customized katex plugin, a plugin for managing bibtex 
>>>>>> citations, 
>>>>>> and a plugin to interface with electron), which is roughly keeping track 
>>>>>> of 
>>>>>> my mathematical writeups, lecture-notes, etc. but I don't think these 
>>>>>> were 
>>>>>> to blame.
>>>>>>
>>>>>> 14 of work amounted to roughly 3-5 pages. That's not much.
>>>>>>
>>>>>> -- 
>>>> 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 tiddlywiki+...@googlegroups.com.
>>>> To post to this group, send email to tiddl...@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/tiddlywiki.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/tiddlywiki/52d252e2-dcc0-4fdb-875a-008e02bcb3b9%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/tiddlywiki/52d252e2-dcc0-4fdb-875a-008e02bcb3b9%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> -- 
>> 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 tiddlywiki+...@googlegroups.com <javascript:>.
>> To post to this group, send email to tiddl...@googlegroups.com 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/tiddlywiki.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/bd625aa3-3198-4c47-a67d-471c8eb5e2c7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/bd625aa3-3198-4c47-a67d-471c8eb5e2c7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/6e376797-8eb4-4ec1-b7da-5019f31523d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to