navigation
a webmaster learning community
     Home    Register     Search      Help      Login    
Sponsors

Shopping Cart Software
Ecommerce software integrated into Frontpage, Dreamweaver and Golive templates. No monthly fees and available in ASP and PHP versions.

Website Templates
We also have a wide selection of Dreamweaver, Expression Web and Frontpage templates as well as webmaster tools and CSS layouts.

Frontpage website templates
Creative Website Templates for FrontPage, Dreamweaver, Flash, SwishMax

Search Forums
 

Advanced search
Recent Posts

 Todays Posts
 Most Active posts
 Posts since last visit
 My Recent Posts
 Mark posts read

Microsoft MVP

 

CSS and the future role of Fireworks and Photoshop

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
Printable Version 

All Forums >> Web Development >> Cascading Style Sheets >> CSS and the future role of Fireworks and Photoshop
Page: [1]
 
paul rayner

 

Posts: 200
Joined: 3/15/2001
From: yeppoon, qld, aus
Status: offline

 
CSS and the future role of Fireworks and Photoshop - 3/5/2008 0:59:01   
As we move to more and more use of CSS, and less use of tables for layouts, I'm wondering where the use of Photoshop and Fireworks for creating sliced images for "intricate" page designs fits in?

Is that an acceptable use of tables?
Is there a way to deal with those sliced images using CSS?

Hope this post is in the right place.

Cheers



_____________________________

" In theory, there is no difference between theory and practice. But, in practice, there is!"
Tailslide

 

Posts: 5771
Joined: 5/10/2005
From: Out here on the raggedy edge
Status: offline

 
RE: CSS and the future role of Fireworks and Photoshop - 3/5/2008 4:50:17   
No tables are for displaying tabular data only.

Photoshop and Fireworks etc are useful for creating images for the markup and background images that you can then insert into a stylesheet.

The problems arise when people either:

1. Try to get Photoshop or Fireworks to produce a web page by itself (save as .html) which results in pretty appalling code.
2. Try to use big sliced up images to assemble their sites sort of like a jigsaw.

The term "slicing" tends to be used for the latter - dicing up a big image of a web page into chunks and reassembling it into a .html page. This isn't a good idea at all. It's too fragile, too hard to maintain, too difficult to read mostly.

There's nothing wrong at all with using (for example) thin slices of an image, repeated vertically or horizontally as a background to a page or a section of a page - that would expand and contract with the content and wouldn't actually include text-as-images. Nothing wrong either in using a bigger image as a background for a banner or anything actually - the secret is to plan for flexibility.

Edit: Have a look at this page: http://tuscany.cssmastery.com/ It's done as an example for a tutorial on CSS. Have a look at the images used and how they are used (right-click and look at the background images for each section for example).

Personally I'd have put the colour photos into the markup itself but still - it's a reasonable example.

Another edit: while you're there have a look at the main site page: http://cssmastery.com/ that's a nice book - you can download a sample chapter.

< Message edited by Tailslide -- 3/5/2008 4:56:54 >


_____________________________

"My strategy is so simple an idiot could have devised it"
Little Blue Plane Web Design | Blood, Sweat & Rust - A Land Rover restoration project

(in reply to paul rayner)
Page:   [1]

All Forums >> Web Development >> Cascading Style Sheets >> CSS and the future role of Fireworks and Photoshop
Page: [1]
Jump to: 1





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts