AddHandler php5-script .php
 
RewriteEngine On
 
RewriteRule ^\.htaccess$ - [F]
 
RewriteCond %{REQUEST_URI} =""
RewriteRule ^.*$ /public/index.php [NC,L]
 
RewriteCond %{REQUEST_URI} !^/public/.*$
RewriteRule ^(.*)$ /public/$1
 
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^.*$ - [NC,L]
 
RewriteRule ^public/.*$ /public/index.php [NC,L]

This will properly re-route all of the requests to make some prettier url’s.

Let’s start out by opening up XCode and creating a new window based application from the standard iphone OS templates. Save the file to wherever you save your iphone files to and create.

Once you create and save your new window-based application, open up the classes and resources folders in the XCode folder explorer. Open up the ViewDemoAppDelegate.h and insert the following code…

//
//  ViewDemoAppDelegate.h
//  ViewDemo
//
//  Created by Mark Hazlett on 10-03-26.
//  Copyright Code Perspective 2010. All rights reserved.
//
 
#import <UIKit/UIKit.h>
@interface ViewDemoAppDelegate : NSObject
{
    UIWindow *window;
    UINavigationController *navController;
}
 
@property (nonatomic, retain) IBOutlet UIWindow *window;
 
@end

All we’re doing here is creating a UINavigationController object so that we can access it in our application delegate implementation file. Let’s go ahead and open up our ViewDemoAppDelegate.m and add the following code to the application did finish launching method.

- (void)applicationDidFinishLaunching:(UIApplication *)application
{
	//Allocate and instatiate a new UINavigationController Object
	navController = [[UINavigationController alloc] init];
 
	//Allocate and initialize a First View Controller Object
	FirstViewController *firstViewController = [[FirstViewController alloc]init];
 
	//Push the first view controller onto the view controller stack without animation
	[navController pushViewController:firstViewController animated:NO];
 
	//Some memory management
	[firstViewController release];
 
	//Make it visible
	[window	addSubview:navController.view];
 
    // Override point for customization after application launch
    [window makeKeyAndVisible];
}

The first thing we’re doing in this function is instantiating the UINavigationController that we declared in our header. We pass it an alloc and init to allocate the appropriate amount of memory for it as well as an init to initialize it properly. The next thing we’re going to do is create a new FirstViewController object. Now you may be asking what a FirstViewController object is? That’s because we haven’t created it yet. So let’s go ahead and go to “File > New File” and add a new file that’s of the type UIViewController subclass. Make sure you check the little check box that says “With XIB for user interface”. This will give you an XIB file to work with instead of producing your interface programmatically. Now that we have our FirstViewControllerObject the only thing we have to do is import the header into the ViewDemoAppDelegate. So make sure to declare #import “FirstViewController.h” at the top of your code. Now onto the rest of the code in our application did finish launching method. The first thing we do with our allocated view controller is push it onto the navigation stack. Now because this is our first view we’re pushing onto the navigation stack we want to make sure to pass “NO” to the animated parameter because we don’t want to animate the root view when it’s pushed onto the stack. Now for some memory management. Once the FirstViewController is pushed onto the navigation stack the retain count on the object moves up to 2, therefore we can perform a release on the FirstViewController object so that the retain count stays at 1. Last thing we do in this method is add the view so our window so that it’s actually visible when we load the application.

Now we’re going to get into some interface builder stuff. Let’s start by opening up our FirstViewController.xib file in Interface Builder(or by just double clicking on it). You should see just a plain white view. Now in order to transition between views we need a button to press to actually transition between views. So let’s go ahead and add a UIButton to the view. Label the button anything you would like to to transition between views. Go ahead and save that file for now(we’ll come back to it later to connect the pointers). Next we’re going to create a new file in our project that’s a subclass of UIViewController. Again we’re going to make sure that “use XIB for user interface” is selected and press create. We’re going to name this view controller “SecondViewController” as it’s the one that we transition to from pressing the button on our first view controller. Once you create the new View Controller you should see it appear on the left hand side in your package explorer. Let’s go into our FirstViewController.h and add the following code.

#import <UIKit/UIKit.h>
@interface FirstViewController : UIViewController
{
	IBOutlet UIButton *transitionButton;
}
 
- (IBAction) pushViewContoller:(id) send;
 
@end

All we do here is create an IBOutlet for the UIButton we added to the XIB file and call it transition button. Then we create an IBAction method that will get called whenever the user presses inside the UIButton. Let’s open up our FirstViewController.m implementation file and implement the IBAction method like so…

