-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 21 Mar 2006, Daniel Swarbrick wrote: > bkml wrote: >> On Mar 21, 2006, at 4:10 PM, Beau Hargis wrote: >>> I think we will have to port AEL or AEL2 to OpenPBX >> P L E A S E ... >> let's not open pandorra's box, > I second that. I looked at AEL late last year, and really wondered what > the point of it was. Different syntax for people more used to C-like > syntax? Well, it "compiled" to native dialplan commands (sometimes), so > really, why couldn't you just use native syntax in the first place? > It would be a waste of developer resource to port AEL to OpenPBX. I'd > rather see the existing res_js improved, or perhaps a res_python added.
There has been talk of replacing the dialplan with something good and beautiful. I think benjk has some examples online (but I forgot where). What features do we want/need in the dialplan and how should they work? And, do we have anyone who wants to code it? /B - -- * GPG-Key: http://evil.gnarf.org/mrbk.pgp A: Because we read from top to bottom, left to right. Q: Why should i start my reply below the quoted text? - -- http://www.i-hate-computers.demon.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEH+vDckvkFeO3ANARAt/rAJ9c0XeKoJGoB2hfixYwONNqd61IWgCeKLMD JrD2Qaek9auj8AFUt4Va1N0= =DN9U -----END PGP SIGNATURE----- _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
