Announcing TiddlyWiki 2.6.0 Beta 1

[FND]

We are pleased to announce the first beta of TiddlyWiki 2.6.0:
http://www.tiddlywiki.com/beta/

This release includes a variety of bugfixes and enhancements. The most
obvious changes are:
* Added WindowTitle shadow tiddler
* Added creator tiddler field
* Upgraded to jQuery 1.4.2

For the full list of changes see http://trac.tiddlywiki.org/wiki/History

As usual, help testing this release would be greatly appreciated, please
leave any feedback here. Conversely, this is a beta release, so exercise
caution before entrusting it with irreplaceable data.

Many thanks to all the contributors.

-- F.

[AlanBCohen]

*WindowTitle tiddler looks like it is just a redirection layer,
calling the SiteTitle and SiteSubtitle tiddlers.
*Has the TiddleySaver file changed between 2.5.3 and 2.6.0b1?
*What is the purpose of the creator field, as opposed to the existing
modifier field? Are you planning to add this to the default
ViewTemplate?
*Does the JQuery upgrade mean anything to end-users?

[Eric Shulman]

> *WindowTitle tiddler looks like it is just a redirection layer,
> calling the SiteTitle and SiteSubtitle tiddlers.

The *default* for the title is the same as before...
however, the shadow [[WindowTitle]] makes it *much* easier to
customize the content/format of the titlebar, so that it can be
different from the SiteTitle/SiteSubtitle default combination.

> *What is the purpose of the creator field, as opposed to the existing
> modifier field? Are you planning to add this to the default
> ViewTemplate?

The creator field is stored *once*, when a tiddler is first created.
The modifier field is updated every time the tiddler is re-written.
For some use-cases, especially shared and/or server-based documents,
the distinction between the creator and modifier of a tiddler can be
significant for tracking, notification, and version control handling.

enjoy,
-e

[twgrp]

Considering the emphasis on microkernel and the fact that TW not is
very suitable for multiple collaborators (and even officially named "a
personal notebook") I'm wondering why even bother with creator or
modifier. It clutters and IMO it seems more suitable as a plugin? And,
if in a plugin, an option to put this and perhaps even the date
information as field data...

[Eric Shulman]

> Considering the emphasis on microkernel and the fact that TW not is
> very suitable for multiple collaborators (and even officially named "a
> personal notebook") I'm wondering why even bother with creator or
> modifier.

The 'modifier' field has *always* been included in the TW core data,
and the 'creator' field was first implemented as a
TiddlyTools' [[CoreTweaks]] plugin, in direct response to several
requests from the community for the feature, in order to support real-
world use cases.

Although TW is quite obviously well-suited for individuals, many
scenarios involve a single file being copied, shared, edited and
merged amongst a small group of people. Just because a document is
self-contained and edited locally by one person, does not mean that it
will never be shared or edited by others at some point in the future.
In addition, you can import/export individual tiddlers into other
documents, so that a single document may include tiddler content
edited by several people, even if that document is only ever directly
modified by one 'owner'.

Also, there are server-side adaptations of TiddlyWiki, such as
http://www.TiddlyWeb.com, which provide robust remote storage
mechanisms, with support for multiple users, permissions, revision
tracking, etc. All of these features depend heavily on being able to
track both the creator and last modifier information reliably.

> It clutters and IMO it seems more suitable as
> a plugin? And, if in a plugin, an option to put this
> and perhaps even the date information as
> field data...

Obviously, the creator field *can* be implemented as a plugin using
custom field data, since that is how it originated. However, by
placing this very small piece of code into the TW core, it ensures
that *all* new TW documents will properly support these fields in a
standard manner, so that even if a document is not directly shared or
hosted on a server, any tiddlers that are exported from those
documents can be tracked by both creator and last modifier.

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[overett1]

On Mar 11, 4:01 pm, FND <F...@gmx.net> wrote:
> This release includes a variety of bugfixes and enhancements.

Would it be possible to add support for excludeLists to the tagging
macro as well? I have a number of tiddlers that have no content but
each contain a list of unique tags in order to create a 'master list'
of tags in combination with the IntelliTagger plugin. I'd like to tag
these tiddlers with 'excludeLists' so that they do not appear in the
tagging list of a tiddler.

Thanks

Jonathan

[Martin Budden]

If you want to remove visual clutter you can edit the ViewTemplate
shadow tiddler. You can remove items from the line containing
class='subtitle', or indeed you can remove this entire line.

Martin

[Martin Budden]

Jonathan,

I'll look into the possibility of applying excludeLists to the tagging
macro.

Martin

[FND]

> *Has the TiddleySaver file changed between 2.5.3 and 2.6.0b1?

Yes; it has been signed with the new UnaMesa certificate.

> *Does the JQuery upgrade mean anything to end-users?

jQuery 1.4 comes with significant performance enhancements. Apart from
that, as usual the benefits of jQuery mostly come to end-users
indirectly via plugins, as developers make use of the functionality.

-- F.