Announcing TiddlyWiki 5.0.7-beta

[Jeremy Ruston]

TiddlyWiki 5.0.7-beta has just been released at:

http://tiddlywiki.com/

Particular thanks to Mario Pietsch, Stephan Hradek and João Bolila for their GitHub contributions to this release. And thanks to everyone whose feedback here has helped to shape and improve this release.

This release improves the documentation documentation:

* A new video tutorial: TiddlyWiki on Firefox for Android Video

* A first pass at TiddlyWiki Coding Style Guidelines

* Added an explanation of TemplateTiddlers

* Added documentation for saving on a custom PHP server

* Added documentation for TextWidget

* Summary of the approach for Naming of System Tiddlers

New features for 5.0.7

* Added support for importing encrypted TiddlyWiki documents

* Added several new filter operators, including reverse, first, last, butlast, rest, nth

* Extend list filter operator to allow other fields to be used via a TextReference

* Added emacs and vim keymapping support to the CodeMirror plugin

* Added the highlight.js syntax highlighting plugin: http://tiddlywiki.com/highlightdemo.html

* Added the first export option to the Tools tab of the control panel

* Added an ellipsis for advanced search next to the search box in the sidebar

Bug fixes include:

* Fixed problem with default format of ViewWidget substituting seconds for minutes in displayed times

* Fixed problem that was causing several animations to fail in Safari

* Fixed problem with unclickable sidebar under the Centralised theme

* Fixed problem with non-system tiddlers showing up in system tiddler advanced search

* Fixed problem with notifications not always disappearing in Firefox

As ever, exercise caution when using TiddlyWiki5, and take care to protect your data. Any feedback, questions, issues are welcome here or on GitHub.

Best wishes

Jeremy

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Danielo Rodríguez]

Awesome!!!

I was waiting for this so much!

I will try it out.

Is any incompatibility expected? 

The new filter operands are from the Stephan widgets?

Thank you very much for this awesome work.

[Danielo Rodríguez]

Ok, first issue here:

If I drop this tiddler on TW5.0.7 I get a Javascript Internal error error.

It has the tags $:/tags/stylesheet and topmenu. The title is: $:/stylesheet/topmenu

This is the content.

``` /* STYLES FOR A TOP MENU WITH TOOLBAR BUTTONS */ /* + STYLES FOR OTHER TOOLBARS */ /* DISTINCTION BETWEEN MOBILE MEDIA & STANDARD MEDIA */ /* MOBILE MEDIA MAX. 770px */ @media (max-width: 770px) { html .sidebar-header { padding : 42px 0 0 15px; } /* TOP MENU */ html .tw-topmenu { padding : 0 15px; } } /* STANDARD MEDIA MIN. 770px */ @media (min-width: 770px) { /* TOP MENU */ html .tw-topmenu { padding : 0px 42px; } } /* TOP MENU, FIXED IN POSITION */ html .tw-topmenu { background : #EFEFEF !important; /* as background */ height : 45px; margin : 0; position : fixed; top : 0; left : 0; width : 100%; z-index : 99; } /* TOP MENU CLEARANCE */ /* TO AVOID THE TOP MENU OBSCURES PART OF TIDDLERS */ /* transform : translate(0px, 56px); for standard buttons ViewToolbar */ /* transform : translate(0px, 51px); for small buttons ViewToolbar above title */ /* transform : translate(0px, 44px); idem + smaller title 0.9em */ /* these are just indications; adjust for aligning Wiki title - tiddler title */ html .story-river { padding-top : 0px; transform : translate(0px, 44px); /* Firefox */ -ms-transform : translate(0px, 44px); /* IE 9 */ -webkit-transform : translate(0px, 44px); /* Safari and Chrome */ } /* PADDING TIDDLERS */ /* no top padding in case of small buttons in ViewToolbar */ html .tw-tiddler-frame { padding : 0px 32px 32px 32px; } /* FLOAT RIGHT */ /* PUSHES THE TOGGLE BUTTONS TO THE RIGHT OF THE TOP MENU */ .floatright { float : right; } /* TIDDLER BUTTONS: VIEWTOOLBAR, EDITTOOLBAR */ html .tw-tiddler-controls button svg { height : 0.5em; } /* DISTANCE BETWEEN BUTTONS */ /* Firefox margin: 0px 0px 0px 0px; */ /* Chrome margin: 0px 0px 0px 10px; */ /* adjust to your liking */ html .tw-tiddler-controls button { margin : 0px 0px 0px 5px; } /* TITLE - TOOLBAR SPACING VIEWTEMPLATE */ html .tw-tiddler-title-space { font-size : 1.4em; line-height : 1em; } /* DISPLAY IN 3 COLUMNS */ /* for List all tags */ .threecolumns { display : block; column-count : 3; -moz-column-count : 3; -webkit-column-count: 3; } /* HELP TABLE */ /* styles the Help menu */ html .help-table { font-size: 0.9em; background-color : #EEF4FD !important; /* as background */ } /* SCALE SVG IMAGES IN HELP TABLE' */ html .tw-images svg { height : 1.1em; } ```

