Reply to thread

Message

<blockquote data-quote="RubaDuck7" data-source="post: 64774" data-attributes="member: 21523">Heh, well... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />I agree with you, marshall, that the best designs come from small design teams, often just one person. Constant feedback is still crucial, even if the group as a whole don't get to make the final call on every single detail.Re: the artist and 'worker' scenario I'd like to add that my experience is that all the different parts of making a piece of software tends to have a creative component, they're just different.Interaction design - defining what screens are needed, how they work and how you navigate between them.Visual design - final layout, pictures, animations etc.Architecture - designing what the underlying classes/objects are and how they work together, database structure etc.Coding - Implementing the different classes etc in the most efficient way possible.Some of these obviously may not apply when making a skin. Oh, well. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Re: XAML, styling power is *very* extensive, to the point where UI controls are just behaviors. I.e. a button still looks like a button by default, but you can remove everything and start from scratch, making it look however you want. Since a button in XAML/WPF is just something you can click, a hyperlink is also, technically, a button. It just looks different. Weird, but *very* flexible.There are huge amounts of information about WPF/XAML on the web, for anyone who's interested.</blockquote>

[QUOTE="RubaDuck7, post: 64774, member: 21523"] Heh, well... ;) I agree with you, marshall, that the best designs come from small design teams, often just one person. Constant feedback is still crucial, even if the group as a whole don't get to make the final call on every single detail. Re: the artist and 'worker' scenario I'd like to add that my experience is that all the different parts of making a piece of software tends to have a creative component, they're just different. Interaction design - defining what screens are needed, how they work and how you navigate between them. Visual design - final layout, pictures, animations etc. Architecture - designing what the underlying classes/objects are and how they work together, database structure etc. Coding - Implementing the different classes etc in the most efficient way possible. Some of these obviously may not apply when making a skin. Oh, well. ;) Re: XAML, styling power is *very* extensive, to the point where UI controls are just behaviors. I.e. a button still looks like a button by default, but you can remove everything and start from scratch, making it look however you want. Since a button in XAML/WPF is just something you can click, a hyperlink is also, technically, a button. It just looks different. Weird, but *very* flexible. There are huge amounts of information about WPF/XAML on the web, for anyone who's interested. [/QUOTE]

Verification