Comments for Nate's Code Vault

Comment on Transmission AS3 gets a logo and forum support! by Nate

Nate — Mon, 30 Aug 2010 15:12:10 +0000

James! That’s awesome! I have been bested for sure. I’d love to use that logo for the project. The only feedback I have is if you could add a second ‘i’ right before your ‘o’ graphic. Thanks for taking the time to do it!

Comment on Transmission AS3 gets a logo and forum support! by James Lei

James Lei — Mon, 30 Aug 2010 11:37:26 +0000

Hi, I’m from Singapore. Although I am an average Flex developer, I took it as a challenge to improve your logo if you don’t mind.

I’m not a logo designer but fairly good at modifying picture into a Web 2.0. I don’t mind to give away my design for your project for free. Let me know what you think.

http://img440.imageshack.us/img440/3729/transmission.png

Comment on Transmission – AIR 2 to Java Communication Layer by Nate

Nate — Sun, 29 Aug 2010 15:44:59 +0000

The fixes have been pushed up. Go ahead and update. If you have any more problems make sure to file a bug in Google Code.

Comment on Transmission – AIR 2 to Java Communication Layer by Rob McKeown

Rob McKeown — Fri, 27 Aug 2010 13:28:15 +0000

no problem… That’s exactly what I did to get past it too.

Comment on Transmission – AIR 2 to Java Communication Layer by Nate

Nate — Thu, 26 Aug 2010 22:01:39 +0000

Hi Rob,

Verified your error. It’s a null pointer. I will get it fixed later tonight. As a work-around, if you create a file in your user home directory (~/Users/nross83 on Mac or C:\Documents and Settings\nross83 on Windows) called .transmissionLog.log. All the System.out.printlns in your project will be written to that file for debugging purposes. I always have this file so that’s how the error slipped through.

Comment on Transmission – AIR 2 to Java Communication Layer by Rob McKeown

Rob McKeown — Thu, 26 Aug 2010 21:37:03 +0000

thx… I also noticed that in Transmission.java there is a try/catch block that tries to find the .transmissionLog.log file. It if doesn’t find one, the FOS is null. But then the null FOS is used to create two TransmissionStandardStreams. As a result, in my app, it fails if I don’t have that log file. I’m not sure what is unique about my app that is different than the demo app except that, in my app, the handler is actually delegating the work to ANT. Perhaps something is trying to access it System.out? In any event, nothing is actually written to the file.

Comment on Transmission – AIR 2 to Java Communication Layer by Nate

Nate — Thu, 26 Aug 2010 20:02:41 +0000

Hi Rob,

Make sure to call Transmission.getInstance().exit(true) as your app closes to kill that process (I use the WindowedApplication close event normally). I forgot to add that to the demo app. I’ll be sure to update it.

Comment on Transmission – AIR 2 to Java Communication Layer by Rob McKeown

Rob McKeown — Thu, 26 Aug 2010 19:59:38 +0000

I’m not sure if it is just me or not, but when I kill the AIR application, I can still see the javaw.exe process still running. Though, it seems that the AIR docs say that the native process will be killed automatically. I don’t know if this is an AIR bug or a Transmission bug. Anyone else seen this?

Comment on Solving relative DataGrid column width problems with ScalableDataGrid! by Andrew

Andrew — Mon, 23 Aug 2010 19:08:33 +0000

Worked perfectly for me. Thanks for saving me time…

Comment on Creating a bundled AIR / Java Installer on a Mac by Nate

Nate — Mon, 23 Aug 2010 16:16:37 +0000

I just wrote a library called Transmission which uses AIR 2.0 native process to start up a Java jar in your project and receive messages via standard output in much the same way that Merapi did. The biggest benefit is that you don't have to create a custom installer (you can use the native AIR 2.0 installer for both PC and Mac), and you also can use the AIR updater framework. Check it out here.