[openstack-dev] [horizon] static files handling, bower/

Matthew Farina matt at mattfarina.com
Thu Jan 22 17:27:40 UTC 2015

I would like to add one more nuance to this discussion that I don't
remember seeing.

JavaScript libraries run in web browser in their JavaScript engines (like
v8) rather than on the server. A version of a JS library may be fine on a
system, without any security issues, but contain browser issues. The
version used matters more to the application and the web browsers consuming
the application than to the system it's on.

Some of the libraries exist as packages. For example, there are some debian
packages. These have older versions of libraries than those that will work
in Horizon. The libraries need to integrate for horizon and the browsers.
So, supporting varying versions of a js library, their interactions
together, and creating a usable interface will be a real problem. For
example the debian packages of old or varying versions will a problem for
those of us attempting to craft a UI. What's there isn't practically usable
today. Some things are missing.

Does that help add clarity?

On Thu, Jan 22, 2015 at 11:53 AM, Matthew Farina <matt at mattfarina.com>

> Radomir and Matthias,
> Has anyone done an inventory of xstatic packages that are available as
> system packages? I ask because I started asking these questions after doing
> a cursory inventory and finding few xstatic packages as system packages. It
> appeared to me that the common case was the one Matthias noted where the
> xstatic package bundles the js libs. That we're actually getting them from
> pypi or a mirror. Can someone show me there really are system packages to
> replace the xstatic packages?
> On Thu, Jan 22, 2015 at 5:15 AM, Matthias Runge <mrunge at redhat.com> wrote:
>> On 22/01/15 09:48, Radomir Dopieralski wrote:
>> > All of the XStatic packages had to be packaged for the respective
>> > distributions in order to package Horizon. That was a lot of work, but
>> > it has been done my the packagers of the distributions. As far as I
>> > understand, most of those XStatic packages are just dummies, pointing to
>> > the actual system-wide JavaScript packages -- XStatic has such a
>> > capability. So while we are indeed maintaining some of the XStatic
>> > packages for our own convenience, the packages that contain actual code
>> > in the distributions are maintained by those distributions' packagers.
>> >
>> Yupp,
>> poniting to system packages is something, which makes the XStatic
>> approach way more acceptable.
>> But, if you don't have them (yet), xstatic packages will bundle js libs
>> for you.
>> Matthias
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150122/bb3a7c9d/attachment.html>

More information about the OpenStack-dev mailing list