Hi Stephan The mockup began > <https://dl.dropboxusercontent.com/u/14610481/story_planner_mockup.html> > as a jQuery-based thing with no TiddlyWiki plans, no data model whatsoever, > and no templating. (Again, attached for posterity) >
Aha, makes perfect sense. > The plan is to extend the list widget to allow entries to be dragged and >> dropped, but it's not implemented in the core yet. BJ has a plugin >> implementation, though: >> >> http://bjhacks.tiddlyspot.com/#TagList >> >> > I do remember seeing that in the roadmap but, given that I can't wait, > that doesn't help here. (Back when I planned to do this a couple of weeks > ago, today was the "ready for use by" date I set as a goal and I have a > writing buddy who's still waiting for the first time I'll be the one doing > the writing and he the editing rather than the other way around.) > > Unfortunately, I've just tested TagList on bjhacks.tiddlyspot.com and the > drag-and-drop behaviour is too finicky and has no visual drag-in-progress > indication. (I still don't know why drag-and-drop sometimes works and > sometimes opens the tiddler instead... seemingly at random.) > > I'll have to either patch it or write my own. > Best of all, you could work on the feature for the TW5 core.... > Does TW5's plugin format have a TWc-like license field I can check without > looking at the source and risking my freedom to write clean-room clones if > the license isn't both CC-BY-SA compatible and GPL-compatible? > Just to check, you'd like to be able to check the license of a plugin without inspecting the source? That makes sense. There's no license field on plugins at the moment, but I would be happy to add support for one. All the plugins that are part of the tiddlywiki repo are covered by TiddlyWiki's BSD license. Does the BSD license meet your needs? > (That's why you've never seen me contribute anything to TiddlyTools > plugins or write any of the TWc ideas that'd be trivial to write by > combining and adjusting existing bits. With TWc being more or less > invisible to Google and the main source of functionality being CC-BY-SA > only, I had no impetus.) > Just to be clear, the issue here is the licensing of TiddlyTools, not TWClassic itself? > > 1. I'm still interested in implementing this as a custom StoryView but > I'm not sure how to reconcile the "two story rivers" part with the API > exposed at that level of the stack so it's conditional on the timeline view > being active. (I've been specifically tuning my vision for the data model > with the intent that it still make sense when viewed as a normal TiddlyWiki > and I'm envisioning the two-river timeline view as analogous to things like > cecily.) > 2. I still have to dig into the navigation mechanism enough to figure > out how to redefine clicking a link as "If it's present in the timeline > river, hide the normal river and scroll to it. Otherwise, show the normal > river, insert the tiddler if necessary, and scroll to it." > > Basically, you'll need a new widget that's something like the navigator widget, processing tw-navigate messages more selectively. Having said that, there are features like the suppression of $:/temp/ >>> tiddlers when saving, which relies on specialised treatment of a certain >>> prefix. >>> >> >> > > That's the main thing I was wondering. Which prefixes have which special > behaviours. (That's actually part of what kept me from making the mockup's > internal representation even more TW5-like while I was iterating.) > I think the only cases are the prefix check for $:/state/popup tiddlers used in the save filters such as: https://github.com/Jermolene/TiddlyWiki5/blob/master/core%2Ftemplates%2Fsave-all.tid > On a related note, since I don't mind improving the documentation whenever > I run into a question like this, when I'm working on a draft and don't > fully understand the subject matter, how much of the Q&A would you prefer > be done where while I'm bringing a draft up to spec? > Any amount of Q&A is great, and very useful for me too. Obviously best for it to be public so that other people can benefit. > 5. What would be the least face-meltingly horrible way to monkey-patch the >>> search field so that Ctrl+Enter treats the contents as a literal tiddler >>> name and opens it directly? >>> >> >> I don't think that that can be done right now without some core changes. >> We'd want something like this: >> >> <$keyboard key="ctrl-enter" message="tw-navigate" >> param={{!!$:/temp/search}}> >> <$edit-text tiddler="$:/temp/search" tag="input"/> >> </$keyboard> >> >> But the trouble is that the tw-navigate event currently uses a >> non-standard parameter name for the tiddler title, and this cannot be set >> by the keyboard widget. >> > > Hmm. Should I open a feature request for that on the issue tracker? > Fixing it well is likely to be a big job; I think we need to bring in far more flexibility to the representation of sequential actions to be performed on a button click, message etc. But there's a quick fix by modifying this line: https://github.com/Jermolene/TiddlyWiki5/blob/master/core%2Fmodules%2Fwidgets%2Fnavigator.js#L143 To: this.addToStory(event.navigateTo || event.param,event.navigateFromTitle); Best wishes Jeremy -- 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.
