ANNOUNCE 1.0.5

Version 1.0.5 of gmtk, gnome-mplayer and gecko-mediaplayer have been released

The build process is the same as 1.0.5b1 which is documented here:

http://kdekorte.blogspot.com/2011/10/105b1-of-gmtk-gnome-mplayer-and-gecko.html

The following fixes have been made since 1.0.4

gmtk

This library is new as of 1.0.5 and is required for the build. Several common functions and routines in gnome-mplayer and gecko-mediaplay have been moved to this library. Which should result in a slightly smaller installed code size.

gmtk can be used to build your own media players as widgets have been created to control mplayer. A simple media player can be built using this library very quickly. If you have questions about this library and how to use it in your GTK application, please email the list and I will cover its usage.


gnome-mplayer

Removal of large amounts of code that are now present in gmtk
Customization of Menu Hot keys
Remove need of mplayer config file
--vo and --dvd_device command line options
Several other small fixes


gecko-mediaplayer

Due to changes at Apple, QT files from Apple.com are now fully downloaded before playing, prevents mplayer from crashing or going into a infinite loop

Workaround xulrunner issues due to the API changing but Mozilla not bumping the API version

Conversion to gmtk for preference storage and other common routines.


Download links:

http://gmtk.googlecode.com/files/gmtk-1.0.5.tar.gz

http://gnome-mplayer.googlecode.com/files/gnome-mplayer-1.0.5.tar.gz

http://gecko-mediaplayer.googlecode.com/files/gecko-mediaplayer-1.0.5.tar.gz

1.0.5 is getting closer

Sorry for the long delay in getting 1.0.5 out the door. There have been a lot of changes and fixes for some minor issues that have been painful to fix. Apparently, the nsapi has changed again and was not properly versioned in all instances. So several attempts were made to detect and work around the problems. I believe we have solved the issues. You can read issue 161 for all the gory details: 158-162 are all related to this problem.

I hope to have some time in the last weeks of December to get the release out the door. Hopefully, it will be painless as packages have been made and a large amount of testing has been done.

My work schedule has been a little busier over the last few months so I have had less time to spend on these applications. Also, I want to make sure we don't have any surprises. I expect we will, but I want to try and minimize them.