On Oct 25, 7:43 pm, ccahua <[EMAIL PROTECTED]> wrote: > On Oct 23, 5:20 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > For spowt I wrote a plugin that changes the defaultCustomFields so > > that clicking on new tiddler or new journal will result in tiddlers > > being saved back to the server, but that behavior hasn't been > > transferred anywhere else yet. You can see that plugin > > >here:http://svn.tiddlywiki.org/Trunk/verticals/tiddlywebclient/plugins/Tid... > > I tried changing the config.defaultCustomFields in the plugin, but > couldn't get it going:
I think you've got the syntax a little bit messed up, although that may not be the entirety of the problem. The basic issue here is that TiddlyWeb doesn't know to save stuff to the server unless some values are set in the fields. The default fields that you are setting need to have values that exist on the server. The SpowtDefaulter plugin sets specific values based on what it can assume is available on the server, but only when the plugin has been delivered by spowt. So we need to choose some different values. > first with an empty workspace attribute: > > 'http://0.0.0.0:8080/':tiddler.fields['server.host'], > 'bag1': tiddler.fields['server.workspace'], > '': tiddler.fields['server.workspace'], > 'tiddlyweb': tiddler.fields['server.type'], Here you are a creating a dictionary (or hash or associative array) of the values you want to the values present in the TiddlyWebAutoSavePlugin. What you want instead is something more like: 'server.host': 'http://0.0.0.0:8080/', 'server.bag': 'bag1', 'server.workspace': '', 'server.type': 'tiddlyweb', This assumes that you want all your tiddlers saved back to the bag named bag1. If server.bag is present it is always used. If it is not present and workspace is, workspace represents the name of a recipe on the server. I think thus far in your testing you haven't been using recipes, so just using bag should be fine. > Despite failure, the interesting result out of this after importing > the defaulter plugin was in Windows, the chkHttpReadOnly would default > to 'true' (tiddlers.wiki view is readonly) and I'd get that 'you have > to Save this TiddlyWiki..." dialog (when i tried to save a new > tiddler) but on OSX i get no dialog notification and no readonly > default which I like and think should be the default status. Please > let me know if i should put this comment in some ticket. Wait awhile until you get the other things working and then if it is still there, then yes, please make a ticket. > From a user perspective if TiddlyWeb could retain that familiar > TiddlyWiki experience but with all the cool flexible serverside access > that would be reassuring and add in adoption. We're hoping to get it to that level of niceness someday. > I'm hoping your TiddlyWeb server side reference can help me with the > local scale issue I have with TiddlyWiki without having to install > xampp or big server distro and where the stores in the filesystem are > the nodes in the 'network' ~ big and localhost with that TiddlyWiki UI > beauty. This is definitely one of the use cases that I'm hoping TiddlyWeb will facilitate. One of the reasons for using Python's WSGI spec is so the code can run with servers little or large. And the storage mechanism is extensible so it is possible to adapt the storage system to little and large situations as well. Thanks for all your input and work. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
