fusiongrokker

Entries Tagged as Apple

Easily Ignore CFBuilder Meta Files in a new Git Repo

When you create a new ColdFusion project in CFBuilder, you end up with 3 things in your project folder:

During the pre-release process I voiced my opinion that this was too much meta and that they should find a way to cut back or combine where possible. That hasn't happened. In addition, I complained that the file name "settings.xml" is too generic and quite likely to be something that the average developer would want to create for their project. This, too, seems to have fallen on deaf ears.

Oh well. Maybe next time.

However, in the meantime, I've created a quick shortcut for my Mac to create a new git repository and ignore all of the CFB Project Meta files all in one step. On Snow Leopard, edit the .profile file in your account folder (/Users/[your username]/.profile) and add this line:

alias cfgit="git init;echo '.project' >> .gitignore;echo '.settings' >> .gitignore;echo 'settings.xml' >> .gitignore;echo '.gitignore' >> .gitignore;git status"

It all has to be on one line to work properly, but I'll break down each command individually here so that it's easier to read.

alias cfgit="..."

Here we're creating a bash command alias. This translates to, "When I type cfgit I want you to do [this] instead." Where [this] is what you put inside the quotation marks. You can put multiple commands here as long as you separate them with a semicolon.

echo '.project' >> .gitignore;
echo '.settings' >> .gitignore;
echo 'settings.xml' >> .gitignore;
echo '.gitignore' >> .gitignore;

Each of these appends a new line to the file .gitignore with the contents of the single-quotation marks; so in this case it's adding a new line for .project, .settings, settings.xml, and .gitignore (ignore itself). By using >> instead of >, you append to the file if it exists, or create it otherwise. If you're unaware, the .gitignore file tells the local git client which files in the folder are to be excluded from the repository.

Lastly, it runs git status to show the current status of the folder/repository; mostly just as a sanity check to make sure that everything that I want to have happened has.

Posted in Apple | CFBuilder | Git | 4 Responses July 06 2010

Do The Right Thing

This entry started out as a tweet, but after some more time to let the idea percolate I thought I might expand on it in a little longer form.

In late 2006, not terribly long after the Wii was released, we started seeing reports of TV after TV being damaged by a careless player losing their grip of the Wii Remote and accidentally launching it at the TV (most frequently, during a heated Wii Sports: Tennis match, if memory serves). There was even a website dedicated to posting thrown-wii-remote related injuries, both to TVs and to people.

One such TV injury
Not my TV!

The issue really hit the mainstream with this commercial for Southwest Airlines, mocking the situation:

In October of 2007, Nintendo announced that it would include new "Jacket" covers for the remotes with all future sales, and in addition to that, gave all current owners the option to have up to 4 jackets sent to them by mail, free of charge, including shipping. [Wikipedia]

As a Wii owner now concerned for the safety of my TV when anyone but myself played, I ordered the 4 free jackets. They are large bulbous and squishy at the front end, which is presumably the end that most often hit televisions, causing damage. They do look like they would protect the TV, at least for the most part, but thankfully I haven't had occasion to know first hand. What is most important, though, is that Nintendo recognized there was a problem — one inherent in the design of their product — and did the right thing. That gave me confidence in my purchase and made me happy to continue to purchase Nintendo products.

If they had done nothing, and I had been vigilant in protecting my TV, then I would probably still be a satisfied customer. But if they had done nothing and I (or one of my friends) had broken my TV, I would be furious!

Now, I don't own an iPhone4, and thus I have no experience with the defect. But in my eyes, the ongoing issue with the antenna is not entirely unlike the Wii Remote issue. The Wii Remote works as intended, so in that regard, there was no flaw. However, the intended fashion of play put players into a risky situation: waving a fairly weighty object in what may become sweaty hands in the general direction of your TV. This idea is probably what prompted the creation of the wrist strap before the console (and remote) went to market — and the strap was also improved after launch. It took them a while, but Nintendo admitted some guilt and made some concessions.

That seems to be all that people want from Apple. Admit that you're not perfect, and provide a free piece of rubber that probably costs you less than $1 each to make. (As the Gizmodo petition points out, it is "essentially a double wide livestrong armband.")

But if Apple is following in Nintendo's footsteps, it could be a long ride until they do.

Posted in Apple | Nintendo | 1 Response June 29 2010

What Apple has learned from Blizzard

