Danielo,

I explored using noteself as a replacement for tiddlyfox saving. IOW, I did 
not use the couchdb server functionality. I faced some issues which I share 
below:

Issues 3 and 7 seem to be pouchdb/noteself specific, the rest might be 
fundamental issues with the skinny tiddler approach. I guess even 3 is 
skinny tiddler related.


   1. *Feedback on import progress* - I used the browse widget to select a 
   tiddlywiki file with over 1000 tiddlers and it wasn't easy to tell that the 
   import was still in progress. Not realizing it was still in progress, I 
   refreshed the page only to discover after careful inspection that the 
   import was incomplete. Finally I learned I could tell the import was 
   complete in one of two ways
   1. During the import the save button stays solid red and it loses the 
      color once the import is complete
      2. Open the javascript console and wait for the import messages to 
      stop
   2. *importvariables widget* doesn't work unless all the tiddlers being 
   imported are opened manually ahead of time
   3. *Drafts* - directly opening a draft is empty. "Directly opening a 
   draft" happens when you have a tiddler in draft mode (and it gets saved 
   that way) and then you refresh the browser. Steps to reproduce:
   1. open wiki and create a new tiddler, adding some text to the body
      2. leave it in edit mode and refresh the TW browser page
      3. click on the "Draft of 'New tiddler'" link in the recent tab
      4. the tiddler will be empty (i.e. the body text is lost)
   - This is a data-loss situation...I didn't find a way via tiddlywiki to 
      recover the draft contents. Probably the data is somewhere in pouchdb, 
but 
      I didn't dig into it.
      4. *Shadow version of some tiddlers wreaks havoc*
   - I use the codemirror plugin with vim mode and its use of the Escape 
      key conflicted with cancelling edits, so I had a modified 
      $:/core/ui/EditTemplate wherein I changed the cancel key to Ctrl-Escape. 
      For some reason (probably a good reason), having a shadow version of a 
      tiddler causes a periodic scan (20-30 seconds maybe?) into pouchdb for 
      changes. Whether there were any changes found or not, all the tiddlers in 
      the scan list get refreshed. Refreshing the edit template while there are 
      any drafts open causes focus to move from the text body and into the 
title 
      and the title is selected. If typing is going on, then the title ends up 
      getting deleted and replaced by that typing. I found the newest version 
of 
      TW has keyboard configuration which obsoletes my need for the shadow 
      instance of the Edit Template
      - TLDR: Don't store shadow instances of Edit Template in the pouchdb
      5. *Having lots of tiddlers loaded really slows things down* - with 
   my >1000 tiddler TW instance it became very slow if all the tiddlers get 
   loaded. For example, if I hit the save button in order to get a json export 
   of the TW, that would cause all the tiddlers to be loaded. It would also 
   cause >1000 periodic scans to pouchdb for changes to these tiddlers. I 
   would have to refresh the browser page after exporting to json in order to 
   not suffer slowdowns.
   6. *Manual load of any tiddler required before accessing anything other 
   than title field*. This affects
   1. Search can only match on titles
      2. Any list filters matching against fields other than title field. I 
      have several pieces of custom functionality which use such filters
   7. *Export from search broken* - I decided to move my changes back into 
   a non-pouchdb TW, but found the menu which allows export to .csv, .json, 
   .tid, etc. was broken. Instead of downloading the results of the search in 
   the requested format, the entire TW was downloaded only in json format. 
   Seemed like the export was taking the same functionality as the Save button 
   in the sidebar. I ended up dragging the tiddlers one-by-one into the other 
   TW instance. Only a dozen or so, so it wasn't too bad.
   
This was a fun experiment...thanks for sharing your work.

Brian

-- 
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/e232e345-b788-4fcc-a8e3-3d9a19435a27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to