Would like to make calendar with repeat items

[DaComboMan]

It is hard for me to find a Linux compatible app to shareware Calendarscope.

Hoping something could be done to that effect with TiddlyWiki, but how?

[TonyM]

DaComboMan,

There is a number of solutions for getting things done in TiddlyWiki, including some "editions" and of course you could build something from its parts.

I am not familiar with Calendarscope and it seems fairly comprehensive so it is a bit hard to consider your requirement = Calendarscope

Responding to the title of this post "Would like to make calendar with repeat items" however let me share with you a recent discovery, perhaps I should keep this to my self, but I love sharing.

I like to organise tasks into OTSB operational (daily review and action), tactical (respond to unusual events and review weekly, and strategic (longer term planning and monthly review), and sometimes blueSky (review Quarterly).

The "algorithm" I discovered is on any given tiddler (or task tiddler) you want to review on a periodical basis, have a corresponding date field. If this field even exists it means you want it reviewed on that periodical basis. You can quite easily review same tiddler in more than one regular period. Now use a time stamp of now  (in that field) to say you have reviewed it. 

eg review-tactical

Now in a tiddler of the same name as the field eg; review-tactical have some list widgets to list all tiddlers with this field, but importantly for a weekly review only list items that have a time stamp older than 7 days. Each time you action an item simply time stamp it again and they will disappear from the tactical review list for another 7 days.

I also first list items with a blank review-tactical field, which are basically new items I have not yet reviewed.

The advantage of this method is you could visit the list tiddler once a week (every 7 days) or every day (and you will only see things you did not review for 7 days) and 

you can actually change the length of the review period in the list tiddler, without touching all the tiddlers. Any thing that is not reviewed stays on the list indefinitely. All it takes to review something is to click a time stamp icon, which can be set to not even update the modified date.

Finally if you need to ensure you do this review you could add it to your daily operational review or at most you need to set a reminder to open the review-tactical once a week (not on every tiddler). In the past I have used operational list to prompt the tactical review, the tactical review to prompt the strategic review, and the strategic review to prompt the blue sky review. For example a strategic review item asks (once a month) is this the first month of the quarter?, if so do the blue sky review! in typical TiddlyWiki style you could even time and date stamp the review tiddlers on each review, then test if they are due or not, indicating when to do them.

The above is all with little or no alarms and reminders, they are just built into the system.

I may may package and share it one day.

Regards

Tony

[PMario]

Hi Tony,

That's an interesting approach.

-m

[DaComboMan]

I'm embarassed!

I've re-read 3 times and it's like reading algebra (never went that far), sorry!

From what i can understand, (apart from notifications which i don't need), it is possible.

If a visual tuto. could be attached here, then i could probably appreciate this elaborate post a bit more.

My apologies for my ignorance, but thank you for your time and sharing.

Surely others will enjoy! ;)

[TonyM]

Sorry unloading an advanced algorithium on you, but the thread was left very open because you asked for us to provide a replacement for another piece of software.

Thus I focused on your calendar with repeat items.

Try searching for "tiddlywiki gtd" or calendar.

Feel free to provide more details, a less open question. And I am shure we can help.

Regards
Tony

[DaComboMan]

Not a problem!

It's better to have more than less right?

Actually, it's more to have all kinds of anniversaries (b'days, marriage, death etc.) of people and a repeat function (best with evidenced no. of anniv. - as with 2nd b'day etc.).

Thank you for your willingness to help out a newbie!

- - -

Btw, with Firefox extension out of order and as i hope to become more of a dedicated Linux user (Solus Budgie) to be more precise... it could be a good thing to consider having a "snap" for TiddlyWiki that could easily fit on most Linux distros. But that would be for another thread huh.

[Mark S.]

Making an instance  completely compatible with an obscure linux app would be really difficult, I suspect.

A lot of us like Thomas Elmiger's TodoNow TW edition (https://tid.li/tw5/plugins.html).

His app allows you to re-use tasks that have been completed. So if I have something that needs to happen in two weeks, I set it up for two weeks, and then mark it as complete. As part of the daily process, completed items are then either recycled with a new date or archived. While this isn't automated, I find there are very few activities in life that are 100% repeatable at regular intervals.

-- Mark

[TonyM]

Mario,

I basicaly built it today on top of my current project "edit filds" because all I had to was define the date fields and create a listing tool.

Personaly I am moving away from specific plugins and more to how to empower the use of tiddlywiki in what ever way I fancy. My oft stated desire to make fields a 1st class citizen is baring a lot of fruit. This method is a result of this endevour. Normal calendar and to do lists evolved from paper systems, it is time to reimagin them, especialy with tiddlywikis versatility.

Do you or anyone understand the mechanisium by which default date, icon and color fields in tiddlywiki opperate? Is there a framework behind them I could leverage or have they developed in an adhoc way?

I would love to say in answer to this threads question use a reoccuring date field as a pre defined field type.

Regards
Tony

[TonyM]

DaCombo,

Anaversaries are one of the easiest date handling things to do in software. Record the first date and indicate you want an anaversary, except for feburary 29th its simple. Then use the current month day to search for all items that are anaversaries and share the same month day. Then use the year to find the age.

Best wishes
Tony

[PMario]

On Friday, July 20, 2018 at 3:40:05 PM UTC+2, DaComboMan wrote:

Btw, with Firefox extension out of order

I did create a new extension named "file-backups", that allows you to save TWs. ... The only limitation is, it needs to be the "downloads" folder or a subfolder.

have a look!

-m

[PMario]

On Friday, July 20, 2018 at 5:23:36 PM UTC+2, TonyM wrote:

I basicaly built it today on top of my current project "edit filds" because all I had to was define the date fields and create a listing tool.

:)

 