A bit sad since I really wanted the Highlight feature. 

[Danielo Rodríguez]

This is the exact error (sorry for posting so much)

Internal JavaScript Error

Well, this is embarrassing. It is recommended that you restart TiddlyWiki by refreshing your browser

Uncaught TypeError: Array.prototype.map called on null or undefined

El domingo, 26 de enero de 2014 22:20:36 UTC+1, Jeremy Ruston escribió:

[João Bolila]

please try to put the begin of the block and the end of the block in
separate lines:

```
<content>
```

it is also possible specify the language of the block, in this case css:

```css
<content>
```

the plugin works with codeblocks not with codeinline.

(I think highlightjs don't support sass or less, for that you need the
lesscss.org)


regards,

jb

> --
> You received this message because you are subscribed to the Google
> Groups "TiddlyWiki" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to tiddlywiki+...@googlegroups.com.
> To post to this group, send email to tiddl...@googlegroups.com.
> Visit this group at http://groups.google.com/group/tiddlywiki.
> For more options, visit https://groups.google.com/groups/opt_out.

--
PGP: 0xD39BB7C9
853F 9D17 E5F9 2EE0 50C4 B276 6B5A F53C D39B B7C9

[Danielo Rodríguez]

Thank you João.

The code is between ``` and ``` and the error still raising.

the plugin works with codeblocks not with codeinline.

(I think highlightjs don't support sass or less, for that you need the
lesscss.org)

Sorry, but I don't understand this part. Do you mean that I have to install the codeblocks plugin?. What is less ? some kind css syntax?

Thank you for answering.

[Danielo Rodríguez]

Ok, I find the problem

The problem was having the css between ```. 

With normal CSS code the error doesn't raise. So... when appears the problem? It appears when you have some css code between ``` and you tag it as $:/tags/stylesheet. The problem appears even while you are editing the tiddler. In the moment you tag it. Maybe it's some kind of interaction between the plugin and the core.

I made several test and every time the behavior is the same.

El domingo, 26 de enero de 2014 22:20:36 UTC+1, Jeremy Ruston escribió:

[Jeremy Ruston]

If the behaviour has changed between 5.0.6 and 5.0.7 this sounds like a bug, so I'd like to be able to reproduce it.

I tried the following:

1. Opened tiddlywiki.com/empty.html

2. Opened http://tw5toolbar.tiddlyspot.com/ and located the system tiddler $:/stylesheet/topmenu

3. Dragged the topmenu stylesheet from the tw5toolbar window into the empty.html window

Did you do something different?

Many thanks,

Jeremy

[TheDiveO]

On Sunday, January 26, 2014 10:20:36 PM UTC+1, Jeremy Ruston wrote:

New features for 5.0.7

* Extend list filter operator to allow other fields to be used via a TextReference

I've tried to find out whether this would solve the "iterating over a list of tiddlers" given in a field problem I have ... but I couldn't find an answer or further documentation about this feature in the 5.0.7 beta documentation. Maybe someone in this group can help me understanding what the aforementioned new feature is about and how it is being used correctly?

[Stephan Hradek]

