In your application.ini file, you will need something that looks like this.

notice that you don’t need a “resources.db.paramas.host” line here. The “mydbinstance” part comes from your tnsnames.ora file…

Hope this saves someone some time!

First of all, download Zend Server CE you can get it here:

http://www.zend.com/en/products/server-ce/downloads

I chose the PHP 5.3 version.

Start the install, and choose custom install if you want to also install MySQL Server and PhpMyAdmin.

Once the install is complete, you would think that you would be ready to go…Should be simple…Zend Framework on running Zend Server. Not so!

First of all, at the time of this writing, Zend Framework 1.9.0 and 1.9.1 have a bug which makes it impossible to use the command line tool to do anything other than create a project on a windows system. If you are installing on Windows, you will need to manually add a few lines to the

file. This is a pain, but I’m sure it will be fixed soon.

You can get all the details the fix for it here:

http://zendframework.com/issues/browse/ZF-7465

I used the second fix, and it works fine. If you don’t patch this, you will get an error when you try to create a module after you’ve created your project, and you will probably tear your hair out finding the problems.

Next, once you patch, and create a project, you would think that it would be easy to create a virtual host for your new project. After unsuccessfully trying many different snippets of advice, I finally came across this, buried in the “best practices” part of the installation guide here:

http://files.zend.com/help/Zend-Server-Community-Edition/configuring_zend_framework.htm

First, assuming that you created your project in the web root of your new installation, and your project is called “yourprojectname” you would cut and paste the following text directly into the very bottom of your

file. I’m not sure why this is considered a best practice (as opposed to using /extra/httpd-vhost.conf file), but it works.

Now your new project will be served on http://localhost:84/

Next, you need to have an .htaccess file in the \public directory of the new project you just created. So if the module you created was “mynewmodule”, you would create a file called .htaccess in

C:\Program Files\Zend\Apache2\htdocs\mynewproject\public

If there is already contents in that file, you should comment out existing code first, then past this below:

Whew! That’s it!

Remember to restart your apache server, you should now see your zend framework homepage at http://localhost:84/

You should be able to get started coding now!

A better place to start, in my option, is to just get a set of photos, and return data about the photos. Extremely useful, dead simple. Here goes.

And let’s say we wanted to return the titles for designs for that are tagged with “New Year”. This is tricky because the tags are further down the XML tree than the title, which is an attribute of the design itself.  How would we express this in e4x and actionscript?

var titles:XMLList = designViewerPanel.designListXml.design.@title.(parent().design.tags.(tag==”New Year”));

The key here is to use the parent() function, which returns us back to the top level of the xml tree. We can then express the particular tag we are looking for.

I still haven’t figured out how to do the same expression with out specifying the designs.tags…in other words, I’d like to say something like

but when I try this I get an error…actionscript doesn’t seem to like the parenthesis next to ‘tag’. Ideas anyone?

This can be changed.

Open firefox. Type in

about:config

into the address bar. Right click anywhere on the page. From the menu that appears, select New->Interger.

It will ask for a name of the new preference. Enter:

extensions.ybookmarks@yahoo.sharemode

It will ask for a value next. Type

1

That’s it! Now the delicious app will default to having the “Do Not Share” option selected. I really wish they made this more straight forward.

There is a great script that shows you how to set up subversion with lighthouse here:

http://www.lighthouseapp.com/help/setting-up-subversion-integration

The documentation is sufficient, but too sparse for my tastes.

Here’s some notes that might help you.

1. First of all, you’ll need to know where your subversion repository is stored on your server. Let’s say its in: /svn/repos

2. In that folder there should be another folder called “hooks”. You’ll need to create a file called “post-commit” in this directory, if there isn’t one already. In that empty file put the following:

4. Next, copy the script from the link at the top of this page to a file called “lighthouse.rb” in the /svn/repos/hooks/ directory. You’ll need to change a few things in this file. You’ll need to set the token to the api token you created on lighthouseapp. I’m not entirely sure what the seperate user tokens that follow that are for…ours seems to work fine without each user having their own token. “Account” is the the base url of your lighthouseapp page. Should be something like ‘http://mycompany.lighthouseapp.com’. The project number, which the author claims is self expanatory, is the number that you find in the URL when you are looking at a particular issue. For instance, your URL might look like this:

