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

Matthew Farina matt at mattfarina.com
Thu Jan 22 21:13:48 UTC 2015


I'm quite familiar with node.js and browser development. I think some of
the issue here may be a lack of detailed explanations and assumptions. By
asking questions here I, and some others, have been learning details that
we didn't know before. And, we're getting to follow from the intent from
start to finish. I'm finding this to be incredibly revealing.


On Thu, Jan 22, 2015 at 3:47 PM, Richard Jones <r1chardj0n3s at gmail.com>

> On Fri Jan 23 2015 at 4:28:59 AM Matthew Farina <matt at mattfarina.com>
> wrote:
>> 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.
> I think you're confusing Javascript in the browser vs. Javascript for
> node.js
> Those are two separate things. Javascript used in the browser is rarely
> (never in our case) used also for node.js development. There are even two
> separate packaging systems: bower is all about components for browsers,
> whereas npm is all about packages for node.js. Our discussion is about
> bower, and definitely not about npm or the node.js programming language.
>> 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.
> Thanks to packagers working with OpenStack we are able to get newer
> versions of the components we need once we have pinned them in our code.
>> 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.
> It's entirely up to us to specify a pinned set of component versions that
> we need, which we then need the system packagers to ensure are available as
> deb or rpm. Gaps will be filled as part of the usual packaging efforts that
> go on during the OpenStack release cycle.
>      Richard
> __________________________________________________________________________
> 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/eef7c967/attachment.html>

More information about the OpenStack-dev mailing list