W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2016

Re: [whatwg] Some Clarification on CML Proposal

From: Roger Hågensen <rh_whatwg@skuldwyrm.no>
Date: Thu, 6 Oct 2016 01:04:31 +0200
To: whatwg@lists.whatwg.org
Message-ID: <cf7c3965-11f5-1e51-9cde-717c87579988@skuldwyrm.no>
On 2016-10-05 08:17, Jacob Villarreal wrote:
 > I was proposing a really simple markup language.  I call it content 
markup language (CML).

You do realize that HTML stands for Hyper Text Markup Language right? 
Adding a markup language to a markup language is illogical, it is better 
to improve the existing markup language or create a new markup language 
instead.

 > It implements a simple object-oriented content markup infrastructure 
which treats every page element as an object.

This sounds like it might be better served by Javascript which is object 
oriented.

 > It consists of a simple batch html infrastructure with only four 
batch file types for forms, fields, menus, and submenus 
(.frm/.fld/.mnu/.smn).  .... All text objects would be text data.  All 
other objects would be treated in the standard manner, but would be 
applied at the corresponding page coordinate. ... the table, and field 
html elements are bitmap objects ...

This sounds overtly complicated. Also if things are purely bitmaps then 
that would cause issues with screen readers, there are enough issues 
with tables as it is, if they become bitmaps they'll be a huge pain in 
the ass (more than currently).

By the sound of it these file types are container formats, why would you 
put a PNG image file inside a container file? Server side filetype 
negotiation would need to be redesigned to handle this as well.

Perhaps HTML imports is what could be the solution you are seeking (or 
needing), it's still a draft though
http://w3c.github.io/webcomponents/spec/imports/
But Mozilla has decided to not support it (that was in 2014 though).

But there is also Javascript imports
https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Statements/import
"The import statement is used to import functions, objects or primitives 
that have been exported from an external module, another script, etc."
And sounds closer to some of the stuff you mentioned by the sound of it.
Chrome an Firefox should support import, and Edge is in the process of 
adding modules.
https://blogs.windows.com/msedgedev/2016/05/17/es6-modules-and-beyond/#PQc593TJJwqRbpO4.97
But the specs are still not complete yet as far as I can tell.

A "modular" web page where a header and footer and menu and other parts 
can reside in different files without the need for server side scripting 
is very close.

In the meantime have you tried iframe with the seamless attribute and 
some javascript?



-- 
Roger Hågensen, Freelancer, http://skuldwyrm.no/
Received on Wednesday, 5 October 2016 23:05:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:39 UTC