[ Content | Sidebar ]

LibGDX – Simple Shooter Demo Broken (update – fixed)

February 13th, 2014

I seem to have somehow cocked up a commit to the LibGDX demos and deleted some asset files for the Simple Shooter demo. My apologies to anyone trying to build this. The really bad thing is that I thought I had backups in my own subversion repository and to my horror it isn’t there at all so I am going to have to put the missing fonts and stuff together again which isn’t going to be quick. I’ll put a notice up when it’s fixed. Sorry about this.

Update

Okay, I  have fixed it. As noted in the comments I did look at the version history but it seems I may not have committed the files properly in the first place. Pretty lax of me not to check a fresh build out on my most popular github repo but I hopefully have learned my lesson. I am going to make sure I have a back up to my local SVN as well in future. 

One last note is that the Android maven build seems to be broken still so I am going to look at that next.

Dart: Pub Get not working – Solution

January 23rd, 2014

I haven’t posted anything in ages. I have been working away on various projects some of which were dead ends some of which might lead to something, we’ll see.

Also, I have been playing around with Dart, Maven and Tomcat which I will post about later. One problem I came across which I couldn’t find a straight answer to anywhere on the web was an issue I had with ‘pub get‘ for Dart. This command downloads your dart application dependencies to a folder local to your Dart project. For some reason is just stopped working properly for me. It would create the folder structure but not fetch any (or not the majority of) files. I tried

  • Deleting the pubspec.lock file and redo ‘pub get‘.
  • Deleting my package folders and redo ‘pub get‘.
  • Trying ‘pub upgrade‘ in case that had some effect. 

None of these actions had any effect.

I knew it had to be something to do with a local cache but I couldn’t find the folder as stated in the documentation. It does mention you can define a system variable PUB_CACHE to redirect the cache to where you want. So I created a system variable (windows) and set it to a folder under my user setting  and then retried pub get‘. This time it worked perfectly.

It is not clear to me what I did to break the ‘get’ mechanism. I wish I knew so I could raise an issue but in the meantime I hope this helps someone else with the same problem.

LibGDX: Noiz2-gdx Vector Shoot Em Up

September 1st, 2013

I have been noticing that there are quite a few instances of my original port of Kento Chos esoteric shooter – Noiz2 available. It has made it’s way across the internet on various app stores mostly unchanged which is fine by me. A few people have added adverts. Good luck to them.

Noiz2

Anyway, just to keep ahead of the game a bit I thought it was time to lavish some love on the noiz2 codebase and see if I couldn’t bring something new to the party. With this in mind I have mavenized it, ported it over to use LibGDX and put it up on Github. This took most of this weekend but I think I have almost got there.

Noiz2

The main new additions are:

  • Mavenized (hurray)
  • Moving star background
  • Minor tweaks to the GFX.
  • Much nicer menu with a lot borrowed from the Simple Shooter demo.

It is not finished. I have not wired the preferences or the persistence of what levels the player has completed. Also the Android platform hasn’t been added yet.

The most interesting thing about the porting procedure was that it was pretty painless. I had abstracted the graphics and control elements previously as I had OpenGL and Canvas renderers available for the Android version. Wiring in the GDX elements was a complete doddle.

Future improvements

  • Rewrite the ScreenGDX primitive renderer to be more efficient (I have yet to try this on Android).
  • Proper glowing vector lines.
  • Saving game state.
  • Saving preferences.

Code is here.

Update #1

I have got persistence of the game state and some of the original setting like sound and volume working with the LibGDX ‘Preferences’ class. Not so hard after all. The settings screen is a little flaky though. I have also started to tidy up a lot of the game text which was a bit wonky looking. One thing to note is I have ditched the original bitmap logo as I just don’t think it looked very good. I am trying to improve the look and feel overall rather than go for a ‘classic’ port of the game. I have, after all, already done that.

Update ‘#2

Added a nice menu. Can’t get it to run on Android yet.

Update #3

Working on Android. Looks good. Persistence of settings not working properly. I plan to fix this and then publish as an update.

GWT: TrafficMap – GWT & Leaflet Map Example

July 2nd, 2013

