2026/05/05

Tuesday, May 5, 2026 (#125)

Monday Tuesday Wednesday posts: prev < this > next

References Ferreteria/v0.6/clade/Sys/FileSys/Aspect/Ident/spex (← links) Ferreteria/v0.6/clade/Sys/FileSys/Aspect/Ident/spex/FSChain (← links) Ferreteria/v0.6/clade/Sys/FileSys/Aspect/Ident/spex/FSChain/@removed (← links) 2026/04/29 (← links) Futilities/v0.6/clade/Sys/IO/Store/Spider/@fx/OnPath (← links) Futilities/v0.6/clade/Sys/IO/Store/Spider/@fx/OnFolder (← links) Futilities/v0.6/clade/Sys/IO/Store/Spider/@fx/OnWantedFolder (← links) Futilities/v0.6/clade/Sys/IO/Store/Spider (← links) Ferreteria/v0.6/clade/Sys/FileSys/Aspect/Ident/spex/FSLink (← links) 2026/05/06 (← links) Futilities/v0.6/clade/Sys/IO/Store/Spider/@fx/FindDiffChars (← links)

FTM update

retrospective note
During the process of working all this out, I moved some stuff: Ident/stringer/Chain ⇒ Ident/spex/FSChain Ident/stringer/Chain/Twig ⇒ Ident/spex/FSLink Where I'm talking about these clades before moving them, I've updated the links but kept the old names (which is hopefully less confusing).

I'm thinking about how best to adapt the FSChain clades (especially Twig) to work with Futilities/v0.6/clade/Sys/IO/Store/Spider.

What's needed, I think, is for the model to work with relative anchor-points -- so I can say "give me the path to get from [here] to [here]".

There is currently FigureRelative(string $fsFull), which just uses string-operations to extract a relative path (remove the part of $fsFull which is already in $this->GetIt()). Maybe that's good enough?

It seems like a lot of unnecessary calculation, though: If I'm saving a node from upstream in the path -- call it $oBase -- and trying to get a path to the current node ($oHere) -- then in order to use FigureRelative, I ultimately have to call SpecArray() (which builds an array by iterating from the base back down to here) and then iterate through that array to build the spec-string) for both $oBase and $oHere, and then do the string-calculation.

Wouldn't it make more sense to have a function which starts from $oBase and works forwards until it gets to $oHere, and builds the array from that?

Even better, why not just build the string directly instead of putting it into an array first? Do we ever do anything with SpecArray()'s outputs besides building a spec?

• 11:29 One thing that needs sorting out: Chain is not actually the parent of Twig. (Clearly my code has been having illicit affairs when I wasn't paying attention.) I'm trying to figure out whether this makes sense, or if Chain should even be a thing...
• 12:46 I think that's all resolved now. Tentatively, FSChain (fka Chain) does make sense, though I will need to think about it more later when I have time.
  • Started SpecTo(SelfIface $oBase) but can't finish it now.
• 22:15 Currently working on moving [WFu]Sys\IO\Store\Node\Pair to [WFu]Sys\IO\Store\aux\Spider\Pair and updating it.