Multiple suggestions concerning blueprints

[Killkrog]

Hi devs!

Most importantly: Grand job on .15, you guys really delivered quite a thing there!
Now, some suggestions of a few things I feel are missing in the API.

1. LuaGameScript::read_blueprint_string(string, overwrite) → LuaItemStack
Reads the specified string, creates an item stack and puts it on the cursor. If the cursor is not empty and overwrite is not set, returns nil.

2. LuaItemStack::write_blueprint_string() → string
Returns the string that defines this blueprint.

3. Create a new static class LuaBlueprintLibrary

4. LuaBlueprintLibrary::get_libraries() → array of string
Returns the names of all libraries available to the player. (Basically the persistant storage, the game storage and the other player's storages)

5. LuaBlueprintLibrary::get_children(library) → array of LuaBlueprintLibraryEntry
Returns a list of all top-level entries in the specified library.

6. LuaBlueprintLibraryEntry::get_children() → array of LuaBlueprintLibraryEntry
Returns a list of children within this entry.

7. LuaBlueprintLibraryEntry::get_name() → string
Returns the name of this entry.

8. LuaBlueprintLibraryEntry::get_blueprint_icons() → array of Icon
Returns the icons of this entry.

9. LuaBlueprintLibraryEntry::get_type() → string
Returns either "blueprint" or "blueprint_book".

10. LuaBlueprintLibraryEntry::get_blueprint(overwrite) → LuaItemStack
Puts the blueprint on the cursor. If the cursor is not empty and overwrite is not set, returns nil.

You get the gist of it. The according setters of course also would be needed.
So, why do I think those things are needed?

Well, while the blueprint library in my eyes is the best addition to the game up to now, its interface lacks. Greatly.
It's like someone told me instead of the detailed view in my operation systems explorer I now have to use the tile view with the biggest icon size possible.
I don't tell you to change the interface of the in-game library, because there is nothing like "the one best interface that everyone likes".
But with the aformentioned additions to the library, it would enable us to "wrap" the functionality of the blueprint library and all its nice features in a functional interface.

Thanks for reading!
Cheers =)