Again, I really appreciate all the creative/innovative solutions you and others have come up with for working with Tinderbox documents. I have much to learn from you and other prolific community contributors.
I should note that I’ve been a BBEdit user since the early '90s (we’re talking classic Macintosh system software version 6 at that time), so I can see lots of benefits to using BBEdit as a complementary tool to Tinderbox, and I already do use it to help shape data structures I want to import into Tinderbox.
However, that said, I am interested in exploring some different approaches now that Tinderbox 9.1 has provided a very useful enhancement with callable functions. In particular, with the logging Toolbox, I am experimenting with a complete applet package. Specifically, a Tinderbox document that combines functions with stamps and other Action code plus any prototypes, notes, containers, and user attributes necessary to provide a complete workable solution. In addition, I favor including the documentation for the applet/tool/utility in the Tinderbox document package. Isolating Action code in separate files outside of Tinderbox is counter to this approach, though something that may be useful during the development phase.
As we noted over in the Logging for fun and profit posting, the importing of user attributes is still a bit tricky, and something to be addressed in a more definitive manner. However, my sense is that taking a complete package approach has the potential to be more useful to the broader base of Tinderbox users.