Skip to main content

Cum sa utilizam optiunea de Pinned Site pe IE9 impreuna cu Windows 7

A fost lansat IE9. Ca de obicei, uni sunt pro, alti sunt contra. Ce m-a facut sa instalez IE9 a fost opțiunea de pinned site. Daca pana acuma doar pe o aplicatie puteai sa faci pin/unpin, IE9 ne ofera aceasta posibilitate si pentru siturile care suporta acest lucru. Chrome are aceasta opțiune de ceva vreme, dar va spun sincer ca nu am remarcato pana acuma( FF fan here).
De ce meta date avem nevoie ca sa putem face ca o pagina web sa poata fi pinned:
  • application-name: numele la pagina. Daca acesta nu este setat se folosește titlul la pagina;
  • msapplication-tooltip: textul care se afiseaza cand esti cu mouseul peste shortcut;
  • msapplication-starturl: URL spre care duce pagina pe care a fost făcuta pinned( de exemplu daca folosti un master page, puteti face orice pinned sa duca spre prima pagina;
  • msapplication-navbutton-color: culoarea la fundal si la text;
  • msapplication-window: dimensiunile default la browser cand se da click pe shortcut;
Toate acestea sunt opționale, ajunge doar sa apelam metoda JS pe care am descriso la sfîrșitul postului. Exemplu:
<meta name="application-name" content="Sample Site Mode Application"/>
<meta name="msapplication-tooltip" content="Programing issues"/>
<meta name="msapplication-starturl" content="http://vunvulearadu.blogspot.com/"/>
<meta name="msapplication-window" content="width=1024;height=800"/>
<meta name="msapplication-navbutton-color" content="white"/>

In cazul in care doriti sa specificati si o anumita icoana puteti sa folosti:
<LINK rel="shortcut icon" type=image/x-icon href="[locatia_de_pe_server_unde_este_icoana]">
<LINK rel=icon type=image/ico href="[locatie_icoana]">


Atentie: Trebuie sa specificați in primul tag locatie web unde se poate gasi fisierul, iar in al doilea tag se specifica calea relativa. Exemplu:
<LINK rel="shortcut icon" type=image/x-icon href="http://vunvulearadu.blogspot.com/raduIco.ico">
<LINK rel=icon type=image/ico href="./raduIco.ico">


In cazul in care acesta icoana nu este specificata se va folosi cea default a IE9. Userul poate sa personalizeze fiecare site pinned.
Pentru fiecare site pinned putem sa definim anumite taskuri in lista de "jump list tasks". Aceata lista se va afisa cand userul o sa dea click dreapta pe "pin"( nu am gasit o traducere care sa sune bine la pin- ac, bolt, cui, tinta? Suna prea ciudat). Pentru acest lucru putem sa ne folosim de meta data denumita msapplication-task. Prin acest mecanism putem sa oferim un meniu utilizatorului care sa il duca pe acesta la paginile principale( pagina de news, setari cont, status comenzi etc).
<META name="msapplication-task" content="name=Pagina logare;action-uri=http://cluj.ro/logare.html;icon-uri=http://cluj.ro/logareIcon.ico"/>
<META name="msapplication-task" content="name=Stiri;action-uri=http://cluj.ro/news.html;icon-uri=http://host/newsIcon.ico"/>


Pentru a se putea face pin la un site ajunge ca intr-o ancora sa apelasi metoda msAddSiteMode().
<a onclick="window.external.msAddSiteMode();" href="#">Pin Me</a><br />

Pentru a verifica daca pagina curenta a fost sau nu lansata ca si un pinned site puteti folosi window.external.msIsSiteMode().
Pentru mai multe informatii recomand: http://msdn.microsoft.com/en-us/library/gg131029%28VS.85%29.aspx

Comments

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