create new tag
, view all tags
It would be useful to have an index of existing pages when editing, since sometimes it is not easy to remeber the name of a referred page. This should be quite easily done with templates and some javascript. Opinions?

-- FrancoBagnoli - 30 Sep 2000

Why not just add a hyperlink (with a target to make it a popup) to the edit template that refers to a search? Shouldn't require any programming work at all.

I tried this in edit.tmpl

<BR><A target=twikiindex 
 HREF="/cgi-bin/search/Codev/?scope=topic®ex=on&search=.*">View Topic Index</A>

-- AlWilliams - 30 Sep 2000

That is a nice idea. Here is a small improvement that omits the topic summaries:

<A target="webindex" href="%SCRIPTURLPATH%/search%SCRIPTSUFFIX%/%WEB%?scope=topic&regex=on&nosummary=on&search=\.*">View Topic Index</A>

As Franco pointed out, it is probably good to enhance it with some JavaScript (degrading gracefully) that opens a smaller window without the browser toolbar (and other window decoration). Anybody up to this task? Thinking of that, it would be nice to do SearchEnhancements with one new type: Show result as a bullet list of topic names only, without author and date.

-- PeterThoeny - 30 Sep 2000

As I pointed out in NewTemplateScheme, it would need different templates. In a few days I'll experiment along the folowing lines:

  • allow the choice of templates in the url (and in preferences, it's so easy)
  • provide a framed view with two or three panels
  • provide an "index" button in the frameless view that opens a new borderless window with a "file navigator".

However, if I remember well, a good "file navigator" (i.e. with the possibility of opening and closing webs) requires storing of information either in a coockie or in the parent frame.

-- FrancoBagnoli - 01 Oct 2000

Probably not as fancy as you had in mind, but here is the bottom of my edit.tmpl :

      <INPUT type="submit" value="   Preview Changes   "> <INPUT type="hidden" name="cmd" value="%CMD%">

function launchindex() {
document.write("<INPUT TYPE=button onClick='launchindex()' Value='Topic Index'>");
<A target=topicindex HREF='%SCRIPTURLPATH%/search%SCRIPTSUFFIX%/%WEB%/?scope=topic&regex=on&nosummary=on&search=.*\'>View Topic Index</A>


If no JavaScript, you get a link as before. The nosummary on my site doesn't work because I haven't gotten to adding that yet. Using launchindex instead of doing it inline saves on quote headaches.

-- AlWilliams - 02 Oct 2000

One possible solution is to have all edit sessions open up a new window.

I modified TWiki locally to generate the html text target="_blank" for any link that could lead to editing or creating a page. Some users here love it because they can browse around while in the middle of an edit. Other users hate it because they wind up with lots of windows open. YMMV.

This is somewhat related to BetterFileLocking.

-- JohnAltstadt - 17 Oct 2000

I changed the javascript to "left=600,width=600,height=700" in the javascript that opens the window at my location. That way on the 1024 or wider monitors that we all use, the list of topics only partially obscures the content being edited and the author (and sometimes date) is offscreen to the right since it is not necessary. I thought about creating another summary format that ommits the date and author completely, along with adding a "refresh" button. Sigh - another idea I don't have time to implement.

-- StanleyKnutson - 03 Jan 2001

This can be done now with TopicListAndWebListVariable

-- PeterThoeny - 08 Jun 2001

What about the following (hairbrained) idea.

For every non-defined Twiki word in a document, alternative Twiki words are displayed during preview in a select box. E.G. If I type IndexDuringEdit I will get a select box during preview formatted (something) like: ? is a bogus topic. The little linked ? is there to indicate that the top option in the list is non-existant.

The options in the box would be returned by a a topic or body search of all the available messages for the individual words that make up the non-defined Twiki word.

Changing the value in the box would also change the Twiki word in the document. When you clicked on save the form would be returned with the twiki words defined. This would also be nice for a save and re-edit button since it will post the form, change the saved text and force the browser to reload the saved text with the new twiki words.

This has implications is SavePreviewTextOnServer is used however since it is possible for the preview on disk to not be the same as what will be sent back after the preview.

Is this a good idea? Is is feasable? Would it be usable? I don't like the fact that it defers Twiki word correction to a later stage, but it should work in text based broswers like lynx or w3m, when the javascript based solutions won't.

Could this could also be extended as a possible interface (skin based) for SpellChecker?

-- JohnRouillard - 28 Nov 2001

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r9 - 2001-11-28 - JohnRouillard
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.