Client-side Scripting Declarations

[GoogleCodeExporter]

Right now only core Angel classes are exposed to the Python layer. It's
expected that the user will either work in Python or work in C++, or
perhaps move a Python class into C++ when it's found to be a bottleneck. 

The use case that isn't supported, though, is a user who creates classes
and functions in C++ that he then wants exposed to Python. He could add
them to Angel itself (for his game), but then he has to be messing around
in the engine, playing with SWIG interface files, etc. and that's all a
pain in the ass. 

In a dream world, there would be a special comment format that a user could
drop in to a header file that a build script could parse, use to generate a
SWIG interface file, and expose to Python that way. The issue then becomes
how to load that Python module into the same runtime, where the init code
lives, etc. 

Either I need to level up my SWIG-fu, or someone who knows more about these
things needs to step up and help. 

Original issue reported on code.google.com by lieseg...@gmail.com on 4 Feb 2009 at 8:53

[GoogleCodeExporter]

Original comment by lieseg...@gmail.com on 10 Feb 2009 at 12:05

• Added labels: Milestone-Release2.5

[GoogleCodeExporter]

This has been set up in the reorganization branch, soon to be merged into 
trunk. 

Original comment by lieseg...@gmail.com on 3 Jul 2010 at 12:22

[GoogleCodeExporter]

Original comment by lieseg...@gmail.com on 3 Jul 2010 at 12:23

• Changed state: Fixed