<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'm interested. Catch up with me on IM or irc and we can discuss.<div><br></div><div>Mike</div><div><br><div><div>On Mar 20, 2013, at 10:28 AM, Seven Du <<a href="mailto:dujinfang@gmail.com">dujinfang@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
Hi,
</div><div><br></div><div>I'm learning ember.js and wondering if anyone here has experience on that and has interest for another open source FS GUI.</div><div><br></div><div><a href="http://emberjs.com/">http://emberjs.com/</a> said it's a framework for creating ambitious web applications. I had used backbone.js and it sames that ember.js is more complicated and short of document so I had a hard time on that.</div><div><br></div><div>Anyway, back to the topic. I started this project as a way of learning ember.js and hope it would be useful for FreeSWITCH. Make another FS GUI is not to reinvent a wheel but, sometimes you just found you have a hard time to get fusionPBX or blue.box runing. So the FS-Portal project is not aims to replace them but sometimes you just need a GUI that is simple and can be used out of the box.</div>
<div><div><br></div><div>Take a look at the code <a href="https://github.com/seven1240/FreeSWITCH-Portal">https://github.com/seven1240/FreeSWITCH-Portal</a>. It's just static html and js files you can put in your htdocs dir and it only depends on mod_xml_rpc right now.</div><div><br></div><div>To make it more fun Websocket is more helpful and I patched mod_event_socket to use the libwebsockets lib. It is kind of working, just I'm not sure if it's a good idea to add the code into mod_event_socket or make a new module. Or should we wait the new WebRTC out which might use Websocket for signalling. Anyway, it's working w/o websocket now and please try and give me some feedback if you thinks it's helpful.</div><div><br></div><div>Well, I do have something more to discuss here. mod_xml_rpc implemented some interfaces like /api, /txtapi, /webapi, and some commands implemented "show xx as xml", "show xx as json" and "sofia xmlstatus" etc. Is there a easy way or interest to make this more consistent to respond to different Content-Type? e.g. api, txtapi, xmlapi, jsonapi etc?</div></div></blockquote></div><br></div></body></html>