Icicles

NSFetchedResultsController

deshartman — Wed, 18 Jan 2012 21:31:41 +0000

Instead of using the usual

NSFetchRequest *request = [NSFetchRequestfetchRequestWithEntityName:@"SomeClass"];

which is prone to String typos, rather use

NSFetchRequest *request = [NSFetchRequestfetchRequestWithEntityName:NSStringFromClass([SomeClassclass])];

This is a neat way to tie the name of the class to the entity.

Of course you have to make sure that you have done the whole CoreData DataModel and create entity based on the entities created in the model.

Empty trash gets stuck

deshartman — Thu, 24 Nov 2011 00:32:26 +0000

Ever had the issue that you click empty trash and it just hangs? Found this useful method here

Go to Finder and select Finder » Secure Empty Trash.

If this operation gets stuck, open the Activity Monitor utility and force quit the Locum process. Enter your admin password when requested.

Go back to Finder and select Finder » Empty Trash.

Configuring SBJSON-framework for XCode 4.2

deshartman — Fri, 02 Sep 2011 05:53:41 +0000

Procedure to use json-framework in XCode 4.2

1) Open or create your project
2) Open the SBJSON XCode project file “SBJson.xcodeproj

pastedgraphic 1

Now drag the SBJson application to you project. There seems to be a bug in the XCode I am using in that it does not display as shown below. Close the project and open it again and it will work.

Now strap it in.

Click on your project file
Click the Targets section
Click the Build Phases

Expand target Dependencies
Click the “+” to add a dependency
Choose “sbjson-ios” under the SBJson project

Now expand the “Link Binary with Libraries”, click + and add “libsbjson-ios.a”

That’s it. All done

Transfer database from one server to another

deshartman — Wed, 24 Aug 2011 23:57:23 +0000

Some times you want to copy a database from one server to another. This is painful and found a easy way to do it from a few other blogs

$ mysqldump -u username -p'password' db-name | ssh user@remote.box.com mysql -u username -p'password db-name

Change MySQL inno dB to file per table

deshartman — Wed, 27 Apr 2011 06:33:02 +0000

This will create a file per table instead of just one big inno db file

cd /usr/local/mysql/support-files/
sudo cp my-huge.cnf /etc/my.cnf
sudo vi /etc/my.cnf

add this under [mysqld]

innodb_file_per_table

Now create the tables as required after restarting MySQL

Eclipse Java Heap Memory size

deshartman — Mon, 13 Dec 2010 02:05:55 +0000

Getting the Out of Memory error when running eclipse? Increase heap space using

eclipse -vmargs -Xmx

but how do you do this in OSX? Surprisingly difficult to find out how to do this in OSX, but here it is:

If you are using Mac OS X, and launch eclipse using the Finder, the eclipse.ini in eclipse folder doesn’t have any effect. You need to open the Eclipse package (right click, show package content), open the Max OS folder, and edit the eclipse ini located there.

FlexUnit4 Async Testing Events

deshartman — Sun, 03 Oct 2010 23:26:23 +0000

When doing Unit testing in FlexUnit 4, you can test Async event firing. This is a tricky test if there are multiple events being fired. The reason it gets tricky is because of the single threaded nature of Flex.

When you simply dispatch one event ofter the other, they are added to the display stack and thus handled in REVERSE order when removed from the stack. However, if you are using remote calls, the stack is given a change to execute, while the remote call is sent off and thus Async events happen in NORMAL order. What makes this really tricky is if you have a combination of local events (reverse order) and remote events (normal order)

Here are some high level examples:

Example 1

dispatchEvent(Event1)

dispatchEvent(Event2)

dispatchEvent(Event3)

Correct Async testing is now done in reverse order, since each event is added to the display stack

Async.proceedOnEvent(this, someEventDispatcher, Event3, checkVars3, 500, null, noEventFired);

Async.proceedOnEvent(this, someEventDispatcher, Event2, checkVars2, 500, null, noEventFired);

Async.proceedOnEvent(this, someEventDispatcher, Event1, checkVars1, 500, null, noEventFired);

Notice the order of the Async.proceedOnEvent is reversed

Example 2

remote call(Event1)

dispatchEvent(Event2)

dispatchEvent(Event3)

