Hi Yakof you can tag your tiddlers with both "projA" and "projB" at once > That is what I actually do, but sometime I miss this point. Also if I found projB tagged tiddlers in projAtw I whish this new line would be added in IncludeList <<include "../projB/index.html" filters:"[tag[projA]]" import:4 noRefresh>>
I understand your priorities FET is in my top5 plugin along with - SharedTiddlersPlugin - TiddlyLockPlugin <http://www.minormania.com/tiddlylock/tiddlylock.html> - FileDropPlugin <http://www.TiddlyTools.com/#FileDropPlugin> - RenameTagsPlugin <http://mptw.tiddlyspot.com/#RenameTagsPlugin> , and I agree I can do it by hand. Some day I'll might ask for TW5 core 2 way tiddlers syncing... Regards Julien Le vendredi 4 avril 2014 20:13:51 UTC+2, Yakov a écrit : > > Hello Julien, > > this is not currently implemented. I have a use-case where this would be > nice, too. But I don't want to implement this using a simple approach like > "addTag" param or something like, because another time, it will be nice to > remove some tag/tags, or add a field value or ... So, what should be > implemented is something like "onTiddlerLoad" param that "eats" JavaScript > that does some changes to the tiddler. Though, actually, "syncing" should > be implemented in another way, using special "import" mode(s) that would > set a "date of syncing" field to a tiddler and take into account dates of > syncing and dates of modification of the tiddler versions in two > TiddlyWikis. > > But, to be honest, this is not a top priority dev tasks for the moment. > Currently, STP is in the process of "core refactoring" that would allow > different things like consistent search through all nodes (TWs) and also > better performance, clearer "priority/conflicts" logic and more compact > code. And, unfortunatelly, STP itself isn't the top priority development > for me now (I have to finish docs and publish an update of > ForEachTiddlerPlugin and some cool addons for it). > > On the other hand, I don't get your idea about tagging. You add the > "projA" tag to show that it's interesting for the project A. But in this > case, what's the point of tagging it projB automatically? May be just tag > it "shared A+B" or smth like that? I mean, what's the difference between > tagging "shared A+B" at once and tagging "projA" and then -- autotagging > "projB"? Does your model have something to do with multiple TWs? If that's > the case, you can tag your tiddlers with both "projA" and "projB" at once, > without waiting them to be imported. Or not? > > Best regards, > Yakov. > > пятница, 4 апреля 2014 г., 14:55:59 UTC+4 пользователь julien23 написал: >> >> Hi all >> >> I use SharedTiddlersPlugin a lot to 2 ways sync tiddlers between projects. >> >> ex projA projB >> >> I would fetch projB's tiddlers of interest for projA by >> tagging them projA in projBtw >> importing them in projAtw with SharedTiddlersPlugin : >> <<include "../projB/index.html" filters:"[tag[projA]]" import:4>> >> >> I would like something in the <<include ... >> that would allow me to tag >> them projB so I can fetch them back to projBtw if they have been modified >> in proAtw. >> >> Does this exist allready ? >> Could consider this in SharedTiddlersPlugin's developpement ? >> >> Looking forward to read from you >> >> Julien >> > -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
