<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>doc.mashweb.club – metaphor</title>
    <link>/tags/metaphor/</link>
    <description>Recent content in metaphor on doc.mashweb.club</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 05 Jan 2017 00:00:00 +0000</lastBuildDate>
    
	  <atom:link href="/tags/metaphor/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Zen-White-Paper: Zen vs. website builders</title>
      <link>/zen-white-paper/practices/website-builders/</link>
      <pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate>
      
      <guid>/zen-white-paper/practices/website-builders/</guid>
      <description>
        
        
        &lt;p&gt;It is important to characterize and visualize how Zen will be different from &amp;ldquo;website builders&amp;rdquo; and WCMSs like Wix.com and Weebly.com. In contrast to such WCMSs, which prescribe construction methods at the level of business type, templates, plugins, modules, fonts, etc., Zen will give the user ultimate control of detail at the element/node/NodeList level of web pages. Zen will allow a DOM node to be grabbed and &amp;ldquo;dragged&amp;rdquo; to different positions in its containing NodeList because this is the simplest metaphor for that operation. Drag-and-drop is a classic feature of direct-manipulation interfaces (DMIs) and this metaphor of &amp;ldquo;moving&amp;rdquo; an HTML element or node is so compelling that we have to look at the code to see that the element has not moved in terms of x and y coordianates, but rather in terms of its cardinal position in a NodeList. Zen will allow a DOM node to be &amp;ldquo;cut and pasted&amp;rdquo; to any valid position in the DOM—an interaction between multiple NodeLists. An HTML element&amp;rsquo;s style has four possible, well-supported values for its display property: block, inline, inline-block, and none. Live demo code to implement GUIs to rearrange element positions in the NodeLists of the first three of these display styles is located on the author&amp;rsquo;s GitHub Pages here, here, and here. (Right-click on the links to open the pages in new tabs or windows.) The method of sliding elements in these prototype GUIs was partly inspired by the 15 Puzzle and JavaScript-based implementations of the 15 Puzzle. There are notes about some of these implementations on this website. Below is a screen recording of Jamie Wong&amp;rsquo;s AI-based automated 15-Puzzle solver, which is written solely in JavaScript, HTML, and CSS (Figure 13).&lt;/p&gt;

&lt;figure&gt;
    &lt;img src=&#34;/images/15-puzzle.gif&#34;/&gt; &lt;figcaption&gt;
            &lt;h4&gt;Figure 13. Jamie Wong&amp;#39;s 15-Puzzle solver.&lt;/h4&gt;
        &lt;/figcaption&gt;
&lt;/figure&gt;

&lt;p&gt;Presently, the customization of templates, plugins, and modules for website builders and web CMSs and the creation of novel comment systems, forums, wikis, and presently unimagined communication systems are far outside the bounds of casual web authorship.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Zen-White-Paper: Values</title>
      <link>/zen-white-paper/values/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/zen-white-paper/values/</guid>
      <description>
        
        
        &lt;p&gt;The values driving Zen&amp;rsquo;s development are:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Creating novel, beautiful, well-formatted, semantic HTML and CSS should be dead simple.&lt;/li&gt;
&lt;li&gt;Amateur web authors should easily create virtually any page structure and style.&lt;/li&gt;
&lt;li&gt;The interface should have a virtually zero learning curve, and zero should mean zero. Zen must leverage well-known interface metaphors and gestures to the hilt. The &amp;ldquo;principle of least surprise&amp;rdquo; should be followed.&lt;/li&gt;
&lt;li&gt;Zen should not clutter its interface for manipulating and creating semantic and presentation structure with every possible detail. Zen should hide details until they are needed; it is better to let the user drill down to these details than to present them by default.&lt;/li&gt;
&lt;li&gt;The interface should have two mutually exclusive modes for semantics and styling. The semantics mode should hide page styling information and help search engines &amp;ldquo;understand&amp;rdquo; the page&amp;rsquo;s subject matter to classify it for the sake of web seekers. Styles will set fonts and colors and the interaction of the page&amp;rsquo;s elements with other elements and with the height and width of the page.&lt;/li&gt;
&lt;li&gt;The interface should have two mutually exclusive modes: a semantics mode and a styling mode. The semantics mode should hide page styling information. The styles will set the looks of the page and the interaction of the page&amp;rsquo;s elements with such things as other elements and the height and width of the page. each other and the The clear and proper semantic structure will help search engines &amp;ldquo;understand&amp;rdquo; the page&amp;rsquo;s subject matter to classify it. The other mode should hide the semantics and focus on the look and feel of the web page. The look and feel is&lt;/li&gt;
&lt;li&gt;Meta organization, like themes, templates, or partials,&lt;a href=&#34;/zen-white-paper/notes/#fn:28&#34;&gt;&lt;sup&gt;28&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:29&#34;&gt;&lt;sup&gt;29&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:30&#34;&gt;&lt;sup&gt;30&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:31&#34;&gt;&lt;sup&gt;31&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:32&#34;&gt;&lt;sup&gt;32&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:33&#34;&gt;&lt;sup&gt;33&lt;/sup&gt;&lt;/a&gt;
&lt;sup&gt;, &lt;/sup&gt;&lt;a href=&#34;/zen-white-paper/notes/#fn:34&#34;&gt;&lt;sup&gt;34&lt;/sup&gt;&lt;/a&gt;
 should not be precluded by the structure of Zen&amp;rsquo;s low-level tools. Zen should empower the creation of these, even if not directly implement them.&lt;/li&gt;
&lt;/ol&gt;

      </description>
    </item>
    
  </channel>
</rss>
