[TW5] Trying to set BrowserTabTitle as per @Eric's example [Resolved]

147 views
Skip to first unread message

Hegart Dmishiv

unread,
Sep 27, 2015, 9:53:50 AM9/27/15
to tiddl...@googlegroups.com
I tried following @Eric Shulman's advice from this post from 2007, to remove the site subtitle from the browser tab in my wiki. I created a system tiddler called $:/config/BrowserTabTitle, tagged it with systemConfig as he suggested, and pasted in his code, but it doesn't seem to make any difference to my wiki. As you can see, I have a very long $:/SiteSubtitle, and I'd like to keep it as it is, but I don't need / want it displayed in the browser tab or the browser application bar.

BTW, sorry, I'm not sure of the etiquette here. Is it more polite to "dumpster dive" for old threads and bring them back to the surface by posting a reply in the old thread, or better to create a whole new thread as I did here, linking back to the old? In some forums I've been on, dumpster diving is strictly taboo (even going to the effort of automatically locking threads that are too stale), while some forums frown on multiple threads about the same issue being created over and over again.

Mat

unread,
Sep 27, 2015, 1:30:30 PM9/27/15
to TiddlyWiki
Hegart...  excuse my bluntess... but why the heck would you read a post from 2007!!!! Is it even TiddlyWiki Classic you're interested in? Are you starting a museum?

<:-)

Eric Shulman

unread,
Sep 27, 2015, 1:50:12 PM9/27/15
to TiddlyWiki
Those instructions are for TWClassic. You can assume that anything posted before 2012 is NOT referring to TW5. From 2012 on, there is a mix of TWClassic and TW5, and currently, mosts posts are for TW5.

One big clue that the post was for TWClassic is use of the "systemConfig" tag for plugins. TW5 doesn't use that tag to define a plugin. Rather, it uses the 'type' and 'module-type' fields.

-e

Mat

unread,
Sep 27, 2015, 2:03:52 PM9/27/15
to TiddlyWiki
Eric was more polite ;-)

Anyway, the problem was intriguing enought for me to locate this tiddler (...in TW5): 

$:/core/wiki/title

maybe it'll be enough of a clue to solve your problem (...if TW5) 

<:-)

Tobias Beer

unread,
Sep 27, 2015, 2:38:42 PM9/27/15
to tiddl...@googlegroups.com
Hi Hegart & @Jeremy,

What would be interesting was if there was a way to actually have the window title reflect the last tiddler being opened in $:/core/wiki/title...

<$list filter="[[$:/HistoryList]getTitlesFromJSON[]last[]]"/> — {{$:/SiteTitle}}

...whereas I wouldn't know how to do the getTitlesFromJSON part, i.e. to extract the title property of the last one in that stack.

@Jeremy,

When I look at $:/core/ui/SideBar/Open, I find an odd construct that has me confused about it using a history parameter with the list widget — something I haven't noticed before — without really telling anything about what that parameter does and why in the ListWidget documentation. I get the feeling that it doesn't help me for extracting only the last opened tiddler, does it?

Best wishes,

— tb

Jeremy Ruston

unread,
Sep 27, 2015, 3:21:13 PM9/27/15
to TiddlyWiki
Hi Tobias

What would be interesting was if there was a way to actually have the window title reflect the last tiddler being opened.

It's actually a bit easier than that. Set $:/SiteTitle to:

{{$:/HistoryList!!current-tiddler}}

It works because when the navigator updates the $:/HistoryList tiddler it also puts the title of the tiddler at the top of the history stack in the field "current-tiddler".
 
When I look at $:/core/ui/SideBar/Open, I find an odd construct that has me confused about it using a history parameter with the list widget — something I haven't noticed before — without really telling anything about what that parameter does and why in the ListWidget documentation. I get the feeling that it doesn't help me for extracting only the last opened tiddler, does it?

The history attribute of the list widget is part of the special behaviour for handling lists that are stories. Essentially, all the list widget does with the history tiddler is inform the current story view of changes to the history stack.

Best wishes

Jeremy.

 

Best wishes,

— tb

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/08d8387c-3ac6-477b-adc9-aeb024ac55a0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Jeremy Ruston
mailto:jeremy...@gmail.com

Tobias Beer

unread,
Sep 27, 2015, 3:44:48 PM9/27/15
to tiddl...@googlegroups.com, jeremy...@gmail.com
Hi Jeremy,
 
It's actually a bit easier than that. Set $:/SiteTitle to:
{{$:/HistoryList!!current-tiddler}}

