Schlagwort-Archive: Development

TimeTracker 1.3.13 beta

A new version of TimeTracker for Mac has been released. This is a new years bugfix release which is supposed to fix a few minor issues:

  • fixed issue 91 – the filter was not reapplied if you left TT running past midnight and it showed yesterdays entries in when having the today filter.
  • fixed issue 95 – replaced BWtoolkit styled but broken ok button with std button
  • general UI overhaul where a bunch of small annyoing issues were cleaned up
  • fixed a bug where on new years the last week/this week filters produced empty results

As always you can download it here as well as via the builtin Sparkle updater (you need to have it set to accept beta versions).

TimeTracker OSX 1.3.11 beta

This is a release announcement of TimeTracker 1.3.11. This is a bugfix release with the following changes.

  • IMPORTANT! requires Mac OS 10.5 or higher
  • Fixed issue 79 made build universal again
  • added keyboard shortcut to confirm a change to a recording
  • fixed potential issue with KVO registration
  • fixed issue which would try to pop up an idle warning when an editor window was open
  • fixed issue 76 where deleting a task would not immediately show the task removed

Please let me know if you find any issues, otherwise I will also release it as „stable“ in a few days.

You can download the release here.

How to give Eclipse a bit more RAM on a Mac

galileo

If you are developing Java on a Mac, chances are pretty high that you are using Eclipse for development. In addition you probably (or at least you better) have lots of RAM too, however, Eclipse is a bit conservative when allocating RAM. If you have tons of plugins installed, or the plugins are quite heavy (Android SDK, I am looking at you), then you can easily get in low memory situations.

The way to change the max amount of memory reserved for eclipse is somewhat buried and not trivial to find (unless you ask Google). The way to do it is to go into the eclipse folder, right click on Eclipse.app and then select „Show Package Contents“. Inside look for the eclipse.ini file (if you are running windows you can skip this step).

Here is my version of the eclipse.ini

-startup
../../../plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
–launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.0.0.v20090519
-showsplash
org.eclipse.platform
–launcher.XXMaxPermSize
512m
-vmargs
-Xms40m
-Xmx812m
-XX:MaxPermSize=512m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts

The sections in bold are the ones that I have changed. Then just save the file and relaunch Eclipse. That should give you a bit more RAM and you should hopefully get better performance.

Meet Hudson: an awesome continuous integration server

I just wanted to recommend Hudson to anyone who is in development (primarily Java) and uses continuous integration for their process. In my company we have been using various products from freeware to commercialware in the past. Recently I stumbled upon Hudson and was seriously impressed by it. It supports SVN, CVS out of the box and can run shell builds, ant builds and a few others right out of the box.

It supports plugins for a lot of other projects (FindBugs, PMD, Emma code coverage, checkstyle, Ruby, …) and is an awesome tool to monitor and improve the quality of your software. The most useful feature is that it can aggregate all results and present them in a timeline (trend). So you can see how your unit test code coverage has changed over time, …

Screenshot of a typical trend view
Screenshot of a typical trend view

The screenshot above illustrates some of the graphs and analysis that hudson can produce. I know that I have previously focused on mainly Mac projects but this one obviously also runs on a Mac, I use it at work and best of all: its open source!

J2ME Bluetooth deployer task


For people who develop j2me applications on a regular basis this nifty tool might be able to be very useful. It basically is an ant task that can deploy a j2me application via bluetooth automatically.
I am usually a little more conservative (and we do build multiple configurations where I keep switching between those) and I simply use Finder (select the JAD/JAR) and hit Apple-Shift-B.

Anyway check the tool out.

Javablog » Bluetooth Deployer

MacOX J2ME development

This Blog entry has
a nice description of what is necessary to get J2ME app development on
MacOSX going including antenna support. I figured out most of the stuff
myself before I stumbled over this post (grr).

To get the WTK recognized by eclipse, you need to try and lauch
<wtk-root>/bin/ktoolbar. This will fail since a folder called Mac
is missing. Just rename the existing Linux folder (in the specified
directory) to Mac and this should work. After this EclipseME will be
able to import the WTK as a device profile which you can then use to
build your project.

To debug you can then use MicroEmu in eclipse (as a standard java app rather than using EclipseME)