Add a new parameter to the bin/view script, to show metadata in raw mode.

Then in the "More" dialog, one can offer the option to show metadata, as in:

• View previous topic revision:
  • Revision:

    in raw text format, and show metadata

  • Revisions: 1.1 ... 1.20

Implementation: in bin/view, add after the line 79:

    my $skin = ...

    if ($query->param( "meta" )) { $viewRaw = "debug"; }

Patch attached.

-- ColasNahaboo - 25 Feb 2003

Colas,

How does this differ from ?raw=debug, or the patch described in RawViewWithMetaData ?

-- TWikiGuest - 15 Jun 2003

Arg... it seems you are right, no need for my patch, ?raw=debug does the trick.

I think what happenned (but I may be wrong, from memory here), is that in previous releases ?raw=debug didnt convert tabs to 3 spaces, confusing users. So I forgot to check that it was still the case in the new version, and I just updated my patch...

So my patch is not needed anymore (if it was ever needed, I am not quite sure now)...

(removing the TWiki patch category)

-- ColasNahaboo - 16 Jun 2003

Ahhh.... I See what you mean. I haven't looked in detail at the raw=debug content. There's two options I suppose:

1. Dump the raw data file as it was stored on disk inside the textarea (this would mean that you have tabs instead of spaces)
2. Dump the data "raw" - ie looking as the user would normally edit, but include the META lines as well.

I'd personally expect 1, but that confused your users which means you wanted 2. (Which it sounds like it does currently.) I'll have a poke around. (I'm thinking of a non-external tools approach to DistributedTWiki again FWIW which is why the distinction matters to me)

-- TWikiGuest - 17 Jun 2003

I've checked this. Results:

• Beijing Release & twiki.org (alpha?) does 2 - that is the "raw" text sent to the client is the kind that they get in their edit box when they hit edit. This is not the same as the on disk storage format.
• Athens Release does 1 . ie the data that gets sent is the same as the data that is stored on disk - no modifications. Whilst 2 is probably better from a users perspective, I think 1 is a beneficial thing to have as well, and should be documented.

I'll look at your patch (and AthensRelease) and see if I can make a "I really mean raw " switch as well.

-- TWikiGuest - 17 Jun 2003

Well, in my case, I found 2 is the only useful option in practice. It is used by users that see a nice effect and want to see how it is done.. and copy and paste it (hence the importance of the 3 spaces). 1 is more used for debugging, but to debug TWiki you are already with an editor looking at the files directly anyways...

(BTW, this whole issue of tab/space is confusing... I would be in favor to store as 3 spaces in files also)

-- ColasNahaboo - 20 Jun 2003

I agree that in the general case behaviour 2 is more useful from an enduser perspective. If however you have behaviour 1, mirroring TWiki Content without any special code on the source Twiki server becomes possible. (ie mirroring a remote web when you don't have access to the server.)

-- TWikiGuest - 21 Jun 2003

I am assuming that raw=debug satisfies this requirement, and so its PathcNotSuitable (thought thats an un-necessarily devicive name for it).

We should use a different topic to work on a mechanism for mirroring.

-- SvenDowideit - 18 Apr 2004