Groundhog day: What about Cardo?

Hello Xrizzy,

I’ve made the requested change.

I do plan to make another update – I’m trying to remove ViewTemplate from the plugin and also switch to using the cascade-driven body filter. This may change nesting which could have an impact on CSS, though so far it’s looking like change are minor.

The ViewTemplate is overridden in at least three different plugins in the file! Which is a good reason to move away from overriding ViewTemplate if possible.

I’m pretty lousy with CSS. If it was me, we’d all be running MS-DOS programs :wink:

That’s great. I think I can fix the CSS and modernize the look & feel a little bit. Great that you look after the MS-DOS Programs ehm Tiddlywiki “Programs”. It would be great if we could make Cardo fit for the future this way.

When I create a new project I get the following:

When I look at the original, I see that same error. So it must be a long-standing problem (i.e., the upgrade isn’t what broke it.). Something else to sift out – somewhere in the edit templates.

I’m thinking there’s no reason to keep in the bits related to Google Analytics.

This is another version where I preview the changes as a plugin by itself before putting the plugin into the shareable version. I did not copiously update the notes like I should have. Maybe later. I’m starting the plugin at 1.0.10, in case there were some missing versions after 1.0.3. There are still some tiddlers overriding the core. Baby steps, right?

So mostly I would like some feedback that it appears to be basically working, or if there are some major omissions.

Thanks!

2 Likes

Hello all!

Xrizzy has set up a new home for us to continue the project collaboratively.

Visit https://cardo-revisited.tiddlyhost.com/

for the latest updates.

My own goal is to try to reduce the places where the code overrides the core so that it will be fairly easy to continue the project into the future. Also so that code can use the newer features of TiddlyWiki.com. For instance, pulling the stash of 4 key plugin/themes directly from the Cardo wiki itself, rather than having to maintain an offsite source. Or using drag and drop to re-arrange tiddlers.

So far we seem to have fixed the recursion problems (knock on silicon) and I haven’t personally encountered a RSOE, but maybe I haven’t tried hard enough.

Xrizzy can speak for herself, but I think she’s hoping to give it all a more modern look, whereas I think the Windows 95 look is pretty avant-garde.

2 Likes

I see the text \parameters (size:"22pt", stroke:"none", stroke-width:"0") visible in multiple tiddlers. In view mode.

That is my mess. :blush: I changed the buttons to Lucide Icons — Lucide v0.515.0 which needs of course the plugin installed.

It’s not that. I am getting it too when editing tasks. Something about the calendar. The pick a date is gone. :thinking:

It’s the parameter line at the top of the new images. The pickaday calendar (and actually even the $image widget) doesn’t know how to handle that. I don’t know if this will work with what you have in mind, but I think you could remove the parameter line and hard code the values down in the SVG.

Or maybe @pmario might have an idea how those icons could be used with pickaday and/or the image widget.

Ok, so removing the parameter line (but then hand-coding the values into the SVG) does work.

But I guess the image widget doesn’t understand SVG at all. Or maybe it has to be formatted differently.

1 Like

Got an error message:

This is actually the same error from 2022. I applied the patch. This takes care of the RSOE, I hope.

The thing is, when I look at the code, there seem to be mis-matches between definitions and calls, so I’m puzzled how it works. It might be that it only looks like it’s working, because there’s only 1 person on the “team”. Possibly most people don’t have large projects with multiple people assigned. Well, I’m sure if there’s a problem someone will spot it.

1 Like

Thank you @Mark_S. This project would go nowhere without you. :mage:t2:

I wondered why David had that multiple dashboards in there. :thinking: Maybe Moms appreciate it?

I am planning on using it with my 2 sisters (We are sharing one TW). Does anybody else use it?

That’s what I wonder. Or maybe it’s too big of a project for everyone to have used it exhaustively. For instance, in the book template I see:

\define loadnedToState() $:/temp/$(currentTiddler)$/loanedto

and down below where it is invoked

<$action-setfield $tiddler=<<loanedToState>> $field="text"/>

Anyone using this would (eventually) notice something was wrong.

But maybe extending GTD to cover book reviews is pushing things a bit far?

1 Like

As I am not the one able to fix that it is probably asking too much (?) but as a book lover that’s exactly what I would love to have. So far I did not use it though. :thinking:

It’s about mission creep. Like there is an endless procession of things people might want to collect – books, recipes, music, receipts, cats, doorknobs. But do they have anything to do with Getting Things Done ™ ?

It seems like there might be a demand for a collection maker TW edition. Like you just change configuration files and then you have a recipe tracker, or whatever else you want to track.

That is great idea. :smiley:

Right.

An instance. For me the recipe for correctly mixing concrete to fix the bathroom subsidence is not (logically) different than that for the pilau rice recipe to satiate the family. Collect my approach: collect first, categorize later.

Don’t get those recipes mixed up – Remember Lot’s Wife!

It looks like we’re getting a 404 at https://dyumnin.com/Cardo.html ??

I didn’t have the presence of mind to download a copy, which I use for reference. Like, “Did we create this problem or was it already there?”