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(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too