Thanks Barry - I'll be checking it out over the weekend and not a quarter past 
one in the morning :)
Cheers

On 09/02/2012, at 12:42 AM, Barry Books wrote:

> Some background
> 
> There was a post on this list about converting the Tapestry example to
> use Twitter Bootstrap. I had never heard of the project so I looked
> and discovered it's basically a grid based CSS layout system created
> by Twitter and there are a number of other grid based CSS systems out
> there.
> 
> The basic idea is you mark your elements with class names that
> describe where in the grid the element goes. Many of the grid systems
> (including Bootstrap) are responsive. This means the layout can change
> based on the device so the same page can work well on desktop, tablet
> and phone. These CSS frameworks also have a complete set of CSS that
> result in a reasonably styled page. Bootstrap uses Less to generate
> the CSS.
> 
> The common theme is you have some markup structure, CSS and sometimes
> javascript to create common elements such as buttons and navigation.
> 
> Bootstrap seemed like a good way to build prototypes and simple
> websites that did not look like they were designed by a programmer. At
> the time Bootstrap was 1.x and I developed some components that used
> it. When the Bootstrap developers created a 2.x branch they started
> over. Of course the 2.0 version is better but not backward compatible.
> That branch was released a few days ago. I wanted to release about the
> same time hence the early alpha designation.
> 
> So what is/was Tapestry-Bootstrap?
> 
> The original idea was to create a set of components that could be used
> along with the Twitter Bootstrap framework. The 2.0 version of Twitter
> Bootstrap has caused me to rethink that idea and the new vision is a
> framework for transforming the look and feel of existing components by
> adapting their output to various HTML frameworks. Currently I'm only
> interested in the Twitter Bootstrap but It because obvious a flexible
> architecture needed to track changes and support existing components
> without rewriting much code.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to