First off, it should be noted that it is often preferable to simply “scan via Intent” from your app to the ZXing “Barcode Scanner” app (available in Android Marketplace), rather than including scanning functionality natively in your app.   However there may be times when you find it necessary to integrate barcode scanning directly into your own app (ie “your client wants it”), hence this tutorial.

Integrating  ZXing into your own Android project boils down to 4 steps:

1. Create an “external library” (.jar file) from the “core” folder included in the ZXing source code.  This folder contains the core code for image decoding.

2. Create an “Android library project” from the ZXing “android” folder included in the ZXing source.  This folder contains the code for the Android “Barcode Scanner” app mentioned above.

3. Include the resulting .jar file from Step 1 and the resulting library project from Step 2 into your own Android project.

4. Copy the CaptureActivity from the ZXing AndroidManifest.xml to your own project’s AndroidManifest.xml

A step-by-step procedure is outlined below.

Before we begin:

1. Download the ZXing source code from http://code.google.com/p/zxing/downloads/list and unzip it.  I like to put it right under my root directory to avoid any potential problems on Windows with a path containing a space.

2. Download Apache Ant from http://ant.apache.org/ (if you don’t already have it).  Ant will be used to create the .jar file from the ZXing “core” folder.

Step 1. Create core.jar file from the Zxing “core” folder.

From a command prompt type “c:\PATH_TO_ANT\bin\ant -f c:\PATH_TO_ZXING\core\build.xml”.  This will create the “core.jar” file which we will include in Steps 2 & 3.

Step 2. Create Android library project from ZXing “android” folder.

1. Start Eclipse.

2. Create a new Android project.

3. Enter project name “zxing-lib” (you may name this whatever you want).

4. Click “Create project from existing source” radio button.

5. Browse  to the location of your ZXing “android” folder.

6. Click “Next”.

7. Select your Build Target.  I have been able to build this as far back as 1.6.

8. Click “Finish”.

9. In the Project Explorer right-click on the “zxing-lib” project you just created and select “Properties”.

10. You are now in the Properties window.  Select Java Build Path in the left pane and then select the Libraries tab.  Now click Add External Jars….

11. You are now in the Jar Selection window.  Navigate to c:\PATH_TO_ZXING\core\core.jar and click Open.

12. You are now back in the Properties window.  Select Android in the left pane and tick Is Library checkbox.

Your zxing-lib library project is now ready.

Step 3. Include core .jar from Step 1 and zxing-lib library project from Step 2 in your own Android project.

1. In the Project Explorer right-click on your android project and select “Properties”.

2. Add the core.jar file just like you did in Step 2, Items 10 & 11.

3. You are now back in the Properties window.  Select Android in the left pane and click the Add button under Library.

4. Select the zxing-lib library project you created in Step 2 and click OK.

5. You are now back in the Properties window and a reference to the zxing-lib library project you just selected is now displayed under Library.  Click OK.

Your android project now includes the necessary core.jar file and zxing-lib library project to allow you to include barcode scanning natively in your own app.

Step 4. Copy the CaptureActivity from the ZXing AndroidManifest.xml to your own project’s AndroidManifest.xml

Currently when you include an android library project  into your own project the AndroidManifest.xml of the library project does not get included.   So you must copy the relevant info from the library project AndroidManaifest.xml to your own project’s AndroidManifest.xml.  In our case we copy the following:

        <activity android:name="com.google.zxing.client.android.CaptureActivity"
           android:screenOrientation="landscape"
           android:configChanges="orientation|keyboardHidden"
           android:theme="@android:style/Theme.NoTitleBar.Fullscreen"
           android:windowSoftInputMode="stateAlwaysHidden">
           <intent-filter>
              <action android:name="android.intent.action.MAIN"/>
              <category android:name="android.intent.category.DEFAULT"/>
           </intent-filter>
           <intent-filter>
              <action android:name="com.google.zxing.client.android.SCAN"/>
              <category android:name="android.intent.category.DEFAULT"/>
            </intent-filter>
        </activity>

