Oh, I’m so glad you see it this way. It really has been a TON OF WORK. Has brought me great joy. It is nice for the effort to be recognized. I and I sincerely hop that people will benefit it and support my efforts so that I can continue with this work. Thank you!
Absolutely I can help with the plan as well. This is how my priority will work, feel free to edit
- We can start with Daily Journaling which will be the building block
I love how you have allowed for individual events and meetings to take place in some day , and yet allowed a time tracking smart lists which allow to see all events / non events etc .
We can look at different time tracking lists only in context of daily journaling only.
We further explore any topics items related to above such as archiving old entries ,
We look at Projects , sub tasks , how due dates auto work
We revisit time tracking but now in context of Projects ,also taking priority in picture
High level concept of Annual Planning , Pie-Charts to see 50,000 ft will definitely require separate videos
I feel in each of your deconstruction video , some context(brief philosophy) would help the user (me) to understand why you are doing some of things you do
I’ll definitely check it out.
Cool! You free later this afternoon or this week? Perhaps we can jump on a Zoom call and we can build out a plan. Shoot me a private message. I can show you the outline for the book I’m working on too. Would love you ideas.
Interesting to see what is possible – a lot more than I might have imagined.
I have sometimes thought that a good way for a user to learn Tinderbox would be to create a Tinderbox file about learning Tinderbx. And that leads me to think that it would be interesting to have a series of Tinderbox files at different stages of development. Instead of asking the student to deconstruct the file, it might be useful to see how an experienced user goes from the very first blank file and gradually builds in new elements. (Probably that is what you are planning.) The learner could then look at Tbx1, followed by Tbx2, Tbx3, etc., and see the building process at each stage, making comparisons between the files in sequence. I’m all in favour of small chunks, but I think that chaining them in sequence could be very powerful.
That is exactly what I’m planning. Now that I have the file that is, for the most part optimized, I am going to take it from three approaches: 1) decontract the file, i.e. “Here is how I did this and why”, 2) Start fresh and build in real-time through a series of points (a lot like what @beck did in her wonderful 4-part 2019 videos, and 3) conduct a series of technique videos, with an explanation and suggestions on where this technique might apply in a different context (in regards to this point, I’d love to know other people’s context, e.g. professor, student, lawyer, doctor, writer, project or product manager, and the project they’re working on, e.g. literature review, case analysis, book or article, project execution or product development, etc.).
On this last point RE context, does anyone of any suggests on how we can most efficiently collect insight on TBX user’s context and projects?
One of the things you’ve achieved is by typing shortcuts of mtg- and tsk- to do linking/expanding , could you tell me how that was done.
I’m not exactly sure which part you’re referring to. Can you give a screenshot?
I tried to create a fresh Project. I can see it but it does not look active.
I must miss something. Need a more smaller step intro to this, may be.
This got sorted during the Zoom Meetup. I wanted the $name.beginswith or $name.contains
Inactive means? I believe Milestone has to be created within a project for this file for the due dates to be activated.
within the existing project the example of the video work fine.
Morning, can you provide a screenshot? What does “not look active” mean? What is your expected experience or behavior?
the color is not blue. I tried to set a start gate and I can type in a date, or select a day, but it is not saved, when I go back it is gone. So I can not get the Project going, somehow.
Don’t forget, attribute names are case-sensitive thus $attrname and $AttrName are not the same attribute; the same is true for action code funxtions/operators. So, you want
Hi Werner, you’re not doing anything wrong.
Try this. As you now have a child of the project, the project will adopt the earliest date as the start date and the latest date as DueDate. So in Tsk- Task go ahead and set the $StartDate and $DueDate to something like this:
Also, for fun, tap on the “prototype selector”, the rectable to the left the ink arrow, with two fingers, and apply the task prototype:
I’ll work on a video this week to explain what’s going on.
The color of the task changed as explained in your one by one explanation.
Thanks a lot.
I’ve just updated the file, also added a related lesson: Tinderbox Training Video - TBX - Deconstructing Daily Journal Date Descendants Management.
Highly recommend watching this video if you want to get inspired. Thank you Michael.