Archive of UserLand's first discussion group, started October 5, 1998.

RFC: New attribute for glossary entries

Author:Jim Roepcke
Posted:1/13/1999; 1:47:39 PM
Topic:Staging Server
Msg #:2106 (In response to 2102)
Prev/Next:2104 / 2107

Add another attribute to #glossary table entries called dynamic.

Example:

 #glossary
    Search Page
       linetext      "Search This Site"
       path          "search/search.html"
       dynamic       false

If html.addPageToGlossary is called in the context of mainResponder or wsf, then dynamic is set to true when the entry is created.

If html.addPageToGlossary is called in the context of the HTML framework, dynamic is set to false.

This could solve the issue Matt Neuberg mentioned a long time ago where you couldn't point to a static site from a dynamic site via the glossary because html.refGlossary changes all file extensions to .wsf whether or not the target page should be browsed dynamically or not.

I wonder if it might also be part of a solution for Alan German's problem posted recently about Staging Servers.

With the 'dynamic' element, html.refGlossary should only change the file extension if dynamic doesn't exist (for backwards compatibility), or if it is true.

It looks like a one line change in html.refGlossary!!

Current code from html.refGlossary lightly edited to work around DG issues

case typeOf (adr^) {
	scriptType { «new in 5.0, glossary items can be scripts
		return (adr^ ())};
	tableType { «new in 5.0, convert a table (prettier to look at) to a glossPatch
		local (s = "[ [#glossPatch ", path = adr^.path);
		if html.inResponder (adrPageTable) {
			path = string.popSuffix (path)   ".wsf"};
		s = s   adr^.linetext   "|";
		s = s   path   "|]]";
		return (s)}}

Replacement for "if html.inResponder" line above:

if html.inResponder (adrPageTable) and ((notdefined(adr^.dynamic)) or (not adr^.dynamic))

Comments?



There are responses to this message:

This page was archived on 6/13/2001; 4:47:16 PM.

© Copyright 1998-2001 UserLand Software, Inc.