HI Matt, I would NEVER want to use Expression (except Web Designer) if I was doing a web site. This is for Silverlight and WPF solutions only. If you ain't doing one of those, don't bother.
But that being said, one of my issues with the method below is that it assume that standard HTML controls are right for everything. This has been my problem with HTML from the beginning. There needs to be a much easier mechanism (I know there are custom controls for sale) to manage custom controls and custom skins on controls within HTML. I do have to say that the one brilliant part of Blend are the controls and the control part templates. the layout controls in particular are amazing. I also love that every control doesn't only have a width and height, but they can all be inherited from a parent with a click of a button AND you can set minimum and maximums on sizing ... AND WAIT! ... so far we have not seen any degradation on nesting of layout controls at all. Nest away!!! It makes no difference what so ever. I really love my layout controls. Yes, I'm deep in the weeds in an Expression Blend desktop application right now. -- dave On Jan 23, 2008 9:19 PM, Matthew Nish-Lapidus <[EMAIL PROTECTED]> wrote: > On Jan 23, 2008 7:56 PM, David Malouf <[EMAIL PROTECTED]> wrote: > > The Thermo stuff is definitely interesting, but thinks like a graphic > > designer, not like an interactive designer. Expression in their > tutorials > > anyway is thinking similarly. > i've always done my wireframes and prototypes with html/javascript ... > html and css are amazing for putting together a quick wireframe.. all > form elements are done, the box model makes it really easy to lay out > distinct areas... and now, with all the nice javascript frameworks, > all the heavy lifting is done for you. throw in something like ruby > on rails and you can have a functional prototype with pretty basic > technical skills. > > the best part is that, if you're like me, the final product will end > up being html/css/javascript anyway, so if somebody else needs to do > production work all your prototypes can be a great starting point.. or > if you're like me you probably do most of the production work too :) > > then, when it comes time to make things pretty, you can fire up > photoshop/fireworks/illustrator and start skinning elements and > building a style guide. > > i will often do html wireframes and use screenshots as a background in > photoshop to do the graphic design... > > > > > Basic assumption that is false that both are making is that I'm going to > > make a finalized high fidelity graphic UI as a flat screen to start and > THEN > > add interactive elements. This goes against the very way IxD's have been > > working. > > > > What is the core element that most (sorry Andrei) IxD's work with? > > Wireframes!!!! > > What we want more than anything is a way to sketch, not to draw, > > interactions as easily as we can wireframe. > > > > THEN! build the styles on top of that! > > -- > Matt Nish-Lapidus > work: [EMAIL PROTECTED] / www.bibliocommons.com > -- > personal: [EMAIL PROTECTED] / www.nishlapidus.com > -- David Malouf http://synapticburn.com/ http://ixda.org/ http://motorola.com/ ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
