I use VirtualBox on my Mac for “other” operating systems.
I was recently creating a new Ubuntu guest OS for doing some work with PostgreSQL on Linux. I like a GUI, so I was using pgAdmin. Normally I don’t care if the window is 800×600, but when I started using pgAdmin, I couldn’t see all of the window.
I’ve only been working on AccelGolf: Golf GPS Rangefinder for a short time, but I’m having an ever-increasing role in it’s development. It’s an awesome tool for Golfers to track and improve their game. The introductory price of $4.99 is unbeatable, but won’t be available at that price for long! Find out more at AccelGolf. Or check it out in the App Store.
I had trouble getting MySQL GUI Adminstration tools to connect to my XAMPP installed MySQL database server on Mac OS X. This solution may help people who have the same problem and don’t know how to figure it out.
I’m working on a Mac with OS X 10.5.7 and a fresh XAMPP 1.0.1 install. XAMPP gives your OS X a complete Apache, MySQL and Perl/PHP installation to work with. With it, you can develop on your Mac with a complete web server. (Sure, Mac comes with most of this stuff built in, but XAMPP is really nice and allows you to have your Mac web services turned off for security.)
XAMPP also comes with phpMyAdmin for managing your MySQL server through a web page. I find phpMyAdmin to be awesome for most of what I do with a database. Sometimes I need to revert to command-line for large datafiles and stuff, but I’d say 99.9% of the time I can use phpMyAdmin for what I’m doing. I ran into a problem with phpMyAdmin trying to view a database table that was imported from an Excel export. For some reason, the phpMyAdmin page is just plain white – making me think there was some web/parsing/display problem involved. I needed a different way to view the DB. For this kind of thing I hate the command line. (The line wrapping…blech!)
I am going to show an example of writing a cross-plaform game for GP2X/GP2X F-200 and Windows Mobile. I’ll test it out on a GP2X F-200, Palm Treo 750W and AT&T 8125 smartphone. It will also be playable on Windows and Linux, too.
When it comes to JNDI Datasources, you really need a fast way to test outside of the container without changing all of your configuration just because your testing.
One of the problems with using a JNDI Datasource is Unit Testing outside of the container. Testing in the container is a pain and it’s slow if you are fixing bugs or just testing to make sure what you have works after a few changes. It’s OK for system tests.
Another option might be to have one set of configuration for the container and one for Unit Testing. An example might be to have two files controlled by your classpath or even worse, one file which you comment/uncomment to get the datasource you need. Then hope you package up the right configuration for the release.