Sometimes we want to write tiddler quickly, so we might create a button with a random title: <$button> <$action-createtiddler $basetitle=<<now "[UTC]YY-0MM-0DD0hh0mm0ssXXX">> $template="$:/state/mobile-imessage-layout/new" tags={{$:/plugins/linonetwo/mobile-imessage-layout/settings/Ta…

Hi @linonetwo I think you are asking for us as a community to agree a common way to represent tiddlers that should not have titles that are visible to the end user. I broadly agree, and welcome the initiative. Firstly, I think it’s important to note that @linonetwo is not proposing a new core featu…

Go ahead and put your argument, but with all due respect I think it in unnecessary, and complicated and I would not myself like such changes. I can solve your problems raised with the current core, and you can introduce your change to your wikis and not touch the core.

It is not about my wiki, it is about the plugin developer’s consensus and plugin community’s interoperability. See Suggestion for all Plugin developers about field name: Let’s use Ontology to maintain Interoperability Tiddlywik is not only a note book, it is an application develop framework, that …

Another way to handle interoperability is to provide configuration settings in each plugin. For example allow the installer of a pluggin to configure the tag and field names used by the plugin. This would allow one plugin to be varied to accommodate another. We could provide some code patterns eve…

I think 1 more config, there will be 1% more new user lost. New user don’t like config things. A good product should work out of box like Notion. This is why Notion comes late, but have a much larger user group.

Here’s my thoughts on this. Autogenerated titles should have a standard ontology (way to name things) A standard method of displaying emphasizing an alternate field in the “title-area of the tiddler-card”, while deemphasizing the literal title field (it should still appear as a popup, or ?) Syste…

Hi @joshuafontany you are late! People above was discouraging the use of prefix in title, but rather use a field _prefer_field for this. I think if you want to reference the tiddler generator that generate the random-title-tiddler, you can add field source: Synthetic Dream Machine. [image] josh…

Hmm. Completely machine-generated UUIDs, etc, as Titles means that we lose the “human readable” portion of the title field. I honestly think that many tiddlers should actually NOT be expected to be rendered directly in the story river, but rather transcluded into another “main” Story River Tiddler. …

I second this statement. I also think tiddler titles should be human readable, because TWs main UI is created for humans. If we need a machine readable ID it can be a field. I think the _prefer_field field is be an option I can live with. If it is there and ignored, we are good. If it is used in s…

[image] linonetwo: I think 1 more config, there will be 1% more new user lost. New user don’t like config things. A good product should work out of box like Notion. This is why Notion comes late, but have a much larger user group. I don’t agree, your config can work out of the box and the abi…

The title is the unique key to the data that is a tiddler. Either they are human readable or hidden from view and accessed via smart tiddlers that know how to handle the auto-generated titles. Placing they unique key at eye level is part of tiddlywinks genius. There are plenty of alternatives when…

Talk TW

What's the standard way to not writing Title

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled