Chris Meller wrote:
> I don't think it was originally added just because the admin used it, 
> but so that you wouldn't have 10 different themes including their own 
> copies of a popular library. Personally I still think this is a good 
> goal. Keeping blueprint doesn't significantly increase our footprint, 
> and it has the potential to significantly decrease the footprint any 
> given installation could have.
> 
> In other words: it isn't hurting anything, leave it alone.

That's usually my stance on things, and on the issue of BP in this case 
I'm ambivalent.

I simply wanted to point out that most of these libraries are available 
directly via Google Code now, which works as a kind of CDN that Google 
even seems to encourage.  So if we decided to remove BP from our 
distribution, we could simply point the mzingi CSS link to GCode's copy 
and that would be that.

YUI can be used similarly.  I haven't looked, but I imagine that 960 can 
probably do the same.

Owen

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to