Should work like this: Instead of "list[TheTiddlerWithAlistField]" use "list[ATiddlerWith!!a_list_field]". In the first case the tiddler has to have a field called "list", in the second case a field called "a_list_field" which is then interpreted as a list.

So "list[tiddler]" (old form) is the same as "list[tiddler!!list]" (new form).

[TheDiveO]

Hmm, this is what I expected it to be; but I can't get my render tiddler working. I've the following stored in my renderRFC tiddler:

<$list filter="[list[!!rfc-updated-by]]" >RFC&nbsp;<$view field="title" /> </$list>

The tiddler I'm rendering has a field named rfc-updated-by, set to "777 888". But the list widget call as specified above doesn't seem to match anything. I would have expected it to render "RFC 777" and "RFC 888" though. What am I doing wrong or what am I missing here?

[Stephan Hradek]

May I have a link please so that I can test?

Additionally I'd put "is[current]" before the "list…".

[TheDiveO]

That'll take some time as I need to strip out any information and put it on my Google Drive.

[TheDiveO]

Can it be a problem that the list is in form of "777 888", whereas the tiddler titles are RFC 777 and RFC 888, and my macros then assemble the full title for linking. Does the "list" operator run into any problems when iterating over non-existant tiddler titles?

[Stephan Hradek]

Am Montag, 27. Januar 2014 14:46:31 UTC+1 schrieb TheDiveO:

Can it be a problem that the list is in form of "777 888", whereas the tiddler titles are RFC 777 and RFC 888, and my macros then assemble the full title for linking. Does the "list" operator run into any problems when iterating over non-existant tiddler titles?

If should start wild guessing: Both shouldn't be too much an issue.

[Stephan Hradek]

Okay… it IS a problem.

list filters. So you can not iterate over lists.

[Stephan Hradek]

Could this solve your issue?

\define updatefilter()
[tag[RFC]list[$(RFC)$!!rfc-updated-by]]
\end

<$list filter="[tag[RFC]]">
!! <$link><$view field="title"/></$link>
<$set name="RFC" value={{!!title}}>
<$list filter=<<updatefilter>>><$view field="title"/></$list>
</$set>
</$list>

Here I assume that we have for example these tiddlers:

1. tiddler titled "RFC 888"
2. tiddler titled "RFC 777" with a field "rfc-updated-by" with content "[[RFC 888]]"

[TheDiveO]

*Slap* Now do I (seem to) understand! I have to admit that I had to reread your reply a few times until my internal semantic parser actually managed to lock onto its meaning though. In TWC we had the "FET" (still thinking of transistors whenever I encouter this acronym) ... anything related to a FET available in TW5 without having to resort to JavaScript?

What I could do is to change the field rfc-updated-by "777 888" to "[[RFC 777]] [[RFC 888]]" and then rewriting the filter as "[tag[RFC]list[!!rfc-updated-by]" ... but the ugly downside is that this won't include those RFCs in the list but not yet currently with a tiddler. Not exactly what I need.

[Stephan Hradek]

When you change the rfc-updated-by field as you wrote, why not simply use:

<$transclude field="rfc-updated-by"/>

[Ton Gerner]

Hi Danielo,

Today I upgraded all my guides mentioned at [1] to 5.0.7beta without any problem (drag & drop to an empty.html of 5.0.7beta).
Using Windows 7 64-bit and Firefox v26/Chrome v32
That means I am still using all CSS styles in my stylesheets within 'triple backticks' without any problem.
The stylesheet you mention is used in my guide about a top menu and toolbars [2].

Cheers,

Ton

[1] http://tongerner.tiddlyspot.com/
[2] http://tw5toolbar.tiddlyspot.com/

[TheDiveO]

cross posting :) As far as I understand your suggestion, it is similar to what I just posted (albeit something more to learn for me). However, it would suffer from the same problem that if the list contains RFCs for which no tiddler exists yet,

[Jeremy Ruston]

I've discovered a bug with the list filter in 5.0.7:

https://github.com/Jermolene/TiddlyWiki5/commit/70ed6e6ad325f602193582d9141ddee942ac28be

The bug means that the list filter cannot omit the tiddler title and have it default to the current tiddler.

