From: http://www.tiddlytools.com/#InlineJavascriptPluginInfo
loading a script from a source url:
http://www.TiddlyTools.com/demo.js contains:
function inlineJavascriptDemo() { alert('Hello from
demo.js!!') }
displayMessage('InlineJavascriptPlugin: demo.js has been
loaded');
note: When using this example on your local system, you will need
to download the external script file from the above URL and install it
into the same directory as your document.
<script src="demo.js" show>
return "inlineJavascriptDemo() function has been defined"
</script>
Mike
On Apr 10, 10:50 am, skye riquelme <[email protected]> wrote:
> Thanks for that information.....seems its basically as I thought..only
> lots of details to work out...
>
> ...one detail would be to make sure that the incoming CSS stuff does
> not use any definitions/classes with the same name as in TW...causing
> conflicts.
>
> Freds question lead me to look a little closer.....he asked about why
> import a static webpage.........
>
> now theres the crunch...its not a static page ...its a system that
> creates a simple slide show presentation.....the CSS the HTML I think
> I can work around.....but on closer study of the code there is one
> line that I don´t know how to handle....
>
> its a call to a .js file.....<script src="ui/default/slides.js"
> type="text/javascript"></script>............can I call this using
> Erics RemoteTiddlerPlugin......ou can I copy it into a tiddler.....and
> run the scritp....I have InlineJavaScript installed ???
>
> Thanks in Advance
>
> On 9 Abr, 23:17, Craig in Calgary <[email protected]> wrote:
>
> > Skye,
>
> > > the <head>................</head> contains definitions of meta names
> > > etc which I figure I don´t need...
>
> > The meta data (e.g. Description, Keywords, Author, Copyright) is
> > useful for Search Engine Optimization (SEO). Google will find that
> > stuff in a TW. According tohttp://tiddlywiki.com/#CustomMarkup,
> > [[MarkupPreHead]] is the best place to put this meta data in a TW. I
> > would keep the meta data. It doesn't impact performance at all or size
> > by very much but it will aid in content discoverability.
>
> > > <link rel="stylesheet" href="ui/default/slides.css" type="text/css"
> > > media="projection" id="slideProj" />
>
> > There are two (2) approaches to handling external CSS files. As Fred
> > suggests, cut/paste the content into [[StyleSheet]] or another tiddler
> > and reference it in [[StyleSheet]]. This will eliminate your external
> > files. However, if there is any chance that the numerous HTML files
> > you want to port to TW might land in multiple TWs, I would suggest
> > keeping the CSS in those external files and move the <link></link>
> > references into the [[MarkupPreHead]] of each TiddlyWiki that needs
> > them. Downside: multiple, external files. Upside: content reuse. Any
> > change in the CSS will propagated throughout the TWs without needing
> > modification. This is the extensible solution and a wise choice from
> > the information architecture perspective.
>
> > > the main body of the original HTML page (between the <body> tags) I
> > > guess I simply have them in the tiddler and in this case wrap them in
> > > <html> tags......
>
> > One potential problem with all the <body></body> content is its use of
> > <div></div>'s, <span></span>'s, and iframes. When you lump everything
> > in the <body></body> of an HTML file into a single <html></html>
> > within a single tiddler, the content might render wonky in TW. A
> > possible solution is to modify the CSS to accommodate the narrower
> > width of [[ViewTemplate]]. Another possibility is to use a grep tool
> > or some regex (regular expression) tool to strip out or modify those
> > wrappers so the resulting rendering in TW is acceptable. If all the
> > HTML files you have to port are similar in CSS, this regex process
> > could be automated to work on many files at once and/or be repeated on
> > demand. I know because data migration is one of my specialties.
>
> > Another potential problem with all the <body></body> content is its
> > use of internal and external links. Resolving them to internal
> > tiddlers or tiddlers of other TWs would require more grep/regex magic.
>
> > I might sound pessimistic but, in fact, I believe your project is very
> > doable and intriguing to boot, regardless of the temporary challenges.
>
> > Hope this helps.
>
> > Craig
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
