{"id":80,"date":"2014-05-19T21:09:46","date_gmt":"2014-05-19T21:09:46","guid":{"rendered":"http:\/\/thomasgardnerofsalem.wordpress.com\/?p=80"},"modified":"2019-06-02T20:18:05","modified_gmt":"2019-06-02T20:18:05","slug":"shapes","status":"publish","type":"post","link":"https:\/\/tgsoc.org\/tech\/2014\/05\/19\/shapes\/","title":{"rendered":"Shapes"},"content":{"rendered":"

As said, this blog is technically oriented<\/strong><\/a>. But, in the nested world of reality, one person’s technical is another’s abstraction (let’s discuss). Those whose services will be in demand in the future (in order for us to have sustainability and a lot more) ought to be able to be able to bridge many levels of technical data. The topmost level of this paradigm? Don’t get me started as we have too many (as in way more than necessary) nestled up there, cloud nine, living off the work of others. The lowest level? Would be truth engineer’d<\/a><\/strong>\u00a0in focus? So, this post is technical in a computational sense (somewhat, we can go much deeper). We will get back to content management. Too, we’ll get back to map-territory<\/a><\/strong> issues that seem to be everywhere inflicting even smart people (listen up, best-and-brightest<\/a><\/strong>).<\/p>\n

The next post will go into peers keeping each other honest (can that appeal to millennials?).<\/p>\n

In a prior post<\/strong><\/a>, I mentioned running across shapes being handled by CSS and HTML<\/strong><\/a>. When I first saw that, I just made note as I was looking at buttons (which can have all sorts of shapes; notice that we went back to the old, Platonic, rectangle<\/strong><\/a>). Since then, I have looked at this advance via HTML\/CSS and wanted to point to a few places to revisit later when I get back to layout issues (table’ing is sufficient for now — I’ll have to find the page, but a modernly focused site had tables still in use – hurrah).<\/p>\n

For now, we will show a few examples.<\/p>\n