W3C home > Mailing lists > Public > www-talk@w3.org > January to February 2007

RE: (MOB)HTML - Merge on browser HTML (was SDPML)

From: S. Mike Dierken <dierken@gmail.com>
Date: Sun, 7 Jan 2007 15:22:17 -0800
To: "'sunil vanmullem'" <sunil.vanmullem@btopenworld.com>, <www-talk@w3.org>
Message-ID: <45a180a9.38b02479.0d9c.ffffbcd3@mx.google.com>

Q: Why use HTML tags at all? 
Q: Isn't this just 'client side includes' or Xlink or such?


> -----Original Message-----
> From: www-talk-request@w3.org 
> [mailto:www-talk-request@w3.org] On Behalf Of sunil vanmullem
> Sent: Sunday, January 07, 2007 3:23 AM
> To: www-talk@w3.org
> Subject: (MOB)HTML - Merge on browser HTML (was SDPML)
> 
> 
> I while ago I posted information about a project that aimed 
> to change the way web pages were written by separating out 
> document structure from the content of the document.
> 
> I've renamed the project to Merge on Browse (MOB)HTML as it 
> uses AJAX to treat the document structure of web page as 
> static content, like an image. And it's the browser that 
> pulls this document structure separately and merges it with
> 
> data encoded within the original served page. 
> 
> Simply put this enables web applications to be written so 
> that the GUI can be skinned without changing the underlying 
> business logic, reduces dependencies on GUI builders vs. 
> application coders, has potential to allow rendering into 
> other forms such as PDF, n and brings efficiency improvements 
> to the server side.
> 
> (MOB)HTML is cross platform and works on Windows and MAC on 
> Internet Explorer, Firefox , Opera, Safari and Minimo.
> (MOB)HTML can be found here: 
> http://www.paglis.co.uk/(MOB)HTML/index.html
> 
> Now that the prototype is running I'm looking to set up a 
> project on Improving (MOB)HTML whose controversial aim it is 
> to make (MOB)HTML the standard for writing web pages. 
> 
> Sunil Vanmullem 
> 
> 
> 
> 
> A MOB page looks like this:
> 
> 		<html>
> 		<body>
> 		<link href="stylesheet.css" rel="stylesheet"
> type="text/css">
> 		<div id="MOB" style="display:none">
> 			<div id="MOB.noCSS">
> 				Sorry, this page requires a 
> browser that supports 
> 				CSS in order to function properly. <br>
> 			</div>
> 			<div id="MOB.Template">index-t.html</div>
> 			<div id="MOB.Static">index.props</div>
> 			<div id="MOB.WriteTo">MOB_OUT</div>
> 			<div id="MOB.StyleSheet">stylesheet.css</div>
> 			<div id="MOB.mergedelim.begin">[[</div>
> 			<div id="MOB.mergedelim.end">]]</div>
> 			<div id="welcome.blurb"></div>
> 			<div id="param2"></div>
> 			<div id="param3"></div>
> 		</div>
> 		<DIV id=MOB_OUT></div>
> 		<script language="JavaScript" src="common.js"></script>
> 		<script language="JavaScript" src="mob.js"></script>
> 		<script language="javascript">
> 			var oMOB = new MOB();
> 			oMOB.main();
> 		</script>
> 		</html>
> 
> And Heres a breakdown of what each part does
> 
> 
> 	<link href="stylesheet.css" rel="stylesheet" type="text/css">
> 	<script src=></script>
> 		* a reference to the javascript and stylesheets 
> that the rendered 
> 		* HTML page needs as I couldn't see a cross 
> browser way to acheieve this
> 
> 		<div id="MOB" style="display:none">
> 			* configuration data within a hidden DIV
> 
> 			<div id="MOB.noCSS">
> 				Sorry, this page requires a 
> browser that supports CSS 
> 			</div>
> 				* currently displayed if the 
> target browser doesn't 
> 				* support CSS. Though works needs 
> 				* to be done to redirect to 
> server side rendering 
> 				* of MOB pages in this instance
> 			
> 
> 			<div id="MOB.Template">index-t.html</div>
> 				* identifies the file that 
> contains the document structure
> 
> 			<div id="MOB.Static">index.props</div>
> 				* identifies any static content 
> that needs to be merged 
> 				* into the structure.
> 				* e.g. a different language 
> could have different static content
> 
> 			<div id="MOB.WriteTo">MOB_OUT</div>
> 				* identifies where the 
> merged/rendered output should be written.
> 
> 			<div id="MOB.StyleSheet">stylesheet.css</div>
> 				* a reference to the 
> stylesheets that the rendered page needs
> 
> 			<div id="MOB.mergedelim.begin">[[</div>
> 				* used to identify the start of 
> a delimited merge field 
> 				* in the template file above.
> 
> 			<div id="MOB.mergedelim.end">]]</div>
> 				* used to identify the end of a 
> delimited merge field in 
> 				* the template file above.
> 
> 			<div id="welcome.blurb"></div>
> 			<div id="param2"></div>
> 			<div id="param3"></div>
> 				* example of dynamic content 
> keyed on DIV ID that will be 
> 				* merged into the template
> 		</div>
> 
> 		<DIV id=MOB_OUT></div>
> 			* the DIV to which the merged content 
> will be written - 
> 			* as defined above in MOB.WriteTo
> 
> 		<script language="JavaScript" src="common.js"></script>
> 		<script language="JavaScript" src="mob.js"></script>
> 		<script language="javascript">
> 			var oMOB = new MOB();
> 			oMOB.main();
> 		</script>
> 			*
> 			* javascript code to run (MOB)HTML
> 			*
> 		</html>
> 
> --
> Suppose I should get my coat then.
> 
> 
> 
Received on Monday, 8 January 2007 04:00:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:29 GMT