[sldev] Scripting the client

[Lawson English]

Dzonatas wrote:
> Lawson English wrote:
>> What should be scriptable by such an interface? How it should 
>> accomidate/facilitate plug-ins?
> A scriptable interface allows us to use higher-level plug-in easier. 
> The script engine has to exist as a binary plug-in at a lower level.
>
> Binary plug-ins have to be somewhat isolated in name-space. I have 
> made the C++ class LLDynamicSharedLibrary to help with binary plug-in 
> models.
>
> The problem is that STL code prevents us from having a stable viewer, 
> but we are working on it. It is a matter of library/API compatibility. 
> Plug-ins need the STL to use a more higher-level API. A very low-level 
> API is possible, but such is much harder to port across platforms and 
> is much harder to maintain.
>
You said  on the forums that you were working on a Python plug-in. Why 
specifically Python, rather than Lua, given the relative simplicity of 
implementing Lua as a plug-in scripting language (that is what it is 
designed for) compared to implementing a Python plug-in, and the fact 
that Lua is already used as the scripting language for the Worlds of 
Warcraft client and has a proven track record for scripting such a system?

Please keep in mind that I use neither language. My question is purely a 
technical one about the relative simplicity and cleanliness of the plug-in.