Volker wrote:
As you mentioned in
the other thread, your problem has been solved, hasn't it? Can you tell us, what was the problem?
the problem was with localization files. somehow mono couldn't parse string data from *.resx files. Thanks to phoenix64 from #horde3d@freenode I made it work with hard-coding string data and getting completely rid off resource file. However as you see, it's not an elegant solution at all. So, when I have time, I'll try to port the resource files to Mono and post the final project files. It will also address some other issues such as:
*MonoDevelop IDE's VS2008 project file support is not yet very good. It would be better to provide a VS2005 project file for cross-platform compatibility. (Currently I get some errors while opening the .NET solution in MonoDevelop)
*Samples uses Windows specific code. They can be ported to other platforms with the use of GLFW instead of Winforms
*Horde3D.NET.dll and Horde3DUtils.dll are not separated. They are merged into 1 DLL file.
*PlatfromInvoke.cs contains Windows specific code. I don't know what it does but deleting it doesn't seem to affect anything on linux.
*Also it's recommended by mono team that, when wrapping native libraries in C#, it's better to call the native dlls without their extension: instead of Horde3D.dll, it should be called Horde3D. From what I understand when done in this way .NET looks for Horde3D.dll and Mono looks for libHorde3D.so which improves cross-platform compatbility. BUT I couldn't get it work yet. For some reason, in linux, it only accepst libHorde3D.so. It may be a Mono bug. I'll try to figure it out
EDIT:NodeHandle and ResHandle are not defined in .NET bindings. Is it made on purpose since they are only typedefs to int or is it forgotten?
cheers