[TW5] based on wiki object, check if title in story

[Tobias Beer]

@Jeremy & others,

Starting from the wiki object relative to a widget,

how would I check if currentTiddler is already in the story?

Best wishes,

Tobias.

[Jeremy Ruston]

Hi Tobias

Only the list widget holding the story view and the navigator widget 'know' about the story list. For another widget to access the current story list you'd need an explicit attribute to pass the title of the story list.

Best wishes

Jeremy

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/90f525e1-73d5-411c-bf48-d1261a0bb2bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tobias Beer]

Hi Jeremy,

Only the list widget holding the story view and the navigator widget 'know' about the story list. For another widget to access the current story list you'd need an explicit attribute to pass the title of the story list.

Ok, this makes sense. Seeing as how I am also doing the headings-anchor-handling in the tiddler widget, I believe the tiddler widget is the right place to do so. In fact, I can actually scratch the anchors="true" attribute I am currently using and imply that if given any history reference, e.g. as history="$:/HistoryList", we do want anchor links within whatever else follows... while checking if the tiddler is already open with respect to the defined history.

Best wishes,

Tobias.

[Tobias Beer]

Mhhh, actually... nope. The bit of code where I need to know the history would be the link-widget that dispatches tm-navigate, so that I can do some more magick after the tiddler is eventually displayed:

see: LinkWidget.prototype.handleClickEvent

Best wishes,

Tobias.

[Jeremy Ruston]

Hi Tobias

> Mhhh, actually... nope. The bit of code where I need to know the history would be the link-widget that dispatches the tm-navigate:

I don’t think it’s reasonable to require the link widget to have an attribute referencing the story and history lists.

Best wishes

Jeremy

[Tobias Beer]

Hi Jeremy,

 

I don’t think it’s reasonable to require the link widget to have an attribute referencing the story and history lists.

I understand, although the bit that I don't quite like is that every single story-view module needs to implement anchor-navigation support, i.e. once the architectural pathways are so streamlined as to attach an anchor-reference to the history tiddler and have the story view pick it up.

Best wishes,

Tobias. 

[Jeremy Ruston]

Hi Tobias

I understand, although the bit that I don't quite like is that every single story-view module needs to implement anchor-navigation support, i.e. once the architectural pathways are so streamlined as to attach an anchor-reference to the history tiddler and have the story view pick it up.

The goal of the storyview architecture is to allow deep customisation of how a story list behaves. That means that they need control of all navigation visualisation, including the proposed anchor navigation. Scrolling is part of the visualisation.

Best wishes

Jeremy

Best wishes,

Tobias. 

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/a7757453-7255-456e-a3fa-b58a2bc14e0c%40googlegroups.com.