Not a bad idea. I'm more than happy to do this and give Richard42 write access to my SVN tree.
My personal feeling about merging the Linux and Win32 builds of RiceVideo is that it's more work than I'm willing to take on right now, and for little benefit. Not to imply that it's a bad idea - I think if anyone feels passionate about it and wants to do it, they should go ahead - but there are better things that we could be working on, and other ways of sharing our work together.
To understand why I feel this way, let me give a little history about how RiceVideoLinux came to be. The original RiceVideo plugin was developed as a windows-only project. Hacktarux took the source for v6.1.0 and ported it to Linux. This involved a boatload of GTK code for the config dialog and a some OS-specific tweaks for things like directory list traversal. He sort-of tried to keep it buildable in Win32 by adding a bunch of #defines for the OS-specific stuff, but he also removed the D3D renderer (obviously wont build in Linux) and used some typedef hacks for D3D-derived objects like vectors. Hacktarux really made a lot of changes. Next, I started with a vanilla copy of Hacktarux's 6.1.0 port and modified it to build and run on the 64-bit architecture - mostly changing 'long' to 'int' and re-writing the inline assembly code. I decided that the code really needed to be cleaned up, since the Linux port left all this junk lying around that was unmaintainable. I know that no-one is going to run the Linux port of RV on Win32 without the D3D renderer, so there's no point in having all this #defined stuff: it will never be tested and is sure to break sooner or later. So I removed all of the "platform-independent" stuff to make it Linux-only: all the #defines, all the D3D-derived stuff, is now gone from my build. It is much cleaner and more maintainable this way. Then I made a bunch of fixes: most of them to the OpenGL renderer, but some of them to the base code as well.
So here's what we're left with: a good Win32-only build of RiceVideo maintained by Mudlord, with an excellent D3D renderer and a mediocre OpenGL renderer. And a good Linux-only build, for 32-bit and 64-bit architectures, maintained by myself, with a pretty good OpenGL renderer. Merging these two together without introducing any regressions for the individual platforms would require a very large amount of work. Someone would need to build an OS-independent layer to avoid #define hacks. Someone would have to add the missing functionality (like the Debugger window) to the GTK GUI. Someone would have to come up with a proper solution for using non-D3D derived data types in the base classes but still be compatible with D3D in the Win32 build.
The primary motivation that I can see for merging the RiceVideo projects is to make sure that fixes and improvements get applied to both systems. As an alternative solution, I think it would be easier if we did the following: I can add Mudlord to the commit email notification list for the RiceVideo project on my SVN server, and he can do the same for me on his SVN server. This way we will each receive a diff through email when a change is applied, and can choose to merge this change into our own repository if applicable. Unless one of us goes on a hacking spree and introduces many changes into the platform-independent core, this will be much less work than merging the two projects together.
I have already merged all of the changes from Mudlord's SVN server up until about r28 into my build - a lot of it was Win32 or D3D-specific stuff, but there were a lot of hi-res texture loading changes which made it in.
