You can use the Gradient Tool in Blend to adjust a radial gradient, as well as a linear gradient. Below is a radial gradient that transitions from a darker green at the center of the region to a light green at the outside of the circle. When you click on the Gradient Tool, you’ll see an arrow appear in [...]
The perhaps most obvious difference between Windows Phone and Windows 8 is that XAML is no longer a part of .NET in Windows 8. The reason for it being so obvious is that all references to System.Windows breaks the build. Simply put – XAML now resides in Windows Runtime instead of .NET.
The problem is quite easy to fix. In this post we will discuss why XAML has moved and how you deal with it. This post is a part in a series - you can find the full index
Phone | Introduction (1 of 12)" href="http://blog.jayway.com/2012/04/04/converting-to-windows-8-from-windows-phone-introduction-1-of-12/">here.
Why move it?
In order to understand why they have made the trouble to move XAML I think that we first need to look at all languages and technologies that can be used building Windows 8 metro applications.
...(Read whole news on source site)
by Jason Lee
Electric effect, like some other effects such as flame, smoke, explosion, is one of the most common factors used in games. However, not too many examples are found, even fewer were proved ready for mobile application use. So I am here to talk about how we can "invent" one. Following picture shows the final electric effect I implemented on Windows Phone 7 using XNA:
...Read the full article
Last night when I was doing some WinRT hacking I was trying to setup databinding to the selected item in the GridView control and I ran into a gotcha that I thought I would share. First, I was using the ‘Split Application’ template for my C# project. This is important because this template will create a bunch to boiler plate code for you and I was taking this code and extending it. When I was setting up my SelectedItem binding had had the following Xaml When I ran the app
everything ran fine but when I selected an item nothing happened. I quickly noticed what I thought was the issue, I had not enabled selection in the grid, aka SelectionMode=Single, so I added that. This made my Xaml look like:
I gave this a spin but nothing….. Then I had a thought, maybe the bindings which allowed the Item to be clicked was causing this, turns out I was right. The boiler plate code does not use MVVM (a real shame and IMO this needs to be addressed by MS)...(Read whole news on source site)
The question came up several times in the mailing list with regards to how the RavenDB Authorization Bundle operates, and I think it serves a broader discussion. Let us imagine a system where we have contracts, which may be in several states: Mine – Contracts that an employee signed. Done – Standard users can view, Lawyers assigned to the company can sign. Draft – Lawyers can view / edit, Partners can approve. Proposed – Lawyers can create / edit, but only the lawyer that created it can view it, Partners can accept. So far, fairly
simple, right? Except the pure hell that you are going to get into when you are trying to show the users all of the contracts that they can see, sorted by edit date and in the NDA category. Why am I being so negative here? Well, let us look at what we are going to have to do in the most trivial of cases:
In this sort of system, we are going to have to show the user all of the contracts that they are allowed to see, and show them some indication what operations they can do...(Read whole news on source site)
is one of the most useful frameworks out there for web development. And while most of jQuery is very much about working with the browser DOM there is also another side to it that makes doing networking real easy and that is all based around the $.ajax()
and related, like the $.getJSON()
, functions. Now HTML5 contains a real useful part in Web Workers
for doing work that should not block the background thread. And using the XMLHttpRequest
for network IO is fine in a Web Worker. Unfortunately however working with the DOM
is not ok in the Web Worker, which makes total sense, but as a result using jQuery, which has lots of DOM related code is not fine in a Web Worker. And that is a shame because using jQuery for just network IO would be much easier that the XMLHttpRequest and totally fine if it would load. So removing the DOM code from jQuery should solve the problem right? Enter the jQuery - No DOM Edition
It turns out Konstantin Pozin
did just that with the jQuery -...(Read whole news on source site)
In the previous article of this series, we wrote our first lines of code for WinRT. The main message was that although WinRT is a new API, we can still use our familiar languages to create Metro style applications. We have used the XAML/C# combination, but it’s perfectly possible to use XAML/VB or XAML/C++ as well. We’ll be using more of the API in the coming articles but in this article, we’ll focus on some specifics around contracts, more specifically, the Search contract. Contracts enable Metro applications to communicate with each other or with Windows itself without there being a
In this development tutorial series we are going to cover another new feature given to developers with the "Mango
" SDK; Background Agents. Background agents give the ability for an application to run code in the background. This can be a reminder, toast notifications, or file transfers just to name a few. These background agents come in two flavors, either a Period Agents or Resource Intensive Agents. A periodic agent runs for brief period of time at a regular interval. A resource intensive agent runs for longer periods of time in a one-time occurrence. For
this tutorial we are going to use a periodic agent in this tutorial to demonstrate how to implement and code it. Jump below for a look at the code and see how to implement a periodic agent. ...Read more
...(Read whole news on source site)
source: blogs.msdn GOT XNA? WRITING AN WINDOWS PHONE GAME? WANT A SHOT AT THOUSANDS OF DOLLARS?
Here's the short version. Over 14? Write a cool Windows Phone Game and submit it to the Dream,Build,Play
site. You could win up to $20,000. Yep, that's it. In a nutshell. So on to the long-winded stuff. Windows Phone
the prizes are $20k, $10k, $5k, and $2500 respectively. The top 20 finalists will also get Phones. Want some inspiration, check out last year's XBOX winners at https://www.dreambuildplay.com/main/winners.aspx
It was a long weekend here in the UK and it rained a little and so I had a bit of spare time to put together a make-it-up-as-you-go-along screencasts around a simplistic Windows 8 metro style app that lets me play music from albums found in my music library...(read more