Javascripting....

[Brian V Hughes]

I think I know the problem you are describing. It sounds like one that 
I "solved" a couple of years ago. All I did was take the code for 
user.html.macros.embedStyleSheet and adapt it to work for JavaScripts. 
I also created a new web-site framework sub-table called #javaScripts 
(analogous to #styleSheets) to hold my JavaScript code objects (I 
always use outlines).

It really only took about 15 minutes to create a 
user.html.macros.embedJavaScript macro that I could then call from a 
#pageHeader object as many times as I needed. You can even use 
page-level directives to pass instructions to #pageHeader to let it 
know which #javaScripts object(s) to load for the specific page.

I'm happy to answer any questions you might have about what changes I 
made to the original embedStyleSheets macro if you get stuck.

-Brian
----
Brian V. Hughes							http://www.dartmouth.edu/~comm/
Webmaster								Dartmouth Computing Services
Web Group								Communications Services


On Wednesday, November 6, 2002, at 02:18  PM, Kris Anderson wrote:
> I've tried making subtables and putting my script in WP text but the 
> only
> success with that is putting the WP text at the root of the Frontier 
> file
> under websites giving it some # name like #editorScript (as a WP text
> element). I put it anyplace else and then I get errors like, there is 
> no
> object by that name. The behavior I am explaining can be found at
> http://frontier.userland.com/stories/storyReader$106 and to me this 
> seems
> undesirable. It can make things very cluttered really fast.
>
> Frontier is a great thing but if I have to load elements outside the
> framework as a separate file as suggested (at least my interpretation 
> of it)
> then what is the point of a CMS that doesn't allow even the simplest 
> of CMS