So, this works in 5.0.7: [list[HelloThere!!field]]

But not this: [list[!!field]]

Best wishes

Jeremy.

On Mon, Jan 27, 2014 at 3:23 PM, TheDiveO <harald....@gmx.net> wrote:

cross posting :) As far as I understand your suggestion, it is similar to what I just posted (albeit something more to learn for me). However, it would suffer from the same problem that if the list contains RFCs for which no tiddler exists yet,

[Stephan Hradek]

Am Montag, 27. Januar 2014 16:23:44 UTC+1 schrieb TheDiveO:

cross posting :) As far as I understand your suggestion, it is similar to what I just posted (albeit something more to learn for me). However, it would suffer from the same problem that if the list contains RFCs for which no tiddler exists yet,

Did you see my other post?

[Danielo Rodríguez]

Hello Jeremy,

This bug only appears when you have the highlight plugin installed. I thought that I wrote it. Sorry for the misunderstanding. Did you read how I fixed it? The problem is having the CSS code between ```.

Regards

[Jeremy Ruston]

This bug only appears when you have the highlight plugin installed. I thought that I wrote it. Sorry for the misunderstanding. Did you read how I fixed it? The problem is having the CSS code between ```.

Ah, OK, that's very helpful, thank you Danielo!

Best wishes

Jeremy

[Jeremy Ruston]

Hi Danielo

On Mon, Jan 27, 2014 at 4:51 PM, Jeremy Ruston <jeremy...@gmail.com> wrote:

