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

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...