@Mat: I.e only delete if what is currently investigated does not match the > template in use. Problem is, there is no "template in use" until one has > been set. But if we could set a faux template value in em-state to begin > then nothing will match this, until the template in use is set, upon which > no subsequent investigation will match that either. I think it could > work... but it would also mean there'd be a state tiddler with the faux, > then real value, hanging around, perhaps until deleted when tiddler closed. > Not a good solution but I'm mentioning it in case it gives you ideas. >
I'll try to find time to investigate this weekend. > By the way, how do we determine priority? I mean if we have an incomplete >> [[ and <$ how is it determined which is being completed? Should be the one >> closest to the caret, not sure if that is how it is already and if so, how >> that is ensured. >> > > That sounds like my original problem in trying to decide where a string > ended and which was seemingly magically solved once you stepped in. But... > yeah, isn't it automatically the one closest to the left of the last key > stroke? > I am juggling quite a few things today and not the most clearheaded. I'll revisit this later to make sure this behaviour is intentional and reliable and not an accident that we cannot rely on. > > Overall I think it's definitely headed in the correct direction and you've >> done a good job with the refactoring. >> > > That's encouraging to hear. Your instructions are, obviously, > indispensible. > Part of my goal here is to make sure you are comfortable with the wikitext portion of the code, so that if this does get into shape for release you are able to maintain it and provide support. It is almost like the popup is just a template now that shows information >> based on what is in the state tiddler, by transcluding other tiddlers. A >> very TW approach in my opinion. >> > > Yes. Interestingly, the popup content tiddlers are also basically > templates. As I've mentioned, one hope is for users to be able to create > these "end templates" themselves, since we probably can't predict what > they'll want access to, so I'm wondering what can be moved upstream into > the popup. They're a bit too complex now, I feel, but I'm not sure what is > general enough to move. > Yeah its a bit like the pattern in: tidder -> ViewTemplate -> tiddlers tagged $:/tags/ViewTemplate. I admit I haven't looked much if at all at the popup content tiddlers. When I find the time I'll have a look to see what can be done in terms of simplifying them. > git saver >>> >>> I took a quick look and did get it working. >> > > I can tell you didn't see my reply before I re-edited my post ;-) As for > seeing diffs, isn't there a plugin with this feature? Maybe it's only for > TW on node. > I did, email subscription to the Dev group ;) I will write up instructions for using the web interface when I get the chance, and I'll encourage you to give it a go at that time. It may feel like there isn't much benefit in it for you, but it would make it a lot easier to collaborate with you and offer assistance. Even in this project, as it grows more complex, we are nearing the point where it takes me more time to figure out what you have changed, rather than study the changes itself. It's the difference between easily being able to take a look at what you are doing and offering feedback when I have a few minutes to spare, vs having to wait until I have a solid chunk of time (which can be a while!). :) > > But if there was some kind of git saver that made it possible to use a TW > as a proper multi user wiki, that would make it very worthwhile for me to > grab the bull by the horns and study this properly. (As I indicated in my > deleted text; I have tried, quite a lot actually). Do you think that would > be possible - i.e a published wiki on gh that many people can edit... > including some checkin/out or versioning...? > Possible, of course. But the checkin/out and versioning would take a fair bit of work. Even now you could have two people with access to the same github repo and both could write to the wiki, but then the usual risks of overwriting each others changes apply. Cheers, Saq -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/5e333745-84b3-436f-9b71-2846c1844702o%40googlegroups.com.
