Yakov, I am using your plugin to perform some collaboration magic at my work. I may have missed it, but I need to make sure all the following are possible. Given 3 files, a "source" TW containing a large amount of content, and 2 "user" files, which are blank using a customized TW as a template. The "user" files include the "source" and the other "user" files, and the "source" includes the "user" files.
Source has a tiddler named "test". User A can see "test", and decides to update the tiddler. In my TW this is possible, but it only modifies it for user A. This is fine. User B looks at "test" and now there are 2 versions of it. I need to make sure user B sees the latest of the 2 versions. In addition, if user B updates the "newest" of the tiddlers, even though user B's physical version is the old, it overwrites the old one (I think this will happen in any case in my TWs). Then, the "source" and User A should see User B's copy as the "newest". Is this functionality included in the plugin, or does it have to be written in? I don't have more than 20 people working off of these at a time, and I think they can communicate enough to ensure they don't edit at the same time, plus I'll be having some policy involved that will help with that. Thanks. On Wed, May 29, 2013 at 5:45 PM, Yakov <[email protected]>wrote: > Right, ladies and gentlemen, > > one (or may be few) more steps to the smooth twWeb workflow. STP 2.2.0 got > the following changes: > > * <<describeNode someNodeName self>> syntax marks the name someNodeName > as the name of the current TiddlyWiki and including from that node is > forbidden (if tried, nothing happens) > ** this is done to avoid some conflicts, including unnecessary conflict > messages and disabling editing of a tiddler included from TW "A" to TW "A" > with substituting (this can happen because of transitive including) > * included tiddlers now have an additional toolbar panel in the edit mode. > As for now, it contains only a link to the origin tiddler in the source TW > -- which improves workflow of editing. It's planned to improve the panel > further -- add an "import" button and probably turn the panel into an > actual toolbar macro. This feature doesn't require any changes in the > EditTemplate as it's a hijack of the edit macro; the panel has > manageIncludedPanel class so that stylings can be adjusted > * some internal code changes are done as well to make further changes > closer > > In addition, the way to configure FireFox so that it includes from > "../some path" is added to the "Installation, configuring and > troubleshooting" section of docs, thanks to Arc. > > Best regards, > Yakov. > > PS Julien, so have you succeeded with "../path" urls? I'm interested in > further investigation regarding Opera (and probably Chrome too). > > > воскресенье, 16 декабря 2012 г., 2:42:51 UTC+4 пользователь Yakov написал: > >> Hello everybody, >> >> today I'd like to announce that the public release of SharedTiddlers >> plugin is ready [1]. >> >> In principle, almost everything, including an introduction, can be found >> in the repository. >> >> In two words: the plugin allows to >> * see tiddlers from another tiddlywikis (as read-only) inside the "main" >> one >> * share theme components (style sheets, templates: PageTemplate, >> ViewTemplate, EditTemplate, ToolbarCommands) which can be stored in one >> central TW >> * do other things, including sharing evaluated transclusions like "toggle >> menus" engines from TiddlyTools [2] or "custom" ones (in fact, most of >> plugins can easily turned into evaluated transclusions, which will be >> described in the documentation later) >> >> Some major improvements since IncludePlugin [3]: >> * now a set of tiddlers (defined by a filter) can be included instead of >> all tiddlers >> * shadows and tiddlers can be "substituted" with the included tiddlers >> (they are not altered and if including is switched off, they remain the >> same as they were) >> * a notification system for name conflicts is introduced >> * elements of themes are now applied on load >> * wikifyIncluded macro is introduced (see docs) >> * simple "importing" engine is added >> * slices are recalculated according to the presence of new tiddlers >> * documentation on how to make plugins "include-aware" is added (and >> pieces of code that make abego plugins "include-aware" are removed from the >> main code) >> >> Feedback is welcome. Though, I'm rather slow in my development, so take >> this into account. Also, if you have some "basic" questions, please take a >> look at the docs first and let me know if I missed something there. >> >> Best regards, >> Yakov. >> >> PS there are some plans for further development including >> * evaluation system for plugins (to remove the need of making evaluated >> transclusions) >> * aggregation tools for analysing data (search and other) among several >> TWs simultaneously (accounting name conflicts) >> but I can't predict how soon I implement this. >> >> [1] >> http://yakovl.bplaced.net/TW/**STP/STP.html<http://yakovl.bplaced.net/TW/STP/STP.html> >> [2] http://www.tiddlytools.com/#**ToggleLeftSidebar%** >> 20ToggleRightSidebar<http://www.tiddlytools.com/#ToggleLeftSidebar%20ToggleRightSidebar> >> [3] >> http://tiddlywiki.abego-**software.de/#IncludePlugin<http://tiddlywiki.abego-software.de/#IncludePlugin> >> > -- > 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?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
