Re: [twdev] Re: Announcing the "innerwiki" plugin

2019-02-09 Thread TonyM
Jeremy, Could you expand on the following please. I think we can do most of that already. The <$data> widget is declarative and so it only helps with operations like that as a way to package their parameters. Since your data widget defines blobs perhaps it could be a blob widget? I am still w

[twdev] Is this doable? -- TOC Question

2019-02-09 Thread TonyM
Josiah, I am not sure I understand the example you shared but from marios comment I belive your answer lies in a custom toc with the kin opperator. I have shared self made tocs in the past because I like demonstrating recursive macros. The kin opperator lets you compare multiple trees and the r

[twdev] Re: Is this doable? -- TOC Question

2019-02-09 Thread Mohammad Rahmani
Josiah, I like the way it highlight the topic under focus. It TW I always lost where I was! Clicking on TOC item and clicking some other hyperlink and then you forget where you were! I know breadcrumbs can help, but they are no as semantic as having TOC item highlighted. --Mohammad On Saturda

[twdev] Re: Is this doable? -- TOC Question

2019-02-09 Thread PMario
Hi, Yes, this is doable ... BUT not with the existing TOC implementation. The existing TOC macros allow users to create toc-elements, that are part of 2 different paths. So a "branch" can have 2 parent tags, which makes it impossible to auto-select the right element in the TOC tree. Because t

[twdev] Re: Is this doable? -- TOC Question

2019-02-09 Thread @TiddlyTweeter
Repeat for email ... On Saturday, 9 February 2019 14:28:35 UTC+1, @TiddlyTweeter wrote: > > I find this simple TOC system for Fountain excellent on docs ... > > https://fountain.io/syntax#section-bone > > I'm not clear how I'd replicate it in TW. Its jump in river. so river > needs to be open I

[twdev] Re: Announcing the "innerwiki" plugin

2019-02-09 Thread @TiddlyTweeter
Could this be used to test mobile phone layouts reliably? Jeremy Ruston wrote: > > Software documentation is better with screenshots. However, the problem is > that screenshots go out of date the moment a typo is fixed or a drop shadow > is deepened. So I’ve been interested for some time in the

Re: [twdev] Re: $view widget new attribute : format="wikified"

2019-02-09 Thread S. S.
Jeremy, You are right, the requested *wikified* format of the <$view> widget would not differ from the wikified behaviour of the <$transclude> widget. But I believe it would be an efficient way to take advantage of this difference shown below: The TranscludeWidget treats any contained content

Re: [twdev] Re: $view widget new attribute : format="wikified"

2019-02-09 Thread Jeremy Ruston
Hi SS As mentioned above, the view and transclude widgets work in a totally different way. Making the view widget behave like the transclude widget doesn't make sense because it would *be* the transclude widget. The behaviour you describe is already available via the transclude widget. So how