There are plenty of single shelved out there to choose from for unbelievable prices, of course heavy duty means u need to spend more dough. A standard one column quality metal shelve system costs around 100$ plus. That could not work since i wanted to get about 8 columns in this little room. Luckless IKEA has basic shelving system for as litle as 25$ a column. Very basic, made of wood, no paint, no polish, smells like a pine forest. All and all I spent around 300$ on about 90 kilograms of wood. Great thing about IKEA they sell everything separately for this shelve system. Each four pillars cost 5$ and each shelf cost 5%, so every column with 4 shelves costs 25$.

Total Buy…
item: amount * price = total
shelves: 38 * 5$ = 190$
pillars: 24 * 5$ = 120$
That is 310$ plus tax.

Upgrading My Computer Room

Step 1

Buy all the bloody shelves and drop em around the house randomly…

Step 2

Take a few pictures, stitch them, play ISpy for a while, continue… This wa smy room from left to right side of my door.

Step 3

Destroy the manuals. In my case: feed manual to Evidence Eater 9000.

Step 4

Build! and… more build! I didn’t have any power tools for first one so I waited an hours. My mother was awesome enough to go borrow one on the spot from somewhere.

Step 4.5

At first I was not planing too, but then I did stain the wood to make it bit more darker. This was verry irritating since i had to cover every inch of every shelve with a cloth using rubber gloves and sniffing the chemical for several hours. Well I did split the job 4 times. The stain is so bad that I had to change the gloves 4 times, and i was using the thick ones. After every few times i fully dipped my hand into the stain container the grew in size, in 4 dips the gloves went from size S to size XL.

Step 5

After hours of moving stuff around back and forth. I had somewhat completed the upgrade. What I noticed is that I need more shelves in between current ones in several places since I have a lot of small things that just wont use the whole space of shelves positioned so far apart. Here is left and right side of my computer table.

Step 7

I went to get few more shelves and attached them in various places mostly around the top half of each column. Also I I was thinking of making an exhaust pipe from the back of my computers to the window because the temperature in this room fluctuates way too much.

Conclusion

All Pictures Taken

For those that do not know what CodeIgniter is, it is a very small but powerful MVC based PHP framework for developing web applications. And for those who not sure what CodeLighter is, it is mini version of CodeIgniter, it follows the same syntax in general but the actual framework is minimized to the core.

Some nice things of CodeIgniter is that it has a separate documentation and lots of useful helpers and functions. This is a full framework so everything in it is separated from each part for the code like routes, hooks, core classes and so on.

CodeLighter has every core class like dispatcher controller loader and such placed in one single file. If you are the type that likes simplicity then this is good for you. Even thought it is in one file it is all very well commented and there is no need for documentation separately. It is very easy to go through the code and understand what each thing does and makes it easy to edit to your likes. CodeLighter of course supports the full MVC but more compact on the configuration end. Separate models, helpers, views and controllers. the whole code it self has only 5 directories and 3 files. One is the index that starts the code the actual CodeLighter core classes and MySQL class, everything else is for you to make.

I tried using both of those frameworks to try them out. The first thing to look at is the page render time. I had both frameworks installed on same server and had them only connect to the database and that is it. The render time of each page has a huge difference. CodeIgniter scored on average of 0.07 seconds at all times and CodeLighter Scored 0.005 seconds on average. The difference in loading times is all there and at the end before choosing what you want to use think about what you need it for. The CodeIgniter woulb be good for something heavy that has lots of pages and lots of features. CodeLighter would still be fine but would be better for smaller websites. It is like, what is the point of using a framework if it actually slower then the original code.

Notes:
CodeIgniter is good for beginners that wish to learn MVC structure. Which stands for Module View Controller.
CodeLighter is good for those who are going in depth and wish to know the full mechanics and use a more plain and dynamic MVC framework.

So here is a basic good directory structure of the website:

/
/include/pages
/include/libraries
/images

This in my point of view is a really simple organized and safe way to create a website that can have a massive amount of pages and easy indexed. Included folder is where we store all our libraries, layouts, our custom functions, classes and pages. And the images folder speaks for it self. The slash at front means root of the website.

It may look good but I can still make it more better. Even thought people will not be able to access those folders we can make it shorter to save some time ans space, even thought its just few bytes of data. Shorten the “include” to “inc” and “images” to “img” for a start. There is no point having a big word like “libraries” because we can make a mistake in the spelling when writing scripts that deal with files in that folder.

So here is what we have now:

/
/inc/pages
/inc/lib
/img

Now it looks and feels very simple.

There are 4 major php pages that we need to create first:

• index.php
  - the page that loads configuration and all our things in the lib/ folder we made and finally the content page that the user wants to see like home or a list of something
