Jump to content
xisto Community

derouge

Members
  • Content Count

    109
  • Joined

  • Last visited

Posts posted by derouge


  1. If below 30 - it's much more lenient towards you - and gives you a big bulk of credits for your posts. However, once you cross thrity, the same post and any subsequent posts would fetch you far less credits. This applies to all. The system simply gives you a push through when you're below thirty to help you make up for a months time - but not after that..

     

    Actually the after 30 credit rating is the real one against which everyone's posts are evaluated. The below 30 scheme is there to help out the new members and for those who haven't been able to post for a while - to quickly raise their credits count back.

     

    Regards,

    m^e

    <{POST_SNAPBACK}>


    Below 30 credits is more lenient, or below 30 posts? It would make more sense, in my opinion, to be 30 posts since once you've got that many you've probably been here awhile and don't need easy credits .. but maybe my logic is wrong, wouldn't be the first time. ;)

  2. My younger brothers play (and love) it. I, however, could never get into it. It may be because I'm a Tibia addict (tibia.com) or possibly because the game is just too darn crowded! I mean, jeez, every 3 steps I take I'm walking on my next door neighbors feet. Annoying. I also find the graphics less than decent. It's sorta a forced 3d, in my opinion. Not a proffessional graphic set. But it's got some good points. I think. Uhh, free .. easy to learn, easy to play. A good time waster. ;)


  3. MySQL is excellent .. fairly easy to learn and fits in perfectly with PHP. For web based stuff I'd definitely say MySQL. However, in the office I work at we do a lot of Access based database stuff. All our Order Management is done through that, and it works pretty well. I have a decent background in Visual Basic, which is what Access uses to write macros and whatnot, so that helps a lot. I think for commercial purposes Access is pretty slick, at least for small business.


  4. Put that function in a separate file, then require (=include) it to your every php file and then just call "changelocation()" where ever you want the 'iframe' to appear.

     

    Other option would be to make the 'iframe' a separate file and then include it to everyplace where you want it. The contents of the file would be what's inside the function scoop.

    <{POST_SNAPBACK}>


    The IFRAME pages I've done in PHP have been done pretty much exactly as described above. Works pretty good, too - the first option, anyways. Not so sure about the second. I might give that a try, too.

  5. My thoughts on the two are as follows:

     

    ASP is supported, obviously, by Microsoft. Fully supported. This is Microsoft's answer to PHP. Therefore you get much, much, better support from the big boys. There is an entire dedicated community on the MSDN. Another good piece of ASP is that if you have any prior knowledge of Visual Basic (or just BASIC) you'll find this language a snap. It is, essentially, a web-based Visual Basic. That was my thougt anyways.

     

    PHP is freeform .. it's not done by some big company motivated only by profits. PHP is much more customizable, much more open. It also, in my opinion, is much better for web site projects. Although to be honest, it's a pain in the butt to install on a computer. I spent quite some time getting it rigged up and running with Apache, compared to the 10 minutes or so it took me to download ASP.NET and have that up and running.

     

    The winner? I'd say go with PHP. Why? Not exactly sure, maybe I'm just not a MS fan. :D


  6. The planning on paper stage is sooo critical, I can't even stress how useful that is. To just go ahead and start sticking links here and there without any planned idea of where they are is just a horrible idea. I'll always sketch my page out first, and then include detailed labels of whats going to go there, the type of thingy (IFRAME, Table, Image, etc.) until I have the entire page planned out. Then I go to doing a rough outline in HTML. I'll code the page, using colors to denote certain things. For example, the last project I worked on had a central IFRAME in a table, surrounded by links across the top. I needed a certain part of the table to have a background, so those areas I filled with red. Other areas needed a different background textures, so I filled those with green. When it came time to actually produce the page, backgrounds included, I just replaced the BGCOLOR="" tags with BACKGROUND="" tags. Another bit of info to consider when laying out your page is the visitor's view. Test in different browsers, different screen sizes. I always include a splash page explaining how the page is best viewed. (800x600 in IE 6.0+) or something along those lines. Another tip is to use percentage values rather than pixel values. This will help reduce the vast differences users get when they view the page with a different screen size.Anyways, great tutorial! The SLIP method is the way to go. :D


  7. Excellent information. I've always sort of wondered if there was some official legal process that I had to endure in order to stick that neat little "C" at the bottom of my pages. Neverseen, you suggested sending yourself an envelope to serve as proof .. so for a webpage you'd recommend printing the source code and mailing that to yourself? Would that stand up as well?
×
×
  • 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.