Making configurable items
- Store filters, tiddler names etc… in $:/config/tiddlername tiddlers then transclude it to get the value into your code
- Just redefine a variable or macro to override an existing one
- TW 5.3.0 will even introduce the ability to override widgets and a lot more.
I will link to a related discussion here soon [edited] In the spirit of Open Dialogue - Avoiding the - Yet another Plugin?
Objects
It actually makes sense to consider tiddlers as objects and that is already what they are in many ways, but it all of course depends on what you mean by object.
- When writing solutions on tiddlywiki I incidentally use the fields system-object (eg viewTemplate) and object-type (eg contact, project) to define what tiddlers are.
- If you are thinking about objects as “Object oriented programming” I believe most of the features “abstraction, inheritance, encapsulation, and polymorphism” or “methods and properties” can be emulated in one or more ways.
- This only issue may be when something is triggered when you want to modify the tiddler store. But there are good tricks to help.
- An outline of OO
Arrays?
- JSON scan store arrays
- List, title lists, variables, list fields and sets are all quite interchangeable with arrays
- The set widgets “select” is an “optional zero-based index of the item to return from the filter output”
- Data tiddlers using the index parameter on a number of widgets also can act as an array.
- We are all born naïve about numerous subjects. We don’t inherit TiddlyWiki skills.
- Fortunately if you can ask a well phrased question we can help you here in the forum.
- You can either pass the whole list to the macro or the name of a macro, variable or reference to the list.
- Use the macrocall widget to call macros with more advanced parameters such as
param1=<<var1>> param2={{!!fieldname}} - Call a macro with a variable name and then use the getvariable Operator
Perhaps you could request something a little more specific.