Here is a nice GWT and Leaflet map application I wrote to ease myself back into GWT again after not having written a line of GWT code since 2009. It is a classic map and list type site which displays some sample data I downloaded from the UK Highways Agency traffic RSS feed.

Trafficmap

Not content to knock something together just to get it working I have as usual done it the hard way by embarking on learning about GWT UIBinder and the MVP design pattern which Google are promoting in the latest version of GWT. My intention is to eventually write something bigger after getting up to speed on GWT again. The result is a simple MVP application which utilises composite binder xml views and the GWT Leaflet map component. All mavenized for an easy(ish) build and deploy process.

You can download the project from here.

Highlights

Data

The data comes from the Highways Agency RSS feed here. This was downloaded and processed by my RSS parser which you can find here.

I used the Google JSON library to convert one of the feeds to a JSON file which was my sample data.

Map

The map is the GWT Leaflet component. The component attaches itself to an g:HTMLPanel defined in the MapView.xml UIBinder template.

<!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">
<ui:UiBinder xmlns:ui="urn:ui:com.google.gwt.uibinder"
	xmlns:g="urn:import:com.google.gwt.user.client.ui">
	<ui:style>
	.mapViewPanel {
		padding-left: 10px;
		padding-right: 10px;
	}
	</ui:style>
	<g:HTMLPanel ui:field="mainPanel" addStyleNames="{style.mapViewPanel}" >
	</g:HTMLPanel>
</ui:UiBinder> 

You cannot instantiate the map control directly in the constructor of the binder. You won’t see anything. It has to be created and attached in the onLoad method of the composite view i.e.

@Override
protected void onLoad()
{
	super.onLoad();

	// ---------------------------------------------------------------
	// Map Widget
	// ---------------------------------------------------------------

	MapWidget mapWidget = new MapWidget(MAP_DIV);
	mainPanel.add(mapWidget);
	mapWidget.setHeight("100%");
	mapWidget.setWidth("100%");

	// ---------------------------------------------------------------
	// Map Configuration
	// ---------------------------------------------------------------

	// Create Map instance
	MapOptions loptions = new MapOptions();
	loptions.setCenter(new LatLng(55.864237000000000000, -4.251805999999988000));
	loptions.setZoom(13);

	Options tileOptions = new Options();
	tileOptions.setProperty("attribution", MAP_ATTRIBUTION);
	TileLayer tileLayer = new TileLayer(MAP_URL, tileOptions);

	myMap = new Map(MAP_DIV, loptions);

	myMap.addLayer(tileLayer);

	myMap.invalidateSize(true);
}

