What Would You Like to See in the Next Versions of Blend and Design?

Even though we just shipped Expression Blend and Design 2, we are already busy planning what to do for future releases. To better help us with our planning, we'd like to hear from you.

What are some things that you would like to see in Blend and Design? What are some of the things that you wish were done differently? Also, what are some of the things in our products that you like?

Let us know by posting in the comments below! We take your feedback very seriously, and your input goes a long way in helping us improve our products.

Cheers!
Kirupa

(On a related note, based on feedback from many of you, this blog has been restyled. A big thanks to Tim Sneath for the help.)

Comments

  • Anonymous
    May 05, 2008
    PingBack from http://blogs.msdn.com/expression/archive/2008/05/05/what-would-you-like-to-see-in-the-next-version-of-blend-design.aspx

  • Anonymous
    May 05, 2008
    TFS/SCC integration.  We have been asking the Expression Web/Blend teams for it since before version 1 was released...isn't it about time?  I know I'm not the only one either; see the Expression product forums and connect sites.

  • Anonymous
    May 05, 2008
    All I need is Expression Design. VS2008, SQL Server and Expression Design for my Developer Evangelism. Don't mean to complain but it seems like a waste for me to buy the entire Studio to get Design. ;-) Note: I do not use it for profit.

  • Anonymous
    May 05, 2008
    Even though we just shipped Expression Blend and Design 2 , we are already busy planning what to do for

  • Anonymous
    May 05, 2008
    In Blend, I'd like to see intellisense for the XAML, better control skinning support, and possibly some animation wizards that could assist with some of the more common scenarios. Most importantly, I'd like to see some sort of "express" version that would let the hobbyist or small development shop be able to use Blend without shelling out $500.

  • Anonymous
    May 05, 2008

  • Intellisense in XAML.  There are things you can't do with the tool that are purely design related and require hand-coding XAML to get the effect you want.  Limiting it to VS only is being bull-headed for no justifiable reason besides $$$.
  • TFS integration.  This seems like a no-brainer for Microsoft since it continually touts its designer-developer integration story.
  • Better style creation and management
  • Anonymous
    May 05, 2008
    Even though we just shipped Expression Blend and Design 2 , we are already busy planning what to do for

  • Anonymous
    May 05, 2008
    There are several features present in VS2008 that are conspicuously absent from Blend, especially when it comes to the direct editing of the XAML.  It is borderline inexcusable that the text search feature is on par with Notepad's.    Intellisense and a client plugin for TFS would also be helpful (and have already been mentioned.)  Although Blend is targeted at "designers", in my experience as a developer, it has become an indispensible complementary tool to VS2008.  As such, my advice really leans towards exploring and enhancing the developer experience, and make the 2 tools feel and funciton like part of a common suite.

  • Anonymous
    May 05, 2008

  • Source code control integration. TFS would be fine, but even generic VSSI-type interface would be fine.
  • Better XAML editor ala Visual Studio.
  • Expression Design available separately. Personally, I buy and use all of Expression Studio, but for some on my team being able to buy just Design would be better.
  • Anonymous
    May 05, 2008
    The comment has been removed

  • Anonymous
    May 05, 2008
    The comment has been removed

  • Anonymous
    May 05, 2008
    I'd like to see Design as part of my MSDN PREMIUM subscription for Software Developers so I could tell you what I'd like to see in the next version so a developer/designer such as myself could actually use it like I should already be able to.

  • Anonymous
    May 05, 2008
    Since Office hasn't yet included Xaml import, Design should include EMF export.

  • Anonymous
    May 05, 2008
    ----- Blend Requests ----------------------------

  • XAML editor intellisense
  • When in XAML editor, auto hide doc panels (or allow separate doc-panel preferences) Blend seems to be very aggressive about “helping” by setting properties such as Width, Height, and Margin on elements in an attempt to maintain visual appearance as the user moves and manipulates elements in the designer. This is particularly frustrating when trying to design robust control templates where an explicitly defined Width, Height, and Margin is seldom desired. I find myself repeatedly having to “reset” properties on the same elements.   This is also problematic for general layout when sizing-to-content is desired, for example, when the content of a control changes size (think of localized strings within a button) or when resizing of a container (e.g.: a window) occurs. (This aggressive setting of properties also tends to bloat the generated XAML)
  • Settings to control this behavior
  • Anonymous
    May 05, 2008
  • Solution folder support
  • Remember what projects are expanded/collapsed
  • XAML intellisense
  • Anonymous
    May 05, 2008
    The comment has been removed
  • Anonymous
    May 05, 2008
    Expression design:
  1. Support the gradient capabilities of XAML gradients.  It's useless as a tool to export XAML without the full gradient transform parameters available in XAML.
  • Anonymous
    May 05, 2008
    I would very much like to see XAML import incorporated into Expression Design. Sometimes things are made entirely in Blend or made in Design and then further manipulated in Blend. It would be nice if it could be loaded back into Expression Design.

  • Anonymous
    May 05, 2008
    Intellisense in the XAML editor is one of the features I miss most!

  • Anonymous
    May 05, 2008
    I think the working environment would be nice if we could switch back and forth to the old black on white interface... sometimes easier to read. Even though the dark gray scene fits for nightsters...

  • Anonymous
    May 05, 2008
    The comment has been removed

  • Anonymous
    May 05, 2008

  • Add Design Time visible property
  • Better integration of "custom" data source provider that can produce sample data at design time without having to specify a datasource type.
  • Better integration of databinding based on sample data produced at design time.
  • Show missing properties of the storyboard
  • Allow better edition of resource dictionary, create, clone, rename (with refactoring)
  • Allow binding statically to resources
  • Add localization / internationalization
  • Allow to consume wcf web services
  • Allow to bind commands, keygesture, inputgesture, etc
  • Provide a way to see and remove identical property value from the xaml
  • Anonymous
    May 06, 2008
    Another one for intellisense for XAML.  Still shocked it hasn't got it. Also: Better databinding support.  There really needs to be a better end-to-end solution for databinding 'mocking' so that you can simulate a data feed into an adhoc databound control.  Basically, take a control and scan it for binding and then provide an input dialog that creates a mock object to simulate the data. Resource editing.  Unless I'm missing something I can't edit a DrawingBrush resource.   Better logical/visual tree browsing.  I can't expand the tree if there are visual elements on the background property.  In fact, the storyboard editor seems the wrong place for navigating the tree - why not just have a generic visual/logical tree browser?  The 'New' buton on the tree should allow you to add any valid element based on references etc (like the intellisense editor in VS2008).

  • Anonymous
    May 06, 2008
    TFS/SCC integration. This should have been there since day one.

  • Anonymous
    May 06, 2008
    I would like it to be easier to edit brushes and resources even if they are not currently being used by an object. What would REALLY be great is if I could be looking at the XAML view and right click on a brush and edit it visually. I would also like intellisense in the XAML view. Thanks for the GREAT work!

  • Anonymous
    May 06, 2008
    The comment has been removed

  • Anonymous
    May 06, 2008
    TFS integration... would be very beneficial to our project.

  • Anonymous
    May 06, 2008
    Adding a new user control to a folder in a project does not append the folder name to the namespace like in VS.  I don't know if this was fixed in 2, but I know it is a problem with Silverlight in 2.5.  Blend also has issues finding controls that are in folders or sub-namespaces. Intellisense. I don't know if this is available now, but a way to move a control up or down the visual tree, not just up or down siblings.  Say I inserted a Grid as a child, and now I realized I want to add a border to that grid.  If I add a new border as a child to the parent, it deletes the grid; the only option is to add the border in xaml view  and then switch back to design view.   Not a big hurdle, but it would be nice to be able to right-click and say "Move up" and "Move down" along with Send Backward/Forward.  Or maybe just a way to easily insert a border between a parent and child.

  • Anonymous
    May 06, 2008
    The comment has been removed

  • Anonymous
    May 06, 2008
    Source Control integration!  I can't believe we don't have this yet.  Thanks.

  • Anonymous
    May 06, 2008
    The comment has been removed

  • Anonymous
    May 07, 2008
    Here is my wishlist (from http://bitbonk.spaces.live.com/blog/cns!E17530AA6EFF7871!433.entry )

  1. extensive designtime support for cutom controls (Microsoft.Windows.Design.dll);
  2. a plugin architecture to write true plugins for blend
  3. better 3D content authoring support (mesh editing, texturing, animation) or give us an external tool with a workflow that really works (maybe the Microsoft Truespace team can do something for you  ); currently building WPF 3D scenes that are little bit more complex is a very timeconsuming task even if you have very good 3D artists in place
  4. XAML intellisense
  5. XAML outlining (folding xml elements) like in Visual Studio
  6. HSV mode in Blend's colorpicker
  7. sourcecontrol integration
  • Anonymous
    May 07, 2008
  • full import of AI and SVG files in Design, including texts, groups and object names.
  • Anonymous
    May 07, 2008
    More unified sane design of Blend GUI itself:

  • calm 'Windows standard' color schema

  • draggable sub-windows

  • Anonymous
    May 07, 2008
    Thanks for the feedback everyone, and please do keep the comments rolling! Many of us on the team have looked through this, and there have even been some in-person and e-mail conversations around what you have all suggested. Cheers!
    Kirupa

  • Anonymous
    May 07, 2008

  • SCC integration is a must!

  • Collapsable menus (Vis Studio stylee)

  • XAML Intellisense Great job so far!!!

  • Anonymous
    May 08, 2008
    The comment has been removed

  • Anonymous
    May 08, 2008
    WPF Controls Emphess.Net: A MenuKiller Control - this article is a work in progress detailing how to

  • Anonymous
    May 09, 2008
    The comment has been removed

  • Anonymous
    May 12, 2008
    Design: Listen, Listen, Listen to the community and stop making statements such as 'The experts said...' or 'We did a survey and found...' as none of the statements made so far reflect the requests made on the ED board. XAML export has gone backwards in V2 when you took away the ability to view the markup - I have no idea why you did this? The exporter is now confusing compared to what it was, and several other options have disappeared without explanation. Design to Blend: At present its poor, it was supposed to be better in V2 but who knows what happened. For the 'average' user its confusing especially when moving text and images between Design and Blend and the option to Copy & Paste only adds to the confusion. Blend: Overall pretty good and has some neater tools when compared with design such as the Brush Transform tool which is streets ahead of the comparable tool in Design. I use VS2008 Express so adding events is not great as the event is copied to the clipboard rather than directly into the code. Maybe you could look at this. Not a big deal but if you are unsure on what you are doing then it is a bit of surprise. Blend is good but Design needs to be a lot better. I never saw one post ever asking for slicing yet we get it in version 2 and 50% of the posts asked for better export options - clearly someone on the team knows better.

  • Anonymous
    May 12, 2008
    Estoy viendo bastantes posts relacionados con los nuevos Services Packs de Visual Studio 2008 y el .NET

  • Anonymous
    May 12, 2008
    Estoy viendo bastantes posts relacionados con los nuevos Services Packs de Visual Studio 2008 y el .NET

  • Anonymous
    May 12, 2008
    Estoy viendo bastantes posts relacionados con los nuevos Services Packs de Visual Studio 2008 y el .NET

  • Anonymous
    May 12, 2008
    Ability to go into a mode where you click on objects to define tab order. I don't believe this is part of Blend and I've seen many WPF apps with really messed up tab order. Setting it manually everywhere seems incredibly difficult for complex UI.

  • Anonymous
    May 14, 2008
    Designing à la Infopath : dropping controls on the design surface automatically creates a corresponding XML schema

  • Anonymous
    May 14, 2008
    Take most of the options and functionality of wpf in Expression Blend - convert to silverlight. Everything from motion tweens on a path to editing templates and being able to build a proper button and control animation within the storyboard. I shouldn't need a dev team to help me control an animation in silverlight, when I can build / design an animation in wpf without a dev team. Just me two cents, Thanks.

  • Anonymous
    May 15, 2008
    Blend:

  • Intellisense in XAML.
  • Designer as part of Premium Subscription.
  • Better usability (sometimes is difficult to find the things)
  • Anonymous
    May 15, 2008
    Design

  • Undo History that allows you to to see and/or select which undo(s) you want executed

  • Scripting ability or XAML import

  • More live effects like lightning, filtered lighting and shadow effects, sparkle effects, water ripples, etc. Blend

  • Glow and Bevel effects for Silverlight!!!!!! This should have been added in version 1!

  • Better help files with more examples and samples

  • Anonymous
    May 15, 2008
    The comment has been removed

  • Anonymous
    May 15, 2008
    My wishlist

  1. In-place editing of data and control templates - like content pages with master pages
  2. The ability to specify design-time only data sources to allow WYSIWYG visualization of templates by designers
  3. An intelligent XAML editor
  4. Ability to specify that the value of a particular control property is valid only at design-time.
  5. Extensible control gallery
  • Anonymous
    May 16, 2008
    I'd like to see bitmap editing in Design. In addition, I think it would be very helpful to be able to use something other than Canvas to layout the objects. When exporting xaml from Design, everything is inside a canvas, however it's often necessary for me to convert the layout to a StackPanel or some other layout control. Thanks.

  • Anonymous
    May 17, 2008
    Design:

  • a more approach to Photoshop style and scripts system.
  • Better vector tools. Blend:
  • Templates for beginners users.
  • Anonymous
    May 18, 2008
    I've been using Expression Design a lot lately, and have compiled a Wishlist while working with it. You asked for it, so...
  1. Drag more than 1 selected layer
  2. Drag layers to bin
  3. Ctrl and Shift click layers like in Photoshop CS3
  4. Ctrl + -> in text jumps to the next word
  5. Underline tekst in Text properties panel
  6. Leading in Points and Pixels instead of Percentages
  7. Deleting Invisible, but not locked layers is possible
  8. Never automatically lock layers
  9. Better text object access
  10. A slimmer (less wide) Layers Panel
  11. Layers in Layers
  12. Drag in text to select characters (including Layer and Object names)
  13. DoubleClick text is Select all text
  14. Default Export format is an option in preferences that is remembered (not always PNG)
  15. Kerning in Words with Alt+<- and Alt+->
  16. Opening dialogs in same screen as application (when multiple monitors) That's all folks :) Keep up the good work!
  • Anonymous
    May 18, 2008
    It's been mentioned a zillion times, but I'll add it once more: Intellisence to XAML-editor.

  • Anonymous
    May 18, 2008
    http://www.malayalamsearch.com/blog/

  • Anonymous
    May 18, 2008
    http://www.malayalamsearch.com/blog/

  • Anonymous
    May 19, 2008
    For Blend:

  • XAML Intellisense

  • Better support for dynamic layouts.  I always tweak my XAML by hand due to all the wonky margins that are added when I move stuff around in the designer.

  • I often use Kaxaml  to supplement my Blend work, because of it's true WYSIWYG.  So perhaps, a real preview pane (in addition to the design pane) that show what's really going to be rendered.

  • Anonymous
    May 19, 2008
    Just a question: Why would you want to rotate the entire canvas (the artboard) in Design? You can rotate your vector objects and your work, but I'm unsure of the benefit of rotating the entire workspace.

  • Anonymous
    May 19, 2008
    Apart from all the others (XAML Intellisense, Design coming seperate from the suite etc)... Ben Cooley's point number 7...

  1. Allow blend and some of its basic panels to integrate directly into visual studio and optionally replace the "Cider" editor if it is installed.  Why support two XAML editors?
  • Anonymous
    May 19, 2008
    VSS Integration as Visual Studio currently offers..

  • Anonymous
    May 20, 2008
    One feature that i need is to draw shapes with variable properties in Design (this was in Expression Graphic Designer --for ex draw sqares but every time we draw the opacity or colour to be variable ,arbitrary)---it was a nice feature and maybe are more others from  Expression Graphic Designer  but i can't remember now . Another wish that i have is that Expression Web to share the same WPF interface like Blend and Design (more exactly the black version i'm interested in ) and have panels that can be hidden like ones in Visual Studio.Expression Web actual interface it's very ugly and nonproductive. Thanks.

  • Anonymous
    May 20, 2008
    One other thing that bugs me all the time working in Blend is the fact that when I open app.xaml to edit Styles and Resources, a message shows that it cannot be edited in the Design View. Since I am going the edit the XAML anyway and won't go to the Resources Panel and since you already know that I want to open app.xaml (because you can show the message), why don't you just open it in XAML Mode? Make it an option if you must, you can even add the opportunity to hide the panels at the same time :) Success!

  • Anonymous
    May 20, 2008
    The comment has been removed

  • Anonymous
    May 20, 2008
    +1 For simplifying grid Margins, Width, MaxWidth. The MaxHeight/MaxWidth properties are collapsed even though there are only 3 properties for row and collumn! Perhaps shift-clicking any property could reset it as this is a frequent operation. +1 For improved databinding, maybe a design time DataContext? Being able to create your own sample data without the need for declaring the class would be helpful for prototyping. *The feature I would most like to see is to be able to open a style or template in its own tab. Editing styles and templates is one of the best features of blend but it seems to require far too many clicks. *Better support for creating/editing tile brushes, they never seem to be aligned when I use blend to create them. *The resources panel could be a bit more useful it could highlight unused resources, be a tree instead of a list so you can easily access a styles' template, move a template inside/outside of a style. It could also show all the resources for a project instead of changing depending on the current file and be more of a navigation aid. When you edit a resource you could switch to the properties panel. *Putting edited properties above the others like some css editors do might be worth consideration or you could just emphasize the properties that have been set more. Thanks for reading.

  • Anonymous
    May 21, 2008
    Please allow it to read/edit old Photodraw .mix files. There is no program to edit these, since the product was discontinued. I have thousands to convert.

  • Anonymous
    May 21, 2008
    Just to reiterate, thanks a lot to all of you for providing us this feedback. While we can't publically communicate exactly which of the suggested features will be in the next version of Blend, the suggestions do help (and are currently helping!) us with our planning on the next versions of Blend and beyond :-)

  • Anonymous
    May 21, 2008
    Previously on the blog I’ve explained how a KeySpline can be used to do animation easing . I also demonstrated

  • Anonymous
    May 21, 2008
    Bevel and Drop Shadow effects for panels, tabs, buttons, etc.

  • Anonymous
    May 21, 2008
    The comment has been removed

  • Anonymous
    May 21, 2008
    Oh and for the designers. Palettes would be greate to store custom color presets.

  • Anonymous
    May 25, 2008
    I would like to see some form of default ordering for properties in the XAML that Blend produces.  I do a lot more XAML coding by hand these days but the randomness that can infest Blend XAML code can be a nightmare ... for instance I think Blend should always add things in a set order like: <Type x:Name=""      Width=""      Height=""      Grid.Column=""      Grid.ColumnSpan=""      Grid.Row=""      Grid.RowSpan=""/> The name first, then layout, style bindings etc ... Source Control integration is just a prerequisite frankly, Blend NEEDS this big time.

  • Anonymous
    May 26, 2008
    One way to think of Styles is as a collection of attributes with a specific name. In Blend, currently the Style attribute itself is tucked away under the Miscellaneous panel out of sight on the bottom of the properties panel. In my view it should be in plain sight at the top of the properties panel, allowing any designer to add a new Style for a collection of properties. The current implementation is too complicated and take too many actions and clicks. The consequence of this is that designers are not creating Styles, which results in XAML files that are not well organized or refactored. Developers getting to work in these files are not laughing. Or worse, maybe they are... Actually I do refactoring in Styles in code myself, because it is much easier that way. Please, rethink the Style implementation in Blend...

  • Anonymous
    May 27, 2008
    I always use drag and drop text in text editors and miss it very much in the Blend Editor. Actually the contextmenu with the Cut, Copy and Paste options is also missing when I regularly routinely rightclick in the editor... Success!

  • Anonymous
    May 28, 2008
    Actually a [View a Fullscreen XAML] option in the Contextmenu in the Objects and Timeline panel would help. Does it look like we are editing XAML in the editor at least as much as in the Design view? We do. At least I do :)

  • Anonymous
    May 29, 2008
    +1 for InteliSense in XAML 3ds Max import (and export) for .3ds modells AND scnenes/animations. Don't try to make a new 3d animationprogram like 3ds or Maya, just integrate them.

  • Anonymous
    June 01, 2008
    Erm ... support Illustrators GradientMesh. then a more intelligent Editor for DataBinding . And for instance my Blend crashes if i like to generate a groupstyle...

  • Anonymous
    June 02, 2008
    The comment has been removed

  • Anonymous
    June 02, 2008
    I second the suggestions from someone above:

  • Solution folder support
  • XAML intellisense Every significant app I've ever seen in Visual Studio uses Solution Folders... thanks
  • Anonymous
    June 03, 2008
    Please add the Blend designer to Visual Studio. As a developer I need it just like the codebehind model of  ASP.NET and Windows-forms. I don't want to use 2 different tools on the same sourcecode. And I want to be able to work together with designers form just one environment. Keep it stupid simple please.

  • Anonymous
    June 03, 2008
    And why is PSD (Photoshop) import/export support not implemented as a WIC codec? Please implement PSD as a WIC codec.

  • Anonymous
    June 09, 2008
    Intellisence is a feature that most here have talked about. We talk about designer developer independance, but that isn't really true. To be able to say create styles for items in ListView or ComboBox or any other control for that matter, i need to work with Data. Sometimes it means that the designer can't design till developer has code for minimal data. Additionally, sometimes this data is only available at run time and not design time, thus making designing  more difficult. Would be good if Blend would come with pre-packaged set of data. 1 for Xml, 1 for object data provider, 1 for SQL etc. These could be used by designers to quickly create some of the visual styles and there should also be an easy way to discard this and replace this with actual application data

  • Anonymous
    June 09, 2008
    I would like to be able to convert my Blend Project into a SharePoint Web Part.

  • Anonymous
    June 19, 2008
    Find and Mark and Delete orphaned XAML attributes for Silverlight projects: For Silverlight it is important to make the download as small as possible. I find that a lot of XAML code remains behind that can and should be removed before making a XAP file: Grid.Column="0" Grid.Row="0" Grid.ColumSpan="1" Grid.RowSpan="1" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" Margin="0,0,0,0" Padding="0,0,0,0" etc. etc. Blend should be able to recognize, mark and delete this orphaned XAML for Silverlight projects.

  • Anonymous
    June 25, 2008
    The comment has been removed

  • Anonymous
    June 25, 2008
    ∙ XAML code folding ∙ Intellisense for the XAML ∙ More flexible layout ∙ SVG Editor ∙ Animation preview ∙ Source control system integration Thanks.

  • Anonymous
    June 27, 2008
    Keyboardshortcuts for Order-> Send To Back, Order-> Bring To Front etc.

  • Anonymous
    June 29, 2008
    Extensibility. Photoshop has plugins, Visual Studio has addins.  Please make the Expression tools extendible so that third party developers can enhance the designer-developer experience.  

  • Anonymous
    July 04, 2008
    It would be great if I could select multiple keyframes in a storyboard in an easier and faster way than holding CTRL

  • Anonymous
    July 09, 2008
    The comment has been removed

  • Anonymous
    July 10, 2008
    My top 3 in order are:

  1. Intellisense for XAML - I do most of my XAML editing in VS because I can then use Resharper which does a good job of this but could be better - but definitely would reduce my saving and app switching if Intellisense was built in ... to at least the same standard which Jetbrains have done with Resharper & VS) - EG event handler generation etc.  Better still - do 2 and I'm sure Jetbrains will be able to support it.
  2.  An Extensibility model.
  3.  It would also be nice to be able multi-select a number of controls and take an option to "surround with" another control (typically a panel of some sort, or a border).
  • Anonymous
    July 16, 2008
    The comment has been removed

  • Anonymous
    August 06, 2008
    A few months ago, we asked you for feedback on what are some of the things you would like to see improved

  • Anonymous
    August 07, 2008
    The comment has been removed

  • Anonymous
    August 15, 2008
    Please include Design with all MSDN subscriptions.  Or at lease allow it to be purchased by itself. I can download Blend and Web as part of MSDN subscription, but now need to purchase Studio just to get Design.  It would be nice if Design was also included for all MSDN subscribers.  It would help adoption. If we are going to end up spending the $700 we will probably end up going with Adobe because of the influence of our graphics team.

  • Anonymous
    September 06, 2008
    The comment has been removed

  • Anonymous
    September 17, 2008
    I would like to see, in order of priority (for Blend)*.

  1. The ability to bind to some sample data at design time. Designing templates without this is a real pain.  This is by far my most desired feature.
  2. The ability to edit resource dictionaries and themes at the same time as viewing a control's appearance, rather than having to switch all the time.
  3. Ability to load/switch/apply resource dictionaries from one project to other, non .exe based projects. Haven't found an easy way to do this yet.
  4. Greater consistency between design and blend in the way they work. Sometimes it feels like they aren't following the same script.
  5. Better file format import / export. For example XAML into design, SVG, etc.
  6. When drawing using the pen in blend, make the mouse down action place the point and while the button is held adjust the position of the control point. Also make it easy to lock the relative position of points to fixed angle increments by holding a modifier key (like holding shift does in design?).
  7. Better intellisense for xaml.
  8. Path offsetting. However, having just spent the past few weeks working on this in my spare time, I can say it's not easy!
  9. Make drawing curves work like Xara X.  IMHO it's so natural and other packages just seem to miss the point completely. Other wishes.
  10. Make it possible to buy the products separately - e.g. blend on it's own. I feel like I'm being fleeced.
  11. Express versions? Any plans for Office 14 to support the import of vector formats other than the evil WMF/EMF? Please. This is a coding nightmare for us. Anyone down the corridor you can pass this hint onto?
  • Of course, there is always the possibility I may have missed something since I am relatively new to blend.

  • Anonymous
    September 17, 2008
    Oh, while I'm thinking about grips, there is one other thing I would really like to see changed in XAML / WPF.

  1. Make it possible to override the default style of common controls, but scope where/when the new default style should be used. Restyling things like the default border causes so much havok in other controls like the groupbox that we've backed off and forced our users to have to apply a chosen default style manually each time. This is generally a pain if your new default style is slightly more radical than the standard Windows style. For example, switching to white on black from the default black on white for text.
  • Anonymous
    October 04, 2008
    I just discovered that while drawing Path Shapes in Blend the Contol key does not switch to the Direct Tool while pressed. This is standard behavior that even Expression Design exhibits (along with other industry standard tools :). Please add this feature in Blend to make drawing Vector shapes more intuitive and give us more control over the Path that is being created.

  • Anonymous
    October 09, 2008
    <a href='http://cathryndake.iespana.es/20080522-autodesk-inventor.htm'>autodesk inventor 7 crack</a> <a href="http://cathryndake.iespana.es/20080522-autodesk-inventor.htm">autodesk inventor 7 crack</a> [link=http://cathryndake.iespana.es/20080522-autodesk-inventor.htm]autodesk inventor 7 crack[/link]

  • Anonymous
    October 13, 2008
    Ability to create an inner bevel in Blend, possibly after clipping...

  • Anonymous
    November 15, 2008
    The comment has been removed

  • Anonymous
    November 17, 2008
    I would very much like to see XAML import incorporated into Expression Design.  To import objects and brush resources in Design.

  • Anonymous
    November 24, 2008
    Better support for the Adobe Suite

  • Anonymous
    November 25, 2008
    <a href='http://clearlyokc.com/wp-content/uploads/2007/10/article-1914.htm'>all media fixer cracks</a> <a href="http://clearlyokc.com/wp-content/uploads/2007/10/article-1914.htm">all media fixer cracks</a> [link=http://clearlyokc.com/wp-content/uploads/2007/10/article-1914.htm]all media fixer cracks[/link]

  • Anonymous
    November 25, 2008
    mascot video las vegas [URL=http://dfwandme.com/wp-admin/css/styles/comment1140.htm]mascot video las vegas[/URL] [url=http://dfwandme.com/wp-admin/css/styles/comment1140.htm]mascot video las vegas[/url] [url]http://dfwandme.com/wp-admin/css/styles/comment1140.htm[/url]

  • Anonymous
    November 25, 2008
    korean dance videos [URL=http://clearlyokc.com/wp-content/uploads/2007/10/article-1821.htm]korean dance videos[/URL] [url=http://clearlyokc.com/wp-content/uploads/2007/10/article-1821.htm]korean dance videos[/url] [url]http://clearlyokc.com/wp-content/uploads/2007/10/article-1821.htm[/url]

  • Anonymous
    December 02, 2008
    The comment has been removed

  • Anonymous
    December 15, 2008
    I'm in Redmond, WA (Redwest campus). Where can I get one-on-one help from someone who knows their way around Blend?   I have work stoppages in so many directions at this point and things are not intuitive from Design to Blend.

  • Anonymous
    January 23, 2009
    In Blend I'd like to be able to format the xaml. It's a pain to do a bunch of messy coding in Blend for hours and constantly opening it up in VS to format it so that it looks proper and isn't messy looking. Make that also able to format a selection as well. Blend ought to have a more simplified mode for the purely design phase when all the more developer kind of stuff is hidden so that a design and more easily concentrate on designing. All of our designers feel terribly challenged trying to design in Blend. Oh, and add some way to save out a png or something to show clients. It's a real pain grabbing screenshots to show clients how parts of a Blend project looks. Fix the color shift from Design to Blend!!! It's awful when designers create stuff in Design and freak when the see the color shift after importing it into Blend, requiring them to rework all the colors. Fix the xaml export! The xaml Design creates is useless unless it's a simple graphic that you want as a path. We use grids, stackpanels, etc, not canvases. And text, why does Design insist in making every letter of text into a run??? Did you ever have to extra letter by letter multiple paragraphs of text out of runs wrapping every individual letters. Not fun. The Visual State Manager could use some improvement. In the older implementation of triggers it was easy to add a trigger to anything to make it interactive. I haven't out, or it's not readily apparent, how to add states to make xaml that is not a control behave interactively with the new Visual State manager.

  • Anonymous
    February 02, 2009
    In Blend:

  • XAML intellisense
  • Solution folders support
  • Remember expanded/collapsed projects
  • Ability to ignore a project without having to remove it from solution (eg: a visual studio test project will make it impossible for the designers to work on the solution) Thanks
  • Anonymous
    February 02, 2009
    Also, forgot to mention:
  • Express version of Blend
  • Anonymous
    February 13, 2009
    Hi everyone, After a bit of a break, we are currently getting the next preview of Deep Zoom Composer

  • Anonymous
    February 18, 2009
    Features in Blend:

  • XAML editor intellisense
  • Adorners support (respectively VS Studio like extensibility support)
  • Plugin architecture
  • The possibility to LINK a source code file to the project, without the worrying that this will be locally copied at compile time
  • Anonymous
    August 12, 2009
    ipF9s8  <a href="http://swfwxoiplbdt.com/">swfwxoiplbdt</a>, [url=http://heitvkjtxnrz.com/]heitvkjtxnrz[/url], [link=http://mfswpbtseyxs.com/]mfswpbtseyxs[/link], http://obbgfvlggaxf.com/

  • Anonymous
    January 01, 2010
    Dear Expression Design team, I am just learning Microsoft Expression Design.  I really like it.  I think that it could fully replace Adobe Illustrator and Corel Draw, and in some respects it may also supplant the great Microsoft product, Visio. However, I have one serious issue -- and that is the fact that Expression Design does not support WMF files. I use MathType, and I need to be able to import the equations from MathType.  GIF files are not an option, because they get rasterized and thus are not presentable when enlarged.  Also, EPS files are inconvenient to use (and in any case Expression Design does not support EPS).  I only wish that Expression Design supported WMF.  This would be tremendously helpful to me. Thank you for listening. Stanley