Async.proceedOnEvent(this, someEventDispatcher, Event1, checkVars1, 500, null, noEventFired);

Async.proceedOnEvent(this, someEventDispatcher, Event3, checkVars3, 500, null, noEventFired);

Async.proceedOnEvent(this, someEventDispatcher, Event2, checkVars2, 500, null, noEventFired);

Notice the remote call clears properly, but the local calls are reverse order.

So the only way to do this is to understand that if a remote call is executed, you check for it and that if there are any local events, they are placed on a stack until no more events or a remote event takes place and then checked in reverse order.

Tricky….

Redirect Tomcat ROOT index.html to your site app

deshartman — Thu, 09 Sep 2010 13:19:46 +0000

If I have a app at https://abc.com/server/client.html, I want to redirect traffic going to https://abc.com to the same app and not the default Tomcat root page.

Put this in the …/webaps/ROOT/index.html

Flex DateTimeValidator

deshartman — Wed, 01 Sep 2010 23:18:16 +0000

I wrote the first version of a Date & Time validator for Flex. This version extends DateValidator and adds optional time. At the moment the time format is fixed to HH:MM:SS using “:” separator. I may update this later.

Enjoy

package com.helper

{

import mx.validators.DateValidator;

import mx.validators.ValidationResult;

import mx.validators.Validator;

public class DateTimeValidator extends DateValidator

{

// Define Array for the return value of doValidation().

private var results:Array;

private var timeArray:Array = new Array();

public static const RANGE_ERROR:String = “RangeError”;

public static const FORMAT_ERROR:String = “FormatError”;

public static const MAX_EXCEEDED_ERROR:String = “MaxValueExceeded”;

public static const MIN_EXCEEDED_ERROR:String = “MinValuesExceeded”;

public static const INVALID_HOUR_ERROR:String = “INVALID_HOUR_ERROR”;

public static const INVALID_MIN_ERROR:String = “INVALID_MIN_ERROR”;

public static const INVALID_SEC_ERROR:String = “INVALID_SEC_ERROR”;

public static const INVALID_TIME_ERROR:String = “INVALID_TIME_ERROR”;

public static const INVALID_SEPARATOR_ERROR:String = “INVALID_SEPARATOR_ERROR”;

private var _wrongHour:String;

private var _wrongMinute:String;

private var _wrongSecond:String;

public function DateTimeValidator()

{

super();

}

// Define the doValidation() method.

override protected function doValidation(value:Object):Array

{

var dateTimeArray:Array = new Array();

// Clear results Array.

results = [];

var dateString:String = String(value);

// Assume Date is now DATE[ TIME]

dateTimeArray = String(dateString).split(” “);

if(dateTimeArray.length > 0 && String(dateTimeArray[0]).length != 0)

{

// Call the parent Date Validator to validate the date part

results = super.doValidation(dateTimeArray[0]);

}

// Return if there are errors.

if (results.length > 0)

{

return results;

}

// Now validate the time part if there is one

if(dateTimeArray.length > 1)

{

// Expecting HH:MM:SS String. Split the String

timeArray = String(dateTimeArray[1]).split(“:”);

if(timeArray.length == 3)

{

var hour:int = Number(timeArray[0]);

var minute:int = Number(timeArray[1]);

var second:int = Number(timeArray[2]);

/////

// Now check the hour values

if(hour >= 0 && hour <= 23)

{

} else {

results.push(new ValidationResult(true,”hour”,RANGE_ERROR,”Hours need to be between 00 and 23″));

}

// Now check the minute values

if(minute >= 0 && minute <= 59)

{

} else {

results.push(new ValidationResult(true,”minute”,RANGE_ERROR,”Minutes need to be between 00 and 59″));

}

// Now check the minute values

if(second >= 0 && second <= 59)

{

} else {

results.push(new ValidationResult(true,”second”,RANGE_ERROR,”Seconds need to be between 00 and 59″));

}

} else {

results.push(new ValidationResult(true,”format”, FORMAT_ERROR, “Please enter the time as HH:MM:SS”));

}

}

// Return if there are errors.

if (results.length > 0)

{

return results;

}

return results;

}

}

}

And just for kicks, here is the FlexUnit testing of the code:

package com.helper

