Splitting a paragraph in css (Full Version)

All Forums >> [Web Development] >> General Web Development



Message

fp2003uk -> Splitting a paragraph in css (2/10/2007 17:54:56)

Me again !

Does anyone know how to split a css paragraph so that it thinks its 2 cells ?

I have a huge amount of price lists laid out in html tables that I want to convert to simple split paragraphs.

Im sure its a simple but of code but I cannot work it out.

Thanks



jaybee -> RE: Splitting a paragraph in css (2/10/2007 18:01:48)

Price lists.

Presumably you have an item name, possibly a number and a price?

That is precisely what tables were designed for. If you have data you put it in a table. Anything else goes in divs, paras or whatever.

Here, this should help



fp2003uk -> RE: Splitting a paragraph in css (2/10/2007 18:43:41)

Thanks for that.

I didnt want to use the traditional html tags but dont have time to learn how to do it in pure css. I cannot import all my old tables as they dont validate and require tons of changes.

Looks like im copying and pasting all the text and numbers over into new tables. 2 columns and loads of rows.

Im in for a long night then !

Cheers



jaybee -> RE: Splitting a paragraph in css (2/11/2007 2:15:53)

You still use the standard HTML table tags

<table>
<tr>
<td>

But at the top of each table you have a <caption> which in your case would say
<caption>Prices of xxxxxxxx</caption>

You then have headers for each column <th>

So your table would be

<table>
<caption>xxxx xxxx xxxxxxx xxxxx</caption>
<tr>
<th>Item Description</th>
<th>Item Price</th>
</tr>
<tr>
<td>T-shirt</td>
<td>$3.99</td>
</tr>
<tr>
<td>Polo</td>
<td>$3.99</td>
</tr>
<tr>
<td>Hat</td>
<td>$3.99</td>
</tr>
</table>
You style the table in css by using

