KevinM1

I never understood the point of gaming mice. I mean, if your mouse is tracking too slowly, simply turn up the sensitivity. Adding/removing little weights to get it to feel just seems like a gimmick.

You just need to keep trying. Also, be sure to word your position listing in a way that will appeal to undergrads. Stress that it's a paid internship with the possibility of it becoming a permanent job. That should keep the professionals away.

Ding ding ding! We have a winner. I strongly suggest everyone not named Pikachu do a Google search for PHP sticky forms. For my own sanity, if not your own.

Since you're new to gaming, I suggest getting a console. They're cheaper than a PC, and you won't have to worry about things like graphics cards. I prefer the XBox 360 (better controller, better online services, better technical support), but be aware that access to the full XBox Live system costs an extra $50 a year. I find it to be worth it, but you may not. And yes, the newest consoles play the newest games. That's kinda the whole point. Just be sure to get the version of the game that's specific for the type of machine you own. The PC version won't work on an XBox, for example.

To the OP, if you're interested in hiring college students, put up fliers at your local colleges, especially in and around their computer science departments. Also, put the job up on Craigslist. The students off for the summer will be found there looking for temp jobs and places to live next semester. $10/hr for the rest of the summer plus professional work experience and references is a pretty sweet deal for a college student.

Also, show your file handling code.

Hey Dan, what are you trying to do, exactly? As a general bit of advice, remember the differences between PHP and JavaScript. PHP is a server side language. JavaScript is client side, meaning it runs in the browser AFTER the server side code has finished processing. The two sides can't talk to each other unless you use ajax, which I wouldn't recommend trying until you're proficient in both languages. As such, file uploads are done with PHP. I'd combine your forms, as I have a feeling you want both the files and user data to be uploaded at the same time. Also, be sure to write some server side form validation code. Your verify() function can be bypassed by someone simply turning off JavaScript in their browser.

To fully unset an object you need to first unset its data members. A prime place to do that is in an object's __destruct() method. Another helpful method is the __unset() magic method.

Once again, this conflict, like virtually all others on here, stems from certain unrealistic expectations not being met because the member in question doesn't know the rules. Rule #1 - don't be a dick. Thorpe was admittedly hasty in moving the thread and giving the first warning. paddyhaig was in the wrong for responding in such a negative manner. Posts get moved all the time, and mistakes are sometimes made. Taking it personally reflects more on you than the person who made the mistake. To paddyhaig, and any other member reading this, calling someone an idiot, or otherwise insulting the people trying to help you is a surefire way to get ignored, if not warned or banned. The same goes for demanding an answer, then getting pissy if it's not spoon fed to you in a timely manner. This is not our job. We're not employees of The Web Freaks. Like the rest of you we're all volunteers, and are under no formal obligation to provide answers to your questions. We do it because we like programming, we like PHP specifically, and we want to help the community. Moreover, despite what your mother may have told you, you're not a precious snowflake. You will be treated in the same manner as the rest of the community. No special treatment - positive OR negative - here. If you want your problem addressed quickly and efficiently, adhere to the second rule. Rule #2 - ask good questions. ALWAYS post code (in code or PHP tags). ALWAYS provide relevant information: What you're trying to do. Expected results. Actual results. Any errors. DB table structure if necessary. In my experience, there's a near 1:1 of quality questions to quality answers. Clarity in means clarity out.

not tested but i do not understand things at one go im quiet weak and slow when it comes to studying but i got soo much interest in learning how to code a site. after class i come home try to do the work asked by my teacher ask like if he shows me how to work with array the same thing he would ask me to do it in a different way and that is where i get stuck. he has taught me how to do a login system but now when im asked to do it myself i cannot. im starting to get dishearted man. It sounds like one of two things is happening - 1. You're not naturally gifted at this. It's okay, not a lot of people are. I often have to read, then re-read, then re-re-read, etc. a lot myself before I finally feel like I grasp the idea of a new bit of code. Discipline and tenacity are really the only ways to get through it. 2. You have a learning disability. I think you should get tested for it. If you find that you do have a learning disability, you'll finally understand what is causing your frustration and can be taught ways to mitigate it. If you don't have one, the person/place testing you could still most likely come up with a way to improve your study habits. Getting tested is a win-win.

