src: http://osxdaily.com/2006/12/19/command-line-keyboard-shortcuts-for-mac-os-x/

open ~/.bash_profile

add as follows

alias name=path

example:

alias zf=/usr/local/ZendFrameworkCli/bin/zf.sh

if you need to pass a parameter where you need to escape characters or spaces wrap the path in quotes as follows:

alias projects="cd /Applications/xampp/xamppfiles/htdocs"

As agencies get bigger and deadlines shorter it becomes harder to work at work. Some people even opt to work away from the office during crunch time due to the many distractions that are created at work.

Instructions

1. Open the SVN Repository Exploring Perspective
2. Add an new SVN Repository
3. Return to the FDT Perspective
4. Select the Project within the Flash Explorer that you wish to link to the new Repository
5. Scroll down to Team and Select Share Project
6. Choose SVN from the Share Project dialog box
7. Choose the Repository from the supplied list
8. Enter the project name you want, and Finish
9. Tidy up those files with ? marks that you do not want committed, by adding to svn:ignore
10. Commit the project
11. You should see each folder with a little ‘database’ symbol, without any white stars which means that that everything is perfectly synchronized

The top of my project has a white star, usually a commit and update sorts this out, but not always! (A topic for a new Blog!)

Here you can see the first design Tyler did:

And here you can see a Delta boarding pass similar to what Tyler used:

to see the real pass he was handed visit his site

I personally haven't done a lot of traveling but on the few flights I have had in the past years i can easily identify the gate and seat number in the boarding pass. At first glance it is difficult to distinguish the numbers in the suggested design since they are aligned one after the other on a black strip and they all look like a continuous line rather than a separate entity.

Some other things that need to be kept in mind when designed to such a broader audience is

Languages

Is the design going to be translated in different languages and and do we have enough room in case they are printed on a different language?
Is the user at any time have to read the boarding pass left to right, is the design going to fit that requirement?

Ink

Will the company have to spend millions of dollars more in order to use color versus only one color ink?

Training

How many men hours do we need to train people so they know exactly where the new information will be located on the new boarding passes?
How long do we expect everyone to get used to it and how long do we expect people to ask why it has changed and how to find the information?

Legibility

Is it legible to everyone?
Can everyone read the numbers?

Finally

Don't get me wrong, the suggested design looks "pretty" but how many times after you went through the inspection point the first thing you look at is the Flight Number? This is a boarding pass not a buss ticket. Once you have gone though security and you look at your ticket, What is the first thing you look at? I personally look at the Gate Number so that I can figure out where to go from there. I don't see people walking by the isles trying to see the flight number on the plane to identify it.

Interestingly enough Tyler's inspiration for his post was the post by Dustin Curtis in regards to the American Airlines website horror experience he had while trying to book a flight which as a consequence one of the UX Designers had his contract terminated due to him taking the time to explain the procedures of large corporations and the reasons behind the "ugly" design though corporate email.

I say I find this interesting because if you follow the post from Dustin you can learn a lot and understand why things are done the way they are and is not as easy as to turn on and off a switch but it is a lot more involved than that. This is part of the response from the UX Designer

Let me explain. The group running AA.com consists of at least 200 people spread out amongst many different groups, including, for example, QA, product planning, business analysis, code development, site operations, project planning, and user experience. We have a lot of people touching the site, and a lot more with their own vested interests in how the site presents its content and functionality. Fortunately, much of the public-facing functionality is funneled through UX, so any new features you see on the site should have been vetted through and designed by us before going public.

However, there are large exceptions. For example, our Interactive Marketing group designs and implements fare sales and specials (and doesn’t go through us to do it), and the Publishing group pushes content without much interaction with us… Oh, and don’t forget the AAdvantage team (which for some reason, runs its own little corner of the site) or the international sites (which have a lot of autonomy in how their domains are run)… Anyway, I guess what I’m saying is that AA.com is a huge corporate undertaking with a lot of tentacles that reach into a lot of interests. It’s not small, by any means.

So the ideas of revamping a site or updating the way a boarding pass is great but keep in mind it is just more than "I like it this way" call by one person but it is a team and layer of contributors that you have to consult before making the final call.

The thing I like the most about the ZendFramework is their tool which comes as a part of their library download. I have mainly used the tool to create the controllers and actions and so far it has been a time saver and has helped me to see how the framework works in a few keystrokes.

After the first site was a success the next step will be to convert a site with a simple CMS built in Kohana to the ZendFramework, I have to admit that there were two things that held me back for a while into using the ZendFramework.

Speed

I read in different blogs how slow ZendFramework was compared to other frameworks such as Kohana, CI, CakePHP and even the new framework called Yii. The graphic below is one of my many findings:

(Source yiiframework.com)

But it is obvious that as the time goes by the framework is getting better and seems like it is getting faster as well.

Initial setup

When I tried the framework for the first time was about a year ago or so, it was brand new and people were still getting their heads around it as well as was very limited content in the subject so my first attempt to try it was a failure but months later I come back and wow, what a difference. Not only that but I stayed away from the full package and downloaded the minimal package and started just with the library and it was a breeze.

It is nice to have different packages to choose from and that they get better day by day. So far Zend has made it an easy transition and a nice new PHP development start.

Accordingly to the Knowledge Base we get a good kick start by letting us know that we need the following:

So in our HelloFlashContext file we are going to add our "xmlConfiguration" property that will be passed to the SwiftSuspendersInjector.

So I am going to borrow the XML_CONFIG from the SwiftSuspendersInjector and use it as a guide for my HelloFlashContext class.

Now that we know how our XML has to be formed we can start adding our custom properties that will substitute the [Inject] annotations.

There are only two locations where the inject annotation is being used.

and there are only 2 properties used in both instances

So with that information we very easily update our XML_CONFIG constant as follows:

And here you have the complete HellowFlashContext class updated:

This way you should be able to update any demo and compile with the Flash IDE.

Updated: Thanks to Jos Yule for pointing out that the XML will be concatenated on the existing XML so no need to recreate it all

To my surprise the Optimizer tool did optimize the SWF files but just by a few bytes:

Test 1:
..._concept1_v1_alt.swf (56569 bytes)
..._concept1_v1_alt_optimized.swf (56456 bytes)

Test 2:
...600_Flash_v1.swf (38164 bytes)
...600_Flash_v1_optimized.swf (38127 bytes)

I also ran a test against a custom SWF file inside a SWC file and this is the result:

...DropDown/library.swf (14810 bytes)
...DropDown/library_optimized.swf (11723 bytes)

So the SWC files are bloated with extra information no needed and can be compressed quite a bit but SWF file no love. And it does make sense since the SWF files that I was testing contain a lot of graphics but I still gave it a go.

Here you can ind more information about Optimizing RSL SWF Files.