Brendon Branigin

Thanks, it's realy to bad that documentation on asp.net is so rare the sites i've seen using asp.net are realy amazing. Thanks for the book links, I will be sure to check these out

Well I’m looking to learn asp.net and c# and I’ve found some information but nothing substantial. Starting with c# what tools do I need (I already downloaded the free c# visual express from MS) and where are the best tutorials at that can take me through the basics all the way to the advanced.Same questions for asp.netWhat tools do I need?Where are some good tutorials?I have already searched Google but most of what i found are video tutorials which are no good since I’m stuff on dialup. Thanks in advance for the help, include you opinions/experiences with these technologies in your post if you like

I will be age 16 on June 26th and I have been designing web pages off and on since 13 ( might have been a little earlier) though I am just now getting serious projects like a site for my towns local library and a site for a 50,000 member gaming emulation community.Im just now getting to a point where im confident in my skills enough to progress to the next level (database driven sites using mysql and php). I love web design (why else would i be a member of w3schools ;/)

Im realy getting sick of this advertising

@snowboard01the site restriction is probably set fourth so that people who have disabled javascript for whatever reason (be it fear of malicious code or something else) can still enjoy the site.it's NOT about the inability to execute javascript (as it is handled client side) its about the un-willingness to use JS.

that kid wouldnt be a webdeveloper, he would be a script kiddie. You dont become a developer until you know atleast the basic language (in this case, xhtml)Though everyone starts as a script kiddie anyone who is serious about web development will read enough to know about the w3 and their work. I personaly didnt know about the w3 until i started reading up on css.A web developer wont come and tell somone to fix his code, hes serious and he wants to understand what he did wrong so that he can further his knowledge on the subject.

'The layout will still be the same no matter what style sheet you use for the reason that the site is made in tables and will always have that default layout. "the WHOLE point of css is to seperate content from design. By using tables to create a basic layout you break the most basic rule of web development. When no styles are applied your site should display as a basic text only page with content after content. go to a fully css xhtml compliant site and disable style sheets and you will see what i mean

webmasters-wallwhere "wall" plays on both your alias and the concept of a bulleting board type wall that has a callaboration of information on it

why not put all the css in the same file if you only have 2 layout styles. Just add the styles to the .css file and make sure theres no conflicts, atleasts that what i do

jump as soon as the w3c says to? css is just in recent years becoming widespread and its been a "standard" since 98

a good start would be to stop calling everyone ignorant, and chances are if you have to say "im not trying to start a flame war" than your post is to agressive."What if a year from now the 'next big thing' comes out,"something new wont come out to replace css simply because css was designed for exactly what it does. the only reason its a new "rule" to use css for layouts is because tables were NEVER designed to be used to make layouts. Even more to the root is the fact that HTML was never designed to make sites look good. Its a structural language <h1> welcome to some site</h1><p>some info</p><h2>a content section</h2>etc etcit was never suppose to be used to create pretty sites its a barebones language for displaying information, not styling it. Learn the new standard, if you already know it then stop complaining and get back to work

Ive seen what someguy is talking about with the unsmooth scrolling, it actualy has to do with the heavy use of transparencies and large background images combined.

i dont have the money and i dont have somone reputable to watch me. When i go to college that will be the time for me to certify myself

or you could do some magic with javascript and spans ;/ lots of spans

background-color : #xxxxxx;height: Xpx;it doesnt have to be px either, theres tons of different measurement units

unfortunately theres no css equivelent to valign. setting the content inside the html element (be it td div li w/e) to have margin top and bottom auto works well in ff but not in ie since it doesnt even read the code. I dont have a good solution unfortunately

neither worked

;/CSS is the new way and more proper way of making layouts. Tables were never designed to create webpage layouts they were designed to tabulate dataTables are inacessible when it comes to things like web bots and screenreaders so by using css and divs it increases your potential audience. In order to conform with the accesibility standards you need to use divs and css.(may not matter to some but if you ever work on a website for a goverment controled group then your site will need to be accesible to those with disabilities)The css can be faster then tables because if a site uses similar layouts through the entire site then the css does not have to be completely re downloaded each time. it may not matter to people on dsl or cable but some people are on dialup due to where they live *me* i recently re did a site uisng divs and css and i was able to nearly cut in half the load times for me and my 21.6k connection.using tables is lazy. I could design a table layout in a matter of minutes by the time i started using css. Now it takes me longer but im getting quicker and soon it will be as easy as tables. Theres no reason other then being lazy to not use divs and css. Its not like its hard to learn

#tabstable is an id, the # tells you thatif it were .tabstable it would be a classID's should be used only on one html element per pageclasses can be used on multiple html elements per pagethat css right there will give whatever element in your html file with the id #tabstable a solid black border on its right side.

instead of giving #content a margin to push it to the left why not just float it left, then it will never try to go left past the #leftnavfloat the footer left aswellapply a clear right on the contentfloat left the header with a clear right aswellthis should keep all the divs properly placed without using static margins and what have you. It should also solve your problem

well thats no good, that means anyone using padding or margins on content containing divs will have to write 2 different css files ;/when i was redoing runuo.com's site (not updated yet) i ended up having to apply margins to all the actual content (<p> and <h#> which is still a bad solution because the <h#> tag looses the margin on the 2nd line if it has one.*sighs*

question on the padding/margins thing asp if you dont mind me asking ;/why is it that in FF when padding is applied it doesnt effect the size of the div but in IE it makes the div bigger?

float left the elements you want to appear horizontaly from each other

you could start by not being so DAMN rude on this site

alright, thanks guys. if anyone finds that answer to this let me know, personaly i think eliminating 50lines of css would be worth it ;/