Something I have raised a number of times but not received feedback on, is allowing the community to develop and agree to some ‘‘de facto’’ standards.
This would allow macros and plugins to be written to these standards such that they are interoperable with other published macros and plugins. To a large extent all that is required is;
- Agreed tiddler names
- Agreed tiddler formats
- Agreed Field names and functions
- A TiddlyWiki.com documentation tiddler or on a custom community wiki.
I intended to build MRU '‘Most Recently used’ features into some of my published solutions and tools.
- Each time you navigate to a tiddler capture the last navigated time, and count the number of visits.
- This allows the user to return to the most recently used or the most visited tiddler easily from a list.
I have also developed a strategy to enhance ‘‘copy to clipboard’’ functionality to include an “in wiki clipboard”, This would allow;
- In Wiki paste button(s)
- A paste box containing past copies
- TiddlyWiki aware copies such as title, titles, tag/tags, list, filter, field value
- from which you can select in context
- Ability to search the clipboard(s)
- A relationship to MRU above
Whilst I can see the above examples are easy to implement, what I am really interested in is setting up a process for the development and documentation of de facto standards we can all use and leverage together.
- Of note, it will be totaly ‘‘optional’’ if anyone makes use of these standards
- However if you do, your solution’s will gain function through interoperability and hackability.
Relationship to core?
- Such standards, being optional, need not be included in the core, thus permitting simpler and shorter adoption.
- Being optional and shared, more generic naming standards can be used without needing to name with qualifiers, and these will be documented to allow clashes to be identified, if not simply avoided.
- Solutions could reference the documented standard to which they have being written. Saving time, adding clarity and assisting modifications.
- Various common and best practice code snipets can be documented and shared this way.
- Existing solutions can be rewritten to use a new standard and gain interoperability.
What do you think?