Yes it does. Just add the process image to your deployment:
The console will now display the image + the current activity the process is in.
So I would then deploy the jpdl separate from the png? Is there a way to keep track of which image goes with which jpdl?
How do the .bar files work? I was under the impression that I could include the jpdl and png in a bar and deploy that.
Is the "g" attribute in the jpdl file the graphical information? If so why would I need to deploy the png file in my deployment?
The console is smart enough to check the package names of the process XML/ process image, which allows for multiple processes/images in one .bar.
The g attribute is only storing the x, y of the activity. So you still need the image to 'draw' for example the current activity on that image, using the x,y from the g attribute.
Ofc, another approach could be that the process is reconstructed using the g attribute only (which is exactly what happens when you use Signavio and the GPD), but we haven't followed that path yet.