Imagine a company who releases a new product. This product isn't the first in its space — sure, it might combine some concepts from two or more existing products, but can you really consider combining Thing A and Thing B, both of which sell marginally well on their own, revolutionary? Well, no, probably not. But this company has taken some extra time to make their product sexy and fun. So not only does it do the jobs of both Thing A and Thing B, but it does so while providing the best visual experience by-far, when compared to any competitor in either Thing A or Thing B's markets. Oh, and it's fun to do.

So while this new product is not incredibly revolutionary in concept, in execution it is the clear winner, hands down, do not pass go, do not collect $200. Game over, man!

Then someone in the marketing department gets a brilliant idea. What if we could update our product so rapidly that there's no way anyone could ever get the full potential of their investment before an update is available. And those updates should be compelling — seeing anyone else with the update before you have it should immediately induce anxiety and jealousy.

The post title mentions both Apple, makers of the iPhone and iPad; and Blizzard, makers of World of Warcraft. But which company am I describing? That's the beauty… The answer is both.

Being both a reformed World of Warcraft addict and an iPhone owner, I've realized that there is an incredible parallel in their business models. Just like WoW gets a new expansion just as people are starting to get bored or starting to have achieved all that is achievable; Apple releases an update to their delicious hardware just in time to get you to lock up for another 2 years with a horrible service provider at an unreasonable price.

Don't think I'm bashing either of them, because I'm not. It's quite brilliant, and obviously it wouldn't work if the content wasn't compelling. So while it's true that there appears to be no end in sight for the expensive re-upgrade cycle thrown down by Apple, it is only made possible by the incredible advances they've made in the technology.

iPhone 4 is a sexy, sexy device. Its hardware has been improved in almost every way we (the community of owners) had hoped, and some we weren't expecting. Certainly, if you're willing to lay down another couple hundred dollars again this year, then it's worth the money. But for the rest of us — those who simply can't justify spending hundreds of dollars per year (even averaged over years with no upgrades) to have the new, better phone — you have to draw the line somewhere.

Continual upgrades is great for the seller, and great for the buyer from a technological standpoint; but if I am your target demographic (and maybe I'm not!) then I have some news for you: it's not a sustainable business model.

When I played World of Warcraft, I got to a point where I realized that there were just too many things that stressed me out (8+ hours of work/grinding to enable 2 hours of fun/raiding?) and that I would always be behind the curve. There would always be someone with more free time to get better equipment and more consumables (sorry if I'm getting too much into the game lingo). I realized that the stress and long hours of continually playing catch-up would never pay off. There was no way to win.

…A strange game. The only winning move is not to play.
-WarGames, 1983

… And so, I got off that treadmill. Occasionally, I look back on the game and remember the good times; and then I start to mull over the idea of playing again. Then something reminds me of all the grinding and long hours, and once again I'm happy to be free of that world. It was a tough line to cut, but once I did I was better off for it.

I have a feeling that leaving iOS, as I plan to do in September when my AT&T contract is up, will be a similar experience. I will miss the finely polished hardware and operating system; and to some extent, even the troubles that come with the device. There is a certain camaraderie to be found in complaining about poor service at the office, or about dropped calls during your commute.

But then I'll remember that I can just pick up my phone and make a phone call or send a text message without worrying whether or not it will fail, and I'll feel the extra hundred bucks in my pocket, and I'll be happy again.

Posted in Apple | Games | 6 Responses June 17 2010

Mobile Safari on iPad doesn't seem to broadcast JavaScript scroll events

You may have noticed that as part of my blog redesign, the sidebar is very minimal, and for longer pages, when it normally would have scrolled off-screen, it stays in-place. This isn't a new idea — not by a long shot — but I do like the functionality. I think it improves the user experience.

I had occasion to check how my site looks on an iPad recently (verdict: looks good!), and for the most part it looks exactly how I had hoped it would: Exactly as you see on the desktop… except for one little thing.

The scroll event isn't broadcast — as far as I can tell, anyway — when you drag around the page. I'm making this educated guess based on the fact that the sidebar content doesn't stay on screen when you scroll past it. I'm sure that my other JavaScript code is running just fine, including other jQuery code that's part of the new theme.

Oh well. Such is life in this Magical* new world that Steve Jobs is creating for us. At least there isn't any porn available** on mobile devices, now, and my children will be safe!

* All things Magical, as well as the word "Magical" itself, are the domain of the Apple Corporation. Steve, please don't sue me.
** Unless you look for it, that is.

Posted in Apple | 2 Responses May 26 2010