<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical"
    android:layout_width="fill_parent"
    android:layout_height="fill_parent"
    >
<TextView
    android:layout_width="fill_parent"
    android:layout_height="wrap_content"
    android:text="@string/hello"
    />
<Button
	android:id="@+id/btn01"
        android:text="@string/goButton"
    />
</LinearLayout>

I hit compile, it built fine and went to the simulator, but the app crashed right when it ran. Apparently, LinearLayout requires the layout_height and layout_width to be defined, as such:

<Button
	android:id="@+id/btn01"
    android:layout_width="fill_parent"
    android:layout_height="wrap_content"
    android:text="@string/goButton"
    />

I’ll continue to post these idiot moments as I find them…

That being said, and because of said java/hibernate project I’ve been working on, I’ve become quite familiar with Apache Ant.  It’s basically an easy way to do some of the mundane work and sometimes heavy lifting in day to day programming.  That, and I use Eclipse IDE, so wasn’t too fond of always running to the command prompt to rebuild my models, create a zend module, etc.

So here’s what I’ve come up with.

I started with this tutorial: Doctrine ORM and Zend Framework It shows you how to create a Zend 1.8.4 project with doctrine.  The key aspect is the doctrine-cli.php script.

I should let you know, while I do use Eclipse for most of my projects, a while back I bought Zend Studio for Eclipse. I think it’s much better for writing PHP than any plugin for eclipse (PDT, PHPEclipse).  If you write a lot of PHP, ZS4E is very very worth the money.  While it does say it is “zend studio for eclipse”, it installs its own installation of eclipse.  If you find yourself in this boat, and want to use Ant in Zend Studio for Eclipse, check out this tutorial.  It’s rather screwy that you can’t install ant tools easily, but this definitely does the trick.

But I digress… let’s get started.

Here is the directory structure of my project, basically defined by the above tutorial:

- root
-  htdocs [zend framework project root]
    - application
        - [all application folders]
        - doctrine
    - library
    - public
    - scripts
    - test
-  .project
-  build.xml
-  env.properties

The body of env.properties looks like this:

zf.project.basedir=htdocs
doctrine.scripts.path=${zf.project.basedir}/scripts

And the body of the build.xml looks like this:

<project name="zf-doctrine-project">
     <property file="env.properties" />
     <target name="doctrine.cli" description="Run a doctrine task on doctrine-cli.php - default reload">
          <input message="Enter a task:"
               addproperty="doctrine.task"
               defaultvalue="build-all-reload" />
          <fail unless="doctrine.task" message="No task selected" />
          <exec dir="${doctrine.scripts.path}"
               command="php doctrine-cli.php ${doctrine.task} y"/>
     </target>
</project>

Although it’s painfully self-explanatory, for the sake of completeness, here’s what it does, line by line:

2.  Loads in the env.properties file
3.  Defines the target, which is like a job/task in ant
4. – 6.  Prompts the user to enter a task to pass to the cli script (just like you would pass in the command line)
7.  Makes sure the user enters a value
8. – 9. Executes the php script, passing in the entered task as a command line option, and forces yes to “are you sure?”

Now, the fun part.

In your project in Eclipse, open the ant window by going to Window > Show View > Other and select Ant under the Ant folder.  When you see the Ant View, either open your ant file in that window using it’s open dialog, or just drag your build.xml to that panel.  You’ll see the little white file with the ant on it and whatever you have as the name attribute of the <project> tag in your build xml.  Expand that so you can see the targets, and you should see this:

Showing the doctrine task in the eclipse ant view

Now if you double click that target, you should see a prompt for the task you want to run.  The default value there will run your schema.yml and rebuild your db and models.

Crafty kids may notice that i have the “Hide internal targets button” turned on in that image… well, those targets are for another show…  (damn you crafty kids…)

<channels>
    <!--USED IN THE LIVE ENVIRONMENT-->
    <!--channel ref="my-graniteamf-secure"/-->
    <!--USED IN THE LOCAL/DEV ENVIRONMENT-->
    <channel ref="my-graniteamf"/>
</channels>

Then in the channel definition below we have both definitions:

<channel-definition id="my-graniteamf"
    class="mx.messaging.channels.AMFChannel">
    <endpoint
        uri="http://{server.name}:{server.port}/{context.root}/graniteamf/amf"
        class="flex.messaging.endpoints.AMFEndpoint" />
</channel-definition>
<channel-definition id="my-graniteamf-secure"
    class="mx.messaging.channels.SecureAMFChannel">
    <endpoint
        uri="https://{server.name}:443/{context.root}/graniteamf/amf"
        class="flex.messaging.endpoints.SecureAMFEndpoint" />
</channel-definition>

We couldn’t get {server.port} to work correctly, so we’re forcing the port in the address for now.

The only problem with this is you have to remember to switch the AMF channel before deploying.  It’s on our checklist before doing the full deploy, but we’re most likely going to add it to the ant task list to deploy dev, deploy live.  Something like that.

The KEY THING TO REMEMBER is this: although this file is deployed with the war/ear, it is ALSO COMPILED INTO THE APPLICATION SWF when it is built.  Make sure to change it locally and rebuild your swf before posting, or you will see no change in your app. (found this out after a significant amount of time changing the file on the server to no avail…)

