« December 2005 | Main | February 2006 »
January 24, 2006
Growl Universal Binary release
So I released Growl .7.4 last night. It's our first universal binary release, and should work on those fancy new intel macs.
And now, a preview of .8:
Posted by Chris Forsythe at 04:49 PM | Comments (2)
Adsense and css
So I decided to throw an ad up on my site. I see no point in paying the fee for the domain and not getting something back on it I guess.
So I decided to go with Adsense. I can choose to only do text ads, and I can specify the size/location/whatever I want. I think it'll work out pretty well, we'll see.
The biggest problem with all of this, of course, is adding it to the site and making it work in a lot of browsers. Have I ever said I hate css?
Posted by Chris Forsythe at 04:16 PM | Comments (0)
January 20, 2006
Blogs, and when you should just email someone
Is it weird to google your name? I dunno, I do it every once in a while. Today I ended up on this post by Peter Saint-Andre, and realize that would have aggrivated me if I had read it right after I had posted on my blog.
I mean, of all the gall. Like I didn't know about the standards list? I mean, come on. I was working on something for Adium, and didn't want to deal with the enormous politics of the Jabber community.
But it's been a while, and I looked more closely at his post. Looks like he obviously hadn't read the post before that.
Had he emailed, I would have just told him what I was up to. But now it doesn't matter, I'm not working on that anymore, and I don't need to worry about it any longer. But their deferral system is quite silly, why not just say "it's deferred, here is a link with more information on what deferred means"? Bla, I don't really care I guess.
Oh, and I like how he didn't get the point here: in a rebuttal to my post regarding what I think jabber sucks in. Also, via email, I would have probably been able to respond. Especially since most people don't understand their email (like my mom).
Feels like high school on the internet sometimes, ya know?
Posted by Chris Forsythe at 12:44 AM | Comments (1)
January 16, 2006
I am not Australian, but I like the country. I promise
So for the last few months I've been working the night shift. But most of the jobs I have worked have been later in the evening/night shift, so this is nothing new. This, however, is the first job where I have worked past midnight.
Traffic is generally better at night. It doesn't take very long to get home. I always hated hurrying up to get out of the office only to sit in rush hour traffic. It was so silly to me. When I work day shifts I always ended up staying a few hours extra just to avoid it. The saddest part is that when I didn't stay that extra time, I'd get home about 10 minutes earlier than I would have if I had stayed at work.
The wife got a semi matching shift a while back, so now we get to spend more time together. It's great, we watch some tv and I get to study even. Life has never been better.
Except for one thing. I now hate most calendar systems. Why? Because I can't make them work how I want them to of course, hehe. Here is why:
Now, if you can't figure out why that aggrivates me, look in the middle. There is all that blank area. I will probably not be using the blank area ever. Most of my waking hours revolve around 2pm to 5 am. Most all of my schedules revolve around the same thing.
I can't even schedule it like this in Outlook. You can't tell outlook to display until 2 am the next day, so it doesn't want to make a calendar event that will go past the viewable area. iCal can do that part at least.
Here is what I want things to look like:
Notice the new problem here though. All my times are completely different. Some of you may have guessed, but if you haven't, here is how that is even possible. Enabling time zone support, in advanced. I'm not even sure why this is a pref, but it is.
To view it this way, there is a drop down in the top right of iCal, like so:
And to set it back, you change it to your original time zone
So basically I want to be able to view it like I can in Sydney time, but without actually being in Sydney time. I've been googling around for a bit, and just can't find a work around for that.
Also, if anyone knows how to make Outlook work in the same way, I'd be glad to give that a go.
Posted by Chris Forsythe at 04:43 PM | Comments (0)
January 14, 2006
Growl Universal Binary Beta 1
So now that the ia-32 macs are here, Growl needs to become Universal Binary. I kinda want an intel mac, I kinda don't, but I'm happy with my current iBook that Apple so generously gave to me last year.
Anyhow, back to the Universal Binary stuffs. For those not familiar with it, basically this is making a binary that will work on 2 cpu architectures, i386 and ppc. You can make one to work on ppc64 as well, but that's pointless for Growl.
Most of the process of making the ub was easy. I even made a nice text file I used a few times
Steps to making Universal Binary Nirvana on an existing project1) Launch Xcode
2) Get info on the main project
3) Go to build tab
4) Ensure it is on the All Configurations drop down selection for Configurations, and Collection is set to All Settings
5) Search for Architectures, edit this setting, and select both PPC and Intel
6) Try to build in Deployment or Release. Leave the inspector window for the main project open.
7) You will see a new error for Undefined symbols. This is because you are not linking to the 10.4u framework.
8) SDKROOT_i386 = /Developer/SDKs/MacOSX10.4u.sdk needs to be put in.
9) If you plan to support or even just not crash on 10.2, you need to set all of these things:
ARCHS = ppc i386
SEPARATE_STRIP = YES
GCC_VERSION_i386 = 4.0
GCC_VERSION_ppc = 3.3
MACOSX_DEPLOYMENT_TARGET_i386 = 10.4
MACOSX_DEPLOYMENT_TARGET_ppc = 10.2
SDKROOT_i386 = /Developer/SDKs/MacOSX10.4u.sdk
SDKROOT_ppc = /Developer/SDKs/MacOSX10.2.8.sdk
SDKROOT_ppc = /Developer/SDKs/MacOSX10.3.9.sdkThe only settings you do not need to add is ARCHS and SEPARATE_STRIP
This worked for most apps. It actually unconvered a problem in GrowlTunes, which was really easy to fix once I found the right docs.
Anyhow, here's the beta. If you have a chance, give it a shot, it should work. It's even built with xcode 2.2.1 and my shiny new 1 gb ram schtick!
Posted by Chris Forsythe at 03:19 AM | Comments (0)