Skip to main content

Metro UI and Windows Metro Style Application is not the same thing

Am inceput sa vad o greseala care se face destul de des. Lumea a inceput sa incurce Metro UI cu Windows Metro Application. Acestea sunt doua lucruri total diferite.
Metro UI este un set de reguli care definesc modul in care interfata grafica a unei aplicatii arata. Acesta are la baza stilul "Swiss" care a fost dezvoltat in Elvetia la inceputul anilor 1950. Stilul Swiss a fost dezvoltat pentru ziare si reviste. Pe baza acestuia a fost definit Metro UI care a aparut odata cu Windows Phone, iar acuma urmeaza sa fie folosit si pe Windows 8. Este bine de stiut ca acest style poate sa fie facut pentru orice fel de aplicatie si in orice limbaj (Windows Forms, WPF, SL, HTML and so on). Exista un set de reguli pentru stilul Metro, iar Microsoft a definit reguli clare si precise pentru a exista o fluiditate intre aplicatii.
Windows Metro Application sau Windows Metro Style Application este tip de aplicatie care o sa ruleze pe Windows 8. Aceste tip de aplicatii trebuie sa fie scrise intr-un anumit fel astfel incat sa nu consume foarte multe resurse. Din aceasta cauza API care este accesibil intr-o aplicatie Metro este foarte diferit fata de cel pe care il avem cand folosim .NET 4.5. Din punct de vedere a UI-ului aceste aplicatii trebuie sa aibe Metro UI. Acest tip de UI este suportat in totalitate de catre API.
Pe PC-uri normale sau pe laptop o sa putem avem versiunea normala de Windows 8. Pe aceasta vs. o sa poata sa fie rulate aplicatii clasice care mergeau si pe Windows 7. Windows Services o sa existe in continuare. In schimb, din cate am vazut pana acuma pe tablete cu Windows 8 nu sa putem rula aplicatii clasice, ci doar aplicatii Metro Style Application. Aceasta versiune se numeste Windows RT si o sa ruleze pe procesoare ARM si WOA.
In concluzie, putem sa avem pe orice device si in orice limbaj Metro UI, dar in acest moment doar pe Windows 8 putem sa avem aplicatii Windows Metro Style.

Comments

  1. Foarte bine punctat.

    ReplyDelete
  2. Normal ca Metro UI e doar un set de reguli de design, si teoretic se pot implementa pe orice platforma, da' ma cam indoiesc ca il vom vedea pe altceva inafara de plaforma Windows > 7 si website-urile Microsoft :) ..

    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