String.encodeTiddlyLink() encloses tiddler titles in brackets only when they contain a space. However, tiddler titles can be non-WikiWords? without containing a space (e.g. "foo"), resulting in those not being encoded as links.

Therefore, this method should always enclose the respective title in brackets (note that this does not have any negative effects on WikiWords?).

By default, this should be a very simple implementation; tiddlers containing the respective search term in the title take precedence over matches in the tiddler body.

The attached patch adds configuration options for three different date formats, tentatively called timestamp, shortDate and longDate and using ISO 8601-style date formats by default.

These are used in the default ViewTemplate? (as evaluated parameters) as well as in the Timeline and NewJournal? macros.

This enables users to globally define their date formats without the need to modify any shadow tiddlers.

Note:
In the original discussion, the use of tiddler slices was suggested. However, this proved to be impractical.

The attached patch provides a function to check whether a tiddler exists (either as regular or shadow tiddler) in the given store. Accordingly, the patch refactors existing code to make use of this new function.

(original isTiddler() code courtesy of Saq)

Extend the <<toolbar>> macro parameters syntax to permit use of "|" as separators between item groups:

merge(config.macros.toolbar,{
	separator: "|"
	});

config.macros.toolbar.handler = function(place,macroName,params,wikifier,paramString,tiddler)
{
...
		switch(c) {
			case '|':  
			case '!':  // (alternative for use in ToolbarCommands slices)
				createTiddlyText(place,this.separator);
				break;
			case '>':
...

As discussed here, the SiteUrl? shadow tiddler should display the current document location (rather than a hardcoded link to http://www.tiddlywiki.com).

With this link any TiddlyWiki document could easily be downloaded from within the document itself.

The attached patch adds a parameter for customizing the search macro's access key.

When a search returns only a single result, the resulting message still uses plural: "1 tiddlers found matching %1"

A plugin should be able to define a list of other plugins it depends on.

If these plugins are not yet installed TiddlyWiki should try to automatically install them (possible after asking the user for confirmation).

The necessary information may be included in MetaData? or Embedded Data (TW 2.1+)

The goal is to refactor the file I/O code to make it easier to re-use.

TiddlyWiki ships with FileSystem? modules for Internet Explorer, Firefox, Safari and Opera/Java that implement file saving and loading, and a set of UTF-8 conversion functions. There's a thin abstraction layer that does some really simple (and not particularly extensible) sniffing to figure out the prevailing FileSystem? type.

The main driver for the work is the way that the current implementation doesn't attempt to hide a fundamental issue with the Internet Explorer implementation, based on the FileSystem? !ActiveX object. It utterly fails to understand UTF-8 when reading a file, and instead sees each byte as an ANSI character. The JavaScript glue around the !ActiveX object dutifully converts the ANSI characters to their equivalent Unicode characters which for all but the core 96 or so ASCII characters will be pretty meaningless. (Note in particular that the Unicode equivalent may not have the same code as the ANSI original). The trick that TiddlyWiki uses is that the FileSystem? object does precisely the opposite thing when saving - from a UTF-8 perspective, it converts the Unicode characters back to their equivalent ANSI codes and writes them out, in the process assembling the original UTF-8 byte sequence.

A further complication is that attempting to save an arbitrary Unicode JavaScript string is tricky. Internet Explorer's FileSystem? object will complain if it sees any Unicode characters that don't map to an ANSII equivalent, so you have to use an HTML or JavaScript Unicode escaping mechanism to express non-ANSI Unicode characters (eg \u2345).

Other goals are:

• to do the FileSystem? sniffing better, particularly to give better error messages when users attempt to save a TiddlyWiki that was loaded over http:
• to incorporate the logic for parsing file:/// URIs, including consistent handling for relative pathnames

If nothing else, the refactoring should result in better documentation about this peculiarity...

Creole is a common markup language to be used across different wikis. See:

http://www.wikicreole.org/wiki/Home

To extend the filter syntax for expressions used in methods such as TiddlyWiki.prototype.filterTiddlers(filter). The need is to be able to filter for tiddlers that are not tagged with a particular tag.

Suggested syntax: [tag[!bad tag]]

Overview of existing filter syntax here: http://tiddlywiki.org/index.php?title=Dev:FilterTiddlers

Overrides ticket #454: http://trac.tiddlywiki.org/ticket/454

This patch extends TiddlyWiki.prototype.filterTiddlers to support complex filter strings, where filter string are of the form:

filterStep | filterStep | ... // only one filterStep is required

where filterStep is of the form:

[filterElements]

where filterElements is one or more of the following:

[TiddlerName?] tag[TagName?] sort[SortField?] limit[NoOfResults?]

...so when you create a new project or action you don't have to always manually set the realm.

make sure that ccTiddly does not allow users to import tiddlers when they are not logged in.