Jump to content
xisto Community

vizskywalker

Members
  • Content Count

    1,084
  • Joined

  • Last visited

Posts posted by vizskywalker


  1. I'm having the same issues, plus the more detailed stats aren't updating either. At first I thought it was just leftover glitches from when my account was suspended, but it lasted over a month after I got unsuspended, so I'm not so sure anymore. I've looked into the problem as much as I can, but without better access to information on the server, that's not much.~Viz


  2. Thanks guys. Two more questions, though.1) The two nameservers (ns1 and ns2) need to be seperate machines, correct?2) How do the names ns1.domain.tld and ns2.domain.tld propogate across the web if the nameservers are responsible for propogating things beneath them across the web.~Viz


  3. Thanks, but more of what I'm looking for is not how to point my registrar to my nameservers, but to create them in the first place. See, right now I don't have machines ns1.mydomain.com and ns2.mydomain.com, nor am I sure what they need to have to work properly.~Viz


  4. So, I'm thinking of setting up a server on my own. Not that I don't love Xisto, but I'd let to get more practical experience. Plus, my college gives us fully routable unique IPs, so I figured I'd take advantage of this. The one hangup, as far as I can tell, is that I need a nameserver to allow my domain name to point to my computer. So I was wondering what is required to create a name server. Is i t something that anyone can do? Or does it require registration? And if it's something anyone can do, as I believe it is, how do I go about setting one up?~Viz


  5. No problem. It's not the most obvious of functions. I only stumbled across it recently when I was working with the object oriented mysqli interface and wanted to obtain an associative array of the results. A comment by someone at the bottom demonstrated how, using this function, so I wasn't clear on what his code did. I looked up the function, and it turns out it is quite useful.~Viz


  6. Just showing us the table code probably isn't going to help. If it's layout issues, it is likely to be a problem with the surrounding layout or the placement of the table in the code. If you could show us a larger snippet, maybe we could help you. Also, which browser are you using, because that makes a big difference. In fact, the cross-browser issue makes doing tables with just CSS and HTMLDivElements is extremely difficult. I spent a couple years working on that before I gave it up, because getting it to work in even one browser is just not worth it when tables work fine unless you break something.~Viz


  7. If you can do local, as is stated by others, it is the better method. Also, depending on the SQL setup, I believe it is possible to prevent non-local connections, so assuming a remote DB connection will work when you don't have complete control over the SQL setup is not a good idea. However, remote connections are used by large companies that maintain servers devoted solely to DB work.~Viz


  8. There are also several other color picking variations. One very useful one is HSV (Hue, Saturation, Value) where Hue picks the color, Saturation determines how deep the color is, and Value determines how bright the color is. This can be a little misleading though, because yellow is a naturally more bright color than, say, red. One of the reasons for using RGB in screens (and thus computers) is that the human eye only has red, green, and blue receptors. The other colors are mixes of those three, so it is natural to emit light from devices in those colors. Since paper absorbs light more than reflects (emits) it is pigment based, so the primary pigments, Cyan, Magenta, Yellow are used, where each pigment absorbs one of the primary light colors, Red, Green, Blue respectively.~Viz


  9. One thing to remember is that Google Analytics (I believe) uses a slightly different definition of "page view" than we do. I'm not sure why, but it's the only thing I can think of for the discrepancy. I've been the only person (pretty much) looking at my site while it undergoes development and testing, so I know very well how many page views there are, upwards of 100 because I keep refreshing. Google Analytics doesn't count many of these as separate page views, instead, it seems to simply keep that count as time on the page. So perhaps for each visit, a jump from homepage to another page back to homepage counts as 1 view, since it is one person viewing the page on one visit, even though it is two loads. I think that is how the calculation is done. It doesn't seem to be total page views, but visits to that page. Also, I haven't noticed a difference depending on where the code is placed. I agree that the end is best, because it doesn't cause a slowdown of the page loading.

     

    Edit: I just stumbled across something on the Google Analytics help that confirms this.

    In Analytics, if a user comes to your site twice within thirty minutes without closing their browser, they'll register as one visit. Other web analytics solutions may treat this behavior as two visits, depending on their definitions.

    For the full article, which explains in pretty good detail differences between analytics and other stat generators, see this help page.

     

    ~Viz


  10. Yeah, that works, but it doesn't seem to work if the include function and the call to include are in a separate javascript file. As opposed to an embedded script tag like the one you have now. Right now I'm using a workaround where I load the javascript via AJAX for Safari, but I don't like that, and I hate it even more because I have to directly include where I want it as it seems to maintain local scope. Unless I'm messing something up.Edit: Also, I don't know if this matters, but I'm using XHTML 1.1 (Strict), so I don't know if Safari treats that as different from 1.0 Transitional, but since the page is served to Safari as text/html (due to issues with DOM manipulation when it is application/xhtml+xml) I don't think that would be an issue.~Viz


  11. I've been working on an include function for javascript. It works just fine in Firefox and IE, but for some reason, it doesn't result in the loading of the scripts for Safari. The code is as follows:

    function include(url) {  // Include Guard  var scripts = document.getElementsByTagName("script");  for (var index = 0; index < scripts.length; ++index) {	if (scripts.src == url) {	  return;	}  }    // Inclusion  var head = document.getElementsByTagName("head").item(0);  var script = head.appendChild(document.createElement("script"));  script.type = "text/javascript";  script.src =  url;}
    Any suggestions as to how to improve this script so it works in Safari would be appreciated. I used alerts to check and make sure that Safari wasn't returning prematurely, so I know it is being "included", but the included scripts aren't being loaded.

    ~Viz

  12. I have a friend who has helped me out a lot with some of the content on my site, so I have acknowledgments to this friend wherever I had help. However, because the name of this friend is pretty common on the page, search engines tend to index the page for searches of this friend's name. However, my friend doesn't like having a lot of results turn up for the name, so right now I have the page set to disallow in the robots.txt. I'd like to both respect my friend's wishes and have the site indexed, so I was wondering if there is some way to tell search engines they are allowed to index the page, but not according to certain keywords.Thanks,~Viz


  13. I'd agree, except tbody isn't only a thing required by IE, it's also a well established part of the DOM for XHTML 1.1, so I see no problem with it. The sample code works fine in Safari, which is my current problem place. I even modified it so that the table was generated dynamically when the body loaded, and that worked. But I can't figure out what's wrong with my code that I showed you up above to prevent the table from appearing even as a table in Safari. All of the data just gets shown as seeming stream of text, with no proper style.Edit: I just tried another experiment, and found the cause of the issue. Since my pages are XHTML 1.1, they should be served as application/xhtml+xml, and I serve them as such to any browser that accepts it. Safari is included on that list. When the page is served as applicaton/xhtml+xml, Safari fails on your code. However, when the page is served as text/html, the code works. So the problem is somehow related to how Safari handles application/xhtml+xml. Since this code works in the new versions of Safari, is this likely to have been an issue with the old version of Safari? Or does the new version do nice error checking to display if I make a mistake and my code is wrong?~Viz


  14. Thanks, I actually figured that out before I read your post. After looking at the DOM specification, it seems that in theory, tbody is not required. Interesting tidbit, though, when running the code under Safari 2, or the original Safari 3 beta for windows, the elements are added, but do not appear to be in a table, and no class is associated with them. Any ideas as to why?Edit: I think I've determined the problem, but not the cause of the problem. No matter what tag type I pass to document.createElement(), I seem to be getting an Element as opposed to an HTML<Type>Element. This would cause display issues, but I'm not sure why this is happening.Edit: So, after further experimentation, it seems I can successfully change the class using the className properly, but only if I pick an internal style. It doesn't seem to work for external styles unless the object was always present.~Viz


  15. I'm writing a search function to search a MySQL database I have. The search uses AJAX with a php server to search the database and generate a result. The result is passed back as a DOM object to the javascript, which then parses the result into an xhtml table. I then add the table to my page. This works just fine under Firefox. However, under IE (version 7, so I assume others as well), the table doesn't display. I used the IE Developer Toolbar to look at the DOM, and the table has been successfully added to the DOM, but it isn't showing up. Interestingly, the property hasLayout is set to -1, which I assume means false even though MSDN claims that tables always have a hasLayout property of true. The javascript snippet is as follows:

    /* Add the Headers */    // Create the Headers Row  var headers = document.createElement("tr");  headers.setAttribute("class", "Compendium");  // Create the Number Header  var number = document.createElement("td");  number.setAttribute("class", "Compendium");  //number.innerHTML = "Number";  number.innerHTML = "Number";  headers.appendChild(number);  // Create the Name Header  var name = document.createElement("td");  name.setAttribute("class", "Compendium");  name.innerHTML = "Name";  headers.appendChild(name);  // Create the Element Header  var element = document.createElement("td");  element.setAttribute("class", "Compendium");  element.innerHTML = "Element";  headers.appendChild(element);  // Create the Expansion Header  var expansion = document.createElement("td");  expansion.setAttribute("class", "Compendium");  element.innerHTML = "Expansion";  headers.appendChild(expansion);  // Create the Card Type Header  var cardtype = document.createElement("td");  cardtype.setAttribute("class", "Compendium");  cardtype.innerHTML = "Card Type";  headers.appendChild(cardtype);  // Create the Primary Type Header  var primarytype = document.createElement("td");  primarytype.setAttribute("class", "Compendium");  primarytype.innerHTML = "Type 1";  headers.appendChild(primarytype);  // Create the Secondary Type Header  var secondarytype = document.createElement("td");  secondarytype.setAttribute("class", "Compendium");  secondarytype.innerHTML = "Type 2";  headers.appendChild(secondarytype);  // Create the Cost Header  var cost = document.createElement("td");  cost.setAttribute("class", "Compendium");  cost.innerHTML = "Cost";  headers.appendChild(cost);  // Create the Cost Header  var actions = document.createElement("td");  actions.setAttribute("class", "Compendium");  actions.innerHTML = "Actions";  headers.appendChild(actions);  // Create the Attack Header  var attack = document.createElement("td");  attack.setAttribute("class", "Compendium");  attack.innerHTML = "Attack";  headers.appendChild(attack);  // Create the Defense Header  var defense = document.createElement("td");  defense.setAttribute("class", "Compendium");  defense.innerHTML = "Defense";  headers.appendChild(defense);  // Create the Move Header  var move = document.createElement("td");  move.setAttribute("class", "Compendium");  move.innerHTML = "Move";  headers.appendChild(move);  // Create the Game Text Header  var gametext = document.createElement("td");  gametext.setAttribute("class", "Compendium");  gametext.innerHTML = "Game Text";  headers.appendChild(gametext);  // Create the Story Text Header  var storytext = document.createElement("td");  storytext.setAttribute("class", "Compendium");  storytext.innerHTML = "Story Text";  headers.appendChild(storytext);  // Create the Rarity Header  var rarity = document.createElement("td");  rarity.setAttribute("class", "Compendium");  rarity.innerHTML = "Rarity";  headers.appendChild(rarity);  // Create the Artist Header  var artist = document.createElement("td");  artist.setAttribute("class", "Compendium");  artist.innerHTML = "Artist";  headers.appendChild(artist);    compendiumResults.appendChild(headers);      // Add Each Card to the Table  for (var index = 0; index < cards.length; ++index) {	// Create the Headers Row	var card = document.createElement("tr");	card.setAttribute("class", "Compendium");	// Create the Number Header	var number = document.createElement("td");	number.setAttribute("class", "Compendium");	if (cards[index].childNodes[0].firstChild) {	  number.innerHTML = cards[index].childNodes[0].firstChild.nodeValue;	}	card.appendChild(number);	// Create the Name Header	var name = document.createElement("td");	name.setAttribute("class", "Compendium");	if (cards[index].childNodes[1].firstChild) {	  name.innerHTML = cards[index].childNodes[1].firstChild.nodeValue;	}	card.appendChild(name);	// Create the Element Header	var element = document.createElement("td");	element.setAttribute("class", "Compendium");	if (cards[index].childNodes[2].firstChild) {	  element.innerHTML = cards[index].childNodes[2].firstChild.nodeValue;	}	card.appendChild(element);	// Create the Expansion Header	var expansion = document.createElement("td");	expansion.setAttribute("class", "Compendium");	if (cards[index].childNodes[3].firstChild) {	  expansion.innerHTML = cards[index].childNodes[3].firstChild.nodeValue;	}	card.appendChild(expansion);	// Create the Card Type Header	var cardtype = document.createElement("td");	cardtype.setAttribute("class", "Compendium");	if (cards[index].childNodes[4].firstChild) {	  cardtype.innerHTML = cards[index].childNodes[4].firstChild.nodeValue;	}	card.appendChild(cardtype);	// Create the Primary Type Header	var primarytype = document.createElement("td");	primarytype.setAttribute("class", "Compendium");	if (cards[index].childNodes[5].firstChild) {	  primarytype.innerHTML = cards[index].childNodes[5].firstChild.nodeValue;	}	card.appendChild(primarytype);	// Create the Secondary Type Header	var secondarytype = document.createElement("td");	secondarytype.setAttribute("class", "Compendium");	if (cards[index].childNodes[6].firstChild) {	  secondarytype.innerHTML = cards[index].childNodes[6].firstChild.nodeValue;	}	card.appendChild(secondarytype);	// Create the Cost Header	var cost = document.createElement("td");	cost.setAttribute("class", "Compendium");	if (cards[index].childNodes[7].firstChild) {	  cost.innerHTML = cards[index].childNodes[7].firstChild.nodeValue;	}	card.appendChild(cost);	// Create the Cost Header	var actions = document.createElement("td");	actions.setAttribute("class", "Compendium");	if (cards[index].childNodes[8].firstChild) {	  actions.innerHTML = cards[index].childNodes[8].firstChild.nodeValue;	}	card.appendChild(actions);	// Create the Attack Header	var attack = document.createElement("td");	attack.setAttribute("class", "Compendium");	if (cards[index].childNodes[9].firstChild) {	  attack.innerHTML = cards[index].childNodes[9].firstChild.nodeValue;	}	card.appendChild(attack);	// Create the Defense Header	var defense = document.createElement("td");	defense.setAttribute("class", "Compendium");	if (cards[index].childNodes[10].firstChild) {	  defense.innerHTML = cards[index].childNodes[10].firstChild.nodeValue;	}	card.appendChild(defense);	// Create the Move Header	var move = document.createElement("td");	move.setAttribute("class", "Compendium");	if (cards[index].childNodes[11].firstChild) {	  move.innerHTML = cards[index].childNodes[11].firstChild.nodeValue;	}	card.appendChild(move);	// Create the Game Text Header	var gametext = document.createElement("td");	gametext.setAttribute("class", "Compendium");	if (cards[index].childNodes[12].firstChild) {	  gametext.innerHTML = cards[index].childNodes[12].firstChild.nodeValue;	}	card.appendChild(gametext);	// Create the Story Text Header	var storytext = document.createElement("td");	storytext.setAttribute("class", "Compendium");	if (cards[index].childNodes[13].firstChild) {	  storytext.innerHTML = cards[index].childNodes[13].firstChild.nodeValue;	}	card.appendChild(storytext);	// Create the Rarity Header	var rarity = document.createElement("td");	rarity.setAttribute("class", "Compendium");	if (cards[index].childNodes[14].firstChild) {	  rarity.innerHTML = cards[index].childNodes[14].firstChild.nodeValue;	}	card.appendChild(rarity);	// Create the Artist Header	var artist = document.createElement("td");	artist.setAttribute("class", "Compendium");	if (cards[index].childNodes[15].firstChild) {	  artist.innerHTML = cards[index].childNodes[15].firstChild.nodeValue;	}	card.appendChild(artist);		compendiumResults.appendChild(card);  }
    Any ideas would be appreciated.

    Thanks,
    ~Viz

  16. The basic style usage I've heard is that you should use some extremely common sans-serif font for main text, and for headers possibly a serif font if you want a different font. I always use Arial for my sans-serif font, as I can't think of any OS that doesn't come with it pre-installed. I never use any serif fonts if I can help it, except for some pages designed to be printed.~Viz


  17. Fonts should practically never be set to a percent. Three different scales were designed for working with fonts, ems, ens, and pts. I prefer to use pts, because ems and ens are defined based on the font, so using them to define fonts can cause some bad things for certain browsers. Pts are well defined in all cases though, at 1/72 in. which means they are resolution independent, but you can control really well the size of text on screen and printed.~Viz


  18. Just because something that is somewhat useful can be used in bad ways does not mean it makes the OS buggy. The only piece of code that is truly secure is one that doesn't rely on any input whatsoever, and even that could still possibly run into problems if run on a system with other code, or if it is written with hardcoded memory addresses that don't match up when actually run on different systems. Removing the task manager is an extremely useful capability for administrators. The problem is that since it is possible to disable it for everyone, along with regedit, there needs to be a backup way to access the registry keys and reset them. Unfortunately this backup is used for exploits in many systems. But the registry really is very little different from one large config file that all systems share.~Viz

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.