Okay, so I have completed Steps 1-4, but how do I use it?

To start the scanner add the following code to your android project:

        Intent intent = new Intent("com.google.zxing.client.android.SCAN");
        intent.putExtra("SCAN_MODE", "PRODUCT_MODE");
        startActivityForResult(intent, 0);

To read the results of a scan add the following code:

        public void onActivityResult(int requestCode, int resultCode, Intent intent) {
           if (requestCode == 0) {
              if (resultCode == RESULT_OK) {
                 String contents = intent.getStringExtra("SCAN_RESULT")
                 // Do something with scanned string
              }
           }
        }

Please note that credit should be given to Zxing in your app’s description if you choose to integrate ZXing natively into your android app.

First, let’s review what Permalinks are.  Permalinks provide an “SEO friendly” URI  for WordPress Pages and Posts.

So instead of the default format URI:

http://www.possumstew.com/?page=2

We get the nicer:

http://www.possumstew.com/wordpress-permalinks-not-working/

Now let’s look at how Permalinks are configured in WordPress.  Click on “Settings” -> “Permalinks” in the WordPress admin menu and you will see a page similar to this:

Select one of the Permalink configuration options and click Save.  WordPress will attempt to add the following code to the .htaccess file located in the the root directory of your installation:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

*IMPORTANT!  WordPress must have permission to write to the .htaccess file.  Contact your site administrator if this is not the case and you are unable to set the permission yourself.

If everything has gone as planned you should now be able to click on any link to your Pages or Posts and be taken the the Permalink URI.  However if your webserver is not configured correctly you may get a “Not Found” error instead.

They key to solving this problem is your webserver’s AllowOverride directive (Apache, IIS, etc).  AllowOverride is set in the webserver configuration file and must be located within a Directory section.  For example:

<Directory ABSOLUTE_PATH_TO_YOUR_WORDPRESS INSTALLATION>
AllowOverride All
</Directory>

Save this in your webserver configuration file and restart the webserver.  Your Permalinks should now work.

perl -pi -e 's/search/replace/g;' .

If you want to replace a string in all files containing the string in subdirectories, simply add a backticked recursive grep command:

perl -pi -e 's/search/replace/g;' `grep -r search .`

]]> http://www.possumstew.com/search-and-replace-multiple-files/feed/ 0 http://www.possumstew.com/how-to-disable-a-cck-field-in-drupal-6/ http://www.possumstew.com/how-to-disable-a-cck-field-in-drupal-6/#comments Thu, 28 Apr 2011 20:14:26 +0000 karl http://www.possumstew.com/?p=237

(Read More...)]]> CCK form elements in Drupal 6 are handled differently than standard node elements.  For instance, a standard node field has the ‘disabled’ property:

$element['#disabled']

while for a CCK field this becomes

$element['#attributes']['disabled']

Therefore a CCK field requires special handling if you want to disable it.  What we need to do is create a callback function to handle CCK elements and call it after the form is built.  Here we call the callback function ‘my_form_after’:

        if (isset($form['type']) && isset($form['#node']) {
          $form['#after_build'][] = 'my_form_after';
        }

Within our ‘my_form_after’ callback function we call another function ‘my_form_disabled’  which we have created to carry out the actual disabling of  specific CCK form elements.

function my_form_after($form, &$form_state) {
  my_form_disabled($form['field_cckfield']);
  return $form;
}

function my_form_disabled(&$elements) {
  foreach (element_children($elements) as $key) {
    if (isset($elements[$key]) && $elements[$key]) {
      // Recurse through all children elements.
      my_form_disabled($elements[$key]);
    }
  }
  if (!isset($elements['#attributes'])) {
    $elements['#attributes'] = array();
  }
  $elements['#attributes']['disabled'] = 'disabled';
}

The code above disables a CCK field named ‘field_cckfield’.