|
The purpose of scripting is to enable someone non-technical to alter
logic at run-time. Basic is a crap language, but it is a perfect scripting language cause even my mother are familiar with it. As a programmer I absolutly hate the language, but I respect the fact that other less technicall can program in VB and VBA alike scripts. TCL is very cryptic and due to that not suited as a scripting language. But, do we need to shoose? No! OpenPBX could make it's own API enabling other languages to call into & control the PBX. Meaning that TCL lovers could use theire beloved TCL and others could use vxml or Java or whatever. There are an open source vxml interpreter etc that I personally hope will be integrated. xml is not a good scripting language either, but it a few strong points: ccxml, sxml, vxml are very popular these days and there exist graphical user interfaces though the eclipse project we could benefit from. There also exist an open source vxml interpreter etc. Lets face it folks: One of the biggest drawbacks with open source projects is that it tend to be for nerds only. Asterisk is great ,except for a crappy non-existing architecture, lack of documentation and lack of user friendliness - I believe we can do better - cause if not there will be no point having this project at all! Jan Chris Albertson wrote: TCL was designed just for this time of application. One where you write and API in C and then use TCL script to scring the API calls togethere. Swig will build the TCL binding for you even if you choose to use only TCL.THe choise of TCL. Perl, Java or whatever is triveal and matters little as long as the language was ODBC, networking and access to the filessystem and of corse they all have all of this. The only points that do matter are 1) Pick a language that somebody else maintains, is widely used and known and most critically has many examples of it being embeded in applactions. TCL, Perl and Guile are leaders in this area 2) Design a clean API that is language interpeter independent and you will preserve the option to switch or add another languages later with only a couple days work. 3) An RPC layer over the API could be useful. --- Justin Tunney <[EMAIL PROTECTED]> wrote:I've talked to a few people who want to integrate _javascript_, which would work out pretty well considering that we could, for example, hijack Walter Bright's (of Zortech and Symantec C++ fame) GPL implementation of ECMAScript (http://digitalmars.com/dscript/index.html) However, and to be quite frank, I am shocked that no one has suggested using TCL. TCL is /perfect/ for OpenPBX. TCL is very lightweight, uses BSD-style license, and is ghoulishly easy to embed in to C applications. TCL is also easy to learn and has years of experience under its belt for embedding in C applications. Furthermore, there is a SourceForge project for TCL ODBC support (http://sf.net/projects/tclodbc/). I am not sure what the status of this project is because SF is down right now. Here's a tutorial on how to embed TCL in your C application: http://wiki.tcl.tk/2074 TCL would certainly save all the OpenPBX developers a _lot_ of time implementing GOOD dialplan scripting. After all, the common consensus here is to reinvent as few wheels as possible, TCL will let us do that better than any other language. (As opposed to AEL which is too good to even use flex/bison) -Justin Tunney On Thu, 08 Dec 2005 22:41:59 -0500, Daniel Swarbrick <[EMAIL PROTECTED]> wrote: |
_______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
