{"id":51654,"date":"2021-02-11T03:01:47","date_gmt":"2021-02-10T17:01:47","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=51654"},"modified":"2021-02-11T18:59:11","modified_gmt":"2021-02-11T08:59:11","slug":"appml-acronyms-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/appml-acronyms-tutorial\/","title":{"rendered":"AppML Acronyms Tutorial"},"content":{"rendered":"
\"AppML<\/a>

AppML Acronyms Tutorial<\/p><\/div>\n

After yesterday’s AppML Primer Tutorial<\/a> we went looking for an apt inhouse web application that allows an interface to these new AppML framework concepts. Do you remember Acronyms Lookup Wikipedia Tutorial<\/a>?<\/p>\n

We first thought we’d be working in the client half of this web application but found it was much better to just add a new input element (ie. textbox) placeholder, just, here, and do the bulk of the changes needed in the serverside PHP that is Ajax called from the client HTML.<\/p>\n

What most pointed us in the right direction here, with the code, was AppML Data<\/a> whereby that “customers.js<\/font>” web server JSON file arrangement of yesterday, can be localized via PHP (where $pageContent is JSON results for acronym query from third parties, thanks and $appml is true for user flagging they want the AppML output report look) …<\/p>\n

<?php
\n
\n if ($appml) {
\n $mytitle=$selname; \/\/ incoming acronym to look up
\n
\n $aml=\"<!DOCTYPE html>
\n<html lang=\\\"en-US\\\">
\n<link rel=\\\"stylesheet\\\" href=\\\"style.css\\\">
\n<title>Customers<\/title>
\n<script src=\\\"\/\/www.w3schools.com\/appml\/2.0.3\/appml.js\\\"><\/script>
\n<body>
\n
\n<h1>\" . $mytitle . \"<\/h1>
\n
\n<h4>Thanks to <a target=_blank title='AppML via W3Schools, thanks' href='\/\/webdevable.com\/w3schools\/appml\/appml_howto.html'>W3Schools<\/a><\/h4>
\n
\n<table appml-data='appis<\/font>'>
\n<tr>
\n <th>Meaning<\/th>
\n <th>Frequency<\/th>
\n <th>Since<\/th>
\n<\/tr>
\n<tr appml-repeat=\\\"records\\\">
\n <td>{{lf}}<\/td>
\n <td>{{freq}}<\/td>
\n <td>{{since}}<\/td>
\n<\/tr>
\n<\/table>
\n
\n<script>
\n var appis<\/font>=\" . (str_replace('\"JUNKJUNK',\"'\",str_replace('\"sf\": \"' . $selname . '\", \"lfs\": ', '\"records\":', str_replace(\"\\n\",\"\",str_replace(\"}]}]}]\", \"}]}]}\",substr($pageContent,1)) ))) ) . \";
\n<\/script>
\n
\n<\/body>
\n<\/html>
\n\";
\n
\n echo $aml;
\n exit;
\n }
\n<\/code>
\n?><\/p>\n

So, you can check out the PHP changed getacronymdata.php<\/a> called by the minor changes of getacronymdata.htm<\/a>‘s acronym web application<\/a> to see (or try) this all for yourself.<\/p>\n

\n

\n

Previous relevant AppML Primer Tutorial<\/a> is shown below.<\/p>\n

\"AppML<\/a>

AppML Primer Tutorial<\/p><\/div>\n

There are hundreds and perhaps thousands of Framework type applications out there that create HTML output. Some set to a Framework the handling of data, and today we’re trying out one called AppML where we are going to use the W3Schools<\/a> Two Step first tutorial as per …<\/p>\n

\nAppML Explained:
\n<script src=”https:\/\/www.w3schools.com\/appml\/2.0.3\/appml.js”> adds AppML to your page.
\n
\nappml-data=”customers.js” connects AppML data (customers.js) to an HTML element (<table>>).
\n
\nIn this case we have used a JSON file: customers.js
\n
\nappml-repeat=”records” repeats an HTML element (<tr>) for each item (records) in a data object.
\n
\nThe {{ }} brackets are placeholders for AppML data.\n<\/p><\/blockquote>\n

Tokenizing this way (or you could call it substituting) gels with our thinking nearly as much as adding global data attributes as ways to make your HTML more intelligent, and more like that “protocol with glasses”, XML.<\/p>\n

All it took to create today’s “pretty swish” table of a web application<\/a> was …<\/p>\n

    \n
  1. index.html<\/a> HTML<\/li>\n
  2. style.css<\/a> CSS<\/li>\n
  3. customers.js<\/a> JSON<\/li>\n<\/ol>\n

    … that JSON serving as a flat file data source. Interesting, huh?!<\/p>\n

    If this was interesting you may be interested in this<\/a> too.<\/p>\n