ScriptingModule

[zola]

Hi CE
I have seen in demo8 that You use Lua for scripting. This language seems to provide the possibility to bind scripting functions directly to guievents (that is, one can have function pointers or something similar).

I'm using AngelScript in my projects, but AngelScript doesn't yet provide function pointers.

Will it be possible to register for guievents without having to bind the scriptfunction?

Something like this would be nice to have

Code: Select all

 guiwindow.subscribeEvent(const String& eventname, const String& scriptfunctionname)


In the ScriptModule we could introduce a member with this signature

Code: Select all

virtual int executeScriptFunction(const String& function_name, const CEGUI::EventArgs& e)   = 0;


What do You think about it?

Regards
Tom

[zola]

I' m completely new to the boost::Signal stuff.
Am I right if I just would do the following

Code: Select all


// in C/C++
struct EventHandlerProxy
{
  String scriptFun;
  operator()(const CEGUI::EventArgs& e){
   // do my scripting function calls using scriptFun as function name
  }

}

// in ScriptCode
EventHandlerProxy* myProxy=new EventHandlerProxy();
myProxy.scriptFun="handleQuit";
windows->subscribeEvent(theEvent, myProxy);



[CrazyEddie]

Your other post came in while I was typing this, so forgive the overlap

This is a reasonable request, just some notes on my preliminary thoughts about this...

I'll definately add a method to ScriptModule, I'll probably call it 'executeScriptEventHandler' or something though to make its purpose clear.

Yes, your proxy approach would work okay. Infact the CEGUILua module handles most of the magic of translating what is provided by luabind into what is expected by the core of CEGUI using a system such as that, though nothing needs to be done manually by the client of the system, it's all done magically for you . I will probably keep this type of translation in the concrete ScriptModule classes rather than extending Event/EventSet, since I don't want to tie these to higher level classes.

(Overlap) It's no major thing to acheive this - just a mini functor class to store some script specific data (in this case the name of the scripted function) and the application operator to do something useful with it (so call the new executeScriptEventHandler method in ScriptModule).

I would have liked to have had the CEGUILua module released by now, but I have had major issues getting the version of luabind I'm using to work with the older VC++ compilers, so untill the luabind guys fix these problems, the Lua scripting module is in limbo.

I actually briefly looked at AngelScript on Friday and thought it was pretty cool

[zola]

AngelScript is very cool and easy to use too.

Which classes do You suggest making available through scripting?

[CrazyEddie]

It all depends on what you want to be able to do.

I had stated that the Lua support would enable you to do anything in Lua that you can do using the C++ interface, and as such The CEGUILua module exposes the entire system

For a more minimal approach, the low-level classes (Size, Vector2/Point, Vector3, Rect, ColouRect etc) would be essential, and then WindowManager, Event/EventSet, plus whichever widget types you want to use would probably get you a reasonable amount of access. If you wanted to do custom rendering stuff via script, then add Image/Imageset/ImagesetManager and Font/FontManager. As I said, it depends