table {
th {
tr {
td {



fp2003uk -> RE: Splitting a paragraph in css (2/12/2007 12:32:26)

Can I change my forum name to "I love tables and boo to css"

Sorry guys but this css positioning lark has been traumatic enough to put me off web building for the rest of my working life !

Heres why:

1: I can get things almost perfect in IE but then it all goes pear shaped in fox with css.

2: With css I have to look at 5 pages (files) to isolate an error and with html tables its just 1 in split mode.

3: Tables give me excellent positioning and easy adjustment for the whole page.

4: Ive noticed no real difference in file sizes.

5: I get waaaay more w3c errors with css than I do with tables, especially the "didnt close the tag error" which seems to come back after fixing it.

6: Css glitchy problems with global changes that I did not make.

7: The guy who invented css was on the right track but you would think he would have made it more user friendly and wysiwyg able.

8: Ive checked out tons of corporate sites and all have lots of tables for layout and none comply with w3c. If it was the 'big issue' that many believe then these corporates would be on the case immediately. Most pure css sites that ive seen have very simple layout and usually positioning errors in fox.

9: If all the browser companies get together on standards and css then I might reconsider.

10: I hope they dont ban tables [:D]

Thanks for everyones help but im sticking with tables for as long as the browsers put up with them.



rdouglass -> RE: Splitting a paragraph in css (2/12/2007 12:53:23)

quote:

9: If all the browser companies get together on standards and css then I might reconsider


There is only 1 'browser company' that consistently has problems. [8|] Don't design in IE. Design in FF and fix for IE. However, that doesn't help you at this point.

If it helps at all, I have simulated that by using an ASP script that basically checks the length of the text you want to post and divides that in half. Then looks for the nearest 'break' point (no widows or orphans please) and builds the second column dynamically.



fp2003uk -> RE: Splitting a paragraph in css (2/12/2007 14:09:35)

"Design in FF and fix for IE"

Makes no difference at all, the problems are exactly equal either way round. Ive tried both scenarios and the problems are the same either way, position in one but not in the other.

If I design for IE = no good for fx
If I design for fx = no good for IE

If I was forced to build for one browser and one browser alone I would go for the one with the biggest user base = IE

I really do appreciate your help but after a couple of weeks of fiddling with css and then studying what others are doing on the net then reading lots of opinions on the whole browser, css, table war I have concluded that its a waste of my time until the likes of ffox, ie, css and w3c all agree together on strict page rendering rules.

My mate runs a website built entirely with tables and his google rank is surprisingly good, web stats show 90% IE hits, and 10% others.

I think the firefox claims are pretty much the same as the old macromedia flash claims, as in they are not as popular as they would like you to believe. 100 million downloads means nothing, how many site based referrals means everything.

Im off to make lots of lovely bullet proof tables.





jaybee -> RE: Splitting a paragraph in css (2/12/2007 14:25:42)

My sites are all reporting over 30% of visits are from non IE browsers.

quote:

reading lots of opinions on the whole browser, css, table war
Most of the people who slag off css are the ones who can't do it, ergo it must be rubbish.

quote:

I get waaaay more w3c errors with css than I do with tables, especially the "didnt close the tag error" which seems to come back after fixing it.
That is either down to you or the editor you're using. You should check the Tools>Options to make sure your settings are the way you want them.

quote:

4: Ive noticed no real difference in file sizes.

If your css is all internal or inline then you won't.

quote:

2: With css I have to look at 5 pages (files) to isolate an error and with html tables its just 1 in split mode.
Eh? html and css = 2.

quote:

6: Css glitchy problems with global changes that I did not make.
The editor again. You can't blame css for that, it's not dynamic.

quote:

: The guy who invented css was on the right track but you would think he would have made it more user friendly and wysiwyg able.
Why? WYSIWYG was built for hobbyists. Most pros don't work in WYSIWYG they work with the code and use display mode as an assist if they use it at all.

quote:

8: Ive checked out tons of corporate sites and all have lots of tables for layout and none comply with w3c. If it was the 'big issue' that many believe then these corporates would be on the case immediately. Most pure css sites that ive seen have very simple layout and usually positioning errors in fox.
Cost and ignorance. Most of the staff have little incentive to do it any other way and if they do, management won't pay for it. It'll change.

quote:

9: If all the browser companies get together on standards and css then I might reconsider.
They are, Microsoft are working with the Mozilla guys on IE8.

quote:

Google rank is surprisingly good
CSS might improve his rank, it might not. Google rank depends on many factors, content is just one.



rdouglass -> RE: Splitting a paragraph in css (2/12/2007 14:33:36)

Don't want to 'extend' anything but frequently FF users will not go to sites that don't work properly. Don't forget that that factor will affect those numbers. If a site doesn't render well in a browser, why would a user visit that site?

I agree with you on those 'bloated' numbers absolutely. And I agree it is hard to justify that additional work for 10% of your viewers (I feel the same way about the accesibility issues) but be sure *your* numbers are acceptable regardless what your mate's numbers are and you really should be aware how your site looks in all the other browsers even if you don't want to fully support them.

Tables will work. No doubt.

CSS is better. My opinion.

It's similar IMO to going from the DRW to ASP. It has a little learning curve but once you get it, you'll ask yourself why didn't I do that a long time ago?

Oh well, all industries change. Some folks adapt; some don't. Maybe you're right and CSS will go away and tables will come back again; they are easier to imnplement most times. I personally feel the table approach will still be functional for a while but you're going to miss out on a lot of nice stuff. Again just IMO.



womble -> RE: Splitting a paragraph in css (2/12/2007 15:05:10)

Tables are very good for what they were intended for - tabular data. If you want to be semantically correct, then tables don't make any sense.

quote:

5: I get waaaay more w3c errors with css than I do with tables, especially the "didnt close the tag error" which seems to come back after fixing it.

If you code right and validate your pages and CSS you should see very few errors whether you're using tables or CSS for layout.

quote:

I have concluded that its a waste of my time until the likes of ffox, ie, css and w3c all agree together on strict page rendering rules.

Firefox does follow the standards. As has previously been pointed out, it's IE that doesn't. Get your facts right before you start slagging off Firefox.



Tailslide -> RE: Splitting a paragraph in css (2/12/2007 15:06:58)

It'll take more than a "couple of weeks" to learn how to build websites properly. I'm guessing it took you more than a couple of weeks to learn to do it with tables.

But, you know - in the end it's your decision. In my view CSS is the future - I've been building with it commercially for 3 or 4 years now - but the less people I have to compete with using modern techniques the better!! [:D]



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.078125