← Back to team overview

launchpad-dev team mailing list archive

Re: Third party JavaScript parts + skinning

 

Hi, Robert.

On Sun, Feb 13, 2011 at 1:48 PM, Robert Collins
<robertc@xxxxxxxxxxxxxxxxx> wrote:
> On Mon, Feb 14, 2011 at 8:00 AM, Paul Hummer <paul.hummer@xxxxxxxxxxxxx> wrote:
>> I would also agree.  In fact, we already have some gallery code in lazr-js.
>>
>> However, in the next month or so, I have time scheduled to take all the
>> eggifying parts of lazr-js out, and make it strictly a javascript
>> library (all other parts will become their own projects).
>
> This sounds horrifyingly disruptive; please consider moving the
> javascript elsewhere, rather than moving the python widgets etc
> elsewhere. We're patching this library every few days at the moment,
> and the last thing we need is the sort of multi-day rework that occurs
> with this sort of change.
>

There are no python widgets in lazr-js.  There is javascript, css, and
what amounts to Python build tools that we use in Launchpad, not
lazr-js.  These are the Python tools we use for jslint, combing css,
etc.  I'm coordinating with Paul on these changes, and when they land
in lazr-js, I'll update Launchpad's js and css build tools to use the
new Python modules.  This amounts to adding tarballs to
download-cache, updating versions.cfg, and changing Python paths in a
few buildout templates.  Easy, peasy, and done quickly.  I can't see
how this will be very disruptive at all.

Cheers,
deryck


-- 
Deryck Hodge
https://launchpad.net/~deryck
http://www.devurandom.org/



References