Just a thought: embedding TiddlyWiki documentation in our TiddlyWikis?

[Charlie Veniot]

Just a silly thought I had.

There are certain pages of TiddlyWiki documentation that I often reference (in particular: filter operators and widgets).

It just dawned on me that these (the static pages) would be nice to have displayed in a sidebar tab for all my TiddlyWiki instances.

[ludwa6]

+1 this idea, Charlie; peeling off in search of how-to docs is my most common distraction from the focus i really want to maintain while weaving wiki.  Whenever this frustration reaches the boiling point, i'll take a run at writing up my own little Tech-Tiddlers for Dummies, but then of course when i'm in process of writing them is when i need them the least (having some temporary savvy about the tech), and then i quickly lose track of them.  So having some well-organised help files, easily accessible in whatever TW context i happen to be at the moment, would be of great benefit.  

/walt

[stan...@gmail.com]

Like Walt, +1 for the idea.  This is not really a silly idea.  If one were to look at the Programming Language R (statistics, data science) in the RStudio development environment, one has help functions in a pane along side the source code being worked on, just as Charlie showed above.  I am sure there are many other IDEs with similar layouts and functionality

Stan

[Jean-Pierre Rivière]

For my current project, I have a tw dedicated to be a chest of relative information about the project. daily road-map and daily achievements and also technical article I write about what I encounter and since my project is done on tw, this is tw stuff as well. I'm using tags and macro and Left-Menu to help getting access to these information on my left side on an affordable way.

But yes, for the primary information, I have https://tiddlywiki.com/ in an other tab. and sometimes many tabs.

[Charlie Veniot]

And here is one way (attached) of doing it.

Import the attached tiddler into some TiddlyWiki and give it a spin.

Let us know how you would set something up that would fit your way of thinking !

[Mohammad Rahmani]

Small comments

1. use state or temp tiddler instate of field=curr-topic to work in sidebar tab

2. set the width dynamically from the sidebar-width

Best wishes

Mohammad

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/34e7f518-94cd-44e8-9529-1549a0af97fen%40googlegroups.com.

[ludwa6]

Nice one, @Charlie! works for me... If only i could now position this for easy access in the sidebar.

Tried:  Imported the tiddler -changed the name to "HelpFiles" cuz it was kinda long (i've got the relink plugin handling any potential breakages)- and then tagged it "SideBar", figuring that would make it callable by the $:/tags/SideBar tiddler... But that didn't have any effect that i could see.

What's the right way to do this; i wonder?

[Charlie Veniot]

I put that tiddler together late into the night, which I should not have.

Too late to properly set it up for the sidebar, I decided to just get the basics working so that I could get myself to bed.

Big mistake.

Four hours after conking out, I woke up and could not fall back to sleep, thinking about setting that thing up for the sidebar.

Ugh.

I'll get cracking on that again tonight.

[Charlie Veniot]

Okay folks, disregard/toss that initial version of mine.

This one is my "keeper."  Fixed/addressed:

• changed the name of the tiddler to a "production-ready" name:  TW Ref
  • the original name (Tiddler to reference information from static tiddlywiki site) was intended as an overly wordy descriptive title to just make clear the design of the tiddler
  • now it fits nicely in the sidebar tabs
• added the "$:/tags/SideBar" tag to the tiddler
• set width of iframe to 100%, so it will be as wide as whatever container, be it the tiddler in the story river, or tiddler displayed in a sidebar tab
• fixed references to selected topic field (curr-topic) and the tiddler's self-reference  (The old version was defaulting to currentTiddler.  Fine when viewing the tiddler in the story river, not fine viewing the tiddler in a sidebar tab)
  • <$select tiddler={{TW Ref!!title}} field="curr-topic">
    
    • Was:  <$select field="curr-topic">
  • <iframe  src={{TW Ref!!curr-topic}} height="500" width="100%"></iframe>
    
    • Was: <iframe  src={{!!curr-topic}} height="500" width="300"></iframe>

BTW:  I did not change use of field to use of state tiddler.   I am quite happy for the the help window to show me what I looked at last time I saved any TiddlyWiki

Cheers!

[Charlie Veniot]

Arg.  Forgot to mention that I also added a little link to open selected item in a separate window/tab.  For those times when the full monty serves best ?

[ludwa6]

Perfect! Can't say as i understand how this one little tiddler is doing it's magic;  feels like it's transcluding content from tiddlywiki.com (which i didn't even know was possible), and i'd like to know how i can add in more content items of my own choosing. Not to be a cargo-cult supplicant, i guess i should just RTFCode and figure our how to scratch that itch for myself. This feels like the right tool for the job, Charlie. Thanks, mate!

