Ok, thanks. Fair enough.

Renat Akhmerov
@ Mirantis Inc.



> On 07 Jul 2015, at 21:45, David Lyle <dkly...@gmail.com> wrote:
> 
> At this time, there is no hard requirement on using AngularJS for Horizon 
> plugins. Existing plugins should not feel pressured to rewrite. Support for 
> Django content is not going away anytime soon. The Horizon team feels that 
> long term AngularJS will prove to be a better framework to build on. But we 
> still have open work before being able to make that a requirement.
> 
> New plugins should certainly consider Angular as the framework, but since the 
> tooling and documentation is not fully baked yet, it remains a suggestion.
> 
> David
> 
> On Tue, Jul 7, 2015 at 2:50 AM, Renat Akhmerov <rakhme...@mirantis.com 
> <mailto:rakhme...@mirantis.com>> wrote:
> Hi,
> 
> Unless this is a strict requirement for OpenStack projects to move to 
> AngularJS I’d prefer to keep existing framework within Mistral for purely 
> time/resources reason. I believe such a transition will take weeks.
> 
> I’m not an expert in UI stuff and Horizon specifically so it would be helpful 
> to get input from someone else working in Horizon team.
> 
> Zhenguo, thanks for bringing this up.
> 
> Renat Akhmerov
> @ Mirantis Inc.
> 
> 
> 
>> On 07 Jul 2015, at 13:16, niuzhenguo <niuzhen...@huawei.com 
>> <mailto:niuzhen...@huawei.com>> wrote:
>> 
>> Hi folks,
>>  
>> As Horizon is moving towards an Angular application, I think it’s high time 
>> that we should make a standard for other projects which want to horizon 
>> compatible on  whether they should based on Angular Dashboard or the current 
>> Horizon framework. For new project, I think it makes more sense to build the 
>> dashboard on Angular. But for “old” project like Mistral-Dashboard and 
>> Tuskar-UI, they works fine with Django framework now, do they have to move 
>> towards Angular also, and when that should be done.
>>  
>> -zhenguo
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org 
>> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to