Thanks GabrielI appreciate your answer, it was clear and complete. The best,
~GA 2014-08-19 4:40 GMT-05:00 Joaquín Salvachúa <jsalvac...@dit.upm.es>: > Hello, > > In the Fi-Ware EU research project ( http://www.fi-ware.org ) we have > been developing a version of Horizon fully javascript based (using > backbone.js) that have a much better user experience, keeping most of the > look and feel. Some of the functionality is packed into a pure javascript > library called Jstack ( https://github.com/ging/jstack ). > > It includes the full horizon functionality and some extras for the > project. > > It is open source ( https://github.com/ging/fi-ware-cloud-portal ) and we > would love to contribute it to Openstack and make it evolve within the > OpenStack community. > > How do you think we may proceed on this? > > Best Regards > > Joaquín Salvachúa > > > ------------------------------------------------------------------------ > Joaquin Salvachua tel: +34 91 549 57 00 x.3026 > Associated Professor +34 91 549 57 62 x.3026 > dpt. Telematica > E.T.S.I. Telecomunicacion > Ciudad Universitaria S/N fax: +34 91 336 73 33 > E-28040 MADRID SPAIN > > mailto:joaquin.salvac...@upm.es <jsalvac...@dit.upm.es> > -------------------------------------------------------------------------- > > > > > El 19/08/2014, a las 03:40, Gabriel Hurley <gabriel.hur...@nebula.com> > escribió: > > At the point at which the Horizon project first began (during the Cactus, > I believe) the handful of folks working on it wanted a Python web framework > that would get them up and running as fast as possible. That meant lots of > built-in, “batteries-included” features so they didn’t need to reinvent a > bunch of wheels; and that also meant something they had at least passing > familiarity with. So they chose Django. > > Speaking from personal opinion at this point (and as a former Horizon PTL > and Django core developer): Flask is good for writing APIs or very simple > sites, but not for large webapps. They would have had to write a ton of > code for things other frameworks have built-in. And Pylons and Zope don’t > have nearly the base of community, resources, or documentation that Django > does. Twisted would have been another option, but the event-driven model of > Twisted is hard for many people to wrap their heads around and wasn’t > appropriate at the time. > > All things considered I think the choice of Django was relatively sound (I > had nothing to do with the original choice). It’s allowed the project to > grow and scale effectively over the last 3+ years. > > At this point, though, there’s a clear demand for a more responsive and > real-time dashboard experience, and that generally means moving as much as > possible into a client-side JavaScript-based webapp. That’s why the Horizon > team has been making efforts to move towards things like angular.js and > socket.io to help bring the next era of modern Horizon functionality. > It’s not a simple or easy transition, but as that transition takes place a > vast amount of the Django code will likely go away. > > I hope that helps shed some light on the historical reason for “why > Django” as well as why it may matter less that it was Django and not > something else over time. > > All the best, > > - Gabriel > > *From:* Guillermo Alvarado [mailto:guillermoalvarad...@gmail.com > <guillermoalvarad...@gmail.com>] > *Sent:* Monday, August 18, 2014 4:20 PM > *To:* openstack@lists.openstack.org > *Subject:* [Openstack] Why Horizon use Django instead Flask or other? > > Hello, > > I am wondering why Horizon is built in Django instead other Python > Framework Like Pylons, Flask, Zope or oher ? > > > Thanks for your time! > ~GA > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