A few things to point out.

  • I couldn’t get the the ‘fitBounds’ method to work which I believe should set the view bounds and zoom to the data set.
  • You must call ‘invalidateSize’ to force the map to redraw otherwise the map is kind of half-drawn.
    • Layout

    The whole view is actually a composite of the left, middle and right panels. I.e.

    <!DOCTYPE ui:UiBinder SYSTEM "http://dl.google.com/gwt/DTD/xhtml.ent">
    <ui:UiBinder xmlns:ui="urn:ui:com.google.gwt.uibinder"
    	xmlns:g="urn:import:com.google.gwt.user.client.ui" xmlns:my="urn:import:com.netthreads.gwt.client.view">
    	<ui:style>
    	</ui:style>
    	<g:HTMLPanel ui:field="testLabel">
    		<my:TopView ui:field="topView" width="100%" height="100%"/>
    		<g:DockLayoutPanel width="100%" height="650px">
    			<g:west size="300.0">
    				<my:ListViewImpl ui:field="listView" width="100%" height="100%"/>
    			</g:west>
    			<g:center size="80.0">
    				<my:MapViewImpl ui:field="mapView" width="100%" height="100%" />
    			</g:center>
    			<g:east size="220.0">
    				<my:PropertiesViewImpl ui:field="propertiesView" width="100%" height="100%" />
    			</g:east>
    		</g:DockLayoutPanel>
    
    	</g:HTMLPanel>
    </ui:UiBinder>
    
      DataTable

    I had bit of trouble trying to get the data table to do a single selection when a row was clicked. After a fair bit of Googling and hunting around stackoverflow I found that you cannot define this in the binder template CSS. The only was to get this to work was to define a CSS resource and pass it into the constructor of the DataGrid.

    The css.

    .dataGridSelectedRowCell {
      border: selectionBorderWidth solid #ffffff; /*#628cd5;*/
    }
    
    /**
     * The keyboard selected cell is visible over selection.
     */
    .dataGridKeyboardSelectedCell {
      border: selectionBorderWidth solid #ffffff; /* #d7dde8;*/
    }
    

    The resource.

    package com.netthreads.gwt.client.view;
    
    import com.google.gwt.user.cellview.client.DataGrid;
    
    /**
     * Override the datagrid style resources.
     * 
     * http://stackoverflow.com/questions/7394151/datagrid-celltable-styling-frustration-overriding-row-styles
     *
     */
    public interface DataGridResource extends DataGrid.Resources
    {
    	@Source(
    	{
    	        DataGrid.Style.DEFAULT_CSS, "DataGridOverride.css"
    	})
    	DataGrid.Style dataGridStyle();
    };
    

    And the usage:

    	private DataGridResource resource = GWT.create(DataGridResource.class);
    	
    	@UiField(provided = true)
    	protected DataGrid<TrafficData> dataGrid = new DataGrid<TrafficData>(50, resource);
    

    I am going to write more GWT stuff again as I am heartily sick of javascript, css and html.

    Apache License 2.0

    Java: Standard RSS and UK Highways Agency RSS Pull parsers on github

    May 26th, 2013

    I have been looking at GWT again recently and was considering trying to write a traffic application again. I wanted to generate some traffic incident data so I dug around into some old code which I had knocking around which parsed UK Highways Agency incident RSS.

    The parser is a pull-parser. Pull parsers are fast and can be cancelled mid operation unlike SAX and DOM parsers which will block while they do their thing. This makes pull parsers ideal for Android. I did have a bit of search but this library appears to be unique in that I haven’t seen any RSS pull parsers elsewhere which is probably because they are a bit onerous to write.

    I have separated out the RSS part into it’s own library and made a new component which just does HA RSS traffic incidents.

    So, enjoy. There are unit tests which show how to use them.

    Standard OPML and RSS parser here.

    Highways Agency RSS parser here.

    The license is Apache 2.0.

    LibGDX: Demos on Github

    March 12th, 2013

    I have made a start on fully Mavenizing my LibGDX demos and placed them up on Github.

    The good news is that the core netthreads-libgdx library and the demos have been converted to use the latest version of LibGDX (0.9.9 at the time of writing). Taking the latest build from the LibGDX repo should mean that it will be easier to keep these up to date with changes to Scene2d etc.

    I used the LibGDX archetype so you should have no problems building these once you have jumped through a few (minor I hope) hoops to install some dependencies on non-maven-available jar files like the tween-engine and fixtureatlas. There are detailed instructions. If you are having problems make a comment/email me or raise an issue on the issues list.

    The core library is here. You will need this for the demos.

    The demos up so far are:

    Simple Shooter

    This is the same simple shmup as before but with a lot of code tidied up. It is here.

    Menu

    Simple Shooter

    Main

    Simple Shooter

    Box2d-Test

    A straightforward Box2d demo with a central rotating fixture, falling objects and nice fading labels. It is here.

    box2d-test
     

    Box2d-Bumpers

    Bumper walls, anti-gravity, tumbling blocks and flashing psychedelics..what’s not to like? Shows how to detect collisions between box2d elements and how to handle them.

    box2d-bumpers

    Putting these all the once place I have discovered a ton of bugs which I have had a chance to go through and fix. Later demos fixed stuff which I never went back and applied to the earlier ones like SimpleShooter so this has been a great exercise. It’s even given me a bit of a kick to write some more.

    NOTE: All the LibGDX demos linked on this blog go to GitHub now. It is easier to manage them all in the one place. The new demos have a bunch of new concepts in them like the removal of the old Singleton patterns with Google Guice managing this stuff instead. Also it’s Maven from here on. If you are familiar with the old code and build mechanism then you’ll just have to come along for the ride. I promise you’ll learn stuff that will benefit you.

    JavaFX: Java OSC library and JavaFX-based OSC Router

    March 5th, 2013

    As part of my Tonome LibGDX project I decided to convert the LibGDX application to use OSC messages instead of triggering samples internally to the application.

    Tonome2

    The application could broadcast OSC note on and off messages to a Puredata instance and map that down to MIDI with a Puredata script. The first part of that was to use a Java OSC library that I would build into the application.

    I had a look at the existing Java OSC libraries available but I couldn’t use them as they relied on creating a new instance of each message for each message sent. This is a no no with Android as you would have the garbage collector running. The OSC specification is up on the OSC website so why not try and write my own using a pooled approach where we reuse messages sent. The result is the osc-common and osc-network components.

    osc-common

    This is an almost fully compliant implementation of the OSC message spec. There are bits missing but for my purposes nothing essential.

    The library like all the components is fully mavenised and has unit tests to ensure the output of the objects comes out as expected using the encode and decoder components.

    Technically you can flood your client app with messages unless you set the pool size to a maximum but hopefully that won’t be an issue if the throughput is high enough. I guess that remains to be seen in the real world. It’s not been an issue for me yet.

    osc-network

    This implements a client and server implementation for the encoder and decoder components. It uses NETTY a super fast networking library for all the networking parts and is unique in that I have not seen any examples of NETTY4 using UDP to implement anything like this. This was a big sticking point in the development as I wanted to use NETTY4 but it was still in beta at the time with not many source code examples. There might be more recent version of NETTY but I’ll leave it as it is for now.

    I got this component working with my Tonome project against the Puredata script that I had written but I found out that Puredata would choke when sent a lot of messages. Initially my heart sank I as I could see that I would have to write my own application to do this. But any failure is an opportunity right? My Swing skills are non-existent but my Flex skill are strong so I figured I would try to look for a Java UI library that would fit my needs. After looking around I noticed Pivot and JavaFX (which had just reached version 2 at that point). Rather than go straight in I thought I would prototype something easier (and more useful) so I embarked on trying to put a front-end on my Mavenize command line tool instead.

    Pivot was eventually thrown out instead of JavaFX which I have successfully used to put a useful UI onto my application for converting any existing Java project to the Maven file structure. Once I had the skills I sat down and started to develop an application which uses the osc-common and osc-network libraries to route OSC messages to MIDI. That application is osc-router.

    osc-router

    oscrouterfx
    The osc-router will listen to OSC messages sent to it on the chosen port and then you can assign labels to the message value received. You can’t edit the labels whilst the tool is in ‘listen’ mode but once you pause you can set them. The interface lets you route the messages (as long as they have the expected note-on and note-off values) to a specified MIDI device. It will let you save and load your settings.

    This is very much a work in progress. There are possibly latency issues to do with the fact I am creating other objects to represent the incoming messages. I think there is a rewrite of the message path on the books.

    The project has been put up onto GitHub here.

    Lot’s of interesting JavaFX stuff to look at including file open/save dialogs,  editable label cells, combobox selection cells, icon status cells and a background service. The application also sports a message cache, MIDI device handling  and lots more. I’m also  using XStream to persist the the OSC message values and label settings to an XML file which has proved to be quite seamless.

    Update #1

    • I have modified the application to load a default message configuration file. This is for illustration so you can see how the UI works without having to have an OSC producing tool.
    • I am in the process of posting the Tonome OSC code up on Github as well.

    Update #2

    The Tonome OSC-aware application is now up on Github. You can find it here. It runs on Android but there are still a few issues to iron out like the inability to edit the hostname and port values. It is here.

    If you run it from the desktop it will connect to the stated hostname and port that the OSC-Router application is setup for. I have altered the router to load up the Tonome message definition by default. All you need to do it map the note on/off message and route them to a midi target.

    More details in further posts.

    JavaFX: Mavenize-FX – GitHub

    March 3rd, 2013

    The mavenize-fx project is now up on GitHub. This will be the new home for the project.

    jfx1

    I have left the google code site up to host executables only.

    You can download an executable JAR file from here.

    I have used the 32 bit JDK so I think it should run on any x86 based platform.

    JavaFX: Mavenize-FX

    December 21st, 2012

    As part of learning JavaFX I decided to put a nice UI onto my existing ‘mavenize’ tool. This is currently a command line tool and does what it says in tin, so to speak. To find out more about this you can read the original post here. I modified the original component to allow a ‘listener’ to attach itself to the processing section. The mavenize process calls back into the listener to notify of what it was currently doing. I wanted the UI to reflect the changes being made (not as simple as it sounds as we will discover).

    What I wanted for the user interface was:

    • Source and target folder selection.
    • Choice of package type.
    • Choice of version number.
    • A list which shows the projects being processed.
    • A big button which you hit to kick the process off.

    So here it is:

    jfx1

    I will discuss each feature in turn and what was interesting about it. Here is a rough class diagram of how the various components are connected.

    mavenize_class

    I have numbered the parts of the interface I want to focus on.

    jfx2

    Here goes…

    (1) Inputs

    These are the source and target directories. They are standard TextField controls and are populated from the choice of folder made using the java directory chooser. They are not populated on startup. You will need to choose a folder for each. It can’t be the same folder. If you do not populate or make them the same you will get an Alert box popping up.

    jfx3

    This is one thing which I was a bit non-plussed about. There doesn’t seem to be a standard Alert box for JavaFX. I ended up rolling my own from suggestions I found on StackOverflow. I have some ideas to improve my implementation to make it much nicer. I always liked the Flex alert which defocussed the whole screen and had a message in the middle. I think it would be nice to have something like that.

    (2) Browse Buttons.

    When these are clicked we use the folder chooser.

    
    // At the top of the controller class.
    @FXML
    private TextField sourceInput;
    
    @FXML
    private Button sourceButton;
    
    // The method.
    public void sourceButtonAction(ActionEvent event)
    {
    	Window window = getWindow(sourceButton);
    
    	if (window != null)
    	{
    		File directory = directoryChooser.showDialog(window);
    
    		if (directory != null)
    		{
    			sourceInput.setText(directory.getPath());
    		}
    	}
    }
    

    The DirectoryChooser object is created in the constructor and shared between the source and target button handlers. Straightforward stuff.

    (3) Process button.

    This is an interesting one and brings in a bit of an overlap to the table view. When this button is pressed it will validate the UI inputs and if fine then it will call a method from the MavenizeClient class.

    public void activateButtonAction(ActionEvent event)
    {
    	logger.debug("activateButtonAction");
    
    	String sourcePath = sourceInput.getText();
    	String targetPath = targetInput.getText();
    	String versionText = versionInput.getText();
    
    	if (sourcePath == null || sourcePath.isEmpty())
    	{
    		// Alert
    		Alert alert = new Alert(stage, ApplicationMessages.MSG_ERROR_INVALID_SOURCE);
    
    		alert.showAndWait();
    	}
    	else if (targetPath == null || targetPath.isEmpty())
    	{
    		// alert
    		Alert alert = new Alert(stage, ApplicationMessages.MSG_ERROR_INVALID_TARGET);
    
    		alert.showAndWait();
    	}
    	else if (versionText == null || versionText.isEmpty())
    	{
    		// alert
    		Alert alert = new Alert(stage, ApplicationMessages.MSG_ERROR_INVALID_VERSION);
    
    		alert.showAndWait();
    	}
    	else if (sourcePath.equals(targetPath))
    	{
    		Alert alert = new Alert(stage, ApplicationMessages.MSG_ERROR_INVALID_PATHS);
    
    		alert.showAndWait();
    	}
    	else
    	{
    		// Process
    		mavenizeClient.process(sourceInput.getText(), targetInput.getText(), versionInput.getText(), packageCombo.getValue());
    	}
    }
    

    The MavenizeClient will start the background service which performs our potentially long running process.

    public boolean process(String sourcePath, String targetPath, String version, String packaging)
    {
    	boolean status = true;
    
    	if (sourcePath == null || sourcePath.length() == 0 || targetPath == null || targetPath.length() == 0)
    	{
    		throw new IllegalArgumentException();
    	}
    	else
    	{
    		mavenizeService.setSourcePath(sourcePath);
    		mavenizeService.setTargetPath(targetPath);
    		mavenizeService.setVersion(version);
    		mavenizeService.setPackaging(packaging);
    
    		mavenizeService.reset();
    
    		mavenizeService.start();
    	}
    
    	return status;
    }
    

    Note the call to ‘reset’ before we call ‘start’ on the service. We need to this as each run has an internal status. Once complete we cannot call ‘start’ again without resetting the status.

    The service has an ‘active’ property which we ultimately ‘bind’ the button ‘enabled’ status to so that as long as the service is running the button will be disabled. This is the power of binding and is a very elegant means to do this sort of thing.

    (4) Table View.

    This binding worked fine between the process button and the service active status. Not so for the TableView and the associated ObservableList. Here are the main points:

    • Create an ObservableList in the controller to act as the ‘model’.
    • The ObserveableList is passed by reference to the service.
    • The service updates the list with new data objects and alters the properties of the object as the proocess runs.
    • The properties of the data object are ‘bound’ to columns in the TableView which (technically) should update.

    Now, I wasn’t actually expecting this to  work. Can you really update a bound list in a background thread? Well, yes so it seems..sort of.  The problem is this – the TableView does update (just to be on the safe side I used a synchronised version of the ObservableList) but it is not consistent. The TabelView was updating or not updating the list on a purely random basis. In short, we can’t expect the view to refresh itself when we are adding stuff to the bound list in a thread which is not the UI thread. It works perfectly if you fill and update the data items in the UI thread.

    After a lot of head scratching I implemented a method to force the view to update. This must be kicked off using the runLater mechanism otherwise it would be modifying the scene view directly and throw a massive wobbly. It gets called whenever an item is added to the list or modified. This is a bit of a crufty solution but it works! If you examine the class diagram above you will see that the service is given a reference to the ImplementsRefresh interface.

    @Override
    public void refresh()
    {
    	Platform.runLater(new Runnable()
    	{
    		public void run()
    		{
    			ObservableList<TableColumn<ProjectResult, ?>> columns = dataTable.getColumns();
    			TableColumn<ProjectResult, ?> column = columns.get(0);
    
    			if (column != null)
    			{
    				column.setVisible(false);
    				column.setVisible(true);
    			}
    		}
    	});
    
    }
    

    Binding a list to a table in this way is a really cool feature.

    (5) Icon cell.

    So I am thinking that I want is a column with icons which will change according to a bound property in the data item.

    Here is the data item

    package com.netthreads.javafx.mavenize.model;
    
    import javafx.beans.property.IntegerProperty;
    import javafx.beans.property.SimpleIntegerProperty;
    import javafx.beans.property.SimpleStringProperty;
    import javafx.beans.property.StringProperty;
    
    /**
     * Project result bean.
     *
     */
    public class ProjectResult
    {
    	public static final String ATTR_GROUP_ID = "groupId";
    	public static final String ATTR_ARTIFACT_ID = "artifactId";
    	public static final String ATTR_FILE_PATH = "filePath";
    	public static final String ATTR_FILE_COUNT = "fileCount";
    	public static final String ATTR_STATUS = "status";
    	public static final String ATTR_WORKING = "working";
    
    	public static final String TITLE_GROUP_ID = "groupId";
    	public static final String TITLE_ARTIFACT_ID = "artifactId";
    	public static final String TITLE_FILE_PATH = "File Path";
    	public static final String TITLE_FILE_COUNT = "File Count";
    	public static final String TITLE_STATUS = "Status";
    	public static final String TITLE_WORKING = "~";
    
    	public static final String STATUS_CREATE = "Creating";
    	public static final String STATUS_COPY = "Copying";
    	public static final String STATUS_FILE = "Add File";
    	public static final String STATUS_POM = "Pom";
    
    	public static final int WORKING_READY = 0;
    	public static final int WORKING_BUSY = 1;
    	public static final int WORKING_DONE = 2;
    
    	private StringProperty groupIdProperty;
    	private StringProperty artifactIdProperty;
    	private StringProperty filePathProperty;
    	private IntegerProperty fileCountProperty;
    	private StringProperty statusProperty;
    	private IntegerProperty workingProperty;
    
    	/**
    	 * Construct results.
    	 *
    	 */
    	public ProjectResult()
    	{
    		groupIdProperty = new SimpleStringProperty(this, ATTR_GROUP_ID);
    		artifactIdProperty = new SimpleStringProperty(this, ATTR_ARTIFACT_ID);
    		filePathProperty = new SimpleStringProperty(this, ATTR_FILE_PATH);
    		fileCountProperty = new SimpleIntegerProperty(this, ATTR_FILE_COUNT);
    		statusProperty = new SimpleStringProperty(this, ATTR_STATUS);
    		workingProperty = new SimpleIntegerProperty(this, ATTR_WORKING);
    
    		groupIdProperty.set("");
    		artifactIdProperty.set("");
    		filePathProperty.set("");
    		fileCountProperty.set(0);
    		statusProperty.set("");
    		workingProperty.set(WORKING_READY);
    	}
    
    	public final String getGroupId()
    	{
    		return groupIdProperty.get();
    	}
    
    	public final void setGroupId(String groupId)
    	{
    		this.groupIdProperty.set(groupId);
    	}
    
    	public final String getArtifactId()
    	{
    		return artifactIdProperty.get();
    	}
    
    	public final void setArtifactId(String artifactId)
    	{
    		this.artifactIdProperty.set(artifactId);
    	}
    
    	public final String getFilePath()
    	{
    		return filePathProperty.get();
    	}
    
    	public final void setFilePath(String filePath)
    	{
    		this.filePathProperty.set(filePath);
    	}
    
    	public final int getFileCount()
    	{
    		return fileCountProperty.get();
    	}
    
    	public final void setFileCount(int fileCount)
    	{
    		this.fileCountProperty.set(fileCount);
    	}
    
    	public String getStatus()
    	{
    		return statusProperty.get();
    	}
    
    	public void setStatus(String status)
    	{
    		this.statusProperty.set(status);
    	}
    
    	public int getWorking()
    	{
    		return workingProperty.get();
    	}
    
    	public void setWorking(int working)
    	{
    		this.workingProperty.set(working);
    	}
    
    	/**
    	 * Properties.
    	 *
    	 */
    
    	/**
    	 * Return property.
    	 *
    	 * @return The property.
    	 */
    	public final StringProperty groupIdProperty()
    	{
    		return groupIdProperty;
    	}
    
    	/**
    	 * Return property.
    	 *
    	 * @return The property.
    	 */
    	public StringProperty artifactIdProperty()
    	{
    		return groupIdProperty;
    	}
    
    	/**
    	 * Return property.
    	 *
    	 * @return The property.
    	 */
    	public StringProperty filePathProperty()
    	{
    		return filePathProperty;
    	}
    
    	/**
    	 * Return property.
    	 *
    	 * @return The property.
    	 */
    	public IntegerProperty fileCountProperty()
    	{
    		return fileCountProperty;
    	}
    
    	/**
    	 * Return property.
    	 *
    	 * @return The property.
    	 */
    	public IntegerProperty workingProperty()
    	{
    		return workingProperty;
    	}
    
    }
    
    

    So the table column definition looks like this:

    // Working indicator
    TableColumn<ProjectResult, Integer> workingCol = new TableColumn<ProjectResult, Integer>(ProjectResult.TITLE_WORKING);
    workingCol.setCellValueFactory(new PropertyValueFactory<ProjectResult, Integer>(ProjectResult.ATTR_WORKING));
    
    // Custom Cell factory converts index to image.
    workingCol.setCellFactory(new Callback<TableColumn<ProjectResult, Integer>, TableCell<ProjectResult, Integer>>()
    {
    	@Override
    	public TableCell<ProjectResult, Integer> call(TableColumn<ProjectResult, Integer> item)
    	{
    		WorkingTableCell cell = new WorkingTableCell();
    		return cell;
    	}
    });
    

    The WorkingTableCell class takes the integer value you set in the workingProperty of the ProjectResult data object and sets the appropriate icon.

    
    package com.netthreads.javafx.mavenize.controller;
    
    import java.io.InputStream;
    
    import javafx.scene.control.TableCell;
    import javafx.scene.image.Image;
    import javafx.scene.image.ImageView;
    import javafx.scene.layout.HBox;
    
    import com.netthreads.javafx.mavenize.app.ApplicationStyles;
    import com.netthreads.javafx.mavenize.model.ProjectResult;
    
    /**
     * Working status custom cell.
     *
     */
    public class WorkingTableCell extends TableCell<ProjectResult, Integer>
    {
    	private String[] ICONS =
    	{
    	        "/bullet_white.png", "/bullet_red.png", "/bullet_green.png"
    	};
    
    	private ImageView imageView;
    	private HBox hBox;
    
    	/**
    	 * Construct cell image holder.
    	 *
    	 */
    	public WorkingTableCell()
    	{
    		imageView = new ImageView();
    
    		hBox = new HBox();
    		hBox.getChildren().add(imageView);
    		hBox.getStyleClass().add(ApplicationStyles.STYLE_WORKING_STATUS_CELL);
    	}
    
    	/**
    	 * This will take the value and lookup the appropriate icon for display in
    	 * the cell.
    	 */
    	@Override
    	protected void updateItem(Integer item, boolean empty)
    	{
    		super.updateItem(item, empty);
    
    		if (!empty)
    		{
    			if (item < ICONS.length)
    			{
    				String iconName = ICONS[item];
    
    				InputStream stream = getClass().getResourceAsStream(iconName);
    				Image goImage = new Image(stream);
    
    				imageView.setImage(goImage);
    
    				setGraphic(hBox);
    			}
    		}
    	}
    
    }
    
    

    I wanted the icon image to be centred in the cell. I’m unsure if there is a programmatic way to do this but I figured I coud do it by defining a style and setting it to the holding HBox.

    .workingStatusCell {
    	-fx-alignment : center;
    	-fx-fill-height : true;
    }
    

    And that’s it. I am going to publish the code onto either Google code or github but in the meantime here is the code. As usual Apache 2.0 licence.

    JavaFX: Pivot and JavaFX

    December 19th, 2012

    I have been trying out both Pivot and JavaFX as means to write a user interface for my proposed tool to route OSC messages to Midi (see previous post).

    Rather than jump straight in with something which needs lots of features I decided to try something simple. My mavenize tool needs a front end so I thought that would be a good candidate. Mavenize takes a source and target directory and produces a ‘mavenized’ version of the source project in the target folder. It will create the appropriate folders and move all the files into the appropriate place. It is the dogs-bollocks and I have used it a lot to save me lots of boring graft. Stop being a mug and just download the command line version from here and better still there is a version with a proper UI coming in the next post.

    Since I was once a big Flex user I decided to look at the two SDK’s available for Java which use a ‘flex’-like approach. These are Apache Pivot and JavaFX that is now part of the standard Java 7 SDK. Both of these have the UI layout and components defined in an XML file and the logic for the UI in the code. Also, these SDK’s embody the concept of a scene-graph for assembling the interface components which at least promises to deliver something more elegant than the somewhat old-skool collection of composite objects which make up Swing.

    pivot1

    I put a basic Pivot version together fairly quickly. I am not entirely sure why they need to have their own version of the collection classes, I am not going to speculate as I am sure there is a good reason. This put me off for a start. Does the world need another set of collection classes beyond those tried and trusted from the JDK? This is a desktop app and they were always going to have to use the JDK. As you can see from the screenshot below there was also a custom file chooser dialog. Somewhat frustrating.

    pivot2

    Also, as I was trying to write a desktop application I was a bit confused by the data model that the table view used. It turned out to be a list of maps which was fine but I couldn’t find a single example of how to use this in a programmatic way outside the bxml examples. I figured it out the end but was left with a sense that this is glaring gap in their otherwise exhaustive set of examples. If you try to use a framework and suddenly find yourself rushing towards an edge case that is a bad sign.

    I am not going to spend much time on my Pivot version of the application. The framework is usable but pales into insignificance against JavaFX in terms of ease of use.

    So, then I decided to take a look at JavaFX. I have to say I am pleasantly surprised. The scene graph and concept of data binding is very close to Flex. So much so that I think I might be a bit miffed if I was Adobe. There is a lot of (ahem) influence from Flex in the feature set. The scene builder tool is probably one of the nicest UI builder tools I have ever used with lots of cleverness to help you layout your user interface. Here is screenshot of the finished tool.

    javafx1

    There is a whole bunch of JavaFX goodness here where I have solved the issue of updating the table view from a background service and have a nice custom cell with selectable images. I put the last one in because I knew I would need it for my proposed OSC router application.

    I am going to outline what I did in the next post.