PS : I think that it is best to let the functions like they are, it is more easy to find them in the documentation.
i don't think this is a good argument.
how hard can it be to look for pan_setslider if you see that setslider is a method of panel objects? and a search function will find pan_setslider anyway if you enter setslider.
having a clean and non-verbose/non-redundant API should always come first.
ideally the wrapper should come with its own complete documentation since the usage of some functions will be quite different to lite-c. but i know that doing such a documentation would be a lot of (quite boring) work.
