The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
I've been here brfore preaching about using xHTML and CSS to layout pages instead of tables. One or two of you were sceptical about this method, and a few of you have seen the simple CSS/xHTML layout I have used for my own site... But I had to show you this...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
http://wip.blackwellpublishing.com/wwwsubjsitescorp/
It's only a concept a the moment, but the layout is generally the final product. But check out source code (minus comments, about 130 lines), almost a 3rd less than if built using tables for layout. Look at the CSS for the #leftcolumn, #centercolumn and #rightcolumn, tru static/fluid layout.
Rob... before you ask, it works perfectly in IE6, NN6.22/7 and Moz 1.2 still a few minor positioning bugs in IE5/5.5, but this is due to it's box model handling.
I rock...
CSS rocks, this is the future of website design...
Page:
that website looks quite similar to the new-look Nintendo Edge. Check it out when Issue 3 gets published on May 1st.
boadle wrote:
> Lads, Tyra,
>
> I've been following this excellent thread, and was hoping to ask a few
> questions. I'm an experienced web designer, with a good knowledge of
> the workings of HTML, and basic CSS.
>
> I'm working on a very big application for a large Pensions company.
> We're building a web application that will allow brokers to apply for
> and manage pensions of their customers, amongst other things.
>
> One of our main drivers, from a technical point of view, is keeping
> the file size down, and this method of using the Style Sheet seems to
> be an excellent way of seperating content from design.
>
> Can you advise as to whether you think this will be apt for what I'm
> trying to do based on this description:
>
> We will be building a system which consolidates all the existing
> offline applications. It will consist of (probably) several hundred
> screens of data entry, customer management and account viewing info.
>
> This will typically be in the form of a dozen or more form elements
> per page, including radio buttons, drop downs and text fields, created
> in HTML, then developed in JSP.
Your going to need more than just JSP/HTML and CSS... How about XML? xSLT? CSS2? xHTML? It's good you've reduced your target browsers, but you'll hit loads of problems using a pure CSS layout between IE and NN/Moz... Box Model, filters, pseudo classes, voice-family.
I can give you more advice on this privately if you wish in my capacity as a Senior Website Designer. I have produced stuff like this in the past and would be willing to discuss anything you want about this with you.
Drop a line to a.tyla@(spamtrap)talk21.com and we can go from there.
> Lads, Tyra,
>
> I've been following this excellent thread, and was hoping to ask a few
> questions. I'm an experienced web designer, with a good knowledge of
> the workings of HTML, and basic CSS.
>
> I'm working on a very big application for a large Pensions company.
> We're building a web application that will allow brokers to apply for
> and manage pensions of their customers, amongst other things.
>
> One of our main drivers, from a technical point of view, is keeping
> the file size down, and this method of using the Style Sheet seems to
> be an excellent way of seperating content from design.
>
> Can you advise as to whether you think this will be apt for what I'm
> trying to do based on this description:
>
> We will be building a system which consolidates all the existing
> offline applications. It will consist of (probably) several hundred
> screens of data entry, customer management and account viewing info.
>
> This will typically be in the form of a dozen or more form elements
> per page, including radio buttons, drop downs and text fields, created
> in HTML, then developed in JSP.
Your going to need more than just JSP/HTML and CSS... How about XML? xSLT? CSS2? xHTML? It's good you've reduced your target browsers, but you'll hit loads of problems using a pure CSS layout between IE and NN/Moz... Box Model, filters, pseudo classes, voice-family.
I can give you more advice on this privately if you wish in my capacity as a Senior Website Designer. I have produced stuff like this in the past and would be willing to discuss anything you want about this with you.
Drop a line to a.tyla@(spamtrap)talk21.com and we can go from there.
Lads, Tyra,
I've been following this excellent thread, and was hoping to ask a few questions. I'm an experienced web designer, with a good knowledge of the workings of HTML, and basic CSS.
I'm working on a very big application for a large Pensions company. We're building a web application that will allow brokers to apply for and manage pensions of their customers, amongst other things.
One of our main drivers, from a technical point of view, is keeping the file size down, and this method of using the Style Sheet seems to be an excellent way of seperating content from design.
Can you advise as to whether you think this will be apt for what I'm trying to do based on this description:
We will be building a system which consolidates all the existing offline applications. It will consist of (probably) several hundred screens of data entry, customer management and account viewing info.
This will typically be in the form of a dozen or more form elements per page, including radio buttons, drop downs and text fields, created in HTML, then developed in JSP.
The forms will include some basic images, background colours and images.
We are only supporting IE 5+ and NN6+.
I don't quite (yet) understand how this advanced CSS works, and before I invest any serious work time into testing it out, I was wondering if someone could point me in the right direction?
Thanks in advance,
boadle
www.boadle.com
I've been following this excellent thread, and was hoping to ask a few questions. I'm an experienced web designer, with a good knowledge of the workings of HTML, and basic CSS.
I'm working on a very big application for a large Pensions company. We're building a web application that will allow brokers to apply for and manage pensions of their customers, amongst other things.
One of our main drivers, from a technical point of view, is keeping the file size down, and this method of using the Style Sheet seems to be an excellent way of seperating content from design.
Can you advise as to whether you think this will be apt for what I'm trying to do based on this description:
We will be building a system which consolidates all the existing offline applications. It will consist of (probably) several hundred screens of data entry, customer management and account viewing info.
This will typically be in the form of a dozen or more form elements per page, including radio buttons, drop downs and text fields, created in HTML, then developed in JSP.
The forms will include some basic images, background colours and images.
We are only supporting IE 5+ and NN6+.
I don't quite (yet) understand how this advanced CSS works, and before I invest any serious work time into testing it out, I was wondering if someone could point me in the right direction?
Thanks in advance,
boadle
www.boadle.com
Agreed, CSS is the future. It's also bloody amazing. Maintenance becomes a simple task of changing a single declaration and the things you can actually do with CSS are amazing.
It is without a doubt the best, most effective and (once the base codes written) easiest way to build, update and modify a website.
It is without a doubt the best, most effective and (once the base codes written) easiest way to build, update and modify a website.
Whooo! wrote:
> What you don't seem to appreciate is that this is the future, CSS will
> take over from tables and all that other crap that was never designed
> to be used how we use it.
Indeed Andi, this is true
With being deprecated as of HTML4.01 and xHTML 1.0/2.0 and newlaws coming into place regarding Accessability and Disabled right (this applies to anything within the public domain), CSS is the way forward with well structured xHTML. On top of this, CSS allows you to repourpose your site for other media such as PDA, Print, Tablet and Text browsers without having to rewrite the page everytime you want to use the code again.
is nologer accepted as the correct way to layout a site, tables were never designed to do this, but have been used due to poor browser support for CS standards. This in now being rectified in the latest version of browsers and you'll soon see more and more CSS based sites appear.
> What you don't seem to appreciate is that this is the future, CSS will
> take over from tables and all that other crap that was never designed
> to be used how we use it.
Indeed Andi, this is true
With being deprecated as of HTML4.01 and xHTML 1.0/2.0 and newlaws coming into place regarding Accessability and Disabled right (this applies to anything within the public domain), CSS is the way forward with well structured xHTML. On top of this, CSS allows you to repourpose your site for other media such as PDA, Print, Tablet and Text browsers without having to rewrite the page everytime you want to use the code again.
| 's and |