Updating the community showcase page on TiddlyWiki.com

[odin...@gmail.com]

Hi everyone!

With the new year starting tomorrow I was thinking about updating the community section on the official TiddlyWiki site. To check if all the links are still working, and to add helpful plugins and editions that have been made this past year. My goal would be to increase the chance that we inspire newcomers to try out TiddlyWIki, and to help them find the building blocks to adust TiddlyWiki to their use.

My plan is to collect entries in this thread. And then to create a pull request to add them to the website.

Secondly, the list under the tab 'resources' is really long and thus a bit unwieldy. I would like to propose to split up this list into different categories for easier browse, search and lookup. My proposal would be to split it into the following tabs: 
1) Plugins (for all community made plugins such as shiraz, krystal, projectify etc.)
2) Themes & Palettes (self-explanatory. Maybe even split this one in two as well)
3) Editions (preconfigured Wiki's with a number of plugins for a certain goal/usecase such as: drift, stroll, tiddlyresearch etc.)
4) Other resources (such as macro's, widgets, code snippets etc. that don't fall into the other categories)

To clarify, this is to split the current 'resources' tab and thus keep the Tutorials, Examples and Articles categories for their respective use.

I am opening this thread to ask for input on what to add. This is the draft of the list based on my bookmarks and the entrees people gave in the best of 2020 thread:

Plugins
1) Projectify
2) Command Palette
3) TWCrosslinks
4)  Editor Autolist  

5)  TiddlyRemember 
6)  Streams plug in 
7) danielo's Context
8) Relink Plugin
9) linonetwo's Copy on select plug in
10) My own recipe plugin ; - )
11) Timer Tools

Themes
1)  Mono theme 
2)  Whitespace theme 
3)  Notebook theme    
4) 

Palettes
1) Dracula palette
2) jd's palletes

3) 

Editions
1) Stroll
2) Drift
3) TiddlyResearch
4) Noteself (is already in the resource list, but I would sort it into this category instead)

This is a list of current tiddlers on the tiddlywiki.com website that I've found so far with broken links, that are out of date or need updating:

1)  Plugins by Uwe Stuehler - Link to a tidldywiki with javascript error
2) "PETTIL - Forth for the Commodore PET" by Charlie Hitselberger - website is not online anymore. 
3) TiddlyDrive Add-on for Google Drive by Joshua Stubbs - link to the instructions gives a 404 error
4) "TiddlyWiki5 Coding" by Chris Hunt - site not found
5) "TWeb.at" by Mario Pietsch - gives an empty unstyled 'work in progres' website
6) IndexedDB Plugin by Andreas Abeck - coudn't reach site (can anyone check if it is the same on their end?)
7) TiddlyWiki Jingle by Måns Mårtensson - page not found

8) "How Does Twederation Work" by Jed Carty - the wiki does loads, but the tiddler is missing. Seems to be discontinued since 2016

Some closing thoughts: 
1) Third party/community build plugins and editions are not always updated. A disclaimer on top of the list reminding people to carefully read the instructions of the plugin creator, telling them the plugin might be outdated, and to BACK UP BEFORE INSTALLING would be in order.
2) In the future, maybe we can strive towards a community github repo with mature community-made plugins to build a plugin library. this way the installation of plugins is more seamless for the user. But this is a topic for another thread.

I hope my ideas have come across clearly (English is not my native language) Let me know if you have any questions on this plan.
I am curious and am looking forward to any thoughts and recommendations you may have. Let me know!

[David Gifford]

Hi Odin! Awesome, glad you are doing this. The community section needs some love.

While you are at it, please have the Obadiah TOC tiddler removed from tiddlywiki.com. Dead link to an old site of mine. I alerted people here years ago to remove it, and nothing happened. Thanks.

[odin...@gmail.com]

Thanks for the reply!
The link works for me. I can remove it of course, but It might still be useful for people as inspiration, don't you think? Or Do you want it removed because you don't want it featured?
I just realised that your personal documentation wiki might also be useful. Can we add it to the list or would you rather not?

Op donderdag 31 december 2020 om 12:16:49 UTC+1 schreef David Gifford:

[Saq Imtiaz]

This might be relevant:

https://github.com/Jermolene/TiddlyWiki5/pull/5116

[Mohammad Rahmani]

Hi Odin,

Great work! Thank you!

David Gifford may have some good inputs from his experiences in the great Tiddywiki Toolmap.

Just few suggestions

1. I suggest preparing a template for any new submission. Right now everybody submit his/her plugins/themes in any format he/she wants!

2. Some old resources need to be checked if the link works or not and reformatted to some standard form (if a template is prepared)

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/583a18db-8a00-4b25-96a3-61effdc950d6n%40googlegroups.com.

[David Gifford]

Hi Odin

Remove the Obadiah TOC link because it's old, ugly, and there are many more new and better ways to do that.

Yes, feel free to add my documenting TW site.

And please, please add Stroll.

[odin...@gmail.com]

Did the first pass through all the entries and added some new.

I did the following:

1. Split the 'resources' tab into categories (Community plugins, Community themes, Community palettes, Community Editions, Other Resources)
2. Removed entries with dead links (and one entry on by request)
3. Added entries based on the 'best of 2020 forum thread'
4. Went through all existing entries and sorted them into the new categories by changing the tags and moving them into new folders.

See the pull request here: https://github.com/Jermolene/TiddlyWiki5/pull/5353
This was my first or second time using git outside of tutorials, so it was a fun learning experience, hopefully, everything went well.

@Mohammed: For now I just went with the recurring standard I saw. But a standardized template is a good idea. What would you include in the template?

Op donderdag 31 december 2020 om 15:42:29 UTC+1 schreef David Gifford:

[Jed Carty]

