So, why should we then include blueprint at _all_, if we don't use any of it? We don't bundle software from others just because we can. We did include it since the admin used it and we thought that this was something that could benefit theme developers. If the decision now (made by who?) is that we won't use Blueprint, I can't find a single reason why we should bundle it _at all_.
Can someone please clarify my confusion? From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Heilemann Sent: 27. august 2008 22:21 To: [email protected] Subject: [habari-dev] Re: Vote: Blueprint Inclusion +0 I don't find it particularly interesting for me personally. For the admin, it's really only the baselining, which we can do for ourselves (and currently it's applying some styling that's got to go, so I'll look into that in the near future). -- Michael Heilemann http://binarybonsai.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
