[Whoops, should have been posted under CSS, XHTML/HTML & Javascript??]

 

This may be a pretty general question but there is something I can't quite grasp at the moment.

 

I'm familiar with doing 'structured' type programming, ie. simple high level solutions using filemaker, visualstudio, basic and some pic chip stuff. Once I've learned the syntax I been able to achieve my goals.

 

What I'm struggling with at this point is how html, css and javascript, flow and mesh together. I'm used to seeing the flow, ie. line by line, and with conditional branching returning back to the main etc.

 

I'm trying to learn html/css/javascript all at once and are getting sidetracked ie. learning a bit about each, but mastering none. I've got the gist of styling with css and creating the page with html but implementing javascript into the page is causing issues. I'm ok on the syntax side of js.

 

Sometimes input boxes and buttons are here, there and sometimes not depending on how i'm positioning or styling the page. I don't get it.

 

There is no point in posting any code as that would be too specific. What I would like to understand is how the web browser reads and interprets the code.

 

Any thoughts appreciated.

 

[EDIT] btw. I'm coding by hand in notepad++

 

Steve.

Edited March 17, 201412 yr by stixstudios

JavaScript supports much of the structured programming syntax from C (e.g., if statements, while loops, switch statements, etc.). One partial exception is scoping: C-style block scoping is not supported. Instead, JavaScript has function scoping (although, block scoping using the let keyword was added in JavaScript 1.7). Like C, JavaScript makes a distinction between expressions and statements. One syntactic difference from C is automatic semicolon insertion, which allows the semicolons that would normally terminate statements to be omitted

For a greater understanding you might want to delve into "How browsers work". This will kind of put it into a scope of a 'programmer' mind set.

WARNING: it's a large article with lots of information.

For a greater understanding you might want to delve into "How browsers work". This will kind of put it into a scope of a 'programmer' mind set.

WARNING: it's a large article with lots of information.

 

Yet another excellent link bookmarked. If I ever to to read all of my bookmarks I'll be a world class repository, only hope I wont need a world class suppository to get it all back out again.

For a greater understanding you might want to delve into "How browsers work". This will kind of put it into a scope of a 'programmer' mind set.

WARNING: it's a large article with lots of information.

 

Oh sh*t, you're not wrong!! This is perhaps the most dumbest question I've ever posted on a forum Oh why oh why did I ever do it. I was actually hoping for something just a little more concise.

 

All jokes aside though, thanks for your efforts drt. I'm slowly trawling my way through it and now I at least know what the DOM and DTD is, so I've learnt something already. It's probably worth anyone getting into web dev to browse through it, I'm sure there's something to be gleened from it. Although I reckon that if you can understand all that waffle, you should be working for NASA.

 

Steve.

Edited March 18, 201412 yr by stixstudios