What do you do outside of class? How do you study/do homework? Also, in all seriousness and no offense intended, have you ever been tested for a learning disability?

To be fair, paddyhaig is saying that Thorpe was mean to him in PMs. Without being to see them, and only having the CSS sub-forum thread to go on as evidence, methinks he's going a tad overboard. Again, all based on the evidence at hand.

Of course, none of us are employees of The Web Freaks, so I'm not sure what the OP hopes to accomplish. It's not like we can be fired.

All I saw was: OP: Please help me make my form look cooler. Maybe I'll use CSS tables to make rows of alternating colors. Thorpe: CSS is used in conjunction with HTML. The tables would still be written in HTML. OP: I know that, you idiot (even though I'm the one who didn't take the time to clearly write what I meant)! Thorpe: Oh. Well, using tables for site/form layouts is a bad idea. Use divs instead. Here's a thread explaining it. OP: You're an idiot! No help at all! And you called me Princess! Me:

Okay, try: echo "<select name=\"country\">"; $result = mysql_query("SELECT * FROM tbl_country"); while($row = mysql_fetch_assoc($result)) { echo "<option value=\"{$row['country_name']}\">{$row['country_name']}</option>"; } echo "</select>"; Since you're trying to output an array value within a string (within quotes), you need to use {} around them.

Do you know how to retrieve data from a database? Do you know how to write a while-loop? Do you know how to echo variables? Combine them.

What have you tried so far?

That was pretty awesome.

Larger apps are typically written in an object oriented style, with each class being stored in its own file and included dynamically when needed. If that doesn't make any sense, don't worry about it. Put another way - large apps are written in a way that makes them flexible to change and easier to maintain than what you're used to seeing/writing yourself. Lots of files is a byproduct of this programming style.

If you want to learn C#, do yourself a favor and download Visual Studio 2010 Express. It's a free IDE from Microsoft that has a built-in database server. In addition, get yourself a copy of C# 4.0 In A Nutshell from O'Reilly Press. Now, to your questions... A constructor is not the start of a program/app, but rather the mechanism that creates objects. The basic analogy is that a class is a blueprint, an an object is an individual thing made to the specifications of that blueprint. The constructor is the middle man - it's what actually builds the object. The assembly line. Like Mchl said, whether or not you define a custom constructor is irrelevant. A constructor is ALWAYS invoked when a new object is made. Custom constructors are often necessary as they allow us to control the default state of a new object by giving us a place to run our own initialization code and to populate data members dynamically. Return and echo are two different beasts entirely. Echo merely spits output to the screen. Return is more useful as it allows us to retrieve the value generated by a function to use in other code. Return is necessary due to scope - values generated within a function are not accessible to the code that invoked the function unless they are returned (exception made for arguments passed by reference, but that's another discussion entirely). PHP is a little different than the other languages you're familiar with in that function signatures have no visible return type, and the types for arguments are optional, and often not used. Despite these visible differences, you can (and most likely should) treat PHP functions as though they do have a particular return type (void is legitimate) and argument types. It'll made your transition smoother.

So... where's the PHP in that last large chunk of code? Or, to look at it a different way: Who wrote the '$this' that's causing the error?

Why don't you tell us what you're trying to do? It's hard to give a fix for your problem without seeing more than one line of PHP.

Easier code maintenance. Say you needed to modify that code sometime down the line. What's easier - going to every file that has the code hard wired into it and copy/pasting the changes, or visiting one file, editing it, and having the changes automatically applied to all the other files that use that code? EDIT: along similar lines, modularity.

The '=' is the assignment operator. You want to use '==' in conditionals for equality.

Much better :thumbs up: