On Tue, Jun 9, 2009 at 4:26 PM, Damian Krzeminski<[email protected]> 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.
+1 for going with GWT and incorporate javascript as needed. It's also possible to write native methods to use js directly within the java code - of course that should be used carefully, since it makes debugging harder, but it's a nice feature when properly used. I'd like to cite mosaic-gwt, which has a superset of GWT widgets and it's not bloated as ExtGWT. > > 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. > > The challenge now is to start using what we learned in user portal. We will > start slowly, replacing just a new phonebook UI (in 4.1.0 phonebooks get > more details). > D. > > > > _______________________________________________ > 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/ > -- Arnaldo M Pereira Fugazi at freenode _______________________________________________ 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/