The twederation link is supposed to be http://twederation.tiddlyspot.com/#How%20does%20the%20TWederation%20work%20anyway%3F%20-%20The%20TWederation%20(2016122014h0034)

I don't know why but the browser cuts off the last ) when you copy it from the navigation bar.

But the twederation updates haven't been put on that site for a while, but the information in that tiddler is still correct. I don't know if it is worth keeping on tiddlywiki.com or not, everything is going to be moving over to ookwiki.com as I make more progress with that.

[clutterstack]

Hi Odin, just confirming the IndexedDB plugin's subdomain does not seem to exist.

Best,

Chris

[Jonathan Lundquist]

Found the https://odinjorna.github.io/recipe-plugin/ because of top post.  Just one wish... Is there a way to make the edit button for any tiddler tagged 'Recipe' open in the recipe editor, instead of the default editor which is useless for recipes created with the plugin?

On Thursday, December 31, 2020 at 2:56:40 AM UTC-8 Odin wrote:

... 

10) My own recipe plugin ; - )

...

[Odin]

Hi Jonathan,

That is a great question! I am not sure how to add a conditional rule to the edit button to check if the tiddlers tag is Recipe, and then code to open up the recipe editor. This would also lead to change/edit the core tiddlers, which is not advisable because it makes updating to new versions tricky. 

However, it is possible to add a button that when pressed navigates to the recipe editor plugin and sets the selection tiddler to the recipe. Here's how I did it:

<$list filter="[all[current]tag[Recipe]]">

<$button>

<$action-setfield $tiddler="$:/plugins/Odin/Recipe/Selection" text={{!!title}}/>

<$action-navigate $to="$:/plugins/Odin/Recipe/RecipeEdit"/>

Open this recipe in the Recipe Editor

</$button>

</$list>

The list widgets lists all tiddlers with tags: Recipe (this makes the button only appear under recipes). Then a button is created that has two actions upon pressed. First, it sets the selection tiddler to the title of the recipe on which the button is showing. Then it navigates to the recipe editor. 

Create a new tiddler (title name doesn't matter) and tag it $:/tags/ViewTemplate. Copy the code above and paste it in. The button will appear at the end of the recipe. If you want it to appear at some other place you can add a field 'list-after' or 'list-before' that contains the title of the tiddler you want to have it appear before/after.

Hope this useful. I might add this functionality next time I spend time updating the plugin. I was also thinking of adding a course category, i.e: breakfast, lunch, dinner etc. Which would add another filter to work with.

Op zaterdag 2 januari 2021 om 08:05:30 UTC+1 schreef Jonathan Lundquist:

[Mohammad Rahmani]

Hi Odin,

@Mohammed: For now I just went with the recurring standard I saw. But a standardized template is a good idea. What would you include in the template?

Op donderdag 31 december 2020 om 15:42:29 UTC+1 schreef David Gifford:

I have used a template in TW-Scripts for several years, but I think it is good to post on GitHub discussion panel to see what Jeremy and the developers say.

Do this and get the idea of Jeremy.

1. Go to https://kookma.github.io/TW-Scripts/
2. From left open the menu bar and then click on Links branch
3. Open any of the links. I Have attached a screenshot
4. I propose three properties in bold
1. Resource name
2. Url
3. Developer(s)
5. I also propose a section with heading 2 called 
• Description
• include a brief and informative description here

In TW-Scripts I used a ViewTemplate to format and display these in a semantic form. BUT using fields and ViewTemplate in your case is a BAD practice because they do not appear in standard search in tiddlywiki.com. You may add a part as keywords (or use tag).

Please feel free to use any info, design, tool from TW-Scripts. It belongs to the community not me.

Good luck

Mohammad

 

[Jonathan Lundquist]

Good evening Odin,

Based on your earlier message and my limited knowledge, this is what I did, feel free to use it:

created: 20210103032740086

creator: jhl

list-before: $:/core/ui/Buttons/edit

modified: 20210103051251570

modifier: jhl

tags: $:/tags/ViewToolbar

title: $:/plugins/Odin/Recipe/EditButton

\whitespace trim

<$list filter="[all[current]tag[Recipe]]">

<$button tooltip={{$:/language/Buttons/Edit/Hint}} aria-label={{$:/language/Buttons/Edit/Caption}} class=<<tv-config-toolbar-class>> >

<$action-setfield $tiddler="$:/plugins/Odin/Recipe/Selection" text={{!!title}}/>

<$action-navigate $to="$:/plugins/Odin/Recipe/RecipeEdit"/>

        <$list filter="[<tv-config-toolbar-icons>match[yes]]">

           {{$:/core/images/edit-button}}

        </$list>

        <$list filter="[<tv-config-toolbar-text>match[yes]]">

          <span class="tc-btn-text">

            <$text text=" "/>

            <$text text={{$:/language/Buttons/Edit/Caption}}/>

          </span>

         </$list>

</$button>

</$list>

I also had to wrap the standard $:/core/ui/Buttons/edit with

<$list filter="[all[current]!tag[Recipe]]">

</$list>

I think there must be a way to hide the standard edit button for Recipe tags without editing the core, but I don't know how.

On Saturday, January 2, 2021 at 7:11:54 AM UTC-8 Odin wrote:

Hi Jonathan,
...

However, it is possible to add a button that when pressed navigates to the recipe editor plugin and sets the selection tiddler to the recipe. Here's how I did it:

<$list filter="[all[current]tag[Recipe]]">

<$button>

<$action-setfield $tiddler="$:/plugins/Odin/Recipe/Selection" text={{!!title}}/>

<$action-navigate $to="$:/plugins/Odin/Recipe/RecipeEdit"/>

Open this recipe in the Recipe Editor

</$button>

</$list>

...