You want the 8958 from here…you don’t want to include the “-launch” part. I disabled the “prefix:” option by deleting this line completely, and removing the comma from the previous line.

5. Finally, you have to make sure that your permissions on your post-commit and your lighthouse.rb file are executable. To test, you could do a chmod 777 lighthouse.rb and chmod 777 post-commit. You’ll want to set these more strictly once you have your server set up.

6. That’s it. You should be able to run

./post-commit /svn/repos 200

from your hooks directory (200 is the number of an existing revision in your subversion repository), and it should run. On lighthouse, you should see a new entry that says “changeset” with information about the revision, and who made it. Any new commits with now show up in lighthouse as well.

For instance, if I wanted to create a text box on a page. I could something like this.

protected $txtYourNameGoesHere;

function Form_Create{

$txtYourNameGoesHere = new QLabel($this);

$txtYourNameGoesHere->Name = “NameBox”;

$txtYourNameGoesHere->Text = “Write your name here”;

$txtYourNameGoesHere->Width = 100;

$txtYourNameGoesHere->CssClass = “name-box”;

$txtYourNameGoesHere->Required = TRUE;

}

If you just have one or two controls on a page, this is not big deal, but if you have a full page of text boxes and labels this gets unwieldy quickly. One solution for this is to first create an array with details about all the controls you’d like to have on your pages, then create a second control array that contains all of your controls. For instance, you can do something like this:

$arrListOfControls = Array(

‘BillName’ => Array(’Name’ => ‘BillName’, ‘Text’=>’Default Name’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’addressee’),

‘BillAddress1′ => Array(’Name’ => ‘BillAddress1′, ‘Text’=>’default Address1′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’street-address’),

‘BillAddress2′ => Array(’Name’ => ‘BillAddress2′, ‘Text’=>’default Address2′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’street-address’),

‘BillCity’ => Array(’Name’ => ‘BillCity’, ‘Text’=>’default City’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’locality’),

‘BillZip’ => Array(’Name’ => ‘BillZip’, ‘Text’=>’99999′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’postal-code’),

‘BillState’ => Array(’Name’ => ‘BillState’, ‘Text’=>’ST’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’region’),

‘BillPhone’ => Array(’Name’ => ‘BillPhone’, ‘Text’=>’123-452-4444′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’country-name’),

‘ShipName’ => Array(’Name’ => ‘ShipName’, ‘Text’=>’Default Name’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’addressee’),

‘ShipAddress1′ => Array(’Name’ => ‘ShipAddress1′, ‘Text’=>’default Address1′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’street-address’),

‘ShipAddress2′ => Array(’Name’ => ‘ShipAddress2′, ‘Text’=>’default Address2′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’street-address’),

‘ShipCity’ => Array(’Name’ => ‘ShipCity’, ‘Text’=>’default City’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’locality’),

‘ShipZip’ => Array(’Name’ => ‘ShipZip’, ‘Text’=>’99998′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’postal-code’),

‘ShipState’ => Array(’Name’ => ‘ShipState’, ‘Text’=>’TS’, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’region’),

‘ShipPhone’ => Array(’Name’ => ‘ShipPhone’, ‘Text’=>’777-777-7777′, ‘Width’ => 100, ‘Required’ => false, ‘Type’ => ‘Label’, ‘CssClass’=>’country-name’)

foreach ($arrListOfControls as $ctlname => $properties) {

buildTextBoxes ( $arrControls[$ctlname] );

}

$ctl = new QTextBox($this, $properties['Name']);

$ctl->CssClass = $properties['CssClass'];

$ctl->Width = $properties['Width'];

$ctl->Text = $properties['Text'];

$ctl->BlahBlahBlah = $properties['BlahBlahBlah'];

Notice two things of importance here…in the buildTextBoxes function, there is an ampersand…this informs php to pass the whole variable, instead of just the value of the variable. When the function is complete, the new control object dressed up in the properties you provided. Another thing to note is when we create the QTextBox, we specifiy a name for the control. This is important to distinguish the contols in your html source when you view them page…it makes formatting your template easier!

My plan here is to not waste a lot of time customizing this site; I spent 10 minutes getting this blog in place and I don’t want to spend any more time. I don’t want a headache when I go to upgrade to the next version of wordpress.

This blog is all about keeping it simple and saving time.

So there you have it, the stock theme,  plaintxtBlog, by Scott Allan Wallick. Thanks Scott!