Thanks, that's nice. I have added a little Window Title how-to here...


Best wishes,

— tb

Hegart Dmishiv

unread,
Sep 27, 2015, 4:39:40 PM9/27/15
to tiddl...@googlegroups.com
On Monday, 28 September 2015 06:50:12 UTC+13, Eric Shulman wrote:
You can assume that anything posted before 2012 is NOT referring to TW5.

Thanks @Eric, I knew there was a difference between [TW5] and [TWC] but I didn't know when it started.

One big clue that the post was for TWClassic is use of the "systemConfig" tag for plugins.  TW5 doesn't use that tag to define a plugin.  Rather, it uses the 'type' and 'module-type' fields.


Sorry, that wasn't a "big clue" at all for someone new to TiddlyWiki, like me. From your perspective, having used both TWC and TW5 over the years, sure, that may have been obvious, but not to me as a new user. I don't even know what you mean by "'type' and 'module-type' fields". Please remember I've only been using TiddlyWiki for a few weeks, and I'm not a programmer, I'm an end-user, still struggling with concepts like Git and repo's even. Coming from MediaWiki, there is a lot more programming stuff for me to learn here than I'm used to.

I must confess, I even tried using it as a system tag, $:/tags/systemConfig, but that didn't work either. That is a notation I've seen elsewhere in TW5.

Ok, thanks @Mat, I'll look into that. From what I understand of TiddlyWiki so far, $:/core/wiki/title is a system tiddler, which I can override by creating another tiddler of the same name, which becomes a shadow tiddler for it. Is that about right?

Kind regards,

Hegart.

Hegart Dmishiv

unread,
Sep 27, 2015, 5:00:46 PM9/27/15
to tiddl...@googlegroups.com
On Monday, 28 September 2015 09:39:40 UTC+13, Hegart Dmishiv wrote:
From what I understand of TiddlyWiki so far, $:/core/wiki/title is a system tiddler, which I can override by creating another tiddler of the same name, which becomes a shadow tiddler for it. Is that about right?

Looks like I was wrong about that too. I clearly still don't understand much about TiddlyWiki so far. ;-)

There already was a shadow tiddler called $:/core/wiki/title, and that was the one I needed to edit, overriding the shadow tiddler itself, NOT overriding the core/system. But that tiddler didn't actually exist in my wiki (at least, not in the System tab of the sidebar) until I clicked the link from the Advanced Search, in the Shadows tab. So was it that there was a link to a non-existent tiddler by that name (essentially a Missing tiddler), and when I created it, it overrode the core system for that setting? I'm completely confused!

But it worked, whatever it did, so thanks everyone, and I used @Jermolene's answer about the current tiddler, referring to @Tobi's example as well.

I got there, in a roundabout sort of way. Please bear with me as I learn. It will take time. ;-)

Hegart Dmishiv

unread,
Sep 27, 2015, 5:50:13 PM9/27/15
to tiddl...@googlegroups.com
I've been looking back over ShadowTiddlers again in the official TW5 docs, trying to get a handle on all of this. It says "ShadowTiddlers are tiddlers that are loaded from within Plugins." Looking at the Plugins tiddler in the docs, I see a list of available plugins. From the description of "Plugins are used to distribute optional, custom components for TiddlyWiki", I assume I have to install a plugin myself for it to work, right? A bit like the extensions for MediaWiki. As far as I know, I haven't installed any plugins for TW5. Haha, I wouldn't even know how to yet! So where do these Shadow Tiddlers come from, from which plugins, if I haven't installed any plugins yet?

I see a huge list of "current shadow tiddlers" listed on the ShadowTiddlers tiddler in the official docs. At first I assumed that these are only the shadow tiddlers for plugins which are installed in the TW wiki instance at tiddlywiki.com, but then I copied the <$list> filter from the code on that page, into a new tiddler in my own instance of TW5 and got the same results (or near enough, a huge long list) as what I saw on tiddlywiki.com.

So now I'm even more confused:
  1. The docs say that shadow tiddlers come from plugins.
  2. I haven't installed any plugins.
  3. I have shadow tiddlers anyway.
Can anyone explain this to me better, and maybe we can get the official docs updated, or maybe there needs to be a "TiddlyWiki for Dummies" book. I saw @Eric's IndieGoGo page, but that campaign had closed long before I had even heard about TiddlyWiki. Not that I could have afforded to contribute much, anyway, sorry.

Jeremy Ruston

unread,
Sep 27, 2015, 6:15:20 PM9/27/15
to TiddlyWiki
Hi Hegart

