background preloader

The Open Graph Protocol

The Open Graph Protocol

Model View ViewModel MVVM facilitates a clear separation of the development of the graphical user interface (either as markup language or GUI code) from the development of the business logic or back end logic known as the model (also known as the data model to distinguish it from the view model). The view model of MVVM is a value converter[4] meaning that the view model is responsible for exposing the data objects from the model in such a way that those objects are easily managed and consumed. In this respect, the view model is more model than view, and handles most if not all of the view’s display logic (though the demarcation between what functions are handled by which layer is a subject of ongoing discussion[5] and exploration). The view model may also implement a mediator pattern organising access to the backend logic around the set of use cases supported by the view. History[edit] Microsoft MVP Josh Smith reported[6] that A notable Javascript implementation of this pattern is Knockout.js. Timeline[edit]

Microformats Jer's One Stop Shop > Home - MVVM for Tarded Folks Like Me *or* MVVM and What it Means to Me MVVM has been a trending topic lately. And why shouldn’t it be? People want to build great WPF/SL applications and want guidance on how to build them using the framework’s strengths. If you are anything like me, you started your WPF/SL career, learning the framework classes and hierarchy. I’m going to go out on a limb and make a wild assumption. Beginner’s MVVM Challenge #1 |or| Takin’ You Down to MVVM Town So we want to begin our journey into MVVM town by way of Bindingopolis. A model is a class that has your data. class Model public string Name { get; set; } public string Address { get; set; } A view is, for the sake of explanation, is a UserControl. /// Interaction logic for View.xaml public partial class View : UserControl public View() InitializeComponent(); A View-Model is, again, just another class. class ViewModel : INotifyPropertyChanged private Model m_model; public ViewModel() m_model = new Model(); public string Name get { return m_model.Name; } set if (m_model.Name ! if (changed ! Grid >

About RDFa - Webmaster Tools Help Marking up content using RDFa RDFa is a way to label content to describe a specific type of information, such as a restaurant review, an event, a person, or a product listing. These information types are called entities or items. Each entity has a number of properties. In general, RDFa uses simple attributes in XHTML tags (often <span> or <div>) to assign brief and descriptive names to entities and properties. <div> My name is Bob Smith but people call me Smithy. Here is the same HTML marked up with RDFa. <div xmlns:v=" typeof="v:Person"> My name is <span property="v:name">Bob Smith</span>, but people call me <span property="v:nickname">Smithy</span>. Here's how the sample works. The example begins with a namespace declaration using xmlns. Nested items The example above shows contact information about Bob Smith. It is common for one information type to include another. For more examples, see Nested items. Non-visible content

MVVM for Dummies I think that I have found one of the best articles on MVVM that I have ever read: This article sums up what is in MVVM and what is outside of MVVM. In WPF a lot of use is made of the Decorator and Behaviour pattern as well. C# – Ideal public partial class IdealView : UserControl { public IdealView() { InitializeComponent(); } } Figure: This is the ideal code behind for a Control / Window / Page when using MVVM. C# – Compromise, but works public partial class IdealView : UserControl { public IdealView() { InitializeComponent(); this.DataContext = new IdealViewModel(); } } Figure: This is a compromise, but the best you can do without Dependency Injection VB.NET – Ideal Partial Public Class ServerExplorerConnectView End Class VB.NET – Compromise, but works

Sketch2Photo Sketch2Photo: Internet Image Montage Tao Chen1 Ming-Ming Cheng1 Ping Tan2 Ariel Shamir3 Shi-Min Hu1 1TNList, Department of Computer Science and Technology, Tsinghua University 2National University of Singapore 3The Interdisciplinary Center Abstract We present a system that composes a realistic picture from a simple freehand sketch annotated with text labels. The composed picture is generated by seamlessly stitching several photographs in agreement with the sketch and text labels; these are found by searching the Internet. Paper Sketch2Photo: Internet Image Montage ACM SIGGRAPH ASIA 2009, ACM Transactions on Graphics, to appear Tao Chen, Ming-Ming Cheng, Ping Tan, Ariel Shamir, Shi-Min Hu System Pipeline Retrieval Results Composition Results Video Supplementary Materials 1. General supplementary materials, including intermediate results and comparisons. 2. High resolution compositions and detailed statistics of the user studies. Sktech2Photo Team Acknowledgments Note Original Name: PhotoSketch.

