Mustache Helper functions

Recently, implemented the Mustache Template processing framework.  As i worked through this implementation, i found myself creating the same JavaScript call and decided to simplify the overall execution into a single function signature and just call it multiple times.

Root Mustache Call:

1:  /*********************************************************************  
2:     @file - string value, Should be the HTML Template file.  
3:     @filterid - string value, Should the ID value of the Script tag inside  
4:           @file to obtain the HTML content.  
5:     @api - string value, Should be the URL to the API request  
6:     @dest - string value, Should be the destination selector, ideally ID  
7:           value of the control to load the Mustache Template into.  
8:     @func - (Nullable) Function value, If defined this will be executed  
9:           after the loading of the data into the Template.  
10:  ----------------------------------------------------------------------  
11:     LoadTemplate('...', '#...', 'api/.../...', "#...", function(){...});  
12:  *********************************************************************/  
13:  function LoadTemplate(file, filterid, api, dest, func) {  
14:     GetJsonUTF8(api, function (resp) {  
15:        $.get(file, function (template) {  
16:           var tmplt = $(template).filter(filterid).html();  
17:           $(dest).html(Mustache.render(tmplt, JSON.parse(resp)));  
18:           //Execution post-load methodology  
19:           if (typeof func !== 'undefined') {  
20:              if (typeof func === 'function') {  
21:                 func();  
22:              }  
23:           }  
24:        });  
25:     });  
26:  }

Calling Functions:

1:  /*********************************************************************  
2:     @api - string value, Should be the URL to the API request  
3:     @dest - string value, Should be the destination selector, ideally ID  
4:           value of the control to load the Mustache Template into.  
5:     @func - (Nullable) Function value, If defined this will be executed  
6:           after the loading of the data into the Template.  
7:  ----------------------------------------------------------------------  
8:     LoadDropDownList('api/.../...', "#...", function(){...});  
9:  *********************************************************************/  
10:  function LoadDropDownList(api, dest, func) {  
11:     LoadTemplate("Templates/DropDownList.html", "#ddlTempl", api, dest, func);  
12:  }  
13:  function LoadTeamDropDownList() {  
14:     LoadDropDownList('api/teams/get', "#teams");  
15:  }  
16:  function LoadMagnitudeDropDownList(txt) {  
17:     LoadDropDownList('api/magnitudes/get', "#taskdetailsmagnitudes", function () {  
18:        $("#taskdetailsmagnitudes select option").filter(function () {  
19:           return $(this).text() == txt;  
20:        }).prop('selected', true);  
21:     });  
22:  }

Hopefully this will help you on implementations and help in stream-lining new Template implementation.

Comments

Post a Comment

Popular posts from this blog

SysInternals - BgInfo for ALL Users

Image
I have seen various sites that have been pretty good at getting close to the point of getting Background Information created by the tool BgInfo but none of them have actually solved my specific problem. Solutions currently out there include: Placing into the "All Users" folder This did not work for me, as our implementation does not contain an "All Users" folder in the "Users" folder for profiles. Reg-Hacking and HKCU or HKLM entry This is the worst of all the bad choices available.  I am experienced with Registry Editing and I still would not want or find a need to do this. Placing into the "Default" folder This is good going forward but what about those 20+ user profiles that are already logged in.  FYI, if your server has 20+ user account profiles in the "Users" directory you have larger problems than I am willing to assist with in this posting. The solution that worked for me, will be described below in pain-staki...
Read more

Linked Server....

Well today, I started the fun filled adventure of managing data from/to a LinkedServer. During this learning curve, I found plenty of information about how to query from and instert into a Linked server but most of them utilized the OpenQuery  TSQL Statement to operate. One failure of the concepts is to use the inline statement to access the Linked Server. In my situation, i was linking to a MySQL database offsite.  Below you will find the MSSQL statement patterns to used when utilizing query statements against the Linked Server. Select: 1: Select {cols} 2: From {LinkedServer}...{table} 3: [Conditions] Insert: 1: Insert Into {LinkedServer}...{table} [cols,...] 2: Values ([cols,...]) There are more commands you can use but the point is that the developer/dba is utilizing only the 'server' and 'table' portions of the source information.  This being, as described by Microsoft, as ' {server}.{database}.{schema}.{table} ' is simply ' ...
Read more

TSQL - String Concatenation

On current project, I ran into a scenario where I needed to concatenate a series of rows into a single string value.  Nothing major, just concatenate them with a delimiter and return the result.  As all of us Microsoft SQL developer's know and deal with is the lack of a SQL supported function that is able to assist us in this "minor" feature. As this is my knowledge dump for techniques and other methods used for the various platforms, here we go: Construct: The first step is to identify what information you want, the basic's of query design.   SELECT Email FROM Contacts Group By Email Group by is conditional, depending on your situation and how you organize your referential integrity. Stage Next, lets build our environment, not the SProc just the supporting actors in the process. declare @email varchar(max) = '' SELECT @email += Email + ', ' FROM Contacts Group By Email This simply concatenates each of ...
Read more