Skip to main content

Introducing the Blend Art-board

The one thing I like about the Blend is the idea of moving towards a system where the designer, architect and programmer can visualize and talk to each other with ease. Not only intuitive user interfaces is the order of the day but building them fast and with ease is also on the high priority with software manufacturers. This post is to introduce you to the different parts of the Blend Software's UI.

The work surface is referred to as the artborad where you will design your Silverlight or WPF applications. 
The artboard is your work surface, where you can visually design a document in your application by drawing objects and modifying them.

1. The artboard background color can be changed to suit anything you want, it is like the canvas where the majority of your work will be done.  To change the color you can use the Tools >> Options menu to do so. 
2. XAML Editor : The code that is generated is called XAML and can be edited in this window. If you look at indicator 5 it will give you options to be in Split view which means (design+code), XAML View which means you can directly edit the code. 
3. The Artboard controls have five key controls which are snapping on and off the gridlines, snaplines, showing annotations and turning on and off rendering effects. This area also shows the zoom percentages that can be controlled by clicking on the list down. 
4. This is the area where the filenames of your project appear. 
5. See point number 2. 

When you are working on a project you will also see certain tabs on the left and the right which can be turned on and off based upon the objects and actions you are performing on them. I have included these screen shots for your reference, in case you are following for the first time after you have installed Expression Blend. 

Enjoy..Next Time we will go ahead and create a roll over application.


Popular posts from this blog

IT as a Innovation Partner in Business

Usually in Business organizations and especially in organizations where R&D is a separate department itself a tension persists on keeping the IT department away from any decision when it comes to innovation or process improvement. In short the IT department is generally seen as less of a help and more of a hindrance to innovation efforts. One of the main reasons is traditionally information systems are designed to impose structure on process, achieve pre-defined goals, produce metrics and minimize need for human interaction (in some case over maximize human interaction leading to nothing but "meetings").

While Innovation activities are highly unstructured and emergent, IT cannot be ignored or kept in isolation because IT can help in visualization tools, data mining efforts, uncover hidden relationships between data and create tools of knowledge management/information repository that so desperately is needed cross functionally but especially by the innovators within a org…

Analysis of SAP’s Platform Strategy

The software industry has been through high and lows up with the constant advent of new technological innovations and rapid changes in the global economic landscapes. SAP is the leading enterprise application software giant started by Hasso Plattner. The rise of Enterprise application industries started in early eighty’s with organizations needing one single software program that was capable of serving the multiple needs and functions of various departments. One single enterprise-wide application software means integrating applications that fused together for the smooth exchange and extraction of information. For example when customer services sold a product and got stock updated in the inventory by the warehouse people and the same data could be pulled by the Finance department. Enterprise Application software’s were designed exactly to do the latter mentioned processes seamlessly. SAP started by break away engineer’s Plattner and group build the company on strong engineering fort…

How Dashboards can mislead

Read an interesting article from John Shapiro professor at Northwestern Kellog on how dashboards can mislead executives and I cannot agree more. To be honest, I love visualization of data and have pushed my data architects and report writers to give me snapshots of various measures but how often the rich data didn't mean anything as it did not align with organizational goals. Even more, what information is important to me is not necessarily relevant to other executives in the organization.  Data analytics visualized on dashboards typically describe existing measures on past phenomena, some better ones predict future events and past data and the best one prescribe a course of corrective or strategic actions.

Shapiro talks about three types of traps executives can fall for:

1. The Context Trap:  We equate empirical data to the objective. I have blatantly used the cliche "numbers don't lie." But this belief can be dangerous because we can track wrong measures or metrics…