Skip to main content

jquery template - jumate de MVC

Nu odata am scris ceva asemanator cu aceste cond in jQuery:

var sablon = "<b> ${nume} </b>";
Problema la acest template este modul in care se poate manipula . In cazul in care dorim sa facem o modificare, suntem nevoiti sa cautam in cod unde avem definit template-ul si sa facem modificari pe el. In cazul in care un nou dezvoltator trebuie sa faca modificari, el o sa fie nevoit sa cauta in cod.

O solutie este sa folosim un template pentru acest lucru. Primul pas este sa definim template-ul in forma urmatoare:

<script id="numeTemplate" type="text/html">
<b> ${nume} </b>
</script>
Prin acest mod, o sa ne putem referi template-ul nostru in orice loc din cod pe baza unui ID, totodata o sa fie foarte usor de grupat toate template-urile.

Urmatorul pas este sa referim pe langa libraria de jquery si libraria pentru template-uri. Numele ei este: jquery.tmpl.js.

Template-ul pe care l-am definit mai sus trebuie putin modificat, forma sa trebuie sa fie:

<script id="numeTemplate" type="text/html">
<b> ${nume} </b>
</script>
JSON va scoate automat valoarea pentru nume prin ${}. Putem sa avem orice fel de conditii logice, in exemplul dat mai sus, avem un IF care afiseaza imagini diferite pentru barbati si femei. Prin acest mecanism putem sa cream template-uri complexe, in care logica care defineste modul in care se face randarea la anumite elemente din template sa fie in interiorul la template.
Datele pentru care facem randarea sunt:
var persoane = [
{ Nume = "Stefan", IsMan = 1},
{ Nume = "Oana", IsMan = 0},
{ Nume = "Mihai", IsMan = 1}
];
Pentru a putea folosi template-ul definit, putem sa folosim functiile
  • tmpl([data],[options])
  • $.tmpl(template,[data,[options])
Pentru exemplul dat mai sus ar trebuii sa scriem:
$("numeTemplate").tmpl(persoane).appendTo("#listaPersoaneDiv")
Unde listaPersoaneDiv reprezinta id la divul care afiseaza template-ul.
Si gata, in acest moment avem un template pe care il putem folosi in orice locatie. Putem sa privim totul ca o jumatate din MVC, doar partea de Model-View.
Pentru mai multe informatii: http://api.jquery.com/jQuery.template/

Comments

  1. buna ziua
    apropo de jquery am si eu o problema cu aceste program script sau ce este el...in consola de erori imi apare o chestie cum jquery in not defined si inca o eroare $j in not defined....si din cauza aceasta nu pot vedea diferite chesti pe un site de vanzari si cumparari....nu ma lasa sa dau comenzi pe site de cumparare si multe alte...care este problema???

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP