Sometimes I write a function that I only want to apply to certain pages. Say, a form. I may need some javascript to apply to the form when I’m inserting and different javascript to apply when I’m editing. Since I’m reusing the form, I just change the id of the form and use this check:
if ($('#insert-form').length > 0) {
// do stuff that only applies to the insert form
}
Here are the rules regarding using multiple words in your controllers and models. Just use capital camel-case.
Model:
class Default_Model_TwoWords extends Zend_Db_Table
{
}
The name of the file would just be TwoWords.php.
Controller:
class Default_TwoWordsController extends Zend_Controller_Action
{
}
The name of the file would, of course, be TwoWordsController.php.
However, your views will be in a folder called “two-words” and the url will be http://mysite.com/two-words. Note the dash.
Here’s how to create your own custom Zend_Auth_Adapter to use a salt along with a hashed password. Continue reading
I found a great explanation of how form decorators work and how to customize them here: http://devzone.zend.com/1240/decorators-with-zend_form/
I recently needed to modify the errors decorator so that the entire element (label, input, and error message) was wrapped in a new div. In order to do this I had to create a view partial, which if you haven’t used before sounds a little complicated but it’s not at all. Continue reading
Here’s a snippet to list a whole bunch of system properties, including the path where java is installed.
public class TryProperties
{
public static void main(String[] args) {
java.util.Properties properties = System.getProperties();
properties.list(System.out);
}
}
public class DreadfulProblemException extends Exception
{
// Default Constructor
public DreadfulProblemException() {}
public DreadfulProblemException(String s) {
super(s); // Call the base class constructor
}
// Constructor that provides for chained exceptions
public DreadfulProblemException(String s, Throwable cause) {
super(s, cause); // Call the base class constructor
}
}
package packageName; to the top of each file in the packageimport statement at the top of each class that uses the packagejavac -classpath "C:\MyPackages" MyProgram.java. The class path should not include the directory where the package resides, only up to the directory. So for example, if your package resides in “C:\MyPackages\MyPackage,” your classpath would be “C:\MyPackages.”java command as usual.Normally you compare strings with the equals() method. However, you can compare strings with the == operator. The intern() method discards duplicate String objects, which frees up some memory. You really would only do this if your program generates a lot of duplicate strings, as it is usually faster than calling the equals() method. Here’s how you do it:
String string1 = "here is "; String string2 = "a string"; string1 += string2; // Make string1 and string2 reference strings that are identical string1 == string2; // This returns false right now string1.equals(string2); // This returns true but requires the method call every time you want to compare string1 = string1.intern(); string1 == string3; // Now this returns true
Note that only strings containing variables need to be interned. For example, if you create another string String string3 = "here is ";, it would reference the same object as string1 and you would not need to use the intern() method in order to compare using the == operator.
There is a subtle difference between the logical & and && operators when evaluating expressions. When using &&, the right side of the expression is not evaluated if the left side evaluates to false, whereas if you use the & operator, both sides are always evaluated. Most of the time you only want the left side evaluated if it is false for performance reasons, but there are times when you might need both sides evaluated regardless. An instance of this would be if the right side is modifying a variable and you want the variable modified whether or not the left side is true. Here’s an example:
if (++value % 2 == 0 & ++count < limit) {
// do something
}
To run a .jar file from the command line, you’ll need the package name and the class name. But first you need to add the class path in order to tell Java where the class is. This can be set either as part of the java command or as an environment variable. Continue reading