(Ref: http://www.mail-archive.com/discussion@affug.com/msg00605.html)

So, in an attempt to log my efforts, I’m going to start posting little pieces of information that learn/figure out. Today we start with a light lesson in grep.

Side-note(s)
While I am trying to make the switch over to Linux, I find it unfair to my clients to be uncomfortable on my laptop while working billable hours. So this particular lesson will consist of Linux commands, but are run via Cygwin under windows. For those who don’t know, Cygwin is an implementation of the Linux command line and tools that run under windows. Read more about it on the Cygwin website or at the wiki.

My example is at the bash command line. If you’re using a different command line, the methodology may change, I don’t really know (insert lack of Linux knowledge here).

Also, grep is an unbelievably powerful tool. Books upon books have been written on it. This is in no way the only use of grep, nor is it a comprehensive account of using grep in this scenario. I’m just laying the groundwork. The internets (sometimes called blagosphere, tubes, whatever you may like) are a wonderful place, do some more research…

Scenario
I’m working on a website where we had to find all files containing the word “Leads” and change it to “Prospects” (clients… they ask for such weird stuff…). In the project directory, there are a bunch of common website files (php, html, css, js, etc…). But this particular project folder is also maintained by Subversion version control. On windows, that means there is a hidden .svn folder in every directory to maintain the changes to that file. This will make sense in a minute.

Technique – Step 1 – Grep
The manual page for grep says to do a simple search through files is something like this:

grep -R "search value" ./

translation: find every file within my directory and its subdirectories containing this search value.

Technique – Step 2 – | [pipe]
There is a rather handy thing called “piping.” It allows you to run more than one command at once, but also run each subsequent command on the previous commands output. Semi-unrelated example:

ls -la | grep .txt

ls -la will give you a directory listing. What this statement then does is say “ok, with the output of the directory listing, give me only lines containing .txt” giving you a list of all text files in a directory.

ls -la | grep .txt | wc -l

this does the same thing, but wc -l (that is a lowercase L) means “word count, lines only” showing you how many text files you have in your directory.

Back to the task at hand: find all files containing the word Leads.

grep -R "Leads" ./

Output:

$ grep -R "Leads" ./
././.svn/text-base/Popup.php.svn-base:    case 'Leads':
./.svn/text-base/Popup.php.svn-base:            require_once("modules/$currentModule/Leads.php");
./.svn/text-base/Popup.php.svn-base:            $focus = new Leads();
./.svn/text-base/README.txt.svn-base:12. 131  - Sorting Name in Leads
./.svn/text-base/README.txt.svn-base:49. 1161406: Assigned ToUser in Leads can be Assigned to User
./.svn/text-base/README.txt.svn-base:16. FORUM:1276 - Converting Leads and assigning to user
./.svn/text-base/README.txt.svn-base:20. FORUM:1559 - Tasks not working in Leads
./.svn/text-base/README.txt.svn-base:31. SF1095038 - Import Leads - No Mapping Fields

That seems pretty useless because this is all information contained in the .svn files. Eventually, the appropriate info will be contained in there, but make the machine do the work. We want all files containing “Leads” that aren’t in a .svn directory. The -v flag is your friend… It means “find things that don’t contain this.” Code:

grep -R "Leads" ./ | grep -v ".svn"

Output

$ grep -R "Leads" ./ | grep -v "svn"
./include/js/general.js:           if(record_id != '' && module[0] == "Leads")
./include/js/general.js:           if(task_recordid != '' && task_module[0] == "Leads" )
./include/language/en_us.lang.php:'LNK_IMPORT_LEADS' => 'Import Leads',
./include/language/en_us.lang.php:'SINGLE_Leads' => 'Lead',
./include/language/en_us.lang.php:'COMBO_LEADS' => 'Leads',
./include/language/en_us.lang.php:'Leads' => 'Prospects',

See the en_us files there? That’s all I’m worried about, so I can do another pipe to only view those files:

grep -R "Leads" ./ | grep -v ".svn" | grep "en_us"

Output

$ grep -R "Leads" ./ | grep -v "svn" | grep "en_us"
./modules/Emails/language/en_us.lang.php:'LBL_LEAD_TITLE'=>'Leads',
./modules/HelpDesk/language/en_us.lang.php:'Leads'=>'Lead',
./modules/Home/language/en_us.lang.php:'LBL_LEADS_BY_SOURCE'=>'Leads By Source',
./modules/Home/language/en_us.lang.php:'LBL_LEADS_BY_STATUS'=>'Leads By Status',
./modules/Leads/language/en_us.lang.php:'LBL_IMPORT_LEADS'=>'Import Leads'

My task is complete. I’ve gotten all the translation files that contain the word Leads, and I can either manually edit them, or use the command line to edit them, but that’s another lesson.

Optional Step 3 – >>

I want to make a checklist that I can print and have on my desk while i’m working with these files. There’s a simple way to do this:

grep -R "Leads" ./ | grep -v "svn" | grep "en_us" > /path/to/file.txt

This will take all the output and drop it in the file I specified. If you use one >, it will create the file if it doesn’t exist, and if it does exist, replace all content in that file with the output from our grep. If you use two >>, it will create if it doesn’t exist and it will append the text if it does exist.

I know it’s a sloppy example, but that’s how I achieved my goal, and it was MUCH faster than finding all the translation files in the application and doing it by hand.