On Tue, Sep 9, 2008 at 3:02 AM, CodeOfficer <[EMAIL PROTECTED]> wrote:
>
> Now that the project is under new management, ay thoughts on which
> direction you guys might want to take it? I saw it going more of a
> plugin route at one time. Just curious :)
>
I'm with you on the "plugin" thing. To me, blueprint is, first and
foremost, an easy-to-use grid system for laying out a website. Secondary to
that is the way it changes the default HTML.
My suggestion is to break blueprint into something more like a framework +
microformat architecture:
--standard blueprint--
1. reset
2. grid
3. default text look/feel
Then make the plug ins more like microformats:
1. Tables
2. calendars
3. forms
4. buttons
5. etc, etc etc
For example, let's say I'm putting together a site that has a calendar on a
page.
1. I would need the "base package" - reset, grid, and basic text to start.
2. I'd want a calendar microformatting plugin:
a. allows for large and small calendars.
b. there would be some specific guidelines for creating the
calendar(s) (i.e. table has a certain classname, should have a caption,
thead, tbody, and tfoot, etc)
Taking into consideration the success of the YUI, I think that creating a
standard set of class names and encouraging microformatting will help keep
blueprint in the forefront for developers.
My 2.5 cents....
Jon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Blueprint CSS" group.
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/blueprintcss?hl=en
-~----------~----~----~----~------~----~------~--~---
