Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
WIP: Generic wizard plugin
mandrav:
Thanks Takeshi.
The main reason I hold this back (although it is ready), is because scripting doesn't work in all platforms yet. This would make it impossible to create a new project on those platforms...
takeshimiya:
--- Quote from: mandrav on February 21, 2006, 02:14:16 pm ---Thanks Takeshi.
The main reason I hold this back (although it is ready), is because scripting doesn't work in all platforms yet. This would make it impossible to create a new project on those platforms...
--- End quote ---
Yes, I'm worried about the same. So I think C::B should be useable without scripting (at least for now, AngelScript should be an optional dependency).
That's why I think the dependencies are good to be ifdef'ed (except when ifdef'ing introduce too much cruft in the code).
Actually AngelScript works on all platforms (I think), but only when using AS_MAX_PORTABILITY, and AFAIK only the asCALL_GENERIC calling convention is available.
C::B could introduce a header with things like
--- Code: (cpp) ---#ifdef AS_MAX_PORTABILITY
#define ... asCALL_GENERIC
#else
#define ... ...
#endif
--- End code ---
mandrav:
One of the main reasons (besides raw speed) AngelScript was chosen, is because it's so damn easy to bind to existing C++ classes. No need to create wrapper classes, fight with the stack or other annoyances all other scripting languages have.
Plus, Andreas (AngelScript's author) provides excellent support for nothing. Much as we do here :) (shameless plug).
With that said, work has begun by Andreas for a 64bit port and I promised to help him. So I don't think it will really take long before it's done ;)
Also, with the help of afb, a PowerPC port is in the works. I wouldn't know how long this will take because it really depends on afb.
To recap, I think it's worth waiting a little while longer to have native AngelScript support (at least for 64bit) than start writing wrapper functions for everything inside C::B (which would become obsolete anyway once the above ports are done).
takeshimiya:
--- Quote from: mandrav on February 21, 2006, 02:45:38 pm ---To recap, I think it's worth waiting a little while longer to have native AngelScript support (at least for 64bit) than start writing wrapper functions for everything inside C::B (which would become obsolete anyway once the above ports are done).
--- End quote ---
I know, I'll ask Andreas if he can make the wrappers right in AngelScript, because there always will be times where AS_MAX_PORTABILITY is the only thing that works.
Navigation
[0] Message Index
[*] Previous page
Go to full version