Wednesday, October 29, 2008

Integration with WTP - Maven Integration for Eclipse - Codehaus

Integration with WTP - Maven Integration for Eclipse - Codehaus

I am stil working on this issue. I still want to be able to cleanly integrate Maven + WTP + Tomcat 6.

Tuesday, October 28, 2008

Alistair’s cakeBlog » OS X Leopard exposes Axis2 bug

Alistair’s cakeBlog » OS X Leopard exposes Axis2 bug: "Axis2"

I suffered over this one for a few hours yesterday. I've removed the proxy settings from my ethernet settings for now. I'll report back if I note any bonjour issues as a result of removing the settings.

Monday, October 27, 2008

Wednesday, October 22, 2008

all my OS X Applications


Address Book.app Max-0.8.1
Adium.app Microsoft AutoUpdate.app
Adobe Acrobat 8 Professional Microsoft Messenger.app
Adobe Bridge CS3 Microsoft Office 2004
Adobe Device Central CS3 Mozilla.app
Adobe Dreamweaver CS3 MySQL Tools
Adobe Extension Manager Neverwinter Nights 2
Adobe Flash CS3 Notes.app
Adobe Flash CS3 Video Encoder OpenLink
Adobe Help Viewer 1.0.app Parallels
Adobe Help Viewer 1.1.app Picasa Web Albums Uploader.app
Adobe Illustrator CS3 Preview.app
Adobe InDesign CS3 Prism.app
Adobe Lightroom 2.app QuickTime Player.app
Adobe Lightroom.app Quicksilver.app
Adobe Photoshop CS3 RealPlayer.app
Adobe Reader 8 Remote Desktop Connection.app
Adobe Stock Photos CS3 SQLDeveloper.app
AppleScript Safari.app
ArgoUML.app SecureClient
Automator.app Sherlock.app
CSSEdit.app Skype.app
Calculator.app SmartReview.app
Camino.app Sprint Activation Utility.app
Check Point VPN-1 SecureClient StarExpense.app
Chess.app Stickies.app
Chicken of the VNC.app StuffIt 12
Cyberduck.app SuperDuper!.app
DVD Player.app System Preferences.app
Dashboard.app TeamViewer.app
Dictionary.app TeleScope Folder
FileZilla.app TextEdit.app
Firefox.app TextMate.app
Flickr Uploadr.app TheNotePad.app
Flip4Mac Utilities
Font Book.app VLC.app
Font Reserve Client VMware Fusion.app
GarageBand.app VirusScan.app
Google Earth.app Wacom Tablet.localized
Google Updater.app Webmail.app
GoogleAppEngineLauncher.app Wii Transfer.app
HandBrake.app eclipse
HoudahGeo.app iCal.app
Image Capture.app iChat.app
IntelliJ IDEA 7.0.4.app iDVD.app
Internet Connect.app iMovie.app
JarInspector.app iODBC
Journler.app iPhoto.app
MacPorts iSync.app
MacPython 2.5 iTunes.app
Mail.app iWeb.app

Apple Tutorial: Developing with MacRuby - The Unofficial Apple Weblog (TUAW)

saving this one for later

Apple Tutorial: Developing with MacRuby - The Unofficial Apple Weblog (TUAW)

Thursday, October 16, 2008

using google-glog with XPCOM

I added google-glog into an XPCOM library I have been working with and it seems to work okay for debugging. Instead of writing a file into the /tmp folder, I ended up with output into the system log on OS X. This is acceptable for debugging but probably with some configuration it could write into its own file.

compiling google-glog in XCode

google-glog - Google Code

I decided to take google-glog for a test spin by compiling a simple "Hello, World" program using XCode. Being a little new to XCode it was a good exercise in figuring out how to configure my project to find the headers and the dylib to l ink with. Here are my notes.

1. Building and installing google-glog of course results in the libraries and headers ending up in /usr/local. For me XCode did not pick up anything in /usr/local by default so I added these paths under Project Settings: Library Search Paths and User Headers Search Paths.

2. After that I added libglog.dylib to Targets | Link Binary with Libraries.

3. By default google-glog places the log files into /tmp. The docs explain how to configure log file location, etc.

My next step is to see if I can link and use google-glog with an XPCOM project I am working on to aid in debugging.

Sunday, October 12, 2008

linking XPCOM on OS X

I had a difficult time linking my first XPCOM object on OS X. After searching around and reading various posts I wound up with the following setup for the linker:



g++ -dynamiclib -o mylibrary.dylib whatever.o -L$(GECKO_SDK)/lib \
-L$(XULRUNNER) -Wl,-executable_path,$(XULRUNNER) \
-lxpcomglue_s -lxpcom -lnspr4 -lplc4


Thursday, October 2, 2008

Getting started with XULRunner - "Couldn't parse application.ini"

Getting started with XULRunner - MDC

So after working through this example for a bit on OS X I kept receiving "Couldn't parse application.ini" after attempting to use xulrunner-bin with my application.ini.

It turns out I was using a relative path:


/Library/Frameworks/XUL.framework/xulrunner-bin ./application.ini


thus causes the error, but:


/Library/Frameworks/XUL.framework/xulrunner-bin ~/Documents/Xul/myapp/application.ini

succeeds.