raw view macro

[psd]

In RippleRap?, we use a "raw" mode to the "view text" macro to display HTML imported from the Flickr RSS feed as-is:

<pre>{{blog_item{<<view text raw>>}}}</pre>

 http://svn.tiddlywiki.org/Trunk/contributors/PaulDowney/plugins/RawViewMacroPlugin.js

config.macros.view.views.raw = function(value,place,params,wikifier,paramString,tiddler) {
                createTiddlyElement(place,"span",null,null).innerHTML = value;
        };

There may be a better name for the view than "raw", but it does seem like a worthy addition to the core.

[EricShulman]

Without any extra param (other than the fieldname, of course), the view macro shows the value "as-is" (in other words, as plain, unparsed *text*)

<<view fieldname>>

If you add the "wikified" keyword, it parses and renders the value as TW wiki-syntax content:

<<view fieldname wikified>>

I would suggest using a keyword of "html" to parse and render the text as HTML content:

<<view fieldname html>>

[FND]

N.B.: using DIV instead of SPAN

[EricShulman]

I recommend using a SPAN instead of a DIV. Otherwise, there is no way to use the <<view fieldname html>> syntax to insert content inline since DIV will always force a linebreak.

[FND]

I understand the issue here, but I still think that using a SPAN is problematic (block elements within an inline element). Nevertheless, I would understand if SPAN were chosen over DIV in order not to confuse users.

[EricShulman]

Block elements occur within inline elements all the time! If a block element occurs, a newline is started... if no block element, then no forced newline. Consider the following TW usage:

before <<view fieldname html>> after

if the html contained in fieldname does not use any block elements (let's say it's just an <a href="..."> element), then the result might appear, all on one line, as:

before  http://www.example.com/ after

Now, consider if the html consists of "some text" followed by a small table, and then "some more text". Then the result would be:

before some text

Cell 1	Cell 2	Cell 3
Cell 4	Cell 5	Cell 6

some more text after

Lastly, if the author *wants* the HTML to occur on a separate line, they can always explicitly enter the content as:

before
<<view fieldname html>>
after

or even

before {{block{<<view fieldname html}}} after

where 'block' is a custom CSS classname defined as:

.block { display:block; }

resulting in:

before
some text

Cell 1	Cell 2	Cell 3
Cell 4	Cell 5	Cell 6

some more text
after

Thus, using a SPAN within the macro handler gives greater flexibility in formatting, but does not prevent the use of a DIV if one is desired.

[FND]

According to the  specs, inline elements should "contain only data and other inline elements".

However, as stated above, convenience might override correctness in this case.

Another option would be to use a DIV with a class like "rawContainer" defining display: inline;.

If further discussion is required, we should probably move this to [twdev].

[MartinBudden]

Milestone 2.6.2 deleted

[MartinBudden]

Functionality can be added as a plugin by those who require it. Not a core feature, especially since the DIV/SPAN issue not resolved.