|5Cs, 5Cs Learning and Knowledge Management, Agents, Export, Each Operator, Highlighting, Highlighter, Identity Praxis, Indecies, Index, Intersect Operator, Tinderbox
|1) TBX L - Manipulating HTML Export File Name.tbx (264.7 KB), 2) TBX L - Highlighting Syntax.tbx (351.7 KB), 3) TBX L - Index Terms in A Project.tbx (437.0 KB)
In this Tinderbox Meetup, we covered three things:
- How to manipulate the $HTMLExportFileName attribute, which is helpful in previewing if you have notes that have identical names.
- How to use the Highlighting feature to have Tinderbox automatically highlight your text
- How to create an Index of terms (or values in other attributes), this also includes the automatic creation of notes, linking, and other affordances†,‡
†During the video Becker’s index did not initial work. The problem was that he created a note and note an agent for the index. He realized this immediately after the meeting ended. ‡Becker will follow-up with @mwra and @eastgate to see if there is a way to get preview navigation working in the index.
Note: these methods were are through the lens of how Michael Becker (@satikusala) is using the tool. They are not definitive, there are certainly other approaches that can be applied to accomplish the same or similar goals.
TBX Meetup 10FEB24 Unedited Zoom AI Companion Script
The discussion revolved around technical issues related to a note-taking and project management tool called Tinderbox. The participants, including Michael Becker, David Eddy, and Mark Bernstein, explored the possibility of making links created within Tinderbox clickable and using them for navigation within the tool. They also discussed potential performance issues related to constantly rewriting file names. The conversation then shifted to the need to automate the process of changing file names and export names as the month rolls over. They also touched upon the importance of using specific formats and tools for exporting and editing text files to avoid complications with overwriting text. Towards the end, Michael Becker demonstrated how to use highlighting and other text editing features in a file.
Michael Becker, David Eddy, and Mark Bernstein had a discussion about a technical issue related to Tinderbox, a note-taking and project management tool. Michael Becker asked Mark if it was possible to make links created within Tinderbox clickable and if these links could be used for navigation within the tool. Mark suggested that he might be able to find a solution, but he would need to examine the issue further. The conversation ended with Michael Becker agreeing to send a sample document to Mark for further examination.
The meeting focused on a technical discussion about a software platform’s features and issues. The participants considered building a structure and a garage on the platform, faced challenges with the host setting, and discussed exporting files. They also addressed potential performance issues related to constantly rewriting file names. Michael Becker demonstrated how to name export files and planned to follow up on Dave Rogers question about changing the HTML export file name. The meeting also touched on upcoming meetups and promotional efforts. Towards the end, there was a misunderstanding between Dave Rogers and Michael Becker, which was resolved.
Dave, Michael Becker, and Mark discussed the need to automate the process of changing file names and export names as the month rolls over. They explored the issue of manually changing file names when notes are copied, and the importance of automating this process. Michael Becker suggested creating a prototype to manage the blogging process, which would automatically add a unique file name to each note. The conversation also touched upon the historical context of web server design and the changes in URL rules over time. Michael Becker demonstrated how to add a prototype to a new note and how to manually adjust the path name. The team also discussed potential issues that could arise from using certain special characters in file names, especially when dealing with paths and web-related functions. The conversation ended with Dave acknowledging the need for automation and the potential problems that could occur when using certain names.
Michael Becker, Dave, Bill, and Mark discussed technical issues related to note-taking software. Michael Becker highlighted an issue with the preview function jumping to the first article instead of the selected one. Bill Schwartz suggested a solution by changing the HT Malloc export name. Michael Becker explained the root cause of the issue, attributing it to the software’s pathway following. He also demonstrated how to manipulate the text using different stamps and their impact on the preview function. A strategy to change the export file name using the stamp feature was recommended by Michael Becker. Michael Becker also discussed the importance of using specific formats and tools for exporting and editing text files to avoid complications with overwriting text. He shared his personal experience of encountering difficulties when copying edits made in Word back into his Tinderbox file and how he resolved this by using visual indicators. He also demonstrated how to create and use custom highlighters in the Tinderbox app to process notes and apply specific formatting. The team scheduled a review of tinderbox highlights in a 10 and 1010 minute session.
Michael Becker demonstrated the use of highlighting and other text editing features in a file, explaining their usefulness in identifying sections of text and preventing accidental overwriting. Dave Rogers inquired about the location of the CSS style sheet, which Michael Becker was unsure about. The information was found useful by Bill Schwartz. Michael Becker also demonstrated adjusting the size of a highlighted text, removing the highlight, and resetting the formatting to default settings. He suggested the use of an external style sheet for consistent text formatting. Dave expressed interest in using this method with his existing style sheet. The meeting went over the scheduled time due to the thorough discussion of the topic.
Michael Becker discussed the purpose of a project aimed at creating indexes for tinderbox files and demonstrated how to link notes to different projects and terms. He also explained how to export the file to show the index and identify which notes are linked to specific terms. Michael Becker committed to looking into potential navigation capabilities in the preview mode and the possibility of making the preview window clickable after the meeting. He also shared his approach to managing multiple projects in his tinderbox file and his plan to automate the creation of a new project and assign it a unique project ID based on the note ID number. Bill Schwartz shared his personal experience with HTML and expressed interest in the new functionality.
Michael Becker discussed the system of note creation and organization within a project, explaining how each note inherits the project ID of its parent for easy tracking. He demonstrated the process of associating specific terms with notes and highlighted the system’s case insensitivity. Michael Becker also emphasized the importance of the action code in creating a variable path for each item in the term list. A discussion about the creation of an index with notes and the action code running in the P. Index ensued, with Bruce Gale expressing interest in understanding the process further. Dave Rogers praised Michael Becker’s advanced use of the tool. The conversation later shifted to the use of specific terms within a particular project and how they compare to their usage across all projects.
Michael Becker led a discussion about the use of an index in writing, such as reports, books, and blogs. He suggested that this feature might be beneficial in creating a searchable database for terms used in a blog article. However, he also noted that this might be overkill for some blogs. The team also discussed the use of HTML file names and the syntaxing. Towards the end of the meeting, Michael Becker invited the team to share their ideas for future topics. No specific decisions or next steps were mentioned in the meeting.
Please help with the development of future sessions by answering the three questions below.
- What were your top 2~3 key takeaways from this lesson?
- What do you want to learn next? Learn more about?
- What exercises would help reinforce your learning?