• config.php
  - place to hold critical configurations like folder names and database user name and password
• layout.php
  -how our site will look, much better to have a layout in one place rather then writing in every single display page (the beauty of PHP)
• home.php
  - the default page that is shown if no page was selected

Here is what the structure should look like now:

/
/config.php
/index.php
/inc/pages
/inc/pages/home.php
/inc/lib
/inc/lib/layout.php
/img

Now lets get into more detail of those pages.

config.php

You must have a one place where you can put the critical information. This information is basically passwords and folder names. You can store the folder names in a database but the root things like the password for is best be stored here. This is not required but is best for flexibility.

For instance it is much easier to use $dbpass $dbname $dbuser for entering you main database because if you were to change a database name or pass word all you need to do is edit the config.php where you declared those 3 variables. if you got the pass and the name written in every page then its more of a security risk and you will be in pain updating every page where you connected to the database.

Same goes for folders. Make an array for folder places so then if for some reason you want to change the whole folder or select a new version of files you can just edit this variable instead of updating each page of your site.

Make sure that this page must be included to operate, I talk more about this for the index page. Very important.

index.php

Instead of having lots of pages in the root fo our website like index.php as a home page and gallery.php for the gallery and so on we will have just one single page “index.php”. And instead of writing our home page in it we make this our page server, it listens what page clients wants and it loads them. This means that this page will have the highest load.

Basic code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

<php
//Set variable that this is the index of the site.
define('THEINDEX',TRUE);
 
//Load configuration file.
require('config.php');
 
//Array of website required files.
$required_files = array(
'layout.php' //Page layout
);
 
//Include website required files from array or die.
foreach($required_files as $file)
if (@is_file($di['lib'].$file))
require_once($di['lib'].$file);
else
die('Required File Not Found: '.$file);
 
//Page request handle.
if (@is_file($di['pages'].trim($_GET['page']).'.php'))
require_once($di['pages'].trim($_GET['page']).'.php');
else
require_once($di['pages'].'home.php');
?>

Define some complex variable for security measures. This is how it works, this variable is defines only in this page and it better be something big just in case. Basically every other PHP page on your site at the top of the whole code will have one if statement that checks to see if this was defined. Since this is only defined in the index then pages included by the index will be able to see this variables and pass the if statement true. If the included page at work does not see this variable set then we can simple use die() or redirect the user to the home page. This is just one of the simple ways to prevent code execution, there is also lots of other ways. This is not necessary but works for me.

Require the configuration. (config.php) – Writing the PHP script we will first call the configuration file (config.php) that holds all critical data.

Require the your library scripts. (ex: layout.php) – Then knowing all the folder names that we got from the config.php we can include all of the libraries.

The page selection is done by passing URL variables. So if this is the URL “www.example.com/index.php?page=home” then there is one variable by the name of “page” that has a value of “home” (aside the variables set by the server). Simple right (those who know all this probably falling asleep, but I take newbies into consideration). Choosing what variable name you will use for passing the page name is important because it must be the same for every link that you will write in your website. if you got like 30 pages of dense code then its a pain modifying the variable name. Usually this name will have to be something simple like ‘p’ for page or ‘a’ for action. Lets assume we will use “page” as the variable name to keep things simple. So now its basically things we will pass in the page variable will be just the name of the pages that are located in the /inc/pages folder. So if we want the home.php we will use “home” not the whole thing. The ending is unnecessary. Concluding that first we add .php to the value in the “page” variable and check if that page exist in the /inc/pages folder and if it does then load it. If it does not exist then load our default page “home.php”.

layout.php

This is where we store the HTML header and the fotter of the website. Now this may seem very simple and limited but it is not. This is just a mere start. A lot of modifications can be done.

Basic example code:

1
2
3
4
5
6
7
8
9
10
11
12
13

<?php
class Layout {
 
function top() {
echo '<html><head><title>Example</title></head><body>';
}
 
function foot() {
echo '</body></html>';
}
 
}
?>

There you have it, a simple page. This means you will not have to create all teh headers and stuff in each page you make, instead you can just use Layout::top(); to show the top part. This is not limited so your your imagination to how far you can modify this and make it more advance.

home.php

Our simple default page that will be shown if no page is selected or page that was selected is not found.

Example code:

1
2
3
4
5
6

<?php
//Cheking for constants defined in index to prevent direct page usage.
if (!defined('ININDEX')) die('no peeking');
 
echo 'Hello World!';
?>

The first chunk is what I talked about when creating the index.php. This little piece of code will check to see if that constant was defined. If the constant does not exist it will stop working the rest of script and display “no peeking” as the code says.

You can download all those pages already constructed and at their correct place here. I have also added tiny bit of things to the code and a 1 bar layout.

DOWNLOAD