Designer vs. Programmer

[jwade_m]

Are you doing that with CSS? You couldn't really use the slicing process to build from an existing shell could you?

[rossable]

slicing? wow.... i haven't designed a site using slicing for years!


yes, it's all straight CSS/XHTML. the programmers make the controls and then table them all togeather in a rough layout and then i go in and actually put them in divs and apply the correct styling and modify till it works.

what's really fun is they make the page initially in HTML 2 (old DTD references and all) and then i get to go in and make it XHTML 1.1 compliant with the correct class and id tags and all that.



slices.... wow.

[jwade_m]

Yep...slicing. I'm more visual so I like doing it this way. This is basically the first (and only) way I've learned. I don't know much CSS, yet. Why so shocked...is slicing old school or something?

[rossable]

no. it's just slower and relies more on images than more modern websites with strict CSS do.

it's all a matter of preference so i will never tell you not to do something... but there are definite advantages and disadvantages to every technique.

[tommylogic]

Originally Posted by rossable

slicing? wow.... i haven't designed a site using slicing for years!


yes, it's all straight CSS/XHTML. the programmers make the controls and then table them all togeather in a rough layout and then i go in and actually put them in divs and apply the correct styling and modify till it works.

what's really fun is they make the page initially in HTML 2 (old DTD references and all) and then i get to go in and make it XHTML 1.1 compliant with the correct class and id tags and all that.



slices.... wow.

Where does the original comp come from?

[rossable]

you dont have to slice a composition and some times creating the visual elements independently of a composition design can give some added freedom to the outcome sense you're not stuck redesigning the whole thing just to change one part. takes preplanned color control and some added mental agility to keep it all straight though unless you write it all down somewhere.

granted that this would be increasingly difficult the more curves the design has or the more intricate or ornate the patterns were. basically you just slice it up mentally before hand and then only make the images that are necessary for the design. the rest is CSS background colors and borders. do it right and you can get away with only having to have one or two images in your final site. makes load times faster and display a lot cleaner. also if you use the "sliding door" technique, then all your rollovers are cake too!

it's all in hopes of site optimization and streamlining the code and content. again... end results are ultimately the same so it makes no difference the process used to get there.

[bhushan]

Last week I attended a program held by microsoft for the promotion of their newly software Microsoft Sliverlight and Expression.

In an discussion they mention that, they alway have a fight between the microsoft designers and developers.

Designer hates to work with developer because developer never gets the exact look and feel which designer designs, whereas on the other hand developer never likes to work with designers because they designer things which makes them difficult to code.(this is what it was said by those microsoft guys)

And finally it the developer who spoil the whole UI design.

This tells that developer can never become designer and designer can never become developer (some exceptional case like Toon & Gav mentioned).