This bug only appears when you have the highlight plugin installed. I thought that I wrote it. Sorry for the misunderstanding. Did you read how I fixed it? The problem is having the CSS code between ```.

Ah, OK, that's very helpful, thank you Danielo!

Fixed for 5.0.8 here:

https://github.com/Jermolene/TiddlyWiki5/commit/5d3dda1a1721af05e56e301a8b896e53f9868540

Best wishes

Jeremy

[Danielo Rodríguez]

Hello Jeremy, glad to hear that. Anyway, the workaround that I described fixes the problem.

I read that ticket, and I don't understand the description at all :

Fix problem with highlighting only working in the DOM

The current implementation of the highlight plugin only works properly in the browser, and doesn’t work under Node.js.

Does that include tiddlyDesktop and node webkit? Because it is working for me on those.
Regards.

[Jeremy Ruston]

Hi Danielo

On Mon, Jan 27, 2014 at 5:37 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:

Hello Jeremy, glad to hear that. Anyway, the workaround that I described fixes the problem.

I read that ticket, and I don't understand the description at all :

Fix problem with highlighting only working in the DOM

The current implementation of the highlight plugin only works properly in the browser, and doesn’t work under Node.js.

Does that include tiddlyDesktop and node webkit? Because it is working for me on those.

TiddlyDesktop runs TiddlyWiki5 as though it were a browser, which is why the highlight plugin works OK there.

Best wishes

Jeremy

[PMario]

On Monday, January 27, 2014 3:41:06 PM UTC+1, Ton Gerner wrote:

That means I am still using all CSS styles in my stylesheets within 'triple backticks' without any problem.
The stylesheet you mention is used in my guide about a top menu and toolbars [2].

Hi Ton,
If you want to display the stylesheet tiddler as text, just use

   type: text/css

You may need to type it by hand, since the dropdown doesn't know it.

So you don't need to use "non CSS markup in your tiddler". It may fail with weired errors in the future. Such errors are very hard to track down, after 1 year or 2 :/

There is a second thing I just saw in the style sheets. If !important is really needed, then imo the base theme concept is broken because !important is viral. So everyone else that want's to modify your theme, will need important keyword too. So if there are 2 more iterations you'll end up having !important all over the places.  .... I'll need to investigate, to be sure.

-mario

[Ton Gerner]

Hi Mario,

Thanks for the comments.
I had not thought about the text/css type.
The !important is a left-over from old days (alpha10 or so). I'll look into that.

Cheers,

Ton

[Danielo Rodríguez]

Hi Ton,

Did you tried with the highlight plugin installed? I told it several times, this only occurs with that plugin. Just give it a try and let me know ;)
Regards

AD:your tutorials are very helpful, Thank you very much

[Jeremy Ruston]

You should only store stylesheets as text/css if they don't contain any TW5 macros or transclusions. If you use transclusions and macros (like the stylesheets in the core themes), then it is perfectly OK to use triple backticks to mark sections that you want to exclude from wikification.

Best wishes

Jeremy

[Ton Gerner]

Hi Jeremy,

On Monday, January 27, 2014 8:49:32 PM UTC+1, Jeremy Ruston wrote:

You should only store stylesheets as text/css if they don't contain any TW5 macros or transclusions. If you use transclusions and macros (like the stylesheets in the core themes), then it is perfectly OK to use triple backticks to mark sections that you want to exclude from wikification.

 

OK, I didn't know and had no problems with triple backticks.

Anyhow, it looks far better with triple backticks (more readable) than when I change it to txt/css, see atttachments (in edit mode it looks fine).

Is there another possibility to show it like code shows?

If it is needed to change to txt/css it will be handy if:

1) txt/css is in the list of types
2) there is a note in the documentation (searching for stylesheet gives only something about the tag $:/tags/stylesheet)

Cheers,

Ton
 

[Ton Gerner]

Hi Danielo,

I didn't try the highlight plugin, but the problem is known by Jeremy.

Glad to hear the tutorials are helpful.

Cheers,

Ton

[Ton Gerner]

Hi Jeremy,

Is it allowed to use <pre>...</pre> around the styles in the stylesheet while using txt/css as type?

Cheers,

Ton

[Jeremy Ruston]

Hi Ton

Is it allowed to use <pre>...</pre> around the styles in the stylesheet while using txt/css as type?

No, you can't insert <pre> within the text of text/css tiddlers because the text within the tiddler is not subject to wiki processing. But the entire tiddler will be displayed in <pre> tags anyhow, because it's a text tiddler.

Best wishes

Jeremy.

[Ton Gerner]

Hi Jeremy,

A little bit confusing, partly my fault.

I entered txt/css instead of text/css which gave "unreadable" styles, like when there is no type at all.

But text/css is not in the list of type to be selected. Mario said: Add it manually.
But there is a Plain text (text/plain) entry in the type list which gives the same result.
Both text/css and text/plain do show the styles in "readable" form.

Is there a difference in types between text/css and text/plain?
If there is no difference, change the type to "Plain text (text/css)" That will be less confusing.

Cheers,

Ton

[Jeremy Ruston]

Hi Ton

But text/css is not in the list of type to be selected. Mario said: Add it manually.
But there is a Plain text (text/plain) entry in the type list which gives the same result.

I've added text/css for 5.0.8

 

Both text/css and text/plain do show the styles in "readable" form.

Is there a difference in types between text/css and text/plain?

At the moment they'll both be displayed the same, and the stylesheet mechanism will render both the same. But text/css would be a clearer way to mark intention.

Best wishes

Jeremy

[Danielo Rodríguez]

Hello Jeremy,

About the new TW5 features:
  In my opinion most of them are well Hidden. For example, the highlight plugin is only mentioned in the 5.0.7 Beta tiddler, which is not part of the default ones. Maybe people doesn't expect a wiki to have such feature, but they will use it if it is available. I don't know if I'm explaining well my point.
  I'm following the development of TW and I have the feeling that I'm missing something.
This remembers me to google-apps-scripts and google docs. There are lot of awesome possibilities, but people don't know about it. You have to dig into forums because the documentation is short and developer oriented  and does not reflects all the possibilities.
  What I mean is: TW need more publicity about its possibilities.

Regards

[Stephan Hradek]

Am Mittwoch, 29. Januar 2014 00:34:45 UTC+1 schrieb Danielo Rodríguez:

  What I mean is: TW need more publicity about its possibilities.

Can you provide text changes and addittions to be put into TW's documentation to make the power more visible?

I think any improvement in documentation anyone here can provide will be more than welcome.

[Danielo Rodríguez]

Sure! As a good start point I could include highlight in the features tiddler.
Tiddlywiky can highlight snippets of code thanks to higliting plugin. And a link to the example page.