Chromium11

[romainpi]

OK, big pull request. Feel free to use any part of it. Sorry about the excessive number of commits linked to it, I'm not the most skilled Git user.

Most notable changes are:

• Custom URI scheme, using code from K.Gadd taken at: http://code.google.com/p/berkelium-sharp/
• All exes and libs should now be built in the bin/ folder (except demo binaries), this reduces silly mistakes.
• ScriptVariant now uses a real boolean to hold the bool value. There was a bug with the old implementation.

Please note:

• This has all been done on Windows. I hope I haven't broken Linux or Mac... Sorry if I did...
• This work is part of work I've been doing to update BerkeliumSharp, which I will post soon, somewhere.

[romainpi]

Also, I'll try and update the samples to use the new features.

[pathorn]

Hey, thanks for implementing the protocol handlers. I'll see if I can get around to this in the next few days.

I'm going to have to take a look at the HGLOBAL...that's going to cause problems because it's windows-specific. Is there any reason to use a HGLOBAL instead of a simple char*/length?

I think what I am going to do is have the handler implement a function "freeMemory" or something which takes a char*, or a "freeLastRequest" function so that you can allocate the memory, return it, and then free it later.

Too bad we can't use std::string across DLL boundaries--Microsoft messed that one up thanks to all the incompatible VC++ runtimes out there :(

[kg]

The HGLOBAL thing is because it has to be safe to allocate and free across DLL boundaries. It probably makes sense to add a custom solution to this to the Berkelium API. I used HGLOBAL in BerkeliumSharp since it was already windows-only.

P.S. romainpi, thanks for salvaging this stuff! Wish I had the time to do so myself :)