Personaly I am moving away from specific plugins and more to how to empower the use of tiddlywiki in what ever way I fancy. My oft stated desire to make fields a 1st class citizen is baring a lot of fruit. This method is a result of this endevour. Normal calendar and to do lists evolved from paper systems, it is time to reimagin them, especialy with tiddlywikis versatility.

Yes. That's what happens, if you dig long and deep enough.

 

Do you or anyone understand the mechanisium by which default date, icon and color fields in tiddlywiki opperate? Is there a framework behind them I could leverage or have they developed in an adhoc way?

color and icon fields are "just" 2 convetions, that where included to improve tag-tiddlers and especially tag-pills.

Since tag-tiddlers are tiddlers, the solution is generic. So icons work for every tiddler, because the ViewTemplates have been adjusted accordingly.

As fare as I know.

 - The color field isn't used in the default ViewTempate

 - Since 5.1.16 there is a generic tiddler "class" field, which allows "custom tiddler styling"

have fun!

mario

[PMario]

On Friday, July 20, 2018 at 5:23:36 PM UTC+2, TonyM wrote:

Do you or anyone understand the mechanisium by which default date, icon and color fields in tiddlywiki opperate? Is there a framework behind them I could leverage or have they developed in an adhoc way?

I'm not sure if I did understand the question right. This is a second option. No framework default browser behaviour for html input-element: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input

-m

[PMario]

IMO we should have a closer look about the new build-in functionalities and include them into the core. ...

The first step to do this is: -> create plugins and "battle test" them.

-m

[DaComboMan]

Wanted to post sooner but "practical" things have taken precedence.

Your posts are excellent food for thought and will help me to make an excellent calendar.

Thanks!

@Mark S. - sure Snap (much like Flatpak) is a novelty in the Linux world (for now!) but are easy for devs to upkeep.

Hence, they are going to be the way for future app. updates and releases for sure!

[Mark S.]

I misunderstood your original question. I didn't mean to imply that TiddlyWiki was obscure (although it is a bit) .

-- Mark

[TonyM]

Mario,

Thanks for the feedback. Understanding that the different behaviour or icon and colour fields lies in the view template giving them special treatment is helpful. For any field we can edit it as a simple text field but in reality we want to edit and display them differently. 

My question related to are we handling this systematically in TiddlyWiki (in a framework or structured way) or only addressing bespoke internal fields including create and modified? It seems from your answer there is no frame work.

In my own edit-fields project when someone nominates a field be editable in the view template it looks up by the fieldname a corresponding edit tiddler in which the necessary code exists for editing it (I call them field definition tiddlers), so a date field may include a time stamp or calendar look up, an icon or image field the image picker etc... In fact I have gone a lot further and allow bespoke fields like a domain field which provides a manual edit or allows you to lookup a value for the field from all existing values in that field (eg home work tiddlywiki domains)

I am keen to add to this a view field definition and more.

I suppose I am building the framework in this case. However I believe the framework should be in the core with some common field definitions and users can define new ones or change the existing ones.

The plugin approach is appropriate now because when you make fields a 1st class citizen you need to provision features to handle the different types of data in fields. I have made around 2 dozen macros to support this, many of which which can be used standalone.

What are "the new build-in functionalities" you mention? Do you mean the plugins to do this before any move to core?

Regards

Tony

Regards

Tony

[TonyM]

Ah Perhaps you mean the HTML Input definitions

I did not realise they had a date picker etc... available in TiddlyWiki including rudimentary validation. The values are available in the session but can we get them into TiddlyWiki fields and values without a widget?

Or What if we re-wrote edit-text widget to edit-field widget and we could use it like this?

<$edit-field tiddler="test" field="date" tag="date"/> with each of the input tags?

Most of the handling is already in html.

Regards

Tony