The missing piece is that there is a plugin called $:/core that contains the main core code of TiddlyWiki. It is always present, and it is the source of the shadow tiddlers you are seeing. You can see it listed in the "Plugins" tab of the control panel.

Best wishes

Jeremy.


On Sun, Sep 27, 2015 at 10:50 PM, Hegart Dmishiv <hegart....@gmail.com> wrote:
I've been looking back over ShadowTiddlers again in the official TW5 docs, trying to get a handle on all of this. It says "ShadowTiddlers are tiddlers that are loaded from within Plugins." Looking at the Plugins tiddler in the docs, I see a list of available plugins. From the description of "Plugins are used to distribute optional, custom components for TiddlyWiki." I assume I have to install a plugin myself for it to work, right? A bit like the extensions for MediaWiki. As far as I know, I haven't installed any plugins for TW5. Haha, I wouldn't even know how to yet! So where do these Shadow Tiddlers come from, from which plugins, if I haven't installed any plugins yet?


I see a huge list of "current shadow tiddlers" listed on the ShadowTiddlers tiddler in the official docs. At first I assumed that these are only the shadow tiddlers for plugins which are installed in the TW wiki instance at tiddlywiki.com, but then I copied the <$list> filter from the code on that page, into a new tiddler in my own instance of TW5 and got the same results (or near enough, a huge long list) as what I saw on tiddlywiki.com.

So now I'm even more confused:
  1. The docs say that shadow tiddlers come from plugins.
  2. I haven't installed any plugins.
  3. I have shadow tiddlers anyway.
Can anyone explain this to me better, and maybe we can get the official docs updated, or maybe there needs to be a "TiddlyWiki for Dummies" book. I saw @Eric's IndieGoGo page, but that campaign had closed long before I had even heard about TiddlyWiki. Not that I could have afforded to contribute much, anyway, sorry.

--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.

For more options, visit https://groups.google.com/d/optout.

Hegart Dmishiv

unread,
Sep 28, 2015, 9:07:19 AM9/28/15
to TiddlyWiki, jeremy...@gmail.com
Hi @Jeremy,

Thanks for explaining that. Doesn't having the core as a plugin contradict the very nature of a plugin, which you describe in the official docs as "Plugins are used to distribute optional, custom components for TiddlyWiki", (emphasis mine). I would have thought that the core itself is not optional, thus it shouldn't be described as a plugin. It seems confusing to me.

Kind regards,

Hegart.

Jeremy Ruston

unread,
Sep 28, 2015, 11:56:03 AM9/28/15
to Hegart Dmishiv, TiddlyWiki
Hi Hegart

Thanks for explaining that. Doesn't having the core as a plugin contradict the very nature of a plugin, which you describe in the official docs as "Plugins are used to distribute optional, custom components for TiddlyWiki", (emphasis mine). I would have thought that the core itself is not optional, thus it shouldn't be described as a plugin. It seems confusing to me.

Perhaps it should say "plugins can be used to distribute optional, custom components" to make it clearer that not all plugins are for that purpose.

Plugins are a general purpose mechanism for packing multiple tiddlers into the same container tiddler.  They are used for a number of different purposes around the system, but their behaviour is always the same: when activated, their payload tiddlers become visible as shadow tiddlers.

Best wishes

Jeremy.

Hegart Dmishiv

unread,
Sep 28, 2015, 7:29:46 PM9/28/15
to TiddlyWiki, hegart....@gmail.com, jeremy...@gmail.com
Hi Jeremy,

Yes, thanks, that simple change of wording in the official docs would make a lot more sense of this to me. I won't go making a pull request just for that though. But the next time I do, if I remember, I'll add it to the PR if it hasn't been done already.

Thanks,

Hegart.

magev958

unread,
Sep 29, 2015, 5:59:42 AM9/29/15
to TiddlyWiki, jeremy...@gmail.com
Would it be possible to show the field "caption" instead of "title"?

Tobias Beer

unread,
Sep 29, 2015, 8:01:23 AM9/29/15
to tiddl...@googlegroups.com, jeremy...@gmail.com
Hi Magev,
 
Would it be possible to show the field "caption" instead of "title"?

Added here, plus output examples:

or short:

title: $:/core/wiki/title

{{$:/SiteTitle}} — <$tiddler tiddler={{$:/HistoryList!!current-tiddler}}><$view field="caption">{{!!title}}</$view></$tiddler>


Best wishes,

— tb
Reply all
Reply to author
Forward
0 new messages