Hi Danielo > Is there any way to point the meta file from another location to the original file? This way you can take notes to your files without saving it as a tiddler. Or you can edit the file and save it on its original location. Those points are KEY for my plugin.
No, the metafile always goes alongside the associated content file. The metafile convention is quite obtrusive, but that was intentional to a certain extent: if the user has gone to the trouble of assigning metadata to a file (eg adding tags) then that represents a significant outlay of effort and concentration. Keeping the .meta file alongside the associated file makes it easy to find, backup, and to ensure that you know which metadata is current. You're pushing the design towards something a bit different than the original goals, and I'd encourage you to go for it. My main suggestion is whether you'd considered writing it as a new syncer that is independent of the existing filesystem sync adaptor. You could let the existing mechanism load the main wiki folder and introduce a new daemon that syncs with "content folders" that have different semantics, such as centralising metadata into a single file so that it doesn't pollute the file system. One reason for the suggestion is that the filesystem adaptor currently lacks support for automatically reading changes made directly to the file system. I suspect that that is something that you're going to want, and it might be easier to do in the context of a new subsystem. Best wishes Jeremy. On Sat, Jan 31, 2015 at 12:26 PM, Danielo Rodríguez <[email protected]> wrote: > >> Which sounds like the obvious thing to couple the two. Same name, >> different extension. >> > What's the bad thing in having several ways to do things? You can include > a path to the original file on the metadata file. It's just one way to do > it, doesn't mean that is the only one. > > >> >> >> The question is: Why? >> > Did you read my description? To do not pollute the folder you are indexing > with tons of metadata files. Don't you hate that? When a program put their > temp and meta files on your directory? > > >> >> >> You mean notes "about" tiddlers? >> > > No, about files. Add fields, tags, and any data you consider the tiddler > representation of your file should have. Did you get the point of what I > want to do? Is not a regular TW idea, is some kind of file index using TW > technology as backend. > > >> >> Next to the tiddler... why not? >> > > Because people do not want to have all their file in the same location. > The point of having an INDEX is to have a centralized place to search for > your files. If you have all your files on the same place, why then do you > need that index? > > > >> >> I reckon your plugin is about configuration... how do you see that >> intermingled with meta-files? >> > > Sorry, I did not get that point. Could you explain your sentence a little > bit? > > What I'm trying to achieve is something similar to tagspaces > http://www.tagspaces.org/ > > -- > 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 post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywikidev. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