#import "FirstViewController.h"
#import "SecondViewController.h"
 
@implementation FirstViewController
 
- (IBAction) pushViewContoller:(id) send
{
	//Allocate and instantiate the second view controller object
	SecondViewController *secondView = [[SecondViewController alloc] init];
 
	//Push the secondViewController onto the navigation stack
	[self.navigationController pushViewController:secondView animated:YES];
 
	//Some memory management
	[secondView release];
}

Now as you can see, we first provide our implementation with an import of the SecondViewController.h that we created earlier. We then proceed to allocate and instantiate our SecondViewController object. This time we’re going to push it onto our navigation stack and passing the YES parameter to our animated option because this time we do want it to be be animated when we press the button. After that we just provide some basic memory management to bring the retain count of the SecondViewController object back down to 1. That’s al the necessary code we need right now, however if you run this program right now you’ll notice that if you press the button on the first view controller it won’t really do anything. So let’s open back up our FirstViewController.xib file and hook up our IBOutlet and IBAction to our button that we created. After you’re finished hooking up these actions in the File’s owner connections inspector, the file’s owner connections inspector should look something like this..

Now you should be able to run the application and press the button and see the transition to the second view controller(which will be blank unless you added something to the nib) and press the back button in the navigation controller and transition back to the first screen.

If you’re having some troubles, here is the project and all the code. Download

Also again, if you have any questions feel free to leave them in the comments section.

It’s no matter in today’s society we deal with so many programs that crash and don’t work properly. If fundamental programming techniques such as design are not being taught, then when students graduate it is to be expected that they continue the programming practices that they picked up in college/university.

This being said, when you come out of college/university, you’re most likely to have a “code monkey” position, where you’re actually coding the enterprise applications. So it’s almost expected, knowing this that programs you use everyday crash on such a regular basis.

Cheers

Java GridLayout Vs. QGridLayout

QGridLayout is coded in a way that I found extremely easy to use and manipulate. If you change one thing it doesn’t change the rest of the GUI and it keeps everything where you want it to be. You have the ability to set how big you want something to be. Then, based on the size of all the components in your display it displays the GUI in an appropriate manner. Overall the QGridLayout wins this battle.

Java Gui Components Vs. QT Components

The methods that swing uses to handle components causes an extreme amount of code that is not useful when creating a GUI. For instance, when creating a group of radio buttons, you must first create the buttons, then add the buttons to whichever group then add each individual button to a panel or something to make them appear in the GUI. This is crazy in my opinion and there is no reason that you cannot add a ButtonGroup to a panel. In QT you can add whatever component you like to a GUI. This radio button example is just that, one example and there are far too many to display here.

This is just some short thoughts on QT vs Swing, however If you try it out yourself then I’m sure you will find out which is better for yourself. Bye For Now,

Cheers

Now this may be because of changing times and school’s are getting more computer literate now, but, wow, 11-14 year olds now have computer programming as part of their curriculum? This is extremely great to hear! I just wish that we would have had something like that back when I was in school and that age. Even if just basic concepts are taught like loops, variables, etc, it opens up the possibility of programming to be taught at a very young age.

This being said, I think we will see a major jump in programming skills in the next 10-20 years as more kids are now being taught these things earlier. This leads to maybe the posibility of an even easy language than maybe Basic or QBasic to be able to teach the fundamentals at a younger age.

I think that there is a dark side to this as well. Computer programming will take away from fundamental subjects such as math, science, and social studies that all kids must learn to be successful. This could be good or bad, up for you to decide…

Cheers

I have to say, why can’t we build software like that? How many hours of man time and corporate money are wasted each year on software that is not functioning perfectly? Could the time that is spent on ill-conceived software be re-routed to perfecting it? Computers understand the code that humans put into it. So I ask… Is it possible to have a piece of software in today’s market that’s perfect? I’m talking no flaws, no errors, just perfection?

With the software changing the way it is today, I can’t answer that question. Having been coding for only about 6 months, I really am not best suited to answer that. Who can answer that question? As consumers why should we have to accept that software does not function the way we want it to? Is there not a single company out there that can make this type of software? I’m asking these questions because I think that there are companies(not naming any) that can change how the world is run. I’m not talking politically or religiously, I’m talking digitally. Almost our entire world runs on digital equipment… I mean almost everything you can think of. So why is the world putting up with digital equipment being almost “faulty”. Going back to the bridge analogy from the book dreaming in code. Imagine if bridges were built like software is built today? People would not stand for things like that to happen…

So why do we accept it with software?

Cheers