Damian Krzeminski wrote: > following up on my e-mail about sipXconfig beyond 4.0... > <http://permalink.gmane.org/gmane.comp.voip.sipx.devel/16282> > > So based on initial feedback Kevin and I looked at the couple of libraries > and technologies related to creating rich client in-browser applications. > > http://sipx-wiki.calivia.com/index.php/SipXconfig_UI_libraries > > I also experimented a bit with the 2 of them writing some code: > > http://github.com/dkrzemin/sipxecs/tree/sprinkle-gwt > http://github.com/dkrzemin/sipxecs/tree/sprinkle-mootols-jquery > > Kevin tried to do the similar thing with ActionScript/Flash but gave up > after realizing that there is virtually no support for developing that on > open source platforms using open source tools. > > Without getting into too much details (check wiki if you are interested) > looks like writing directly in javascript would probably give us a nicer UI > initially but we would take some time to develop tools and framework to get > productive and handle the pesky little issues like localization or unit > testing. Using GWT would probably give us quick results but a more > pedestrian look and feel. We would need to spend some effort to get to the > level of blink offered out-of-the-box by modern javascript libraries. > > At this point I am quite comfortable with any selection and I do not > envision big problems even if we were too mix and match (for example: GTW > as a framework incorporating pure javascript widgets where we need them). > As long as the UI part effectively runs in the browser communicating with > the server only to exchange data I am happy. > > I know some developers looked at my code examples and commented on #sipx > channel. If you have some opinions that my tip the scales make yourself heard. >
After taking brief look at the GWT and jQuey/mooTools User Portal demos, here's my 2 cents (pretty much same as Damian pointed out). jQuery : The interface themes look a lot more sleek and web 2.0ish out of the box. You develop in javascript, so should give you a more fine grained control of the UI. Quite popular, with a few big sites using it. However, the code does not really look all that structured. It might be a bit of a pain to work with as the application grows. GWT : The code looks more maintainable, has a structure to it, and it's easier to refactor. Statically typed, easier to debug. IDE support is awesome - code completion, debugging, etc. In terms of getting up to speed, GWT will take a shorter time, seeing as you develop in java. Google Waves. However, the UI does lack a certain "je ne sais quoi". Having said that, I vote jQuery. It would be interesting to work in javascript, and would be a really useful skill to have when the time comes to add other fancy stuff/widgets to sipXconfig. Arjun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
