laplink gold 2008 downloadkpt filters for photoshop cs5 free downloadkaspersky internet security 2013 download freemicrosoft visual basic 6 0 free download full version
Expression Web is usually a full-featured professional tool for designing, developing, and publishing compelling, feature-rich websites that in accordance with web standards.
Expression Web 4 provides you with the tools you should produce high-quality, standards-based Web sites: built-in support for todays Web standards, sophisticated CSS design capabilities, and visual diagnostic tools. Whether you use PHP, HTML/XHTML, CSS, JavaScript, or AJAX, Expression Web can make it faster and much easier to create and observe after exceptional sites.
Please note: This free version of Expression Web isn't eligible for Microsoft tech support team and is community support. For more information, go to the Expression Community site.
For additional language downloads for Expression Web, please select one of many following:
Windows 7, Windows 8, Windows Vista, Windows XP
Support for Microsoft DirectX 9.0 graphics with Windows Vista Display Driver Model WDDM Driver, 128 MB of graphics RAM or even more, Pixel Shader 3.0 in hardware, 32-bits per pixel
Some product features require FireFox 3.0 or later, Internet Explorer 8
Actual requirements and product functionality are different based on one's body configuration and computer.
Get the free email app for iOS, Android, and Windows.
The proliferation of rich interactive web applications over the cloud and mobile phones continues to make new opportunities for creative design and development. As these technologies evolve, Microsoft is focused on providing best-in-class tools for building modern applications. In support of the industry trends Microsoft is consolidating our lead design and development offerings Expression and Visual Studio to supply all in our customers a unified solution which brings together the most beneficial of Web and modern development patterns.
Blend continues to ship like a standalone tool with Visual Studio 2012, together with a consolidated designer/developer offering. Blend for Visual Studio 2012 comes with a rich design-centric environment for building Windows Store apps and Windows Phone apps. In addition, WPF, Silverlight and SketchFlow support is obtainable today as being a preview and are released in Visual Studio 2012 Update 2.
Expression Studio 4 Ultimate and Expression Studio 4 Web Professional are not available for sale. For customers who previously purchased these items, all components within Ultimate and Web Professional is going to be supported through their support lifecycle.
Expression Design 4 and Expression Web 4 are actually available for download free of charge. Technical support will not likely be designed for these free versions.
Expression Encoder 4 Pro is no longer designed for purchase. Expression Encoder 4 remains intended for download free.
Additionally a Preview version of Blend for Visual Studio 2012 that supports Silverlight and WPF editing, together with SketchFlow can be acquired. With this addition, developers can leverage a consolidated tool for all your platforms, included in a fully integrated solution with Visual Studio.
We are devoted to releasing a production-ready version of Blend that supports these platforms from the upcoming Visual Studio 2012 Update 2. Please check back within the availability when you go to the Visual Studio website.
The web is about applications together with traditional internet sites, this also requires a new list of tools. Microsoft is invested in offering a unified way of focus on web page design and development features in Microsoft Visual Studio 2012.
As thing consolidation, Microsoft Visual Studio 2012 provides leading website design tool, which permits you to design, develop, and gaze after websites and web applications. Visual Studio 2012 helps it be easy to develop CSS-based websites through the ground up with new CSS layouts, HTML5 support and full featured capabilities for dealing with and debugging JavaScript. Learn more about Visual Studio Express 2012 for Web and WebMatrix 2.
Expression Web is actually available being a free download on the Microsoft Download Center, with out new versions is going to be developed. Customers who previously purchased Expression Web will get support throughout the established support lifecycle.
Expression SuperPreview Remote Beta continue running being a service through June 30, 2013.
Customers are demanding better tools in order to create innovative, user-centric, fast and fluid applications. Going forward, our focus is on building the most effective tools for creating these applications with Visual Studio and Blend for Visual Studio, importing content coming from a range of traditionally used graphical tools.
Expression Design has become available to be a free download in the Microsoft Download Center, without new versions is going to be developed. Customers who previously purchased Expression Design in Expression Ultimate or Expression Web get support over the established support lifecycle.
Going forward, Microsoft is continuing to buy encoding, format conversion, and live on-demand streaming like a part of Windows Azure Media Services.
Expression Encoder 4 Pro is no longer intended for purchase. It are going to be supported for your remainder of that support lifecycle with out new versions is going to be developed.
Additionally, the free version of Expression Encoder continues to be intended for download.
Whats the main difference between the free and paid versions of Expression Web and Design?
The features and functionality are the same between free download and paid versions. The key difference would be that the free versions aren't supported, meaning they are presented as-is without Microsoft tech support team is available they are supported through community.
How do I get tech support team for Expression products?
If you obtain Expression Studio Ultimate, Expression Web Professional or Expression Encoder Pro: youre qualified to receive the same support as today via assisted support, self-support, and also the community. Support is obtainable on the Expression support webpage.
If you did not purchase Expression Web or Design and therefore are using a free version: they are supported through community.
I recently purchased Expression Studio 4 Ultimate or Expression Studio 4 Web Professional and would really like a refund.
Contact the retailer you got it from to find out if your purchase was in their return policy.
North America: submit your refund request throughout the Microsoft Money Back Guarantee program.
Outside of North America: contact the nearest Microsoft subsidiary for assistance.
I have Expression Studio 4 Ultimate and/or Web Professional by using a MSDN, MPN, BizSpark, WebsiteSpark, or DreamSpark subscription. Will the supported versions in the software be for sale to me?
You continues to have access to the identical software and support for Expression.
The team blog on the Expression Blend and Design products.
We released important news today regarding the Expression category of products. Please go to the Expression Community site for details.
If you've got watched the BUILD keynotes and sessions, you might have seen some exciting reasons for Expression Blends support for Metro-style applications.
For all future news and updates concerning Expression Blend, kindly visit our new team blog called BlendInsider. The BlendInsider blog can provide the types of content you found hereand hopefully a lot more!
This blog are going to be kept around for archival purposes, but no new content will probably be added.
As imaginable, right after a major release like there were, the majority of us shift our focus slightly towards discussing and sharing the way you use some from the cool additional features we released. In this initially a two-part series, I hope to generate up with the long period of inactivity with this blog by sharing two Windows Phone focused videos that Unni, Billy, and I recorded for Channel 9.
The first video for this list is certainly one that walks you through, for a breakneck speed, most from the new features we put into Expression Blend that helps make building Windows Phone 7 apps easier:
Through the guise to construct a Bing Search application, I cover features starting from our Device Panel to Application Bar support to cooking Sample Data from your Class file. You can learn more about these characteristics by taking a look at some of my more in-depth Windows Phone 7-focused articles.
The templates they created cover a wide choice of common UIs that you see, so utilize these directly is likely to projects or simply to be a source of inspiration. Before you can inflict of that, obviously, download the templates from codeplex first.
As always, if you might have any questions, twenty-four hours a day comment below. If you recorded some interesting videos, post them inside comments also.
Today, we now have released the ultimate version in the Windows Phone Developer Tools. You can download it below:First, download everything required below:
This installer will automatically install free, phone-flavored versions of Expression Blend, Visual Studio 2010, and XNA Game Studio.
If you have now Expression Blend 4 installed, unlike earlier releases, running this installer will remodel your existing version of Expression Blend 4 and provide you the ability to build Silverlight, WPF, and Windows Phone applications:
Thanks to everyone that has provided feedback within the last few number of releases to aid us be able to this stage. As always, if you might have any additional feedback, go ahead and post them around the Windows Phone Developer Forums.
Its been a little while since we released an update for anyone working on Windows Phone 7 projects! Well, wait no longer! Today weve released an new version of Expression Blend that supports all on the latest changes created to the Windows Phone 7 runtime in conjunction with some cool extra features.
First, download everything required below:
As you can view, you no longer require to download and install Expression Blend separately. You can just run misused Windows Phone Developer Tools installer and acquire Windows Phone variants of Expression Blend, XNA Game Studio, and Visual Studio at no cost.
This version of Expression Blend installs and runs side-by-side with Expression Blend 4 simply supports dealing with Windows Phone projects.
As mentioned earlier, beyond supporting the changes created to the runtime ever since the last release, weve added plenty of new functionality that creates designing Windows Phone 7 applications easier. Some on the more notable features are described below.
Because your applications can be looked at in different orientations, themes, and accent colors, weve made it easier for one to visualize within Expression Blend what the job would seem like.
The Device Panel now will provide you with easy entry to preview between Landscape and Portrait orientations, Light and Dark themes, and Accent color.
For example, here can be a preview of what the application looks like inside default Dark theme:
This allows one to design and make certain that your applications look and the choice of want in spite of which light/dark mode the consumer has their phone in.
Windows Phone 7 applications emphasize consistent utilization of text to be a key design element. To make it easier for one to preview and apply existing text styles, weve added the cabability to preview inline that of a particular text style would seem like:
In this release, we've got exposed an extremely early preview of the support for allowing someone to design the Application Bar. You contain the ability to make an Application Bar, add Application Bar Buttons, and add Application Bar Menu Items. Because Application Bar Buttons display a 48x48 PNG icon, it is possible to specify your individual icon or pick coming from a collection of icons we've got provided in your case:
A future post will check out in greater detail using what you could have today to design a practical Application Bar!
Because Windows Phone applications are certainly page centric, we decided for making navigating between pages easy. To navigate in one page to a different, we exposed a Navigate To context menu:
This menu might be accessed once you right simply click any element that you simply wish to start the navigation when clicked.
We have revised the FluidMoveBehavior being on par together with the improvements we generated for Silverlight 4 4. You can learn more by what this means by reading Kenny Youngs blog post with this topic.
Unlike Silverlight and WPF in which a full keyboard for input is practically always guaranteed, Windows Phone users might not have that luxury when implementing their phones. While a on-screen keyboard can be acquired, because of the size from the screen, obtaining the full keyboard with all on the keys appear on-screen will not be ideal for every situation either. It may be useful to users if your keys displayed were optimized to the type of information they can be entering during that particular moment.
To address that want, we improved our support for your InputScope property on TextBox that allows that you specify what sort of data will probably be entered:
For example, if Number was selected for that InputScope over a TextBox, is going to do the on-screen keyboard appears to be when you target it about the emulator/device:
Notice that you are certainly not seeing the conventional full keyboard. Instead, you might be seeing a keyboard optimized exclusively for numerical input.
As always, if you could have any questions or feedback, please go ahead and comment below or post on our forums.
A couple weeks ago, several Expression Blend downline presented on the TechEd conference kept in New Orleans this season!
You can search all in the sessions on this link.
Creating attractive looking and functioning applications is hard. It requires using a good eye for design, almost all requires some technical exposure to how to generate the design functional.
As you may probably guess, it's our goal to assist you use Expression Blend, Visual Studio, and our related tools to generate those great applications. We spend a lot of time adding the latest features and making existing features better that can help you just do that. Making improvements to your applications is simply one side of how we try to assist you create great applications, however.
The medial side involves letting you better realize how to actually create great applications, and now we try healthy to provide some valuable training resources. Some notable shoutouts include plus the Expression Community sites. While taking a look at videos or reading tutorials pays to, we wished to go further as well as provide you which has a library of xamlcode samples that showcase something small, something specific, something cool. We felt that, most of the time, simply being capable to deconstruct how something was done could be equally or more useful in learning to do something.
This library of xamlcode snippets, known better by its family and friends as the Pattern Library, lives for an extension towards the Expression Gallery:
You can learn more regarding the Pattern Library by reading Lars Powers newsletter article introducing it.
Please do download and use the patterns. If there is something you sense is missing, please feel to permit us know or maybe create it yourself and upload it.
Today at Internet Week in NYC, we announced the provision of Expression Studio 4. You can download the trial of Expression Studio 4 Ultimate that features Expression Blend 4 and SketchFlow by clicking below:
Keep watching your blog for more news, updates, and in-depth talks about some with the new features that weve introduced. Until then, below are a few related links:
Note that if you happen to be currently doing Windows Phone development, please not upgrade to a final version of Expression Blend 4 yet. We will release an new version of the whole phone components within the future, so please carry on using Expression Blend 4 RC.
Of course, no major release could well be possible minus the feedback all of you've provided, so thanks!
While the PathListBox control gives an easy way to set down items along a path, developing a carousel control that appears 3 dimensional and has now smooth scrolling requires additional functionality that individuals did not have time and energy to do in Expression Blend 4. Ive made the PathListBoxUtils sample on CodePlex to provide the instruments that make developing a carousel much like the one shown below a breeze:
Visit the Carousel tutorial to find out how to generate this example, and you may view all PathListBoxUtils-related tutorials here.
Its been a bit since the last article where I promised to create about all on the behaviors that ship with Expression Blend in greater detail. Ill try to get more prompt within the future. Today, lets look on the ControlStoryboardAction and also the StoryboardCompletedTrigger.
Storyboards are on the list of primary ways you create animations in Silverlight, WPF, and Windows Phone using Expression Blend. Creating a storyboard is rather easy, but actually utilizing a storyboard for example having it play will not be. To help using this, you might have the ControlStoryboardAction.
Simply put, the ControlStoryboardAction can be an Action that allows you to definitely select a storyboard and specify what you would love to do for it:
Lets check out some from the properties it includes in greater detail.
When looking at this behavior, you will discover only two properties that you have to concern yourself with. They are the ControlStoryboardOption and Storyboard properties.
From here you may choose whether you would like to play a storyboard, stop it, toggle between play/pause, pause, resume, or jump for the end.
The only missing piece thus far is knowing which storyboard to affect. Not to worry, since you specify the storyboard utilizing the aptly named Storyboard property:
This property are listed all with the Storyboards your behavior has having access to. Once you've got selected a Storyboard, you're done!
This trigger invokes an Action each time a specified storyboard set with the Storyboard property has fully be completion. Of course, because it is usually a trigger, you'll be able to use it with any Action.
In Expression Blend 4, one of many new samples we added is termed MockupDemonstration. If you havent were built with a chance to apply it yet, it is possible to open MockupDemonstration through the Welcome screen, which can be obtained when you first start Expression Blend or if you click Help after which click Welcome Screen. In the Welcome screen, click Samples, and click MockupDemonstration:
As you may tell quickly from exploring this sample, this sample includes a handful of controls designed to aid you create prototypes easily. The catch is the fact that these controls only exist within this particular sample. Since some of you've got requested that it could be useful to obtain these controls available outside in the sample, this short article will explain how to create these mockup controls accessible in other projects.
To enable mockup controls for virtually every SketchFlow project, copy the mockup controls run-time and design-time assemblies from your MockupDemonstration sample on the pre-configured Libraries folder using the steps below:
1. Copy both and Design folder from:
for WPF projects, follow this method but copy files from Libraries Debug
2. Add copied files to your following destination:
Computer OS C: Program Filesx86 Microsoft Expression Blend 4 Libraries Silverlight 4.0
for WPF paste the copied files from your NETFramework folder inside the previous the answer to Libraries 4.0
3. Restart Blend. You may now start using mockup controls by clicking the Mockups category inside Assets panel the right assembly reference is automatically included in your project.
If you might have any questions or comments, please go ahead and post below or on our forums.
At MIX, we released a young preview individuals support for building applications for Windows Phone 7 that only ran over a pre-release version of Framework.
If you've been delaying on upgrading for the latest versions of Expression Blend, Visual Studio, 4, wait forget about! Today, we in conjunction with the Windows Phone team are releasing an update for the components we released a few weeks ago to work for the final version Framework 4.
Besides the RC posted above, you will want the following components installed for developing Windows Phone apps:
Besides support 4, there are some general improvements towards the overall design experience, emulator updates, and breaking API changes. You can get a broader overview within the Windows Phone Developer blog.
As always, we like to hear from you. Please you can comment below or use our forums here.
As almost all of you know, yesterday we released the making candidate version of Expression Blend 4. Shortly after the majority of you experienced a chance to use it, several of you reported that Expression Blend crashes during launch.
If you're one of these people whose Expression Blend crashes after launch, please download this minor revision on the release candidate we released yesterday:
If you arent having any problems launching Blend, you don't need to upgrade. There are no latest features or changes besides some changes to produce sure Expression Blend runs properly on launch.
We were capable of detect this problem thanks largely with the error reports those of you on this crash submitted. We constantly proceed through all with the crash reports we receive, and now we try to fix as lots of them as you possibly can.
While produce your own . you never must experience crashes from running Expression Blend, should you experience this brief, please submit the big mistake reports!
Recently, one more versions of both Silverlight 4 4 happen to be released! To coincide using this, we're also releasing a release candidate version of Expression Blend 4 that it is possible to use to a target them:
There are two things that you simply really need to learn about this release.
First, if you might be doing Windows Phone development, you ought not use the Expression Blend 4 RC. We will produce an update available for you soon with updated components, but from the meantime, please use Expression Blend 4 Beta.
Second, this relieve Expression Blend 4 targets a final versions of Silverlight 4 4, you'll be able to share your creations together with the rest on the world. You no longer are tied to only sharing your creations in source code form or private testing.
If you havent a chance to read the sessions from MIX10 that showcased Expression Blend 4, backlinks below should allow you to out:
Authoring for Windows Phone, Silverlight 4 and WPF 4 with Expression Blend
This post only focuses for the sessions from MIX which might be Expression Blend specific. By now, all from the sessions from MIX should be around online, so head over for the MIX Sessions page to look at more: /Sessions
Click here to observe Kennys MIX 2010 session that covers a lot on the topics which you see in the following paragraphs.
In Expression Blend, weve been thinking to get a loooong time about how to generate it ever easier to produce great animated visual effects quickly on top from the Silverlight and WPF runtimes. Weve been taking a look at large-scale animation needs since Blend 2 SP1 and steadily building features to treat those needs, so we think weve reached critical mass. With Blend 4, we've a compelling number of technologies that work well very well together.
This blog post can be a companion on the Dynamic Layout and Transitions demo app that weve placed inside Expression Gallery at /en-us/DynamicLayoutTrans. That app reveals the features whose motivations are described here.
Since its inception, Blend has offered keyframed editing of Silverlight and WPF properties via Storyboards. While I wont enter into specific particularly that here, it forms the basis for all you features described below. Some of these characteristics work straight from Storyboards you create as well as others create Storyboards behind the scenes as your representative and sometimes both.
Lets start with turning time back 24 months. In Expression Blend 2 SP1, we introduced the States Panel, which edits VisualStates and VisualStateGroups for Silverlight 2 and WPF 3.5 with all the WPF Toolkit. This introduced the notion of an state being a means of communication between visuals and code, making it it dramatically much easier to describe a number of visual changes. Based on input, the control code could decide ought to enter what state, and also the visuals would decide what changes were within that state plus just how long it popularized transition between any set of states it's advisable most state changes for taking 0.25s, but want Pressed state changes to get instantaneous.
This proved to be an incredibly effective tool, but it really had limitations. The core VisualStateManager runtime which well call VSM in the future could only do linear interpolations in the values being set. This is very rewarding for opacity and transform offsets, but doesnt work effectively for discrete properties or data that isnt known until runtime. Also, not every animation scenarios are impelled by state changes. So we put our thinking caps on about how precisely we could have more scenarios to be effective in a way that designers could rapidly tool the impact.
In V3, we added four primary enhancements in this region. The first was EasingFunctions, that happen to be critical to making property animations contain the right feel. Weve got all of the classics quadratics, cubics, bounce, elastic, etc. Plus, you are able to write your EasingFunction in C or VB and put it to use to any animation you'll want. This is all supported in Silverlight 3 and WPF 4. EasingFunctions might be applied with an individual animation or keyframe, and you'll be able to apply a default EasingFunction on your entire state transition.
The second became a GoToStateBehavior in addition to Blends Behaviors engine, which made it an easy task to program your entire state change logic directly inside markup without code. Like all of Blends Behaviors, you may simply drag it from my Asset Panel onto any elements you decide on.
Those two enhancements just made the previous scenarios run better. We also wanted to treat new classes of scenario. The first one we tackled was the situation of elements relocating a StackPanel or WrapPanel. Traditionally, these 4 elements have snapped into place just as one application changes elements or changes size, therefore we wanted an even transition that users could control. So we introduced the FluidMoveBehavior to create it feasible for an element to look at the layout manager because it gone to live in a new spot, and lessen its progress through an animation controlled by some of those EasingFunctions we described earlier. So now its easy to own your elements animate into place for a speed you end up picking!
Heres a picture from the feature doing his thing. Theres get rid of room around the first line for that purple rectangle, so its moving towards the beginning with the second row plus the other elements are moving to produce space. Technically, from the layout perspective, the next thunderstorm in motion are in reality at their destinations already but by adding the correct transforms ahead, we have the change look smooth in the visual perspective that users worry about.
The fourth enhancement we made was probably the most challenging for individuals. We remarked that many times, customers wanted different states inside their control to possess different layouts entirely, yet still respond to active layout changes inside application. For example, one layout will often have a list of task panes visible away from working area, and another probably have one or higher of these panes hidden. Customers planned to describe these different layouts with states to have a good separation between their visuals along with their business logic, though the properties that was required to change between these states werent properties that might be smoothly interpolated. For example, how can you interpolate between and?
What we learned was that within the like these, users werent satisfied together with the direct property animations that the system after they just wanted it to appear right, and so that it is look right required we animate a morph with the change instead of the change itself. So we wrote a train locomotive that would please take a layout snapshot prior to the state change, take another layout snapshot following the state change, and create an even morph relating to the start and end positions, employing the duration and EasingFunction with the users choosing. We dubbed this FluidLayout, and you are able to turn it on here:
Just click that little button, and your entire layout modifications in that VisualStateGroup are going to be animated between states regardless if it seems impossible. Well even simulate a Visibility change through an opacity simulation. Note that youll convey more success in the event you click this before you begin making layout changes otherwise, if you move an item, itll create translate/scale animations which don't respect layout, because thats the very best that the conventional VSM are able to do.
Its hard to accomplish justice to the feature in a graphic, but heres my best attempt. In this situation, the Timeline Pane is inside the process of shrinking on the leftmost column, which I configured by changing the Panes property in a very state. Similarly, I changed the RowSpan with the pink rectangle, and it is from the process of accelerating taller being a result.
In Blend 4, weve managed to adopt these themes further, and have absolutely three more toys for designers to have fun with. Lets start with animating things in and out of lists. In V3, you might apply a FluidMoveBehavior for a ListBox, plus the other items would dutifully make room on your new item or up close the space. But there wasnt any easy way to effectively control an item that was itself being added or removed; in the event you were clever, you might rig up some events to generate an element animate on entry, so you had to get really really clever and pollute your computer data model in unfortunate ways for making an element animate on exit. We worked closely with all the Silverlight team to create a solution here that you may tool effectively, and it is called LayoutStates. To find them, first edit the ItemContainerStyle:
And then, note these three new VisualStates within the States Panel:
You will use these states to model what an element seems like just before its loaded, what it seems as if after its been loaded, and what it seems like just before its unloaded. Silverlight are able to animate hawaii changes for you for the appropriate times, because your items are included in or removed through the list. Remember to include a FluidMoveBehavior towards the ItemsPanel template note its presence from the Edit Additional Templates submenu, a number of pictures above, as well as set AppliesTo Children, for getting the additional factors to move out with the way. Note if your ItemsPanel is often a VirtualizingStackPanel, your ListBox ought to have set to Standard, or else you should learn on the list of other new tricks below.
Heres an illustration of this doing his thing the middle item is definitely entering their list.
The next feature we added is another inside the vein of simulation. In V3, we added FluidLayout to VSM so as to get an even and realistic morph between two states, nevertheless it got us to thinking in regards to the other sorts of morphs we might perform. Enter TransitionEffects. Whereas transition effects in video editing give a pixel-based transition from a single video clip to an alternative, Blends TransitionEffects supply a pixel-based transition in one state completely to another. In Blend, a TransitionEffect is often a PixelShader that's an animatable Progress property. We are shipping several these in our SDK, and if you already know HLSL you may write your. Heres how we set one up:
As configured here, all state changes inside LayoutStates group will work a Smooth Swirl Grid pixel-based TransitionEffect, taking one second sufficient reason for a cubic ease. You can certainly set another transition for just about any individual state change if desired. Some with the TransitionEffects have properties to increase customize them; as an example, Smooth Swirl Grid allows you to control the degree of subdivision plus the intensity from the twisting effect, but those properties are underneath the combo dropdown inside picture. Heres a screenshot of the TransitionEffect for doing things:
The final feature we added is one area that weve been wanting to wrap our minds around for 5 years. Weve seen that in many applications, visuals will move derived from one of part on the application to an alternative even though the visuals in many cases are generated from data. In a true MVVM design the place that the data model ought to know nothing around the visuals, its extremely challenging get these types of effects.
What weve done is train the visuals to learn more concerning the data model specifically, to coach FluidMoveBehavior to associate positions with data as an alternative to with visuals. This requires a little bit of explanation, but is remarkably all to easy to use you may create an animated list-detail example completely from scratch in about two minutes.
What you want is for that large chair within the details view to show up to grow out on the small chair inside the master list. All we've to do is locate the Image element inside the ItemTemplate with the ListBox, and offer it a FluidMoveTagSetBehavior that could register it with all the FluidMove system. That appears like this:
Note which the Tag property shows that element are going to be tagged as outlined by its DataContext, that's the model item behind the visuals. Next, theres a FluidMoveBehavior for the detail Image, which appears to be this:
The other half with the connection is made together with the InitialTag field that is certainly set to DataContext. This means that once the detail element appears, it can consider the registered position of the DataContext for being the place it's going to appear to originated from. And thats the whole lot! Heres a screenshot of their app for action; be aware that in this case I set the FluidMoveBehavior within the entire Grid, so that this details would animate together with the image.
Theres for the better happening behind the scenes, but weve were able to boil this complex scenario to two simple properties. This system can also be used to animate objects derived from one of list to a different list.
If I had included the whole future investigations of this type, this article would be two times as long as it can be already. Were working hard to cope with more and more scenarios inside simplest ways possible. Rest assured that you will be hearing about much more improvements someday inside the not too distant future!
If you could have any opinions or feedback, please you can comment below.
Architect, Expression Blend
As many of you already know, today was the very first day of MIX - Microsofts annual conference for designers and developers. Just like previous years, there has been a great deal of great news coming out on the conference.
The two big things we announced are Expression Blend 4 Beta along with an add-in to Expression Blend that offers you the ability to develop applications with the Windows Phone.
Christian Schormann carries a nice introduction to Expression Blend 4 plus the new features inside, so if you intend to learn more, go read his post.
Of course, there is going to be plenty of posts inside the upcoming days and weeks that dive into detail of what weve released and announced today, so stay tuned for more.
Over another couple of weeks, it seems like like smart to go over some from the behaviors we shipped as being a part of Expression Blend 3. Many of you could have mentioned that you need to learn more regarding the stock behaviors we ship and ways in which they are used, and this blog will likely be a good interim solution with the until we properly add your feedback into our future product documentation.
First through to our list is a of the best behaviors that people shipped, the GoToStateAction!
As you already know, you've got the chance to define and modify your own personal visual states with your applications:
Having a visual state is part products needs to get done. The other part is definitely being competent to switch on the visual state on the appropriate time. For predefined visual states that you simply find within your controls, the mechanism for switching states is created in. For visual states that you simply create on your own personal, you will have to deliver the logic for switching the visual states yourself.
That is when this behavior is available in. The GoToStateAction allows one to easily switch visual states given a proper event using just your Properties Inspector. The following screenshot will show you the standard behaviors UI customized using the properties exposed by GoToStateAction:
Lets look at a few of these properties in greater detail.
Like I mentioned earlier, this behavior primary functionality is in allowing you to definitely change the visual state. How it does may need some further inspection, so lets look for the various properties in greater detail.
The visual state is set through StateName property. By default, you will see every one of the states defined within your root scope ie: UserControl or Window irrespective of where you drag/drop this behavior onto. You can change this by targeting this behavior at another element.
For example, the default target is my UserControl where I have two states defined:
If I were to another element, such to be a Button which has its own states, the StateName list is populated with those states instead:
I spoke a whole lot about changing the target that the states originated from, so lets look on the TargetName property the place that the element you want to target is really specified.
If you would like to target states living somewhere else like another Control or UserControl, you are able to use the TargetName property to affect the element you would like to point to. As mentioned earlier, the default value for TargetName would be the root scope like your UserControl or Window.
If you happen to be trying to select something that isnt easily selectable visually, you'll be able to hit the tiny button to view a flat listing of the of your elements. That is similar to that which you see within the Objects and Timeline panel.
You may switch states suddenly, or it is possible to smoothly transition into states. The UseTransitions property is what controls what your behavior will perform. By default, the UseTransitions property is checked, but it is possible to uncheck it in the event you want a sudden switchover for your new state.
Hopefully this helped provide a summary on the GoToStateAction and exactly how it may be used. If you've any questions, please you can comment below.
For a fixed time, there is often a 30% discount on all Microsoft Expression 3 products Microsoft Expression Studio Expression Web, both full and upgrade versions over the Microsoft Online Store for US-based customers:
No promo code required by any means just go for the store and add to your shopping cart!
Ok, pop-quiz time. Below, you can find two screenshots I took from two different applications:
Can you tell what's different between the two images? If you said which the button from the second image seems a number of pixels off in the image for the top or something similar, you happen to be wrong. The UI depicted in both from the screenshots is exactly a similar. Yes, it was obviously a trick question.
While both applications look almost the identical when run, lets discuss both of the applications when opened in Blend. Here is what the appliance depicted in Screenshot 1 seems like:
As you are able to tell, there is really a major discrepancy involving the first and second screenshot when viewed in Blend. More specifically, the other version from the application seems to become missing some UI plus the button just isn't styled by any means.
The source with the discrepancies have to try and do with what Blend actually shows around the design surface. By and large, Blend is really a XAML editor. Anything defined in XAML, we shall do our very best to display it on our design surface. For visuals defined as part of your code-behind files, you possibly will not always be in a position to see them in Blend.
This is the spot that the differences involving the two apps is a result of. In the initial app, everything was defined in XAML. In your second app, some with the visuals were defined in XAML, but a many in the visuals are not. That is why Blend is simply showing an incomplete subset of what the application actually seems like when you view it within the design surface. This is usually a problem.
The word problem could be a harsh word due to this, however the outcome is lower than ideal should your application is usually a collaborative effort between someone technical and someone less technical. If you're a developer, being capable of visualize code making changes might be straightforward. If you might be more design oriented, thinking about code to define the style and feel of your application is just not natural. You would prefer something that appears to be the application depicted in Screenshot 1 where it is all totally exposed in Blends design surface and you may make changes visually without writing code.
The first and obvious answer that I have is to get you stay away to add controls, define layout, or perform other visual tasks using code. The reason is the fact that, because you saw inside screenshot on the second application, Blends design surface wont be able that can help you out.
Of course, you will find many cases when such an extreme solution won't work. It is common for many people applications to fall under a gray area where visuals are partly defined in XAML and partly defined in code. Fortunately, you'll find some simple steps you may take for making designers more productive while still giving developers the flexibleness to develop the applying.
If you've got visual content that needs for being added programmatically, be sure that content is understood to be UserControls. The reason is that you may define the UserControl to make changes entirely within Blend. Programmatically, you'll be able to add this UserControl which may are actually edited inside Blend to the job without sacrificing the designability from the UserControl itself.
Create Styles in XAML, Apply them Programmatically
Sometimes, UserControls might be a bit excessive. For example, inside second screenshot, I employ a button that may be unstyled:
Instead of which has a dedicated UserControl to wrap your styled button, you may just define the design and style in Blend and programmatically apply the design and style. Lets say you've a style called GreenButtonStyle defined with your Resources panel:
To apply this style in your button, use these code:
GreenButtonStyle as Style;
This allows one to still define the design and feel of your respective Button using Blend, however it is application is handled entirely via code.
Hopefully this post helped provide you with some ideas on the best way to ensure the visuals of you have the opportunity to be modified by Blend. I didnt enumerate all with the various cases, however if there can be something clever which you do to allow developers and designers to function together, please comment below.
Today at PDC, we made some announcements that could well be of interest for your requirements! First, Scott Guthrie announced the availability with the Silverlight 4 Beta. This version of Silverlight contains some cool extra features that many of you could have asked for, so browse the Whats New document to acquire an breakdown of some with the new features.
To coincide with the discharge of Silverlight 4 Beta today and also the release of Visual Studio 2010 Beta 2 a while ago, were making a version of Expression Blend available that allows one to work 4 and Silverlight 4 based projects.
This turmoil Expression Blend successful alongside Expression Blend 3, so you may continue to figure on your WPF 3.5 and Silverlight 3 based projects at precisely the same time.
When using Expression Blend, perhaps the most common task maybe you engage in is utilizing layout. Tasks I commonly associate with dealing with layout involve moving things around, rearranging your order of elements, ensuring everything flows when resized, altering your layout container, etc. For essentially the most part, the alterations you make on the layout of the job are pretty harmlessexcept gets hotter involves DataContexts.
In a nutshell, data contexts allow that you specify the info that elements can inherit and assist. Seems pretty harmless until now. Data contexts may be set on just about anything, but because the details is inherited, data contexts in many cases are placed on parent elements such being a layout container whose children will inherit the information:
What seemed harmless earlier presenting the potential to cause trouble. Because data contexts in many cases are placed on the layout container, also, since data contexts primarily benefit any children listening in, you must ensure that any layout changes you create do not cause important computer data context to sneak. The common ways crucial computer data context can break are:
When a young child is inheriting data, will not reparent a child to a location the location where the data context is not inheritable. This will cause your child to seem for a thing that doesnt exist.
Blend helps it be very easy for someone to ungroup children from your layout container. When you ungroup a layout container which has a data context set onto it, the information context children rely on will probably be lost.
Today, Blend won't let you know if you perform a layout operation that breaks data context. It is up to that you be vigilant, and you will notice which element includes a data context set into it by thinking about its DataContext property:
If this property isnt empty, it implies that a data context may be set upon it. While which has a data context set should never imply that data is in fact being used, it is often a good gauge on whether a layout operation you perform can have any pessimistic effects about the children involved.
One from the goals of Silverlights Visual State Manager technology is to allow you do a substantial amount of control customization while not having to use Blends Timeline, nor even needing to know such a Storyboard is! Feel free to test-drive the Silverlight Button below, after which read on for just a run-down of how easily it could be built.
I begun with some vectors Paths depicting the face area in its normal resting state. Then I used the Tools Make Into Control command for making the artwork right into a template applied in an actual Button. After deleting the ContentPresenter through the template, I selected the MouseOver state within the States pane, so that the modifications I was about for making to the present elements to make a face that appears alert and ready could well be recorded only within the MouseOver state. I moved the head as well as the features upward a bit, and also the rest in the changes involved while using Direct Selection tool to relocate Path points around.
Because I wanted the Pressed state for being a variation within the MouseOver state, I used the Tools Copy State To command to copy all my changes into your Pressed State. Then, together with the Pressed state selected, I adjusted one eye and also the mouth for making the wink.
For the Disabled state I decided I needed new graphics rather then adjusting properties with the existing graphics. So I designed a simplified grayscale version in the face generating that version opaque only from the Disabled state.
For transition timing, I created a quantity of transitions from various states as well as set their durations to taste.
Finally, to ensure each Button instance can customize some aspect from the template, I used template bindings making sure that Brush colors used within the template to get various pieces in the face are likely to properties in the Button instance. So as an example I selected shoulders, then selected Fill within the property inspector, then clicked Advanced property options Template Binding Background. So now, by setting something for Background, Foreground, BorderBrush and OpacityMask, a Button instance on this style set into it can determine the colors on the shoulders, face, hair, eyes and nose.
You can download the sample project files here.
What are these items are they approaches doing precisely the same task? When would I use one out of preference completely to another? Do they all work with all project types?
This post will attempt to answer those questions by describing the animation and control customization tools which can be available to your account in Expression Blend 3 SketchFlow, and discussing what jobs each tool is meant to try and do. Ill be classifying project types along two independent axes: WPF or Silverlight, and Blend or SketchFlow.
In the first relieve Blend, if you desired to change the value of the property as time passes, then this Storyboard was your one option. Using a Storyboard can be known as keyframing. You create a whole new Storyboard or develop a BeginStoryboardAction and allow that workflow build a Storyboard available for you, move the playhead to be able to times after which use the artboard or the house inspector to improve values. Each time you change something, a keyframe is included with Blends Timeline which means that, during this time, the exact property has that value. During the interval between keyframes, the home and property value smoothly assumes intermediate values within a process often known as interpolation. By default, the interpolation between two values is linear, meaning the worth changes steadily after some time to form a straight gradient using a graph. And you may control interpolation between keyframes by describing an easing curve. Whether you are changing the Y coordinate of an bouncing ball, or changing the color of your rectangle within a Button
Storyboards are easily obtainable in all project types. Theyre in the same way useful today as always, plus they are worth learning the way you use, because at some time youll probably must use them. They give you essentially the most control over animation, but control can come with the cost of some effort.
For the duty of customizing the appearance and transitions of any controls visual states, theres another solution and arguably simpler mental model than by using a Storyboard to define the transition to a state. The simpler mental model is that you just draw the control in each of the company's states then, whether it is important for your requirements, specify how much time any in the transitions take. I say draw because thats morally what youre doing; as it happens you opt for a state in Blends States panel, set properties, select another state, and so forth, but youre drafting a static image of how a control looks in each state. You neednt be focused on animation, although its interesting to note which the runtime that supports this mental model that runtime is known since the Visual State Manager, or VSM abbreviated does generate a handoff animation for every single state transition. For practical purposes, drawing states and setting transition durations in this way gets the job done much on the time without needing to determine Blends Timeline in a
Of course you may leverage the Visual State Manager a highly effective UserControls too. This is because states can apply for the level on the individual control inside the MouseOver state a Brush is really a different color together with at the level of the page or scene from the ShoppingCartOpen state an otherwise hidden panel is seen. So, you are able to add states to one within your UserControls that represents a website or scene, set different properties in a variety of states, then use GoToStateActions drive an automobile state alterations in response to events.
The Visual State Manager is fully built-into Blend Silverlight projects and SketchFlow Silverlight projects. You can also use VSM in WPF projects although, as you move the UserControl experience is exactly the same as for Siverlight, you cannot assume all WPF custom controls support VSM. Ive written previously concerning the States panel and WPF controls.
The last tool Ill mention could be the SketchFlow Animation, and also this tool can be obtained in SketchFlow projects only, both WPF and Silverlight. A SketchFlow Animation is logically a storyboard from the true sense with the word: a sequence of frames that tells an account. When youre developing a prototype, you dont would like to implement a function fully so as to demonstrate it. Playing back a scripted example from the interaction you could have in mind has the job done with the prototyping stage. So if you intend to show off how you will imagine you will reorganize and animate responding to an individual dragging a program into the shopping cart solution, you might create a whole new SketchFlow animation after which draw a number of frames showing what sort of product gets dragged between containers and how design of those containers responds, and in some cases specify the easing between frames.
For those that like to recognize how things work in the hood, a SketchFlow Animation is represented internally to be a VSM state group. But you dont need being familiar with VSM try using a SketchFlow Animation. Nor do you should be aware products a Storyboard is, nor be capable to use Blends Timeline. In a sense, each frame or state within a SketchFlow Animation is really a keyframe, but at the macro level to ensure each keyframe defines the whole scene in a point in time instead of the micro keyframes within a Storyboard that comprise a single propertys value for a point in time.
Now that you've an idea products these different pieces do, when theyre available, youll be capable of pick essentially the most efficient tool for every single animation job you want to complete.
As it is likely you know, Silverlight and WPF possess a runtime piece referred to as the Visual State Manager or VSM in abbreviation. As Ill describe on this page, VSM plus the Expression Blend tooling support for VSM lend a pleasant clean mental model on the business of visual states and visual state changes for both custom controls and UserControls.
Although chronologically the storyplot begins with all the control author, Ill focus on that aspect later on this page simply because you can find more people from the world concerned using the visual stuff than with all the logical stuff. The visual aspect begins in Blend, with a group of already-defined visual states organized into groups from the States panel.
You can identify three stages within the design of visual states and transitions. First, the static stage. Here you create each visual state look how you want it to, and you also do so ideally without the thought of transitions. You decide on a state inside the States panel so you change object properties. And speaking in the States panel, this is probably a good the perfect time to introduce the thought of state groups.
Visual states are sorted in such a way that the the states within a situation group are mutually exclusive of each other and b the states within any group are independent with the states found in any other group. This means that one, and then one, state from every group might be applied at a similar time without conflict. An example is really a check box the place that the checked states are separate from, and orthogonal to, the mouse states. Changing an objects property in than one state within a similar group is normal practice. For example, you could possibly change a Rectangles Fill to be able to colors in MouseOver, Pressed and Disabled. This works because just one state in the CommonStates state group is ever applied in a time. But changing an objects property in additional than one state group breaks the independent nature in the state groups and contributes to conflicts where several state is seeking to set exactly the same objects property at precisely the same time. Blend will display a reminder icon which has a tooltip cont
Each state group should contain scenario that represents the default state to the group. CommonStates has Normal, CheckedStates has Unchecked, etc. It can be a good and efficient practice to put objects properties in Base in a way that no changes have to get made in any default state. So, for instance, you'd hide an inspection boxs check glyph and concentrate rectangle in Base and after that show them in Checked and Focused respectively.
So now it is possible to click from the states to substantiate that each looks correct. You can build and run, and test out your states, and also you might even stop by this stage if you're happy which the control switches instantly derived from one of state completely to another. But if instant state switches are certainly not what you want then you may breathe life for your transitions in stage two, the transitions stage. First, add any transitions you want to discover, then set transition durations and easing to them, still from the States panel. And again, in biggest reason so many cases this will probably be enough to your scenario. Whats interesting for all those designers who can visit to this point is the fact there was no requirement to open the Timeline without need being bothered while using attendant concepts with the items a Storyboard is, etc. To keep unnecessary concepts and UI out of one's face, automagically Blend keeps the Timeline closed once you select a visual state or edit a transition duration. You can needless to say open it at any time while using Show Timeline button.
Still from the transitions stage, there could possibly be times if you need a propertys value to improve during the transition from StateA to StateB but, because in the way StateA and StateB are defined, the home and property either doesnt change or doesnt pass throughout the desired value. In this case you have to customize that transition. Select the transition then use the Timeline as normal to define the animations that will take place throughout the transition.
The last stage is dynamic states. If, one example is, you need a blue rectangle to subtly pulse while a control has focus then you will need a steady-state animation. I also contact them in-state animations considering that the animation happens while youre within a state. To accomplish this, just select their state, open the Timeline, and do not delay- keyframe as usual, possibly also choosing the Storyboard and setting repeat behavior and auto reverse.
Now lets find out more about the topic of how states refer to control authoring. Before a designer may start deciding what states and transitions resemble, the control author must decide what states exist. As a control author, your job will not be to think about visual states, but logical states. Forget what it seems as if; precisely what does it mean? You need to consider all of the ways the finish user and perhaps other factors for example invalid data can interact with all the control, and from that thinking build out a group of candidate states; plus the states are logical at now because they don't have any look. Nows the time for you to think about whether your candidate states need factoring. Look for islands of states: closed graphs that do not link to other states. There are two kinds: orthogonal and nested. Orthogonal islands ought to be put of their own state group. An example is the fact that of CheckedStates and FocusedStates. There are no transitions coming from a CheckedStates state along with a FocusedStates state, and also a control is either ch
When a control initializes, it first has for getting itself onto their state graph. This is important. If a control doesnt accomplish this then it really is still in Base after initialization. Base will not be a state; it merely represents the control featuring its local or base property values set, without the need of states applied. When the mouse pointer first moves over this control it should go to MouseOver but it go there from Base, and so the Normal - MouseOver transition won't run the primary time. This is really a subtle bug which the consumer of your respective control cannot fix by defining Base - MouseOver, because Base isn't a state. So once you author your personal templated control or UserControl, you need to define a default state in each state group. Have the control head to those default states if this initializes, and do this with transitions suppressed so who's happens straight away. Once its around the state graph, the control is ready for state transitions that occur so now you'll be able to implement the event-handlers that trigger the transitions
I hope this post has become useful and it has helped clarify some with the less obvious issues with designing and authoring controls to operate well while using Visual State Manager. If you want to discover a walkthrough of some in the ideas presented here, you could potentially try my Button styling video.
2015 Microsoft Corporation.
If you could have watched the BUILD keynotes and sessions, you might have seen some exciting reasons for Expression Blend s support for Metro-style applications.
The second would have been a GoToStateBehavior along with Blend s Behaviors engine, which made it very easy to program your complete state change logic directly inside markup without code. Like all of Blend s Behaviors, you may simply drag it from my Asset Panel onto any elements you end up picking.
The next feature we added is another inside the vein of simulation. In V3, we added FluidLayout to VSM as a way to get an even and realistic morph between two states, however it got us to thinking concerning the other sorts of morphs we will perform. Enter TransitionEffects. Whereas transition effects in video editing offer a pixel-based transition derived from one of video clip to a new, Blend s TransitionEffects give you a pixel-based transition derived from one of state to a different. In Blend, a TransitionEffect is really a PixelShader that's an animatable Progress property. We are shipping several of the in our SDK, and if you realize HLSL you are able to write your individual. Heres how you will set one up:
As many of you realize, today was day one of MIX - Microsoft s annual conference for designers and developers. Just like previous years, there has been lots of great news coming out on the conference.
The word problem can be a harsh word because of this, however the outcome is below ideal in case your application can be a collaborative effort between someone technical and someone less technical. If you might be a developer, being in a position to visualize code to make changes could possibly be straightforward. If that you are more design oriented, considering code to define the looks and feel of the application just isn't natural. You would prefer something that seems as if the application depicted in Screenshot 1 where things are all exposed in Blend s design surface and you may make changes visually without writing code.
The first and obvious answer that I have is to possess you subdue the longing to add controls, define layout, or perform other visual tasks using code. The reason is always that, when you saw from the screenshot on the second application, Blend s design surface wont be able to help you you out.
One on the goals of Silverlights Visual State Manager technology is to permit you do a lot of control customization and never having to use Blend s Timeline, nor even requiring you to know exactly what a Storyboard is! Feel free to test-drive the Silverlight Button below, and after that read on to get a run-down of how easily it is usually built.
In the first turmoil Blend, if you planned to change the value of the property after some time, next the Storyboard was your one option. Using a Storyboard can be known as keyframing. You create a different Storyboard or develop a BeginStoryboardAction and allow that to workflow build a Storyboard to suit your needs, move the playhead to several times then use the artboard or the home and property inspector to vary values. Each time you change a price, a keyframe is included with Blend s Timeline which means that, as well time, the exact property has that value. During the interval between keyframes, the exact property value smoothly has intermediate values in the process referred to as interpolation. By default, the interpolation between two values is linear, meaning the additional value changes steadily after a while to form a straight gradient with a graph. And you may control interpolation between keyframes by describing an easing curve. Whether you're changing the Y coordinate of your bouncing ball, or changing the color of your rectangle in the Butto
For the project of customizing the appearance and transitions of the controls visual states, theres a different and arguably simpler mental model than by using a Storyboard to define the transition in a state. The simpler mental model is that you simply draw the control in each of the company's states then, whether its important to your account, specify the length of time any with the transitions take. I say draw because thats morally what youre doing; as it happens you pick a state in Blend s States panel, set properties, select another state, and the like, but youre drafting a static image of what sort of control looks in each state. You neednt be interested in animation, although its interesting to note the runtime that supports this mental model that runtime is known because Visual State Manager, or VSM in abbreviation does generate a handoff animation for every state transition. For practical purposes, drawing states and setting transition durations this way gets the job done much with the time without needing to find out Blend s Timeline at
For people who like to learn how things work in the hood, a SketchFlow Animation is represented internally as being a VSM state group. But you dont need to get familiar with VSM to utilize a SketchFlow Animation. Nor do you have to be aware products a Storyboard is, nor be in a position to use Blend s Timeline. In a sense, each frame or state inside a SketchFlow Animation is often a keyframe, but in a macro level making sure that each keyframe defines the complete scene in a point in time rather than micro keyframes in the Storyboard define a single propertys value in a point in time.