/walt

[Charlie Veniot]

G'day walt (I'm not sure I'm comfortable writing slash walt ...)

Oh no, not from TiddlyWiki.com.

From tiddlywiki.com/static/

So the static pages exported to TiddlyWiki.com/static, not theTiddlyWiki instance itself (that you get at tiddlywiki.com).

Embedding content from a whole TiddlyWiki instance would be way too slow performance-wise for this kid.

Individual static pages on request, that's pretty fast.

Please, do take a look at the last attachment I posted in this thread yesterday (April 22):  unzip that attachment, import the tiddler into any tiddlywiki (I like to try things right in tiddlywiki.com).

If you have any questions about the content in that tiddler or how to add other items in that select widget, get back to me/us here.

[ludwa6]

Amazing:  Adding topics from tiddlywiki.com/static to browse from within my own TW instance is a cinch, i find.  Have added an entry for "WikiText", and now i can drill down in 2 clicks for a quick how-to that saves me a good minute or few of context-switching penalty, that will quickly amount to hours of time saved.  Even if that's all we do with it, i can't imagine why anyone would NOT such a documentation utility in their wiki.  Certainly i'll be including this in all my instances from now on.

Now going further: I'm wondering how this might be adapted to other reference sites, even if non-tiddly; could this be possible?  I cloned the tiddler from your latest upload, @Charlie, to see if i can adapt it to pull from my most-commonly referenced site: wikipedia.org.  Called my new tiddler "Wikipedia", changed every instance where your code calls "TW Ref" to a "Wikipedia" call, and swapped in https://en.wikipedia.org/wiki/ as the base URL -deleting the suffix .html, since wikipedia doesn't use that, interestingly.  Now i've got a "Wikipedia" tab in my sidebar, with a new pulldown list for the 3 Wikipedia topics i added, so the UI works fine... But this new utility pulls no content, save the error msg:  "It may have been moved, edited or deleted."

So i'm wondering: is there a bug in my adaptation of code appended below? Or is there some more fundamental problem -like maybe it only works with a TW static site?

/walt

8<-------(snip)------->8

\define AddTopic( topic )

<option value={{{ [[$topic$]split[ ]join[%2520]addprefix[https://en.wikipedia.org/wiki/ }}}>$topic$</option>

\end

<$select tiddler={{Wikipedia!!title}} field="curr-topic">

<!--🔴 AddTopic takes as input tiddler titles from wikipedia.org  and  creates a link to same tiddler at the static site.

             Add/modify/remove items as per the following three examples

             Order the topics as per your preferences

             Add   "optgroup elements to group entries" -->

<<AddTopic  "TiddlyWiki">>

<<AddTopic  "WikiWikiWeb">>

<<AddTopic  "Project_Xanadu">>

</$select>&nbsp;&nbsp;<a href={{Wikipedia!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>

<iframe  src={{Wikipedia!!curr-topic}} height="500" width="100%"></iframe>

8<-------(snip)------->8

On Friday, April 23, 2021 at 6:32:07 PM UTC+1 cj.v...@gmail.com wrote:

G'day walt (I'm not sure I'm comfortable writing slash walt ...)

Oh no, not from TiddlyWiki.com.

From tiddlywiki.com/static/

So the static pages exported to TiddlyWiki.com/static, not theTiddlyWiki instance itself (that you get at tiddlywiki.com).

Embedding content from a whole TiddlyWiki instance would be way too slow performance-wise for this kid.

Individual static pages on request, that's pretty fast.

Please, do take a look at the last attachment I posted in this thread yesterday (April 22):  unzip that attachment, import the tiddler into any tiddlywiki (I like to try things right in tiddlywiki.com).

If you have any questions about the content in that tiddler or how to add other items in that select widget, get back to me/us here....

[ludwa6]

PS to my last: have fixed part of the problem: by adding the suffix clause back into macro (as below), it now pulls not a system-level error msg, but the error msg from wikipedia.org site itself, which seems to be objecting to the .html extension only... yet i can't find a way to remove that w/o reverting to the lower-level error msg.  Any insight about this problem would be appreciated!  /walt

 8<-----(snip)----->8

\define AddTopic( topic )

<option value={{{ [[$topic$]split[ ]join[%2520]addprefix[https://en.wikipedia.org/wiki/]addsuffix[.html]] }}}>$topic$</option>

\end

 8<-----(snip)----->8

[Eric Shulman]

On Saturday, April 24, 2021 at 3:16:22 AM UTC-7 ludwa6 wrote:

PS to my last: have fixed part of the problem: by adding the suffix clause back into macro (as below), it now pulls not a system-level error msg, but the error msg from wikipedia.org site itself, which seems to be objecting to the .html extension only... yet i can't find a way to remove that w/o reverting to the lower-level error msg.  Any insight about this problem would be appreciated!

Try this in a tiddler named "ShowWikipediaFrame":

\define AddTopic(topic) <option value={{{ [[$topic$]encodeuri[]addprefix[https://en.wikipedia.org/wiki/]] }}}>$topic$</option>

<$select field="curr-topic">

<<AddTopic  "TiddlyWiki">>

<<AddTopic  "WikiWikiWeb">>

<<AddTopic  "Project Xanadu">>

</$select>&nbsp;&nbsp;<a href={{!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>

<iframe src={{!!curr-topic}} height="500" width="100%"></iframe>

Notes:

* The filter  in AddTopic  needed a closing "]]".  Also, the filter uses "encodeuri[]" rather than "split[ ]join[%2520]".  This handles all special URI characters, not just space.

* The target tiddler for storing the $select widget value is the current tiddler, rather than "Wikipedia" (or {{Wikipedia!!title}}) and the corresponding <a href=...> and <iframe src=...> params simply fetch {{!!curr-topic}} (i.e., from the current tiddler).  This allows you transclude the above content as a template (e.g., {{||ShowWikipediaFrame}}) and each transcluded instance can be used to show a different selected topic.

enjoy,

-e 

[Hans Wobbe]

@Eric: Thanbk you.  

This works nicely and is, of course, quite extensible to sites like TiddlyWikiLinks.

Cheers,

Hans

[ludwa6]

Thanks @Eric : it does indeed work nicely -only not in the sidebar; after the streamlining you've done on Charlie's script, that functionality seems to have been compromised.

@Hans: Have you implemented Eric's script without modification, and does it display & function correctly in your sidebar?

Anyway: Without really understanding the code, i'm now using Eric's macro definition line at the top, followed by Charlie's UI-related code, and that seems to work pretty well, tho the sidebar view doesn't flow so well if it's set too narrow; i can certainly live w/ this -happy!    /w

8<------(snip)----->8

\define AddTopic(topic) <option value={{{ [[$topic$]encodeuri[]addprefix[https://en.wikipedia.org/wiki/]] }}}>$topic$</option>

<$select tiddler={{Wikipedia!!title}} field="curr-topic">

<!--🔴 AddTopic takes as input tiddler titles from wikipedia.org  and  creates a link to same tiddler at the static site.

             Add/modify/remove items as per the following three examples

             Order the topics as per your preferences

             Add   "optgroup elements to group entries" -->

<<AddTopic  "TiddlyWiki">>

<<AddTopic  "WikiWikiWeb">>

<<AddTopic  "Project_Xanadu">>

</$select>&nbsp;&nbsp;<a href={{Wikipedia!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>

<iframe  src={{Wikipedia!!curr-topic}} height="500" width="100%"></iframe>

8<------(snip)----->8

[Charlie Veniot]

That is good stuff, Eric.  Thanks!

If you don't mind me standing on your shoulders for a moment:

If one prefers the one tiddler to handle it all (well, TiddlyWiki.com/static and Wikipedia, others at your discretion) ...

\define AddTiddlyWikiTopic( topic )

<option value={{{ [[$topic$]split[ ]join[%2520]addprefix[https://tiddlywiki.com/static/]addsuffix[.html]] }}}>$topic$</option>

\end

\define AddWikipediaTopic( topic )

<option value={{{ [[$topic$]encodeuri[]addprefix[https://en.wikipedia.org/wiki/]] }}}>$topic$</option>

\end

<$select tiddler={{Docs!!title}} field="curr-topic">

<optgroup label="TiddlyWiki">

<<AddTiddlyWikiTopic  "Custom styles by data-tiddler-title">>

<<AddTiddlyWikiTopic  "Widgets">>

<<AddTiddlyWikiTopic  "Filter Operators">>

</optgroup>

<optgroup label="Wikipedia">

<<AddWikipediaTopic  "TiddlyWiki">>

<<AddWikipediaTopic  "WikiWikiWeb">>

<<AddWikipediaTopic  "Project Xanadu">>

</optgroup>

</$select>&nbsp;&nbsp;<a href={{Docs!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>

<iframe  src={{Docs!!curr-topic}} height="500" width="100%"></iframe>

[Charlie Veniot]

My revised version uses Wikipedia's "mobile" view , which looks really nice in a narrow sidebar:

\define AddTiddlyWikiTopic( topic )

<option value={{{ [[$topic$]split[ ]join[%2520]addprefix[https://tiddlywiki.com/static/]addsuffix[.html]] }}}>$topic$</option>

\end

\define AddWikipediaTopic( topic )

<option value={{{ [[$topic$]encodeuri[]addprefix[https://en.m.wikipedia.org/w/index.php?title=]addsuffix[&mobileaction=toggle_view_mobile]] }}}>$topic$</option>

\end

<$select tiddler={{Docs!!title}} field="curr-topic">

<optgroup label="TiddlyWiki">

<<AddTiddlyWikiTopic  "Custom styles by data-tiddler-title">>

<<AddTiddlyWikiTopic  "Widgets">>

<<AddTiddlyWikiTopic  "Filter Operators">>

</optgroup>

<optgroup label="Wikipedia">

<<AddWikipediaTopic  "TiddlyWiki">>

<<AddWikipediaTopic  "WikiWikiWeb">>

<<AddWikipediaTopic  "Project Xanadu">>

</optgroup>

</$select>&nbsp;&nbsp;<a href={{Docs!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>

<iframe  src={{Docs!!curr-topic}} height="500" width="100%"></iframe>

[Charlie Veniot]

Screenshot for the $hit$ and the giggle$:

[Charlie Veniot]

If one wants to save on screen real estate, that one tiddler could include all sorts of links to external content.

For example:

<option value="https://calendar.google.com/calendar/embed?height=600&amp;wkst=1&amp;bgcolor=%23ffffff&amp;ctz=America%2FHalifax&amp;showNav=1&amp;showPrint=1&amp;showTabs=1&amp;showCalendars=1&amp;mode=MONTH">Calendar</option>

[Ray Vermey]

Charlie where can i find the gigle stuff you just showed?

Looks awesome.

Are there tutorials somewhere to learn to understand the code uses?

I copy and paste the code in a tiddler, i see the result, but understand half of the code used.

Do you know where i can learn to understand this stuff?

This stuff i mean:

\define AddTiddlyWikiTopic( topic )
<option value={{{ [[$topic$]split[ ]join[%2520]addprefix[https://tiddlywiki.com/static/]addsuffix[.html]] }}}>$topic$</option>
\end

\define AddWikipediaTopic( topic )

<option value={{{ [[$topic$]encodeuri[]addprefix[https://en.wikipedia.org/wiki/]] }}}>$topic$</option>

\end

<$select tiddler={{Docs!!title}} field="curr-topic">
<optgroup label="TiddlyWiki">
<<AddTiddlyWikiTopic  "Custom styles by data-tiddler-title">>
<<AddTiddlyWikiTopic  "Widgets">>
<<AddTiddlyWikiTopic  "Filter Operators">>
</optgroup>
<optgroup label="Wikipedia">
<<AddWikipediaTopic  "TiddlyWiki">>
<<AddWikipediaTopic  "WikiWikiWeb">>
<<AddWikipediaTopic  "Project Xanadu">>
</optgroup>
</$select>&nbsp;&nbsp;<a href={{Docs!!curr-topic}} title="Open web page in a separate window/tab"  target="_blank">link</a>
<iframe  src={{Docs!!curr-topic}} height="500" width="100%"></iframe>

Thanks

Ray

Op za 24 apr. 2021 om 16:05 schreef Charlie Veniot <cj.v...@gmail.com>:

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/88893ef2-687f-4ace-96cd-ab70d4a68e64n%40googlegroups.com.

[Charlie Veniot]

Hey, my "gigle" stuff would be impossible to share.  It might leave most folk quite scared.

The Google stuff:  Add a Google calendar to your website

• in my example, I excluded all of my calendars (private, shared, and public)
• you can pick and choose which of your calendars to include
  • if your website is public, nobody but you will see your private stuff, and shared stuff will only be visible to you and the specific gmail users you've selected; the rest of the world will only see the public stuff

As for the TiddlyWiki code, that I learned by digging into TiddlyWiki.com, and hacking away at things to understand them.

Maybe we can peck away at the code chunk by chunk to explain what is going on.

What is the first thing you would like to know about ?

[ludwa6]

This is so freakin' awesome. Next to that moment in 1993 when i booted up Netscape Navigator v0.9 beta for my first-ever experience of surfing the WWW, this is like the most horizon-expanding experience i can recall having at the keyboard. Transclusion within a single wiki is cool enough, though Wikpedia's had that going for quite some time, but being able to transclude content from any static site on the web, and plug that in anywhere you want on your own silly-putty site so easily as this... This Changes Everything!   /walt

[Charlie Veniot]

Just so you know, you totally had me at silly-putty.

[Ray Vermey]

@charlie Veniot:

Well the screenshot shows an oversight of TW documentation i guess?

My 1st question would be: How do you make such a thing?

And more importantly: where do i learn the basic commands for this?

Yes i can look into the code of the wiki but that code only says about say 50% something to me.

So i miss the information on how to program....

Thanks for your friendly answer.

Ray

Op za 24 apr. 2021 om 17:32 schreef Charlie Veniot <cj.v...@gmail.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/629a5d38-2b6e-4074-8756-84af746aae86n%40googlegroups.com.

[ludwa6]

Guess i should be more circumspect in my use of such parochial cultural refs (not to mention a registered trademark -sorry, Crayola!) but again: the feeling of working with TiddlyWiki is a lot like Silly Putty™, in that you can stretch it and shape it into just about anything you can imagine.  Problem is: how does one ever manage to establish boundaries in such a medium?  Am practically paralysed by the possibilities, ATM.  Gotta unplug and get some fresh air!  /w

[CJ Veniot]

Well, I've been programming ever since receiving a Commodore Vic-20 almost 40 years ago at the age of 13, and I am at my best (I think; definitely having the most fun) dealing with complex and highly intertwingled information/problems and architecting solutions with the tools at hand.

So the answer to "how do you come up with such a thing" would be, in short: I bring 40 years of experience/skill/practices to the thing.

The long answer should probably involve a bunch of short and digestible videos on specific little things that subconsciously (i.e. without necessarily spelling it out) demonstrate things that are instinctive to me which might lead to questions requiring other topical video demonstrations.

How about a quick and dirty demo of macro basics ?

You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/opZn6isIZQ8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAAF_p9B2UaF8bO8z0T_e9rtwzLyZLAe37-CyoA4jWWHXcpK4dQ%40mail.gmail.com.

[Charlie Veniot]

Oh no no no, be much less circumspect, for the sheer fun/joy of it.

Pff, it is like who does not call snot-rags kleenex instead of tissue?  In my corner of the world, anyway.

In your context, silly putty is such a poetic way to describe, concise yet conjures up a plethora of happy qualities about Silly Putty that fit TiddlyWiki oh-so-well.

So wax poetic, my friend.  Wax poetic.

And do enjoy the fresh air.  Loads of wisdom in taking little breaks from paralysis by analysis and from analysis by paralysis.

I am going to get my own dose of vitamin D toute sweet.

[Hans Wobbe]

@ludwa6: Walt:

I made a few tweaks to Eric's code to suit my own uses.  I did not put this into my sidebar, by now, you know that would be relatively simple to do.

[Ray Vermey]

Aha @Charlie a legal cheater ;)

I do know some C, a bit php (be it rusty) and i still write bash-scripts.

So yes! A q&d macro demo, bring it oooooooooooon :-)

(maybe in an online session somewhere?? :-)  )

Ray

Op za 24 apr. 2021 om 22:18 schreef Hans Wobbe <hww...@gmail.com>:

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/64e6a5a6-f097-40f7-88f5-c5b20074da94n%40googlegroups.com.

[Charlie Veniot]

I've got this funny thought, maybe completely off, that folk who like and are good at APL can easily be TiddlyWiki masters.

Folk like myself who like and are good at relational algebra, the math of SQL, can maybe come in a close second.

Maybe.  Just funny thoughts floating around in my sponge.

I'm, SQL aside, a 3GL/4GL programming kind of guy, which may be helpful somewhat.  Not being much of a fan of C/C++/javascript, and having no exposure to PHP and other languages, I'm not sure how helpful those would be as foundations for TiddlyWiki Master.  Maybe awesome, maybe not.

Regardless, the programming geek side of me would love to see comparisons re programming languages as useful foundations for TiddlyWiki programming.

There.  If one is going to digress, might as well go for broke ...

Let me see what kind of little introduction to macros video I can put together tomorrow.  It will be very very basic.

[Mohammad Rahmani]

On Sat, Apr 24, 2021 at 6:19 PM ludwa6 <wlud...@gmail.com> wrote:

Thanks @Eric : it does indeed work nicely -only not in the sidebar; after the streamlining you've done on Charlie's script, that functionality seems to have been compromised.

@Hans: Have you implemented Eric's script without modification, and does it display & function correctly in your sidebar?

The problem with the sidebar is the currentTiddler variable! Use

<$select tiddler="yourTid" field="curr-topic">

and everywhere replace {{!!curr-topic}} with {{yourTid!!curr-topic}}

--

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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/cc863530-f058-49d9-a2b6-5a73df6d218fn%40googlegroups.com.

[Charlie Veniot]

But that's not an issue in the updated version I posted a little bit after walt's message.

[Charlie Veniot]

Going from attachments to code posted in posts, I want to make sure that the latest version I have working is available as something that can be imported into any TiddlyWiki.

So my most current version is attached, and it has:

• has an option to display google calendar
• a few sample links to TiddlyWiki.com/static tiddlers
• a few sample links to Wikipedia articles, accessing the mobile version of wiki pages
• the tiddler is renamed to more generic "Refs"

[ludwa6]

This would be perfect Charlie, if the Calendar call didn't pull an error ("accounts.google.com" refused to connect"). So, two questions:

1. The band-aid: How can i modify this calendar call so it's pulling from my own Google Calendar? <option value="https://calendar.google.com/calendar/embed?height=600&amp;wkst=1&amp;bgcolor=%23ffffff&amp;ctz=America%2FHalifax&amp;showNav=1&amp;showPrint=1&amp;showTabs=1&amp;showCalendars=1&amp;mode=MONTH">Calendar</option>
2. The (minor) surgery: As a community resource, can you make this downloadable utility to pull from a calendar that's publicly accessible w/o login -ideally one that would support our community in some way (e.g. schedule of upcoming TiddlyWiki Hangouts, if that is still a thing)?  Otherwise, comment out that section of code, , i would recommend, with instructions that would enable user to turn the feature on as per point (1) above.

I really appreciate @Charlie how you are taking pains- and iterating so rapidly based on user feedback! -to make this great tool really work for everyone.

/walt

[Charlie Veniot]

Ah poop, I thought I had tested that in incognito mode.  Let me look into that and get back to ya.

• While checking things out, I did figure out that a publicly shared Google Calendar is actually only visible on devices when users are logged in with their Google accounts.  Not logged into your Google account, you can't access it.  Makes sense, I suppose.  All about getting people into the Google ecosystem...

In the meantime:  Add a Google calendar to your website.

What you'll get is some html code meant to be pasted into a website.  That code consists of an iframe.   Grab that code, paste it somewhere, then just grab the URL from that code, and use that in this tiddler we are playing around with to get a google calendar link for your calendar.

• If you happen to make your TiddlyWiki publicly available, do make sure the calendars you embed have intended privacy settings for each calendar.  If your calendar is set as private, embedding your calendar in your TiddlyWiki is safe: people won't see your calendar items.
• Aside: In Google Calendar, it is always a good idea to review your security settings for each calendar you have created.

[ludwa6]

Thanks Charlie, but it didn't work.  Am logged into my gCal, got a good URL from the "embed code" affordance, but she won't fly: still pulls the same error.  No big deal, i don't really need this feature; it's just a minor downer to look at the "sad mac" icon (since this is first to load on default), so i'll just comment-out the option until/unless you find a way to make it work generically.  /walt

[Charlie Veniot]

Silly thought: can you grab the iframe code and paste the whole thing in a new tiddler?

Just in case my wording isn't quite right, here's a picture of what I mean for you to grab and paste in a new tiddler:

[ludwa6]

Good thinking Charlie; in fact that doesn't work either - in TiddlyDesktop, where i do all my tiddly-diddling, as a rule. 

It does however work fine when i load this instance into Chrome browser. 

Is this a bug in TiddlyDesktop, i wonder?

/walt

[Charlie Veniot]

Hey, that is mighty fine sleuthing.

I don't know much about TiddlyDesktop (I live in Google Drive with TiddlyDrive Add-on).  It sniffs to me like it (being a desktop app) can't get to Google Calendar because it has no way of knowing/passing-along your Google sign-in when accessing Google Calendar (or something like that.)

[ludwa6]

Ah, of course: absent all the spywarrr... -i mean personalisation features (e.g. cookies) built into Chrome & other commercial browsers- TiddlyDesktop gets the cold shoulder from Google web apps.  No bug therefore; this is clearly a feature.  /w

[Charlie Veniot]

Hey Ray,

I'm still mulling how to split the "gadget" into the various components for a bunch of mini videos.

Starting with macros still feels like a good place to start.

In the meantime, I did just a short introductory video of what I am now tentatively calling the  "Kiosk Gaget" (like a self-serve information kiosk?)

And a new thread of discussion started for the "mini series":  "Kiosk Gadget" (?) tiddlywiki programming mini-video series, I think

On Saturday, April 24, 2021 at 5:31:00 PM UTC-3 rayv...@gmail.com wrote:

[TiddlyTweeter]

Ciao Eric

VERY nice illustration!

FWIW, I think optimizing iframes in their UI aspect could be very useful. 

Passing in height parameters for instance.

I been doing quite a lot of work using iframes with Data Dictionary entries.

The snafus have been mainly that quite a lot of sites now block iframe embedding  because of security issues.(GitHub, for instance, doesn't make it easy) .

Just a comment

TT