I agree that it's useful on its own, but with the current design that the admin has not much of it is used at all. I do not see the point in including a framework we don't utilize. The decision to _not_ use it in the admin is something completely different though, and it's not what is being discussed.
With the current state of Blueprint and it's migration from svn to git, makes things a bit more difficult for us and I don't see why we should include it if we don't use most of its features or plan to do so. It's relatively easy for theme developers to update their themes to include BP if they chose to use it for layout purposes. Don't get me wrong; I Love blueprint and I've used it in all my theming endeavors lately, so this isn't an argument for or against the framework itself. As far as I'm concerned, bundling BP with Habari is bloat, unless we use it. Christian From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Meller Sent: 27. august 2008 23:59 To: [email protected] Subject: [habari-dev] Re: Vote: Blueprint Inclusion On Wed, Aug 27, 2008 at 4:56 PM, Christian Mohn <[EMAIL PROTECTED]> wrote: 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? The admin *does* use it, and I personally think it should use it more to standardize the way we do layouts. And I still think it will be useful to theme developers. It seems Heilemann is the only one who doesn't like / doesn't see the point of BP. That, in itself, does not constitute a decision to not use it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
