Please help to refine this (working!) Google Drive backend

[twMat]

Fellow @Siniy-Kit explains how to use Google Drive as backend for TW as part of how to set up a full internet shop based on TW. (yes... incredible, to say the least).

Considering how huge Google Drive is, it makes sense to refine (scale down) Siniy-Kits creation to make Drive usable as a general backend for TW, even a plugin. I.e all the tiddly data is stored in a Google Sheet - each row is one tiddler: actual example. Opening the TW fetches the data from there and presents it as regular tiddlers. For one thing, this would enable sharing of tiddlers/plugins/etc for a lot of people. It probably also means you can use Google Forms to make people create tiddlers in your wiki!

This post is a request for help in how to refine Siniy-Kits bits. I think this will be EASY for most of you guys reading this because Siniy-Kit has already done the actual work.

A reasonable first milestone would be to be able to fetch the data. The completed project would be to also write data to Drive. Here I will focus on the first milestone because this is as far Siniy-Kit's describes it.

Thus:

The Google Sheet is presented in JSON format simply by using the right URL to view it. For example, here is a real Sheet with tiddlers and here's the same sheet presented as JSON. Here is a friendly beginners guide how to get the "JSON URL" for a Sheet.

My interpretation is that Siniy-Kit uses a boot module in TW to fetch that JSON data: Siniy-Kit explains that he has a bootup tiddler named, bootprefix1.js. As you note, it unfortunately contains all other shop related js also. I (who can't code) identified the following as the key bit:

function getSheetsData(worksheets_id) {
var fields = Object.create(null);
fields.title="$:/StoryList";fields.list="";
       if($tw.browser) {$tw.wiki.addTiddler(new $tw.Tiddler($tw.wiki.getModificationFields(),fields,$tw.wiki.getCreationFields()))};
scriptRequest("https://spreadsheets.google.com/feeds/worksheets/"+worksheets_id+"/public/values?alt=json-in-script", ok, fail);
}

I can't tell if there are also other parts critical for the fetching of the JSON.

There's also a second tiddler $:/core/templates/tiddlywiki5.html which, among other code, has snip (and which Siniy-Kit agrees is the only important line in it):

<div id="bootKernelPrefix1" style="display:none;">
{{ $:/boot/bootprefix1.js ||$:/core/templates/javascript-tiddler}}
</div>

Sooo... that should be pretty much it. Unfortunately I get RSOE when I'm trying it.

I will also post a tiddler below that Siniy-Kit uses to, if I understand, convert urls into JSON urls.

[twMat]

Here is a tiddler Siniy-Kit has in his Controlpanel (7'th tab) to - if I understand right - convert the sheet URL into a JSON URL. Because it is in Russian I have manually replaced google translated parts:

!! After making changes, you need to save and refresh the page.
---
id of MY published and shared google table  <$edit-text tiddler="$:/constant/_spreadsheetid" tag="input"  type="text" size=56 placeholder="enter your table id *" />

<$button>
<$action-sendmessage $message="tm-sheetgetdata" />
upload data from google table NOW
</$button>
 {{$:/core/ui/Buttons/delete_ALL}}

`*` -id of the table this part highlighted @@ color: red; red @@

~https://docs.google.com/spreadsheets/d/
@@color:red;1GzZFzmgF-vBrRYOyz5VqjJC8QAQcOHnFBa1PEW9NhcU@@
/edit#gid=1627697525

Examples of stores that load data from google tables upon opening

[["1"|http://novye-podarki.ru/frame.html?id=1GzZFzmgF-vBrRYOyz5VqjJC8QAQcOHnFBa1PEW9NhcU]]
[["2"|http://novye-podarki.ru/heeg33_.html?id=1Oaeue_pQWn01EY5f2ghiTgkLsq5Rm7xbFr89_R801JQ]]
[["3"|http://novye-podarki.ru/black.html?id=1GzZFzmgF-vBrRYOyz5VqjJC8QAQcOHnFBa1PEW9NhcU]]
[["4"|http://novye-podarki.ru/grey.html?id=1GzZFzmgF-vBrRYOyz5VqjJC8QAQcOHnFBa1PEW9NhcU]]

you can change the id in the URL of these stores to your own.

Examples of tables from which stores can get information.

https://docs.google.com/spreadsheets/d/1GzZFzmgF-vBrRYOyz5VqjJC8QAQcOHnFBa1PEW9NhcU/

https://docs.google.com/spreadsheets/d/1Oaeue_pQWn01EY5f2ghiTgkLsq5Rm7xbFr89_R801JQ/


GO ON ONE OF THE TWO LINKS AND CREATE A COPY TO YOUR GOGL ACCOUNT. AFTER THIS YOU WILL HAVE THE OPPORTUNITY TO EDIT (ALREADY YOUR OWN) TABLE OF SECTIONS, GOODS, etc. AFTER EDITING, PUBLISH AND SHARE THE TABLE (both are mandatory, just publishing or sharing is not enough), THEN SPECIFY THE TABLE ID IN THE STORE SETTINGS.

---
<br>
<$tiddler tiddler="SpreadsheetsUse">
<$radio value="yes">Load store data from google table if ANY is specified? id = in store URL</$radio>
<br>

<$radio value="no">Never download data even if? id = is specified in URL </$radio>
<br>

<$radio value="ondemand">Load data only from MY id, if it is specified in the URL, do not load others</$radio>
<br>

<$radio value="hide">Load data only from MY id, even without specifying in the URL, do not load others</$radio>
<br>

</$tiddler>

[twMat]

OK, here is a demo where I've remade a lot of optics so you'll recognize it as a TW, for testing stuff. Github doesn't accept attaching html files but it does accept zip files.

Fill in the iframed form or the iframed table... and click to import... and what you just filled in becomes as tiddlers!

This should be very useful. If someone knows how to extract the used js stuff. It is not much, from what I understand.

TiddlyGoo.zip

[twMat]

...and now there are public editing rights in the iframed table as it should be, sorry.

[kookma]

Thank you @twMat - I will give a try and will return to you!

[twMat]

@Marxsal wrote

All I see in the code he shows is making a single, empty tiddler. I'm missing how the data comes in.

Here is my tracking:

So the import button sends the message tm-sheetgetdata to $:/core/modules/saver-handler.js which contains

/*
Instantiate the saver handler with the following options:
wiki: wiki to be synced dirtyTracking: true if dirty tracking should be performed
*/
function SaverHandler(options) {
   .........
   $tw.rootWidget.addEventListener("tm-sheetgetdata",function(event)
    {getSheetsData($tw.wiki.renderTiddler("text/plain","$:/constant/_spreadsheetid"))});
   ........

I find the getSheetsData in $:/boot/bootprefix1.js. This seems to be defined as:

function getSheetsData(worksheets_id) {
   ...
   scriptRequest("https://spreadsheets.google.com/feeds/worksheets/"+worksheets_id+"/public/values?alt=json-in-script", ok, fail);
}

The getSheetsData function is called a few times in that bootprefix1.js tiddler

The scriptRequest function is this (poorly edited so it looked like it was cut after the first paragraph) reads:

function scriptRequest(url, onSuccess, onError) {
  var scriptOk = false; 
  var callbackName = 'cb' + String(Math.random()).slice(-6);
  url += ~url.indexOf('?') ? '&' : '?';
  url += 'callback=CallbackRegistry.' + callbackName;
  CallbackRegistry[callbackName] = function(data) {
    scriptOk = true; 
    delete CallbackRegistry[callbackName]; 
    onSuccess(data); 
  };

  function checkCallback() {
    if (scriptOk) return; 
    delete CallbackRegistry[callbackName];
    onError(url); 
  }

  var script = document.createElement('script');
  script.onreadystatechange = function() {
    if (this.readyState == 'complete' || this.readyState == 'loaded') {
      this.onreadystatechange = null;
      setTimeout(checkCallback, 0); 
    }
  }

  script.onload = script.onerror = checkCallback;
  script.src = url;

  document.head.appendChild(script);
}

[Marxsal]

The formatting threw me off. I think I understand where the data comes in, though the magic of how is still a little unclear. Formatting the code really helps readability.

I think the entire bootprefix1.js tiddler is wrapped up as a javascript script wrapper (template) and then sucked up by TW at load time. Why it's done that way rather than using a raw tag ? I'm sure there's a good reason. Maybe it does something more than a raw tag will allow?

getSheetsData calls scriptRequest which seems to make a call to google. Google then invokes a callback somewhere (not sure how that auto-magic works) . This invokes function "ok" which then makes 3 tiddlers and makes another scriptRequest run. The result of that gets picked up by function "ok2" which (I think) loops through the return values, does a lot of field processing, and creates the tiddlers. I don't understand the stair-cased calls to scriptRequest, but I'm thinking the first call might be for meta data used for the 2nd call.

In the bootprefix1 call there are 1300 lines alone dedicated to function "cart", which I suspect could be deleted. Following that there is lots of other code which I think is also cart-related. I imagine all the cart stuff could go for your purposes.

That's all for now. Reading code is sleepy work.

[saqimtiaz]

A few thoughts that might be informative, since I've worked with Google Sheets in this manner elsewhere:

• Fetching JSON data using a httpRequest runs into the familiar CORS security restriction
• The workaround is to use JSONP, which is what I presume SiniyKit is doing.
• I don't recommend pursuing this route as I believe it uses the deprecated older API: https://developers.google.com/gdata/samples/spreadsheet_sample
• My experience with deprecated Google APIs is that they are discontinued suddenly and with no warning.
• From what I remember of looking at the new API a while back, there was no equivalent API endpoint and there might have been a need for Google API credentials/authentication: https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets

[twMat]

@saqimtiaz , I appreciate you input.

*Fetching JSON data using a httpRequest runs into the familiar CORS security restriction
*The workaround is to use JSONP, which is what I presume SiniyKit is doing.

Is that a problem? It does demonstrably work and enables things that are not possible otherwise.

*I don't recommend pursuing this route as I believe it uses the deprecated older API:

I tried it with their new(?) "URL string" and it works there too. This is presumably the only "contact point" between the TW mechanism and the sheet so if they change it then it is easy enough to update the mechanism. I'm assuming they won't shut off the sheet-in-json-form all together because I imagine millions of people rely on it.

[saqimtiaz]

@twMat Well yes, that is why JSONP is described as a workaround. It gets around the CORS restrictions. As also stated, those comments are meant to be informative and this one is the answer to how the data is being fetched, which there seems to be some confusion around. I don't really have time to spare for TW at the moment, but thought I would share some quick pointers and information that might be helpful.

Regarding API v4, it isn't as simple as using a different URI. As far as I know, once the older API is deprecated an API key (and potentially also authentication) will be needed to use the new API. You would also need to confirm that the new API supports JSONP as that should not be considered a given. It has been a while since I looked into it though and don't have a reference for the API key changes at hand, so recommend doing your own due diligence.

[twMat]

OK, valuable info. Thanks @saqimtiaz !

[Marxsal]

I'm assuming they won't shut off the sheet-in-json-form all together because I imagine millions of people rely on it.

If this was in other company that would be true. But Google has demonstrated many times that is willing to disregard the preferences of millions. Sketchup. RSS Reader. More than 40 abandoned projects.

[saqimtiaz]

I expect JSON support to continue though it may require an API key, but JSONP is much more likely to be discontinued and that is what this implementation relies on. It has fallen out of favour quite some time ago and slowly been abandoned by most projects due to security considerations.

[twMat]

After a lot of cleansing I have updated the file. It still has a lot of Siniy-Kits original shop stuff but now it basically behaves like a regular TW and it is much easier to investigate stuff.

TiddlyGoo.zip - updated this in post at: see "edited" feature here in post.

[CodaCodr]

Works here @Marxsal

I did see a JavaScript error - weirdly, without the usual red div. It was written across the top of the story, bleeding over the topmost tiddler. I turned off sticky titles and now I can't repeat it :/

[twMat]

Just tested. It does import the tiddler but, like Coda, I get this (above river):

[twMat]

I will dig further into the many system files this weekend, testing which ones can be cut out.

[Marxsal]

@twMat @CodaCodr

Just tested. It does import the tiddler but, like Coda, I get this (above river):

The error actually came in with Mat's changes yesterday. The code is trying to add onclick events to tables that don't exist any more.

[Marxsal]

Just tested. It does import the tiddler but, like Coda, I get this (above river):

The error comes in because bootprefix1.js is attempting to add "onclick" to the tables you removed. In this version, I've commented out that code. There was a timer element in it as well, so it's possible we'll have to add that part back in if the page doesn't update correctly for large spreadsheets.

TiddlyGoo-Marx-2021-02-11b-sheet-handler-and-fix-onclick-err.html.zip

HTH

[twMat]

By the way, anybody know Siniy-Kit's gh nick? I tried asking him via the google forum but I don't think it was noted.

[CodaCodr]

@twMat

yeah, re-import overwrites. I would guess that IF the code somehow pulls in things so they can be evaluated before they're turned into tiddlers then this could be prevented...

Possibly. But I think the current behaviour is probably the way it should behave - as long as it's expected/known. A case of documentation/education ahead of time. But if that were to happen unknowingly, that could be pretty painful.

The other possibility is to create indexed tiddlers (tiddler-1, tiddler-2) - not a huge fan of that, myself, but would avoid the issue.

[Marxsal]

The original idea, I think, was that the TW file would just present the spreadsheet data. So anyone could host the TW file out on the net, and then everyone could view the spreadsheet in TW form. In this scenario, overwriting the existing tiddlers would be the thing to do.

The other scenario, where the tiddlers are retained, would then beg the question of what to do with changes. Append them? Save them as versioned tiddlers? My feeling is that overriding is the thing to do. TW files can't keep unlimited versions. And (someone will correct me if I'm wrong), I think Google sheets does it's own versioning, so you could always go to the source if you needed to look up some old stuff. Well, at least with other documents they do some sort of (limited) versioning.

[CodaCodr]

Like I said, it's a matter of documenting the behaviour to avoid nasty surprises.

[Marxsal]

This version resets (deletes) shadow tiddler $:/core/templates/TiddlyWiki5, adds script tags to top and bottom of bootprefix1.js, and marks it with tag $:/raw/Markup . In my tests, there were no errors and it was still able to import. This means that there is now one less core tiddler that needs to be overwritten. I think $:/bootprefix1.js should probably be renamed to something more like $:/googlesheets.js to reflect it's actual usage.

TiddlyGoo-Marx-2021-02-1c-remv-core-template.zip

[Marxsal]

@twMat

There are very few system tids left. Your "sheethandler" - does it replace bootprefix1 (that I can then delete)? That Yandex stuff is a sore thumb.

Oh, we definitely need bootprefix1.js. That's the room where it all happens. But it isn't core, so shouldn't conflict. It should be renamed, since it's really not much like the reall bootprefix.js My sheet handler just added the eventListener that was previously in the SaverHandler. It would be a good place to add other listeners (like the contact form listener).

We need to look at bootprefix1.js (which I would call guglesheets.js or something) and see what parts can go. A lot has to do with the cart.

[Marxsal]

Any ideas what the extra cells-to-twfield mapping is/are?

@CodaCodr - yeah, I'm not sure how they're generated. In the spreadsheet, row 1 (hidden) has no "heading" beyond "id" and "text".

@twMat @CodaCodr

I think the mapping occurs in function ok2 in the increasingly incorrectly named $:/core/bootprefix1.js .

You might suggest a better mapping arrangement and then we could see how easy it is to tweak.

[CodaCodr]

I'd be happy with something obvious like sheet-col-c, sheet-col-d, etc.

If the sheet itself has a meaningful/handy id, then <id>-col-c, etc

[Marxsal]

Just thinking out loud. What about configuration tiddler/s that matches field names with columns? That way you could pull information into your existing TW calendar app, contact list, recipe list, etc. without any changes to the app.

An old school version of this idea would put the field names in the first row of the spreadsheet. The advantage is that people editing the spreadsheet are reminded what the fields mean.

Edit: Actually, I think Google Sheets will let you assign names to columns.
@twMat Could you assign a name to say, column 5 in the original structure, so we could look at the JSON ?

[twMat]

@twMat Could you assign a name to say, column 5 in the original structure, so we could look at the JSON ?

Good ideas. OK, so I just named column 5 col5. I think anyone can do this since it is an open editable sheet, it's just to unhide the first row. Feel free to test around and add/remove stuff freely.

(I will return to this tomorrow.)

[Marxsal]

This version took Mat's version and made changes to bootprefix1.js (which really needs a better name.)

• Removed cart-based field references
• Tags tiddler with Sheet name
• For "images" sheet only, "url" field is made as _canonical_uri, and tiddler is not tagged. Also a type field is added with "image/jpeg" .
• Removed the "i" field, which was just an incremental counter. I'm not really seeing a value for that since it will change when the data changes.
• You can specify an id field or a title field. If you specify both, probably "title" will win because the incoming data is alphabetical.

Observations.

If you don't specify a column name, GS makes up a name. That's where those odd field names are coming from.

The JSON structure you get if you follow the directions on the import page is different from the JSONP structure that the program sees. The big difference is that the JSONP doesn't give you row/column information -- just "column" in the indirect form of a field name. Thus, we can't make sensible default names based on column/rows, in case anyone was wondering. Solution: Always specify a column (field) title.

The load process generates 3 tiddlers on the fly:

• googlespreadsheetmail
• googlespreadsheet
• googlespreadsheettime

The question is whether these retain any value now?

Do we still need a timestamp field?

TiddlyGoo-Marx-2021-02-12b-bootprefix-changes.zip

[CodaCodr]

Do we still need a timestamp field?

If that's the time of the import, I see no harm in keeping it (and no harm in ignoring it).

[twMat]

We're getting really close!
I could have sworn I posted a reply yesterday evening, saying something like:

• No modified core tids - fantastic!
• I added a column 5 with heading col5. Feel free to edit the spreadsheet any way you want. (Actually, I/we should probably stress test things to see if any content can be imported. Hopefully a sheet can contain a full plugin per row... not sure exactly how to add it there...)

---

AFAICT these are currently the only tiddlers needed for a TiddlyGoo plugin :

• $:/bootprefix1.js <------> $:/googlesheets.js - I changed into the latter name, good idea.
• $:/mas/sheethandler.js - what does this do actually?

Am I missing some necessary component? There's also:

• $:/constant/_spreadsheetid - this is created when user adds sheet ID
• Initialize bootprefix1 - should this be in the plugin?

Would anything else "programmatic" (as opposed to e.g docs) be useful in the plugin?

I note $:/bootprefix1.js / $:/googlesheets.js still has a lot of "remnants" from SK. I will look into this today some more. Here's the latest update, based on @Marxsal 's vesion from above:

TiddlyGooMarx5.zip

@Marxsal writes:

If you don't specify a column name, GS makes up a name. That's where those odd field names are coming from.

That's probably a good functionality to keep, right? But maybe the made up name could be friendlier like field-1, field-2, etc? So tiddlywikians feel at home.

The JSON structure you get if you follow the directions on the import page is different from the JSONP structure that the program sees. The big difference is that the JSONP doesn't give you row/column information -- just "column" in the indirect form of a field name. Thus, we can't make sensible default names based on column/rows, in case anyone was wondering. Solution: Always specify a column (field) title.

So are you saying that tiddler titles cannot be auto generated from row+col, like the other column/fields can? For example, it is not possible to get a title to be, say, B3 (i.e the sheet cell name)?

The load process generates 3 tiddlers on the fly: [...]
The question is whether these retain any value now?

For a minimal plugin, yes, I think they should be eliminated. But then, it would make sense with some equivalent to TW's $:/Import listing, perhaps using the content for that "googlespreadsheet" tiddler as the title. (But currently that "googlespreasheet" tiddler only reads "...docs.google.com/spreadsheets/d/undefined/" so it seems something is not working.)

Do we still need a timestamp field?

Actually, maybe this could be used as fallback tiddler title? If the time is down to milliseconds I guess it is unique. The format is currently 09/02/2021 18:35:49 so I guess it'd have to be changed then. (Incidentally, that "spreadsheettime" tiddler contains 2021-02-12T20:21:34.440Z so maybe that date-format-string can be used.)
Good/bad idea? Of course, that would need some fiddling and is not needed to get this baby out in its first version.

[Marxsal]

We're getting really close!
I could have sworn I posted a reply yesterday evening, saying something like:

You did. This is why I'm not really enamored with the github forum. GH folds your old responses under "View replies" making it hard to pick back up where you left off.

• $:/mas/sheethandler.js - what does this do actually?

It has the eventlistener that catches the message (tm-worksheets ??) when you click on the import button. BTW, I assume the submit doesn't work at the moment. The eventlistener for it also needs to be moved into the sheethandler.js or it's own tiddler.

• Initialize bootprefix1 - should this be in the plugin?

I think those were just notes so that I didn't lose the system tiddlers while working.

If you don't specify a column name, GS makes up a name. That's where those odd field names are coming from.

That's probably a good functionality to keep, right? But maybe the made up name could be friendlier like field-1, field-2, etc? So tiddlywikians feel at home.

The problem is, there's no way to know that it is a made-up name. The only special characteristic is that it starts with an underscore, but actual tiddler fields can also start with an underscore.

So are you saying that tiddler titles cannot be auto generated from row+col, like the other column/fields can? For example, it is not possible to get a title to be, say, B3 (i.e the sheet cell name)?

Exactly. The JSONP discards the sheet location info. It also changes all the field names prepending gsx$ to each one. That gets fixed in function ok2.

The load process generates 3 tiddlers on the fly: [...]
The question is whether these retain any value now?

For a minimal plugin, yes, I think they should be eliminated. But then, it would make sense with some equivalent to TW's $:/Import listing, perhaps using the content for that "googlespreadsheet" tiddler as the title. (But currently that "googlespreasheet" tiddler only reads "...docs.google.com/spreadsheets/d/undefined/" so it seems something is not working.)

I hadn't looked at it. Maybe SK was just using it for debugging purposes.

Maybe we can table the import listing idea for later?

Do we still need a timestamp field?

Actually, maybe this could be used as fallback tiddler title? If the time is down to milliseconds I guess it is unique. The format is currently 09/02/2021 18:35:49 so I guess it'd have to be changed then. (Incidentally, that "spreadsheettime" tiddler contains 2021-02-12T20:21:34.440Z so maybe that date-format-string can be used.)

I think the timestamp is made by the contact form. Or it was made by some other process that SK had for managing his cart. In any event, it's not made by the import process. I think it was important for SK, but probably not for us (I think the regular created and modified fields are created during the load).

A default title field of some type is probably a good idea, if anybody and her brother can make inserts into the spreadsheet. Somebody is bound to forget a title. Maybe something like "Default ". There's already some code in there that could be borrowed for that.

[twMat]

@Marxsal
OK, so I find I can take out substatntial bits from the (newly named) $:/googlesheets.js ... but I'm concerned that some of it may be better kept in, for reasons I don't understand like error checks, likely-to-be-implemented-features (that SK may have utilized but that I just don't appreciate the value of at the moment), or that it is simply something used in the google API - because my method to naively search if a function name or variable is called anywhere might not work. ...So I figure it's better if someone who knows what the hey he is doing takes a look instead - could you, @Marxsal ?

I suggest using that file form last post, i.e TiddlyGooMarx5.zip (I made TiddlyGooMarx8.zip using my naive cutting approach before realizing better leve it to someone who understands more, but the file does work.)

[Marxsal]

If we're thinking of sharing plugins via spreadsheets, we may have to come up with some clever way to split the text of a plugin. Apparently there is a 50k character limit per cell. That's kind of low. Tiddler Commander, for instance, requires more than twice this capacity. Hmm. The same would apply to tiddlers that contain book chapters. Maybe some convention that fields text, text1,text2... are to be combined as one tiddler text field.

[twMat]

$:/mas/sheethandler.js
... has the eventlistener that catches the message (tm-worksheets ??) when you click on the import button.

OK, so it is necessary in the plugin.

[...] BTW, I assume the submit doesn't work at the moment. The eventlistener for it also needs to be moved into the sheethandler.js or it's own tiddler.

What "submit"? In SK's shop the user could submit their order (is this what you refer to?) but I don't know how this was dealt with, i.e if it went into a spreadsheet. Is that what you refer to as "the submit"? ...cos you're not referring to the Google Form that I set up, right? (to the left of the sheet in the wiki. The interaction between the google form and the google sheet is totally outside of our code, of course.

Apropos submitting things, I did ask SK if modifying a tiddler also could update the spreadsheet, to which he replied:

2. No, now it is not possible to modify spreadsheet through Tiddlywiki, But in future (I hope) I will write googlescript hook. Spreadsheet can receive POST ang GET with password and commands what to do with spreadsheet, so it wil be possible to add and remove lines, look for tiddler by id (title) and modify it. May be tiddlers will be in JSON, not to create many colons.

That would certainly be something!

...
Maybe we can table the import listing idea for later?

Of course. Now it is just about refining the thing and make a plugin.

I think the timestamp is made by the contact form. Or it was made by some other process that SK had for managing his cart. In any event, it's not made by the import process.

Ah, yes, the google form that I set up does create a timestamp.

A default title field of some type is probably a good idea, if anybody and her brother can make inserts into the spreadsheet. Somebody is bound to forget a title. Maybe something like "Default ". There's already some code in there that could be borrowed for that.

Yes, that'd be very useful. I assume it would still be a problem if there are multiple rows without titles. Then they overwrite eachother so there's only one "Default" in the end. Maybe there's some code in there that also adds a counter? I do see some "counting type loops" but I don't know what they're used for.

If we're thinking of sharing plugins via spreadsheets, we may have to come up with some clever way to split the text of a plugin.

Good idea. To collect all these ideas that have popped up here, I'll make another google form and note them down, and share it.

OK, so today I hope to package the few necessary tiddlers into the first version of a TiddlyGoo plugin. If not today, then Tues/Wednesday. The latest version I have, before I started cutting out functions and variables that I deemed unused and then regretting it, is TiddlyGooMarx5.zip. If anyone submits something improved, I'll use that instead.

[Marxsal]

What "submit"? In SK's shop the user could submit their order (is this what you refer to?) but I don't know how this was dealt with, i.e if it went into a spreadsheet. Is that what you refer to as "the submit"? ...cos you're not referring to the Google Form that I set up, right? (to the left of the sheet in the wiki. The interaction between the google form and the google sheet is totally outside of our code, of course.

Oh, good. That simplifies things.

A default title field of some type is probably a good idea, if anybody and her brother can make inserts into the spreadsheet. Somebody is bound to forget a title. Maybe something like "Default ". There's already some code in there that could be borrowed for that.

Yes, that'd be very useful. I assume it would still be a problem if there are multiple rows without titles. Then they overwrite eachother so there's only one "Default" in the end. Maybe there's some code in there that also adds a counter? I do see some "counting type loops" but I don't know what they're used for.

Either I fell asleep between "Default" and the end of the sentence, or I forgot I was in markdown ;)

I meant "Default #####" where ##### is a random code so every title is unique.

OK, so today I hope to package the few necessary tiddlers into the first version of a TiddlyGoo plugin. If not today, then Tues/Wednesday.

I'm going to see if I can add the default title thing.

[CodaCodr]

Sorry, been off doing other things...

   If you don't specify a column name, GS makes up a name. That's where those odd field names are coming from.

That's probably a good functionality to keep, right? But maybe the made up name could be friendlier like field-1, field-2, etc? So tiddlywikians feel at home.

The problem is, there's no way to know that it is a made-up name. The only special characteristic is that it starts with an underscore, but actual tiddler fields can also start with an underscore.

Potentially worse, if you don't "police" your imports, you end up with "dark matter" in your TW. The columns are visible in the sheet, far less so in TW fields.

[Marxsal]

If we create a report tiddler, then maybe it could include a short fields report. We'd leave it up to the user to hunt down the field if it looks out of place. Or maybe a reveal widget and a listing. But sometimes it's better to see what people are really concerned about.

[twMat]

Note that it is still somewhat unclear what use cases that bring the data into the spreadsheet to begin with. If it is via a google form, then it already has a column name. And if it is tiddlers that are converted/exported into the sheet then, again, there are already column names.

...so I think this is a concern for later on, and I can think of many much more important matters for the greater concept of this.

[Marxsal]

Here's a version that adds a default title and makes an import tiddler called Googlesheets import report listing tiddlers and unique set of fields. Nothing slick.

I haven't researched the remaining functions in Googlesheets.js. Most of them are small, so that's ok. But there's one that called "stickmenu" that I don't know what it does. And somewhere in there the code is checking for a function called "Swiper" which I don't think is needed, but since it possibly sets a timeout I'm ignoring it for the moment.

TiddlyGoo-Mark-2021-02-14a-default-title-reports.zip

[twMat]

Last comments before bed:

Stickmenu is, I believe, for a menu that was present in the store.
Swiper is also some store specific functionality part of some popular package or something like that.
I know this from when I cleansed out the other tiddlers and the UI.
IMO all stickmenu and swiper stuff can be cut out.

[twMat]

• What is actually the idea with keeping the commented out code? And, to keep it in the code, as opposed to on some backup?
• I'm eager to get this out but it seems likely that people, right away, will want to batch manipulate imported tiddlers. But currently the only thing (other than date) that fully distinguishes imported tids from all other tids is the "hard coded" list in the "Report for" text! So, can the Report instead put the titles list in a imported-tiddlers field, and the new fields in imported-fields, and the Report text can list transclude those fields? This gives users a possibility work with or copy those lists before next import overwrites the Report.
  (note to self: If this is implemented, I need to update the docs about it.)

Updated, see overwrites. I am now happy with the styling and the docs. Other than what's mentioned here above I don't expect to update this more.

TiddlyGoo-v019a.zip

[twMat]

• ...actually, maybe the proposed fields imported-tiddlers and imported-fields should be set in the SpreadsheetTiddlers instead of the reports. For now, the Report tids can transclude from the SpreadsheetTids.

Yay/nay? We could just wait with this and see what people say but I do think we can expect people to want to batch manipulate imported tiddlers. (I can see how I'll want that.)

• In a later release: The imported tids are presented in the SpreadsheetTid itself. "Later release" because this will take some fiddling in the JS where the Spreadsheet tiddler is created.

One aspect with this is if you share the SpreadsheetTids: Then you can easily show what tiddlers (at least their titles) a user can expect if they import!

[Marxsal]

• ...actually, maybe the proposed fields imported-tiddlers and imported-fields should be set in the SpreadsheetTiddlers instead of the reports. For now, the Report tids can transclude from the SpreadsheetTids.

No, that would be too hard. The SpreadsheetTiddlers are made before fetching imported tiddlers. In a list-only call, the tiddlers aren't even fetched. The report tiddler is the logical place the new fields. Remember each tiddler is tagged with the sheet it came from, so any time someone wants to see a list of related tiddlers it can be done with a simple list. If people want to retain a history of imports than that should be up to their own initiative, just like it is with the real import.

[twMat]

OK, that makes sense.

[Marxsal]

v020

1. Mat's changes.
2. Tiddler reports now include fields imported-tiddlers and imported-fields.

pluginstiddlygoosheetsin-v20.json.zip

[Marxsal]

Yikes: using current updated plugin (v20), i just imported what was to be an incremental update of 1 sheet from my 3-tab gSheet... And now the many named tiddlers i had are all renamed with the title "New Tiddler n" (n= 1-82). This was unexpected, and made a real mess of the wiki. Can anyone propose a fix?

Well, Mat did warn you about the dangers of using a thing still in development ;-)

You can use the filter in the advanced search to delete your "New tiddler" s.

Your old sheet probably had an "id" field. In this update we're matching TiddlyWiki, and the "id" field should be called "title". If there is no title field, tiddlers get named by default.

[Marxsal]

PS: just noticed my wiki has TWO of these plugins installed: both v0.0.20 AND v0.0.17. Dunno how this happened -i always just drag and drop the new ...json file, presuming that it's an incremental (replace old w/ new) update- but this is the first time i've actually checked under Plugins tab of Control Panel to see.

That's because we renamed the plugin.

[Marxsal]

Also: i'm trying some different things, using both old (v0.0.17) and new (v0.0.20 "sheetsin") plugins, and i'm wondering: what exactly is the function of that "Confirm?" checkbox that appears when i re-import the same gSheet -and it asks if i want to confirm that (for example) there is 1 sheet with updates. ?

Be sure to delete old v17. Save and reload. TWICE -- otherwise the old code could still be written into the TW header.

The confirmation tells you if there have been changes to the sheets (new tabs, deleted tabs, renamed tabs). It's mostly a heads-up that things may look differently in the drop-down list.

[ludwa6]

Thanks @Marxsal -i cleared out the old plugin/code per your advice- and am clear that the "Confirm" tickbox is just a heads-up warning (good to have). Yet: i'm having the same problem with import overwriting my gSheet assigned tiddler names with the generic "NewTiddler n" name -which problem i never had in the last several days of using each successive version as it appeared. :-(

[Marxsal]

same problem with import overwriting my gSheet assigned tiddler names with the generic "NewTiddler n" name -which problem i never had in the last several days of using each successive version as it appeared. :-(

Did you remember to rename your "id" field to "title" ? Eventually we should make it possible to select your key field, but for the moment it needs to match TiddlyWiki, which uses the "title" field as the key field.

[twMat]

@Marxsal - whoops! I had completely missed that you posted an update! Looking into v20 right now.

@ludwa6 - frankly, you're disturbing us. Don't use this.

[ludwa6]

Apollo 13 to Houston: roger, wilco -standing by, pending further instruction.

[twMat]

@Marxsal - it seems you missed to insert ...readme_use
Didn't try more stuff yet but will, of course.

[twMat]

OK, things look great! I am now entering destruction mode. First find:

*A sheet-tab named with forbidden characters (e.g this well take this! [ and ( and ] ) !(////// causes RSOE )

[ludwa6]

Dunno if you are speaking hypothetically, @twMat -but in my case, tabs names are all just standard alphabetic letters, tho they are in mixed case. Is that illegal?

[ludwa6]

ps: if you want to collab on debugging in realtime, we could do in the TW5 Discourse channel -or anywhere else you want, i can make time for this.

[ludwa6]

Oops -guess i missed the memo on that one, @Marxsal, i hadn't renamed the "id" column on gSheet to "title".  Now i have done.. And YES it does name the tiddlers correctly per each record in that renamed column.  Question tho: What about the Spreadsheet name? Right now i'm working with a 3-tab gSheet called "SpreadsheetTiddler 1"... But when i start pulling different sheets into the same wiki, that could get awkward.  Can the importer not pick up the hame of the gSheet (as it did in some early version, IIRC)?   /w On March 5, 2021 at 5:05 PM, Marxsal <[email protected]> wrote: same problem with import overwriting my gSheet assigned tiddler names with the generic "NewTiddler n" name -which problem i never had in the last several days of using each successive version as it appeared. :-( Did you remember to rename your "id" field to "title" ? Eventually we should make it possible to select your key field, but for the moment it needs to match TiddlyWiki, which uses the "title" field as the key field. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Marxsal]

Question tho: What about the Spreadsheet name? Right now i'm working with a 3-tab gSheet called "SpreadsheetTiddler 1".

Er, what about the spreadsheet name? I don't understand. You can change the spreadsheet name at google. However the name isn't used much. It's only used when generating the spreadsheettiddler that contains the id, sheet list, description. I don't see what impact it would have on anything.

[ludwa6]

My gSheet is called "PlantsDb" , @Marxsal, and i'd like to keep it that way -and what i'd like even more is if that name could appear in dropdown menu of the import widget, over the names of the 3 tabs in that gSheet. Right now the tabs appear with their correct names, nested under the name of "SpreadsheetTiddler 1". This is no problem now, while the wiki is only pulling data from that one gSheet, but if i get into pulling from multiple gSheets (as i am hoping to do), it would be good if the dropdown menu -and the reports that it creates- could reference the name of the gSheet that data is coming from, instead of nondescriptive title. I only ask for this because it did work that way in a version of some days ago, IIRC... But if that feature was sacrificed for some higher purpose, it's not a problem.

[ludwa6]

Please ignore my last, @Marxsal : i just noticed that if i change the name of that "SpreadsheetTiddler 1" and save it, then the dropdown import menu reflects the change -and that solves the problem i was anticipating w/ multi-gSheet confusion.

[twMat]

@Marxsal , some very positive reports.

In the demo spreadsheet I added three new sheets with some limited challenges - they all work:

• TickerPlugin is an actual plugin (not a very impressive one, but still)
• HugeTid has a 50000 character text. That should actually be enough for quite a lot but I agree it won't cover everything. BTW SheetsIN is some 32000 chars - but including a lot of commented out stuff, so updates could probably be provided by the plugin itself.
• Connected cells is a simple summation of two numbers but the point is that the sum is correctly exported as opposed to the formula behind the sum.

In summary: Extremely promising.

Regarding the forbidden tiddler title characters, is there a way to manipulate these? Is there perhaps a direct slugify command in JS?

[Marxsal]

@Marxsal , some very positive reports.

In the demo spreadsheet I added three new sheets with some limited challenges - they all work:

cover everything. BTW SheetsIN is some 32000 chars - but including a lot of commented out stuff, so updates could probably be provided by the plugin itself.

I'm not sure what comments you're referring to. There's only a few "alerts" commented out that are helpful whenever we make changes ... which we still are.

Regarding the forbidden tiddler title characters, is there a way to manipulate these? Is there perhaps a direct slugify command in JS?

I need to tweak the code to no longer use regular expressions to read the title. That may fix it, unless there is an underlying, deeper problem with the sheet name handling. Let me know when it's safe to code.

[twMat]

I'm not sure what comments you're referring to. There's only a few "alerts" commented out that are helpful whenever we make changes ... which we still are.

Hm, I lately only briefly looked at the .../googlesheets.js tiddler and as soon as I see the Yandex thing and the HEEGreadyState var, I've been assuming that "OK, Mark wants to keep some old stuff for reasons that only JS guys understand". Now that I look closer I see that the other previous old stuff has indeed been removed! :-)

Should the following bit inside .../SheetSelector stay?

<!-- 2021-02-28 Moving this process to javascript . Keep for reference ... 2 months ?

Let me know when it's safe to code.

It should be fine now. I ask you to do these tweaks:

• insert the readme_use that appeared in my last release
• In /Stylesheet I mistakenly added three empty initial rows (you'll see what I mean)
• Depending on your reply to the above about the commented out code in /SheetSelector - keep or remove

For later version but for the record
I stumbled over this site that instructs some script command to insert directly in a cell: =GOOGLEFINANCE("GOOG", "price", DATE(2019,1,1), DATE(2019,12,31), "DAILY"). It is a fantastic feature but the result is two columns - one with heading Date and the other with heading Price. The example creates a row per day, i.e hundreds of rows but thousands of rows would be very common for such things.

It stikes me that it is very common to list such "index:value" pairs (here date:price) vertically like that. But one tiddler per row is probably a bad idea both because of the volume but also because it partly loses the context for each row among the other rows. It would make more sense to put all that data into one tiddler with a field for each item.

The sheet could perhaps be transposed but the TW user might not have rights to manipulate the sheet, so it will be desirable to do this on the TW side, somehow.

There, if you didn't pull your hair before then when we get to this I think that will be a good time.

[Marxsal]

It stikes me that it is very common to list such "index:value" pairs (here date:price) vertically like that. But one tiddler per row is probably a bad idea both because of the volume but also because it partly loses the context for each row among the other rows. It would make more sense to put all that data into one tiddler with a field for each item.

I've never seen a spreadsheet function that turns into two columns. The first thing I wonder is whether it imports as two columns, or as one column with the contents =GOOGLEFINANCE(blah) . If it actually imports as two columns, then the next thing to determine would be how you would convert those into tiddler fields. presumably you'd have to parse out something like price-2020-02-01 .

Edit: D'oh! Why not just import as a data dictionary?

[twMat]

I've never seen a spreadsheet function that turns into two columns.

Me neither but my point was just that the index:value form is common.

The first thing I wonder is whether it imports as two columns, or as one column with the contents =GOOGLEFINANCE(blah) .

So I just tested (TL;DR: it works fine): For that particular command - but maybe that is a common google script trick - the command actually converts so the displayed value in that very cell becomes Date. This becomes a date field in TW. Similar to previous test of how =SUM(A2:A3) becomes the calculated value in TW.

Edit: D'oh! Why not just import as a data dictionary?

Yes, for the two column thing a dictionary sounds spot on. ...But I am uncertain about naming conventions for data indexes. I can't find anything in the docs.)

[Marxsal]

I didn't test for the odd-ball sheet tab names, but I did change the code I thought was responsible.

pluginstiddlygoosheetsin-v021.json.zip

[twMat]

Ye intuition is sharp my friend. I imported the odd sheet tab name, seeing it in the Recent list and thinking... well, it still has all the messy characters so why would it work this time? - but it did!

I note you removed the old code in /SheetSelector. We can always find it in old backups. But there must not be an empty line before the <!-- New, post-js code --> because the import field gets double height. Can I ask that you make that little correction, please?

Now I can only think of two matters:

• Where publish? For this particular JS heavy project, I think it makes more sense with gh. But putting it in my repository is not a good idea because I would mess things up. So can it be in your repository? Or can we/I/you start a "TiddlyGoo" repository?
  And if it is on gh, can it be demoed there? Otherwise I can put up a demo on tiddlyhost.
• For the DEMO, I'll lock the public editing but it will still work as a demo and can be viewed. It is just too trivial to type in e.g a core shadow title.
  ...But I'll keep the google form. Again, it is trivial to post something malicious but it takes at least a tad more effort and intention than to do it directly in the spreadsheet.

[Marxsal]

I'll look into putting it on GH. I'm sure it can be demoed, if it can be set up at all. It will need some sort of introduction tiddler. I'll probably make some minimal version as a landing spot.

[twMat]

Could /readme_about serve as introduction or do you mean someting else like how to download it form gh etc?

[Marxsal]

Here's where it's deployed:

https://marxsal.github.io/TiddlyGoo/

[twMat]

That's exciting news!

OK, I now see what you mean with need for a proper into tiddler. I will write it tomorrow.

BTW, I made a small start for a wiki to collect useful TiddlyGoo stuff: https://tiddlygoo.tiddlyhost.com/ Yes, very messy at the moment. Obviously, the next milestone is SheetsOUT but it also makes sense to to collect scripts and stuff for further integrations. For example, I will personally use this with google drive and have found some useful stuff to fetch from drive into sheets.

[Marxsal]

It says "forbidden".

[twMat]

sorry, now fixed hopefully. And now bed...

[twMat]

First a Q: Considering the wiki name of your side ("TiddlyGoo") - is the site intended for SheetsIN only or for TiddlyGoo stuff more broadly? IMO either intention is good as long as the name reflects this.

For the default tiddler then; I think this makes sense as a default tiddler:

title: About (if the site is titled "SheetsIN") |  title: About SheetsIN (if the site is titled "TiddlyGoo")
text:
Install by drag'n dropping this into your wiki: <<tag "$:/plugins/tiddlygoo/sheetsin">>

{{$:/plugins/tiddlygoo/sheetsin/readme}}

For a prettier tagpill I just raised this question.

[twMat]

@Marxsal - what remains to be done before official announcement, in your opinion?

[Marxsal]

You mean before everyone starts breaking stuff ?

BTW, I just uploaded your about tiddler. I bumped the vsn to v22. I got to see the Github angry unicorn avatar.
So, technically it should be ready to go. If anyone is reading along, the main repository is at https://github.com/Marxsal/TiddlyGoo/ .

My thought was that there is an "TiddlyGoo" repository, which initially has plugin "sheetsin" but may eventually have "sheetsout", "sheets-twed", etc.

But I'm thinking that this project isn't really about JS. So it might make sense for you to host everything on your new TiddlyGoo site. That way you can add notes and updates at your leisure. But it's up to you.

[twMat]

But I'm thinking that this project isn't really about JS. So it might make sense for you to host everything on your new TiddlyGoo site. That way you can add notes and updates at your leisure. But it's up to you.

When you say "host everything on TiddlyHost" - do you mean no github even for developing the JS stuff?

Because if that is what you mean, then consider that there is probably no Siniy-Kit stuff to piggyback on for SheetsOut... sooo, if we hope for anyone else to engage with the JS then I'd guess they will demand GH for co-development, right? I think our back-and-forth work process (which I have enjoyed) would scare off JS developers or at least not attract them to this project.

...because we do need help, right? Or are you willing to take lead for SheetsOUT? It can't realistically be me since I don't know JS and I would have very little to offer until late in the process (the UI). If you work on it, I would obviously make the coffee, and run out on google search missions etc and I will, regardless, in parallel work on further integration things that use SheetsIN (and SheetsOUT) but the actual dev of SheetsOUT would in that case be mostly you alone. If you are willing to do this, then hosting it on TiddlyHost will be perfectly fine and I can create a great site for serving these things and a lot of surrounding things (but my vacation end today so things will be somewhat slower than it has been this 2 weeks).

[twMat]

Strangely, the pill at https://marxsal.github.io/TiddlyGoo/ is not droppable into another Chrome tab!? It looks like it can be dragged but not dropped. The link is no problem to DnD.

[Marxsal]

When you have a tag pill, it drags and drops things tagged with that pill. There is probably a way to use CSS to make a link look like a tag. I bet Mat would know ...

[Marxsal]

Updated TG with linked drag-n-drop for now.

[twMat]

Ah, clever. Quickfix

Install by drag'n dropping this into your wiki: <div class="pill">[[SheetsIN plugin|$:/plugins/tiddlygoo/sheetsin]]</div>

Source code is currently being maintained at [[https://github.com/Marxsal/TiddlyGoo]] .

{{$:/plugins/tiddlygoo/sheetsin/readme}}

<style>
.pill {
  display: inline-block;
  padding: 0.16em 0.7em;
  font-size: 0.9em;
  font-weight: 400;
  line-height: 1.2em;
  color: #ffffff;
  white-space: nowrap;
  vertical-align: baseline;
  background-color: #ec6;
  border-radius: 1em;
}
.pill a {
  color:black;
  font-weight:normal;
  text-decoration:0 !important;
}
</style>

[twMat]

@ludwa6 - so, I promised to alert you when the time was in: I think the time has come for beating the cr*p out of this to find its flaws: https://marxsal.github.io/TiddlyGoo/

@Marxsal - feel free to make that tweak I posted yesterday if you want to.

[ludwa6]

***@***.***Mat: got a heavy week of work happening down here on the farm, but i will be all over this thing IMCST (In My Copious Spare Time -ha! :-), and will be happy to provide feedback.  To that end, two questions: How do you want feeback delivered?  Marxsal's issue tracker for the project, perhaps? Which version is most current?  I'm running v0.0.21, and while it's nice to see this site that looks just like the installed plugin, with a drag&drop link right at the top, but (putting my n00b hat on for a moment :-) i'm not clear if that's the. thing to do over a previous version.  Might do well to preempt that doubt on the site. Yours, Walt On March 9, 2021 at 5:12 PM, twMat ***@***.***> wrote: @ludwa6 - so, I promised to alert you when the time was in: I think the time has come for beating the cr*p out of this to find its flaws: https://marxsal.github.io/TiddlyGoo/ @Marxsal - feel free to make that tweak I posted yesterday if you want to. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[twMat]

@ludwa6

OK, so if it will take a few days then maybe we can release it (I did already test some stuff) and you can test it whenever you find time. Appreciated.

The latest release can be found here https://marxsal.github.io/TiddlyGoo/ and it is .23 but I don't think theres really any difference from .21.

I would say the best place for feedback is here: https://github.com/Marxsal/TiddlyGoo/issues

I'm not sure what you mean with:

[...] while it's nice to see this site that looks just like the installed plugin, with a drag&drop link right at the top, but (putting my n00b hat on for a moment :-) i'm not clear if that's the. thing to do over a previous version.

Do you mean about drag'n dropping the link onto your current wiki? Yes, this is standard procedure for updating plugins.

Thanks for your help.

[Marxsal]

Hi @twMat , @ludwa6

We all know what it's like when GH hides posts from you -- I totally did not see the latest update from Mat! I just posted what I think is v23, with Mat's improved tag pill. Sorry if I've managed to get the version numbers off.

[twMat]

Further confusion: I didn't see this last post of yours and meanwhile just posted the next so to say.

Anyway, I think it should be obvious what to do next, i.e to update so it matches what I posted. And then RELEASE! :-D

[twMat]

@Marxsal

OK, I took the liberty of tweaking a few things with the https://marxsal.github.io/TiddlyGoo/ site:

• the tagpill
• /about_demo - I've changed the settings for the google demo sheet so one now has to use the form to send in stuff
• DEMO spreadsheettiddler - updated some sheet-tab names

tiddlygoosheetsin23.zip

Thereafter, I say we... RELEASE THE KRAKEN

[Marxsal]

v024 posted.

[twMat]

@Marxsal - looks great!

Will you or I do the honours of announcing it? I'm fine either way.

[twMat]

Come to think of it, it is a good opportunity to mention thoughts about the bigger project, i.e to invite people for the SheetsOUT project and that we hope people will experiment with further integrations and share google scripts.

[Marxsal]

Come to think of it, it is a good opportunity to mention thoughts about the bigger project, i.e to invite people for the SheetsOUT project and that we hope people will experiment with further integrations and share google scripts.

It seems like you have a lot on your mind, so you should make the post to be sure to get all that out there.

[twMat]

The sheet has hit the fan and it is now announced.

When authoring that writeup I found an official intro link for google scripts. This is more suitable than the current link I give at the very bottom of .../about_use so if you can please just exchange the very last bullet in that tiddler into this:

*...or, better yet, hack your own integrations with [[Google scripts|https://developers.google.com/apps-script]] and ''share your scripts with the ~TiddlyWiki community''! :-)

(I'd personally not even bother to change the version number for this peripheral detail, to avoid confusion.)

Thanx!

[Marxsal]

Made quick fix.

[twMat]

(I replied to your deleted message, and when I discovered it was deleted I consequently deleted my reply. I'm guessing you got some email with it so to avoid confusion for you I'm writing this post.)

[Marxsal]

I'll call it a prerelease for now. Made About default.

[twMat]

@Marxsal - I say this thread has reached its end and we continue over at https://github.com/Marxsal/TiddlyGoo/issues if there are more issues.

It has really been a true pleasure to cooperate with you! The process definitely took longer than I expected but I'm super satisfied with what we've created. DANG! - It is elegant!