boen_robot
-
Posts
8,493 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by boen_robot
-
PHP - the language - is interpreted by an interpreter.PHP - the interpreter - is written in the C language, which is compiled.What you have on your machine is a version of the PHP interpreter. That interpreter itself is considered to be "compiled/built" since it was produced by a compiler. You don't have a compiler.So, when the page says It's referring to the thing that produced the interpreter.You don't upgrade the compiler, since you don't have one. You upgrade the interpreter with another one that was generated by another compiler.Since you're currently using XAMPP, it might be a better idea to uninstall it before you continue, and then install Apache separately. A compilation of Apache built with VC9 that PHP recommends is ApacheLounge's compilation. Installation instructions are found within the zip archive.PHP builds are found on a separate page on the PHP site. Since you'll be using ApacheLounge's build, you'll need the "VC9 x86 Thread Safe" build. The "VC9" part is important for XDebug, and the "Thread Safe" part is important for Apache.
-
How would you go about creating the code for this display in Xhtml?
boen_robot replied to Isibella's topic in HTML/XHTML
As dsonesuk hinted, you can specify borders to make the table look L-shaped, even though that's, strictly speaking, impossible.So, something like: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8" /> <title>L-shaped table</title> <style type="text/css"> table {border-spacing:0;} td {border:1px solid black;} .left-merged {border-left:none;} .right-merged {border-right:none;} </style> </head> <body> <table> <tr> <td rowspan="3" class="right-merged">Left</td> <td class="left-merged">Right1</td> </tr> <tr> <td>Right2</td> </tr> <tr> <td>Right3</td> </tr> </table> </body></html> Not required is not the same thing as forbidden . -
SVN repos usually have the form of having folders called "branches", "tags" and "trunk" at their root, and then go from there."tags" is supposed to contain your code at certain deployed versions, and a common naming convention is for each folder in "tags" to reflect the version (number) itself."trunk" is supposed to be the latest, bleeding edge, yet to introduce to the outside world version. Nothing to name there (since it's only one version, there's no need for subfolders and naming conventions about them).And as for "branches"... that one depends on the kind of project... some developers use it for experimental modules (each name reflects the module) that would eventually be merged with the trunk, while others prefer for branches to be a kind of trunk for modules, while trunk itself contains the glue for all branches. Exactly what I thought the first time I used it .Important note (so that you don't suffer like I did after I "relaxed"): Rename ONLY with TortoiseSVN's rename command. Forget the Windows equivalent, and given that some IDEs, despite being SVN aware, mess up, avoid renaming from them too. If you don't do that, you may have to re-checkout your code (i.e. delete your code folder, and in a new empty folder, do a "SVN checkout"), which in turn means losing any uncommitted changes.
-
Yes, but like I said, this "server" is actually a collection of special files, not a constantly running binary program (i.e. it is NOT in the style of MySQL or Apache). TortoiseSVN can create the initial empty version of these files => You don't need anything beyond TortoiseSVN if your "server" is on the same machine as TortoiseSVN.
-
TortoiseSVN is not an SVN "server" in the sense that you can't remotely extract stuff from it by default.However, an SVN repository is merely a collection of (special) files - files, which TortoiseSVN is able to create. It simply is unable to serve them over a network. So with TortoiseSVN, you do have a client and server, but have the client be on the same machine as the server.But if you're going to push a copy of the repository to a backup server, you don't need to have a "server" in that sense. If you start needing it, there are Apache modules (I'm not sure if they were bundled with TortoiseSVN...) and other binaries that allow remote fetching of repository managed files. In that scenario, the remote clients will have TortoiseSVN as well, but instead of using the "Create repository here" option, they'll "checkout" the repository from the server machine.
-
Sounds good, but... Why Subversion Edge? TortoiseSVN is much more intuitive IMHO.
-
Your fears are definitely unfounded. Besides, what's the worst that can happen? Someone logs into your repo and deletes all of your files... so what? You have a copy at your computer. If you use SVN, you'll lose your history while still keeping your latest files, and if you use Git, you won't lose anything. The only REAL question is if you want your big project's source to be known. If the answer is anything other than "no", you should definitely consider a hosting server in addition to your local copy.
-
I've worked with both Git and SVN, although I can't really call myself an expert at either. My experiences with both echo what justsomeguy said.Comparing Git and SVN... Git and SVN are very different in their approach, with the biggest difference (from which most other differences spawn) being that SVN is a centralized system, whereas Git is a distributed system.What does this mean really? With SVN, you can move or copy the repository (i.e. not simply the files in their current state, but their history and all that), but doing so disconnects you from the "central" server completely, so this is usually only done if you switch servers. You could also instead "checkout" the code, i.e. get the files at a certain state, and place the changes back into the central server (while keeping a copy on your computer, obviously).With Git, everyone has the full repository, and there is no truly "central" server, although any device can potentially act as a server (i.e. allow others to download a repository copy from it or receive changes after an authorization). It's a matter of agreement who gets to host the master code.If your projects are open sourced, you could use GitHub as your backup/(pseudo-)central node. If not (or if you choose another Git hosting service), you could always migrate - as long as there's at least one person with a copy, everything will be intact.
-
Git: Staging All Untracked And Modified Files
boen_robot replied to skaterdav85's topic in Version Control
I just noticed this... I didn't even know GitHub made ANY clients. -
Git: Staging All Untracked And Modified Files
boen_robot replied to skaterdav85's topic in Version Control
Just curious... have you considered using a GUI tool like TortoiseGit for example? Things like that are a check box away there. -
Well yeah, getElementByName and getElementById don't make sense in an XML context (well, IDs do in special circumstances, but that's another story). See the examples in DOM Access Nodes
-
Normally, the output of PHP stats as soon as your first "echo" and the like or first non-PHP content. Once output starts, you can't send headers, which among other things include cookies and redirects (basically, anything that is not "output", you can count as a "header"). It seems your old server didn't immediatly started sending output, but instead waited for your script to finish. This allowed your script to send headers even after your first echo. Why exactly did it do that is not certain. It is typically due to some kind of output altering script that runs transparently after yours - because the output might be altered, the web server would always wait for those scripts to run before it sends the output. Where does ob_start() fit into this? ob_start() holds out PHP output until you either call ob_flush() or the script ends. In other words, you again hold out output. It's just that this time you're doing it on the PHP level rather than the web server level. For performance's sake, it would be best if you could instead rewrite your script in such a way that the redirect detection is done before any output.
-
Considering IE's history, I am. Can't wait for the final version . With the exception of MathML and Web Workers, I'm having a hard time thinking of (stable enough) stuff they're missing.
-
If you ask me, step 4 must be step 1... what's the point of doing the rest without W3Schools' blessing? If they don't want to create a wiki themselves (like wiki.w3schools.com), that's fine, but as said, we still need them to at least "endorse" another wiki made in their honor. And as said, if the answer is explicit "No way", that's fine too, but then the whole plan falls apart. at times like this, I wish I had a blog. (I don't want to use a premade CMS, yet I never have enough spare time to set aside to make a good blogging system... add on that the fact I'm my hardest client to satisfy...)
-
It uses a database of its own kind, along with files of its own kind... like most CMSes... move either or both, reconnect them if needed, and you're set... the usual.
-
The basic features of MediaWiki appear to be quite off from what Wikipedia has... let's just say that we can do better things on the forum with its basic package if we were to dedicate a whole board to that. There are a few add ons for MediaWiki that once added make it feel a lot better, but a hosted package is just not going to let you add those (or perhaps some do... just not the one at SourceForge.net; the one I have small experience with).And porting... what porting? No porting there AFAIK... but then again, I'm not quite an authoritive person to check up for that, so I may be wrong.
-
Stop it, stop it! You're making it sound way too cool and exciting .I refuse to bug my mind with this idea, as I'd otherwise go more rogue than Sarah Palin if it doesn't go through .(BTW, a hosted MediaWiki, from my small experience with one, sucks... a full fledged hosting or GTFO)
-
I wish they could... I don't know... wikify their page or let people post comments... oh, the irony.
-
Yeah, good point... W3Schools is not "authoritive"... it's just "popular" (proven by their top spots on Google about [something] tutorial).
-
Errr... turtle... are YOU the author of this, or was it just a link you found out somehow?I noticed the site just changed some of its comments, and some are conviniently ones I just made remarks about above.Who's the author anyway?BTW, I wish they mentioned something about the forum... I'm sure everyone you ask will say it's a whole different story (that's assuming they know of the forum's existance)... and if there's critisism to that too, we can in most cases tackle it (no, we won't stop manually approving members any time soon; still too much spammers).
-
I wonder what sources they have for that... AFAIK, W3Schools have not "refused" to aknowledge this... quite the opposite, there are aknowledgments all over this forum. I remember there were once quite a few disclaimers around the site too, though I seem to be unable to find them right now.I keep wondering why do people need clarification on that though... first of all, true newbies don't even know W3C... only people that have learned web development from other sources know it... and even then, what could make one think that "Copyright 1999-2011 by Refsnes Data" implies W3C?... you know... considering how some people equate muslims with terrorists, this might not be that surprising.A lot of the errors seem to be HTML5 related... yep... no surprise there... they publish something, and boom, the next day a new browser version or HTML5 iteration comes and makes things false (by "they", I actually refer to both W3Schools and W3Fools really; yeah, the spec is in THAT much flux)... and yet people keep asking that W3Schools make tutorials on [insert fancy draft spec here]... I'm going to use this site as an example of why they shouldn't do that next time someone suggests that.Oh, and some commentary in case the W3Schools' staff or W3Fools' author(s?) reads the site and this topic: This is not true. The heading elements' number defines their rank for their importance on the page. To be fair, that's not exactly true either... those elements define the rank of the heading in the document hierarchy with higher numbers defining headings further down the hierarchy (i.e. more specific; a heading for a smaller scope if you will). What's the problem here? The target property is indeed part of the spec, and assuming that they don't know of any browser that supports this property, the information on W3Schools' page is accurate, is it not? I think that both object literals and the "new" operator were omitted intentionally. The word "template" implies the fact that what you're seeing is not the real thing, and you're somehow creating copies or something (yes, I know the term is "instance"; think about the newbies!). It is expected from the reader to guess that "new" is the way you create these. I guess they could've explain at least "new", but that would involve explaining a ton of terminology, which is not good in a beginner tutorial. How else do you illustrate that even a boolean value is a (special, but still) kind of object? This is just terribly wrong in each part.Agree but... does anyone have ideas on how to explain the ideas of objects and how JavaScript fits with it? And in a simple way too."www.w3schools.com/js/js_popup.asp.alert() and confirm() dialogs with no explanation that they should generally be avoided. Also no discussion of console.log() for debugging purposes."It was only relatively recently (IE8 I think) that IE started requiring a confirmation and page refresh for any dialogs like prompt() and confirm(), and it's only IE that does this, so unless that's the reason "they should generally be avoided", I'm not sure I see the problem. As for console.log()... debugging overall is not discussed in any of the tutorials. Granted that's a bad omission indeed, if such pages are created, I'm sure they'd include console.log() in the picture. Technically… JavaScript is a trademark originally registered by Sun Microsystems and licensed to Netscape when the language was new. Sun was acquired by Oracle, which now owns the trademark, and Netscape passed the license for the trademark on to Mozilla. The language was eventually standardized under the creative name ECMAScript by the ECMA international standards organization to avoid legal conflicts with the trademark owner. Similarly, Microsoft named its clone of JavaScript, JScript. Meanwhile, JavaScriptCore, the implementation of ECMAScript in Apple's Safari, appears to be willing to take the chance, and Google's v8 is off doing its own thing being awesome and breaking the mold, man.To put it… plainly, JavaScript is a subset (or superset, depending upon which version of JS you are describing) of ECMAScript. Gee... much simpler explanation, thanks... not. Not even the "plainly" part would be simple to understand. While the history described on W3Schools may not be 100% complete (it misses the whole name lisence parts), there's no way to further simplify the title while keeping it accurate. I'd hate to see explanations like "JavaScript is just the name of the earliest ECMAScript language implementation", which while sort of accurate is almost as confusing as the above explanation."www.w3schools.com/js/js_image_maps.aspWhat in the world does this have to do with JavaScript? "It's called "a practical example"... yep... contrast THAT remark with the people that suggest W3Schools put more real, fully explained examples that show how it all fits together."www.w3schools.com/No links to the specs, ever. "If they ever do that, it is sure to come along with a "W3Schools is not related to W3C" disclaimer next to every link... I don't want to see that. Besides, specs are not really meant to be read by developers... that's what references are for.(P.S. Sorry for some of the quotes... it seems the forum has a limit to the number of quotations that I wasn't aware of until now)
-
Look hereNext time, try to Google it (ironically enough). "robots.txt" was the search term I used for that one.
-
Why are you calling your PHP files ".txt"? It should be ".php"!Also, their message tells you what's the problem: What's the value of $host? Is it by any chance different than "localhost" or "127.0.0.1"? They're telling you remote connections are not allowed with them, so if you're trying to connect to another server (e.g. your computer), you'll fail.
-
<<Please don't post CSS questions in this topic... the whole forum is for this...A conversation previously in this topic is now at http://w3schools.invisionzone.com/index.php?showtopic=35465>>
-
See Guidelines And Netiquette, and the "Links in signatures" part in particular.