{

import com.helper.DateTimeValidator;

import flexunit.framework.Assert;

import mx.events.ValidationResultEvent;

public class DateTimeValidatorTests

{

private var fixture:DateTimeValidator

[Before]

public function runBeforeEveryTest():void

{

fixture = new DateTimeValidator();

fixture.inputFormat = ”YYYY/MM/DD”;

fixture.allowedFormatChars = “/-.”;

}

[After]

public function runAfterEveryTest():void

{

fixture = null;

}

[Test]

public function formatDateTimeTests():void

{

fixture.inputFormat = “YYYY/MM/DD”;

Assert.assertEquals(“2010/12/31 00:00:00″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31 00:00:00″).type);

Assert.assertEquals(“31/12/2010 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“31/12/2010 00:00:00″).type);

Assert.assertEquals(“12/31/2010 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“12/31/2010 00:00:00″).type);

fixture.inputFormat = “DD/MM/YYYY”;

Assert.assertEquals(“2010/12/31 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00:00″).type);

Assert.assertEquals(“31/12/2010 00:00:00″, ValidationResultEvent.VALID, fixture.validate(“31/12/2010 00:00:00″).type);

Assert.assertEquals(“12/31/2010 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“12/31/2010 00:00:00″).type);

fixture.inputFormat = “MM/DD/YYYY”;

Assert.assertEquals(“2010/12/31 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00:00″).type);

Assert.assertEquals(“31/12/2010 00:00:00″, ValidationResultEvent.INVALID, fixture.validate(“31/12/2010 00:00:00″).type);

Assert.assertEquals(“12/31/2010 00:00:00″, ValidationResultEvent.VALID, fixture.validate(“12/31/2010 00:00:00″).type);

}

[Test]

public function validDateTimeTests():void

{

Assert.assertEquals(“2010/12/31″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31″).type);

Assert.assertEquals(“2010-12-31″, ValidationResultEvent.VALID, fixture.validate(“2010-12-31″).type);

Assert.assertEquals(“2010.12.31″, ValidationResultEvent.VALID, fixture.validate(“2010.12.31″).type);

Assert.assertEquals(“2010/12/31 00:00:00″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31 00:00:00″).type);

Assert.assertEquals(“2010/12/31 23:59:59″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31 23:59:59″).type);

Assert.assertEquals(“2010/12/31 01:09:09″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31 01:09:09″).type);

Assert.assertEquals(“2010/12/31 2:3:4″, ValidationResultEvent.VALID, fixture.validate(“2010/12/31 2:3:4″).type);

}

[Test]

public function invalidDateTimeTests():void

{

Assert.assertEquals(“99/12/31″, ValidationResultEvent.INVALID, fixture.validate(“99/12/31″).type);

Assert.assertEquals(“12/31″, ValidationResultEvent.INVALID, fixture.validate(“12/31″).type);

Assert.assertEquals(“31″, ValidationResultEvent.INVALID, fixture.validate(“31″).type);

Assert.assertEquals(“2010/22/31″, ValidationResultEvent.INVALID, fixture.validate(“2010/22/31″).type);

Assert.assertEquals(“2010/12/55″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/55″).type);

Assert.assertEquals(“-2010/12/31″, ValidationResultEvent.INVALID, fixture.validate(“-2010/12/31″).type);

Assert.assertEquals(“2010/-12/31″, ValidationResultEvent.INVALID, fixture.validate(“2010/-12/31″).type);

Assert.assertEquals(“2010/12/-31″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/-31″).type);

Assert.assertEquals(“2010/12/31 -1:00:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 -1:00:00″).type);

Assert.assertEquals(“2010/12/31 00:-1:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:-1:00″).type);

Assert.assertEquals(“2010/12/31 00:00:-1″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:-1:00″).type);

Assert.assertEquals(“2010/12/31 00:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00″).type);

Assert.assertEquals(“2010/12/31 00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00″).type);

Assert.assertEquals(“2010/12/31 25:00:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 25:00:00″).type);

Assert.assertEquals(“2010/12/31 00:60:00″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:60:00″).type);

Assert.assertEquals(“2010/12/31 00:00:60″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00:60″).type);

Assert.assertEquals(“2010/12/31 25:60:60″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 25:60:60″).type);

Assert.assertEquals(“2010/12/31 00:00 AM”, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00 AM”).type);

Assert.assertEquals(“2010/12/31 00:00 PM”, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 00:00 PM”).type);

Assert.assertEquals(“2010/12/31 3654567″, ValidationResultEvent.INVALID, fixture.validate(“2010/12/31 3654567″).type);

Assert.assertEquals(3654567, ValidationResultEvent.INVALID, fixture.validate(3654567).type);

}

}

}

Site Certificate (HTTPS)

deshartman — Sat, 28 Aug 2010 23:27:46 +0000

Setting up a certificate for your site.

First some background:

An RSA private key file is a digital file that you can use to decrypt messages sent to you. It has a public component which you distribute (via your Certificate file) which allows people to encrypt those messages to you.

A Certificate Signing Request (CSR) is a digital file which contains your public key and your name. You send the CSR to a Certifying Authority (CA), who will convert it into a real Certificate, by signing it.

A Certificate contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that Certificate, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.

1) First thing is set the host name. The hostname needs to be what you will be using in the common name (see below) in the certificate.

$ sudo vi /etc/hostname

Once done, check the name with:

$ hostname

It should be the new value. in this case domain.com.

2) Now create your private key file. Change to Apache ssl directory if you want, but do it as root

$ sudo openssl genrsa -des3 -out domain.com.key 2048

Enter a passphrase to keep it safe

3) Create a .csr (Certificate Request) file. This is a certificate request, that will be sent to a CA (GoDaddy) to verify who you are.

$ sudo openssl req -new -key domain.com.key -out domain.com.csr

Fill in the details with whatever you want. The only important part is the common name. This HAS to be the domain name. If you have done this for a single domain, then use “domain.com” and if you get a wildcard domain use “*domain.com”. HEre is an example:

sudo openssl req -new -key www.domain.com.key -out www.domain.com.csr

Enter pass phrase for www.domain.com.key:

You are about to be asked to enter information that will be incorporated

into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter ‘.’, the field will be left blank.

—–

Country Name (2 letter code) [AU]:

State or Province Name (full name) [Some-State]:NSW

Locality Name (eg, city) []:Sydney

Organization Name (eg, company) [Internet Widgits Pty Ltd]:My Domain

Organizational Unit Name (eg, section) []:

Common Name (eg, YOUR name) []:domain.com

Email Address []:support@domain.com

Please enter the following ‘extra’ attributes

to be sent with your certificate request

A challenge password []:

An optional company name []:

4) Next you need to get your certificates from from your provider (GoDaddy in my case). For goDaddy they will ask you for your CSR (Certificate Request) details. This is the file you generated in step 3 above. Get the certificate request to them as follows:

sudo cat domain.com.csr

Go to the web site. Under certificates, click re-key and paste the detail inclusive of the “—–BEGIN CERTIFICATE…..” and “…. —-END CERTIFICATE REQUEST——” parts.

5) Once provided you can download you Certificate File (CRT) and their bundle file. This comes in a zip file for the particular server you use. In my case Apache2. Download the file locally.

6) Next upload the Godaddy supplied cert zip file to your server. Put it in the /etc/apache2/ssl directory and unzip.

7) Before starting the server, make sure the new certificate lines up with you key’s public identity. In each file the “modulus” needs to match. Check this by comparing the output of these two commands:

sudo openssl rsa -noout -modulus -in domain.com.key

sudo openssl x509 -noout -modulus -in domain.com.crt

The outputted Modulus value needs to be identical!

8)Remove the password on the private key. This is required so that the server can restart without you having to put in the password each time.

sudo cp domain.com.key domain.com.pass.key

sudo openssl rsa -in domain.com.pass.key -out domain.com.key

9) Change the permissions on all these files now to secure them.

sudo chmod 400 *

10)Edit the /etc/apache2/site-enabled/ssl file and change the following:

SSLEngine On

SSLCertificateKeyFile /etc/apache2/ssl/domain.com.key

SSLCertificateFile /etc/apache2/ssl/domain.com.crt

SSLCertificateChainFile /etc/apache2/ssl/gd_bundle.crt

11) Restart your server and check the error log files

sudo /etc/init.d/apache2 restart; tail -20 /var/log/apache2/error.log

If all went well the server should start without any problems.