Chris J. Davis wrote: > > I am firmly -1 for removing blueprint unless a solid technical reason > is offered up.
I guess the reasons both ways should be written out: PROS ---- * Offers an unambiguous library that theme developers can be certain exists in Habari upon which they can build. * Adds negligible amount to Habari's footprint. * An external reference would require an internet connection to work properly. * Google (or whoever hosts the alternate external) would be able to track hits via referrer. CONS ---- * Adds negligible amount to Habari's footprint. * Needs to be manually updated, since updates are not available via SVN any more. (This is true, right?) * When Blueprint is updated in Habari core, themes that use it will need to update or potentially become broken. * Puts the "weight" of CSS load on an external server, potentially speeding up site delivery. * May imply some support is provided by Habari for Blueprint. Feel free to add to either column. Also, please don't take this as me deciding about keeping Blueprint. As I said before, I'm ambivalent to the extent that it continues to fail to affect me. :) 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 -~----------~----~----~----~------~----~------~--~---
