Experience today to see your version of the section of the tutorial, for beginners always say good dongdong ha.
For the big picture of the cutting, I think I can rule cut on the rules of the cut, do not arbitrarily cut ... The reason I say this is because I usually do not automatically generate HTML tables with FW after slicing.
We can first look at the structure of the automatically generated table for FW (not specially set):
If a picture cut two lines, the first line is three plots, the second row is two plots, the width of these five slices are inconsistent, then the output automatically into the table will be 3 rows 6 columns of a large table. We found that each cell that placed the slice is not set to the fixed width and height parameters, in fact, for the control of cell size, FW uses the technique of transparent picture filling, in the last row and last column of the table, with several fixed-size cells, These cells use a spacer.gif picture, which is why we usually see the source of the slice that is automatically generated by FW and the very small image that appears in the file.
After a careful analysis of the principle of not nesting large tables, it will be found that the FW will be in rows (columns) of the smallest width (height) of a slice as the smallest unit, to generate the number of columns in the table how many rows, that is, the above slice example is clearly only 5 slices, There is no reason to layout with a 2-row 3-column graph (in fact, it's hard to achieve seamless results when you manually make table settings in the DW).
In this way, if we adjust the size of a slice, we need to the entire large table to be again output, for the better designers, frequent changes is a very painful thing.
So I am in the actual use of slicing, are only output pictures, do not output the table, the form to do their own .... The practice is to have the same height of peer slices with a table, if you really need a row to do different heights of slices (try not to do so), you need to take the highest slice as the basis for the creation of complex table nesting.
The ultimate effect of this is: a large figure after the cut is not automatically generated by the FW is a large table, but a number of tables grouped together ... One is to facilitate the modification of a slice of the picture, and the second is to speed up the download speed of the large map (we know that the browser for <table> tags are always downloaded to the </table> label appears when it will show you)
I am sorry, wordy so much, do not know if you are listening to my meaning, because the present inconvenience, there is no case diagram to help us explain, another day to fill out the bar ...
PS: Just saw a problem about the output of HTML settings, for beginners is very meaningful, if you read the article, you do not have to listen to me here wordy so much, haha ~ but feel or do the form yourself well ....
