All,
First, Charlies Original video post addresses this very well.
I wonder if the "smart" permalink could be set to use any field eg
[[fieldname[value]] not just [[uid[0000n]] and if there are multiple
tiddlers open them all?
On system vs tiddler "serial" numbers, I built a system I have not yet made
public, that had TSN (tiddler serial numbers) and SSSN (system/shadow
Serial Numbers) it is possible to have both (TSN and SSSN) but unlikely.
The SSN's are recorded separately from the tiddler (if it is or has a
shadow), with the expectation that one day we may put a SSN on all core
system tiddlers but until then I do not want to turn every system tiddler
into a tiddler with an edit.
- We should also remember you can place a unique ID, on demand, for
tiddlers than need it, and leave the rest alone (charlie demonstrates this)
- I will also reiterate we can already do stable permalinks by other
means (missing tiddler handling) not UID's basically before displaying a
missing tiddler content go looking for the new content, people will not
notice it moved.
- UID's have a lot of benefits and I would love a good solution,
Charlies is approaching it,
however there are other ways to address permalinks.
Charlie -
- I would be happy to provide other benefits to serial number fields -
automatic or preset.
- There is a little trick, in generating serial numbers if other users
can access the same wiki. Generate (read, increment, write) the number
inside the button so it happens only at the moment of the click.
- I also have algorithms for making very short serial, numbers,. saving
many bytes/kilobytes for lots of serial numbers.
- Serial numbers can be one way, generate them from an increment with
any unique algorithm, once stored in the tiddler (Hide the field from the
edit view so it can't be edited), and they do not need to be user
readable
although why not?
- It is possible to add additional values to the serial number if
desired, like a wiki name to ensure cross wiki validity. or even add an
epoch, eg design, then published, the serial number remain unique (in
this
wiki) because of the serial component but they can allways carry more
information.
- It would be useful in the wiki to keep a record of the permalink used
to get to the site at least for the current session, thus the content can
be varied for different users and the permalink they used.
Regards
Tones
On Friday, 7 May 2021 at 11:28:10 UTC+10 TW Tones wrote:
> Mario,
>
> It would be simple to enhance the update process to report on the core
> shadow tiddlers it changed that have a "tiddler" (rather than Shadow) and
> give the user the ability to review the differences and decide what to do
> (accept -trash tiddler, ignore -keep tiddler, edit - update new core with
> edited tiddler). Alternatively a "post update" review.
>
> As I understand it the update currently just replaces mostly the $:/core
> plugins, if not all, even if they don't change.
>
> Regards
> Tony
> On Thursday, 6 May 2021 at 18:55:14 UTC+10 PMario wrote:
>
>> Hmmm,
>> I think, that's not very practical. As soon as you want to link to a TW
>> shadow tiddler, you create a clone as a side effect.
>>
>> IMO linking needs to be side-effect free! Those edited shadows are
>> "system" tiddlers. System tiddlers are "user content" and the use always
>> wins. So those tiddlers will not be updated, if a new core will be used.
>>
>> So linking will break the update mechanism
>>
>> Just a thought.
>> -mario
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/5b4d55ff-b493-4d39-9359-23aff050ff13n%40googlegroups.com.
