Visit Our Home Page
 Explored,Designed,Delivered.sm
Welcome, Guest. Please Login or Register (Password Reminder)


Creativyst Forums 
Support & Discussion 
Register Help Search Login  
   
   Creativyst Forums-TOP
   Web Site Design
   JSMsg: A JavaScript Content Display Convention
(Moderator: admin)
 Author
Topic: JSMsg: A JavaScript Content Display Convention       [Link=49]
Reply Please log in first.
JRepici
Administrator


Posts: 328





Gender:
      JohnRHere2
    JSMsg: A JavaScript Content Display Convention   (Date posted: 04/29/03 at 17:32:01) Quote Modify Delete

Hello,

I've published a new document that JavaScript coders and webmasters alike should find very helpful. It will allow them to display dynamic content in whatever format they choose, without requiring them to manually enter or change that content in the display script or HTML.

. . . . . . . . . . .
The entire paper (from the top) is here:
http://www.creativyst.com/Doc/Std/JSMsg/JSMsg.htm

The spec is long so to get a quick overview of what it is and how it can be used, see the sections entitled

Overview
Usage Examples
Message Parts
Function Calls
CvsMsg Servers

. . . . . . . . . . .
FAQ (so far):
. . . . . . . . . . .

Q. Why use namespaces? Isn't that vercomplicating the issue?

A. Namespaces of one sort or another are required, because one goal is to allow content from many different sources to be easily shared on a single web page in a consistent manner.
. . . . . . . . . . .

Q. The functions would have to be duplicated in each JSMsg.js file. Shouldn't there be one copy of the code and separate file(s) for the data components?

A. It is true there is duplication of effort from namespace to namespace because each file may be produced by a different application. Each file may be arbitrarily included in an outside website. Therefore each should (for durability) carry its own consistent means of easy data display and access.

Because the access functions are small and data is the focus of the file, the data's size will likely swamp the size of the access functions.
. . . . . . . . . . .




. . . . . . . . . . .
From the Overview section in the document:
. . . . . . . . . . .

This paper documents and presents a recommendation for the "JSMsg" file format. The JSMsg convention allows changing content to be shared with outside scripts (called "clients"), and on web pages, without concern for how the content will be formatted by the outside script or page HTML.

JavaSript programs that display content in interesting and creative ways are perfect candidates to have JSMsg client capabilities added to them.

Such scripts will be enhanced by JSMsg support because they will no longer need to ask their users to change the static information to be displayed. For example, an information display script, when told to use a JSMsg file from a news service, will display the news information as it changes automatically, without needing intervention from the webmaster. Just as importantly, such a script will work with dynamic OR static content from ANY JSMsg file, not just the news service.

This JSMsg recommendation is a specification for a JavaScript file, functions, and naming conventions which may be included by outside webmasters in their pages, allowing display of their provided content in whatever style and layout the outside webmaster chooses. The convention is also useful as an easy means of content display at the source website.
. . . . . . . . . . .

. . . . . . . . . . .
I'll eventually integrate the FAQ into the document. If you've got questions, ask away.

Thanks for any input or time you may spend on this.

-John Repici.

Last modification: JRepici - 04/29/03 at 17:32:01

   E-Mail   Ip: Logged
Reply Please log in first.
Pages: 1
Jump to:

YaBB Board c 2000
YaBB Programming Team
 



















© Copyright 2002 - 2008 Creativyst, Inc.