Jump to content


  • Posts

  • Joined

  • Last visited

Previous Fields

  • Languages

Profile Information

  • Location
    North Carolina

Dreadful_Code's Achievements


Newbie (1/7)



  1. Good luck with whatever route you take- just remember that there are a thousand ways to build your dream. That's half the fun!
  2. function createList(){ var s; s = "<ul>" + "<li>Armageddon</li>" + "<li>fefwfe</li>" + "<li>wfewfew</li>" + "<ul>"; divMovies = document.getElementById("divMovies"); divMovies.innerHTML = s; That should fix it.
  3. Yeah, markup isn't that bad. It's the coding that takes time to learn. Ooof! Another idea: I've seen webmasters avoid coding altogether- take the basic template, and copy+paste content in between the designated areas. Cut out the middleman! It's quick and dirty, but hey, content is king.
  4. Putting the finishing touches on a kewl webcam app, written with Javascript and PHP. Can't wait to share it!

  5. Ah, yes- just a clarification: in italics The reason your code sample doesn't reach the second alert is because alert() is blocking the other elements from javascript manipulation in the other browsers. Javascript is singlethreaded. Alert() stops javascript in its tracks, and will not resume with interacting with DOM elements until you close the alert box. It just may be that FF is doing a little more than the other browsers the microseconds before firing the alert() function. Replace alert() with console.log() and compare the difference.
  6. If you want a starter site up in a jiffy, go with a CMS. Joomla works pretty well out of the box. Drupal and Wordpress are also great publishing platforms,too. They should also be considered, since you are starting out at 'square 1'. Each CMS offers their own advantages - namely, the community. As a beginner, the community of X platform should be just as important as the software features. You will often times spend more time reading and communicating with others during your journey than you would be pushing code. BUT As a long term project, I highly recommend building your own website from scratch. I only recommend this, of course, if you intend to become more of a coder/developer instead of a marketer. Doing this is not for the feint of heart, though. There are frameworks to help you out. Codeignitor,Yii,Zend, and Kohana are some of the thousands of PHP frameworks out there. They abstract away a lot of mundane tasks such as session handling, page caching, security- the things we often take for granted in cms's. But in any case, building from scratch is not easy, and can fast become a rite of passage. It takes years to really 'get it together'. But once you have built up a toolbox of useful functions and classes, you can build just about anything you can imagine. And you learn more about programming in your favorite language instead of becoming indoctrinated in the culture and idiosyncasies of a CMS. If you want to be really bold skip the frameworks, too. I'm sure that judging by the tone of the above paragraphs, you can guess which route I have taken . Here's an article for your amusement. How to become programmer in 10 years. Written over 10 years ago, and it's spot on.
  7. I don't see a BuildTable() function declared anywhere in the above example, so I'm not sure how it could work on any browser. Can't help you there. However, In answer to your question in the example above the above example: "Code execution actually never reaches to alert("2"); however it does in FF." The reason your code sample doesn't reach the second alert is because alert() is blocking the other elements from loading in the other browsers. Javascript is singlethreaded. Alert() stops javascript in its tracks. It just may be that FF is loading a little more than the other browsers the microseconds before firing the alert() function. Try console.log() and compare the difference.
  8. Use text for a blog post, since it is capped at 65,535 bytes and varchar for a teaser, since it is usually capped at 255 bytes.
  9. So you want the percentages of the widths to change based on the window size. Again, that can be done with media queries.
  10. Okay, I can agree with that. My guess is an unclosed bold or header tag somewhere in the code - or a misplaced { in the stylesheet. Chrome and Firefox tend to 'automagically' fix invalid markup when possible, whereas IE doesn't.
  11. That's not true. This forum would be empty if that were the case. Standards compliant browsers render html specs defined by the w3c consortium. How they do it is up to the browser vendor, and how & when the elements get rendered are remarkably different, as are their rendering engines. Can you please provide a link of a website that looks great in IE8, but terrible in Firefox/Chrome? Conversely, I've can easily give you 10 sites that look good in firefox/chrome but terrible in IE: the topic this thread is about anyway.
  12. Oh brother. First of all, IE isn't the "odd one out". Opera is. IE is the lowest common denominator. It lacks a lot of the wonderful CSS specs we've been enjoying in Chrome and Firefox for years. So why not start with IE? You know that if it works in IE8, it'll rock in a webkit based browser. It's called designing with progressive enhancement. Get the basic features working, then add your fancy schmancy stuff later.
  13. Well, that's awful nitpicky. It's an approach. Reason being: It's a starting point. You could spend 2 hours decrementing the percentage, by a 1/10 of a percent, or exaggerate the layout a little to observe its behavior. You'd know that if the layout wouldn't work at 30% & 60% percent, there are other problems, which is usually the case with WP layouts. One little customization usually spells 3 hours of debugging and code searching for conflicting css sheets and js scripts.
  14. IE has been the bane of web designers everywhere since the 90's. Welcome aboard!.. Piece of advice: Build and test in IE first. Yeah, it's miserable to do that.. but as a general rule of thumb: if if looks decent in IE, it'll look wonderful in chrome and firefox.
  15. Let's try this approach: function cool_object() { this.id=Math.random(); this.created= new Date(); console.log("It's Alive!"); }//Now Let's try it outa= new cool_object();b= new cool_object(); You can see that instead of adding attributes to the Html markup, you can create an object with javascript with just about anything you want. Prototype is used to add methods to javascript objects, and is also needed for extending 'classes' you create with JS. (they aren't exactly classes after all...) Believe me when I say that the above approach using this.property_name to assign properties will give you enough to work with for years. However, Maybe you want to say "It's Alive"- using the above example- by explicitely calling a method name from the cool_object class. function cool_object() { this.id=Math.random(); this.created= new Date(); }cool_object.prototype.talk= function() { alert("It's Alive!"); }//Now Let's try it outa= new cool_object();a.talk(); And that's it in a nutshell. Notice how the method is defined outside of the original cool_object function. This is because javascript is not a 'true' OOP language, but it CAN behave just like one. Hopefully you can glean a few good things from this lesson. You can always refer to MDN for more info on OOP javascript. You will see that my examples are very similar to the ones provided there. That's because that's all there is to it!
  • Create New...