Patron de conception Un article de Wikipédia, l'encyclopédie libre. Pour les articles homonymes, voir Patron. En informatique, et plus particulièrement en développement logiciel, un patron de conception (en anglais : design pattern) est un arrangement caractéristique de modules, reconnu comme bonne pratique en réponse à un problème de conception d'un logiciel. Les patrons de conception décrivent des procédés de conception généraux et permettent en conséquence de capitaliser l'expérience appliquée à la conception de logiciel. Les types de patrons[modifier | modifier le code] Les patrons de conception ne sont ni des patrons d'architecture ni des idiotismes de programmation. Description[modifier | modifier le code] Les patrons servent à documenter des bonnes pratiques basées sur l'expérience. Histoire[modifier | modifier le code] Citations[modifier | modifier le code] Formalisme[modifier | modifier le code] La description d'un patron de conception suit un formalisme fixe : Ci-dessous, les 23 patrons GoF : Adapter Bridge

RDFa vs microformats from Evan Prodromou I'm fascinated by the idea of including semantic markup in Plain Old XHTML pages, and I'm excited by recent developments in this area. But I'm also concerned about the growing discrepancy between the W3C's initiative, namely RDFa, and the more established but conversely less official microformats effort. I think that having competing standards efforts in this area is going to hurt the advancement of so-called small-s semantic Web technologies, which is going to be bad for everyone. Using XHTML as its own metadata substrate makes for some interesting applications, some of which are starting to disseminate on the Web. Rubhub is an interesting distributed social network analyzer; Flocktails is a fascinating example of extracting semantic data ; Ray Ozzie's Live Clipboard shows how to use embedded HTML data objects to make rich browser-based applications. On the surface, the two systems are remarkably similar. Examples An example is probably in order. Differences Collision ahead

LE MOTIF Model-View-ViewModel DESIGN (MVVM) pour WPF Patterns WPF Apps With The Model-View-ViewModel Design Pattern Josh Smith Developing the user interface of a professional software application is not easy. There are popular design patterns that can help to tame this unwieldy beast, but properly separating and addressing the multitude of concerns can be difficult. It is not always the design patterns at fault. As the software world continues to adopt WPF at an increasing rate, the WPF community has been developing its own ecosystem of patterns and practices. By the end of this article, it will be clear how data templates, commands, data binding, the resource system, and the MVVM pattern all fit together to create a simple, testable, robust framework on which any WPF application can thrive. Order vs. It is unnecessary and counterproductive to use design patterns in a simple "Hello, World!" Developers often intentionally structure their code according to a design pattern, as opposed to letting the patterns emerge organically.

What’s Best: Microformats, RDFa, or Micro Data? | SEMClubHouse - Key Relevance Blog In a recent post by Mike Blumenthal about Google’s announcement of supporting Microformats for local search, Andy Kuiper asked in the comments whether it would be best to go with Microdata versus RDFa or Microformat for marking up local business information. As the number of flavors of semantic markup have grown, I think Andy’s not the only one to wonder which markup protocol might be ideal. Here’s my opinion. When you’re asking “which is better?” It’s this last orientation of the question that I’m focusing upon — which semantic protocol is going to work best for Search Engine Optimization (“SEO”)? Now, you might think that since I was probably the earliest marketer to recommend using Microformats for SEO that I’d feel so “invested” in the protocol that I might push it exclusively. Microformats have been established the longest of the three protocols, and used by the search engines the longest. So, which is best for SEO purposes?

Related: