Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
I have not tried it on 5.4 but I will in a week or two. The only problem I see is it's dependent on the html output of the base components. If that does not change then I suspect it will work without much difficulty. As far as the Javascript part goes Bootstrap uses jquery and my module brings in got5-jquery. With 5.4 this may not be needed. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Announce-Tapestry-Bootstrap-2-0-early-Alpha-tp5718845p5718849.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[Announce] Tapestry-Bootstrap 2.0 early Alpha
Hi all! Is this great tapestry-bootstrap module ready for 5.4? Or is it a full-stack replacement for 5.3 like got5-jquery is for jquery? Regards! Matias.
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
I'll take a look. I've been working on iPhone apps for the past few weeks. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Announce-Tapestry-Bootstrap-2-0-early-Alpha-tp5462931p5714379.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
Also there is one pretty serious issue still open. Thanks Barry! On Jul 9, 2012, at 12:07 PM, Alex Kotchnev wrote: > Barry - this is pretty cool. I hadn't seen your module and just ended up > adding the bootstrap related assets into the layout, but I see that you've > added a whole lot of useful components and stuff. > > Does it seem like the project is stable enough to produce a stable release > soon (e.g. in the next few months) ? > > Cheers, > > Alex K > > On Thu, Feb 9, 2012 at 1:27 AM, David Woods wrote: > >> Great work. I'm really looking forward to trying this out. Twitter >> Bootstrap makes great looking sites easy, it will be great to team them up >> with the back-end functionality of tapestry. >> >> On 9 February 2012 01:15, Chris Mylonas wrote: >> >>> 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 >>> >>> >> - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
Barry - this is pretty cool. I hadn't seen your module and just ended up adding the bootstrap related assets into the layout, but I see that you've added a whole lot of useful components and stuff. Does it seem like the project is stable enough to produce a stable release soon (e.g. in the next few months) ? Cheers, Alex K On Thu, Feb 9, 2012 at 1:27 AM, David Woods wrote: > Great work. I'm really looking forward to trying this out. Twitter > Bootstrap makes great looking sites easy, it will be great to team them up > with the back-end functionality of tapestry. > > On 9 February 2012 01:15, Chris Mylonas wrote: > > > 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 > > > > >
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
Great work. I'm really looking forward to trying this out. Twitter Bootstrap makes great looking sites easy, it will be great to team them up with the back-end functionality of tapestry. On 9 February 2012 01:15, Chris Mylonas wrote: > 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 > >
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
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
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
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
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
In relation, this is built with bootstrap - https://gemnasium.com/ It's a gem version thingy for ruby on rails. I guess a gem would be like a tapestry 3rd party module. I recall reading that "this sort of thing for tapestry modules" would be a good idea. Granted RoR has a larger following than tapestry - note the business-model/pricing. Maybe something like this for the whole maven repo would be handy :) Is there a quick way to test what this module is about? I didn't notice a readme.txt in the github repo. Cheers On 08/02/2012, at 9:56 PM, trsvax wrote: > Thanks Steve, > > It was tough throwing out the old version and starting over but I think this > way is much better. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Announce-Tapestry-Bootstrap-2-0-early-Alpha-tp5462931p5466207.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > - > 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
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
Thanks Steve, It was tough throwing out the old version and starting over but I think this way is much better. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Announce-Tapestry-Bootstrap-2-0-early-Alpha-tp5462931p5466207.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
Hi Barry, That's a really neat idea - I love the idea of wrapping the elements and visiting them afterwards! Invisible instrumentation for T5! I've looked at altering components in the past and stumbled over the same sticking point. Awesome solution, Steve. -- Steve Eynon --- "If at first you don't succeed, so much for skydiving!" On 7 February 2012 20:24, Ulrich Stärk wrote: > A short introduction about what Tapestry Bootstrap is about would have been > nice for those that > don't know Bootstrap ;) > > Uli > > On 07.02.2012 13:04, Barry Books wrote: >> I've committed version 2.0 of Tapestry Bootstrap to Github. >> >> https://github.com/trsvax/tapestry-bootstrap >> >> This version supports Twitter Bootstrap version 2.0 >> >> http://twitter.github.com/bootstrap/index.html >> >> This is a complete rewrite of the first version and is very early >> Alpha.The first version required rewriting some components to create >> the HTML structure required by the Bootstrap CSS. After a while this >> seemed like a very bad path to head down so I started over. >> >> This version takes a broader scope. The idea is to support any >> existing components and allow multiple CSS frameworks to exist at the >> same time. To accomplish this there is one mixin called FW (framework) >> that is added to every component via a Worker. This mixin just adds an >> element around the body of its component. After the page is rendered a >> Visitor finds these elements and rewrites the HTML to the supported >> framework if needed. The Visitors are pluggable. This allows the tml >> to contain something like: >> >> >> >> ComboButtons >> Form >> NavBar >> Table >> >> >> >> >> >> >> instead of >> >> >> >> >> >> >> Home >> >> Link >> Link >> >> >> >> >> >> because the Visitor adds all the extra elements required by the framework. >> >> To use the existing Grid component just include the type: >> >> >> >> In this case the Visitor converts the HTML output by Grid into the >> structure needed by Bootstrap. >> >> I've got 2 projects currently using the framework so I'll be flushing >> out the other components soon. >> >> To run the samples >> >> mvn jetty:run >> >> Thanks >> Barry >> >> - >> 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 > - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [Announce] Tapestry-Bootstrap 2.0 early Alpha
A short introduction about what Tapestry Bootstrap is about would have been nice for those that don't know Bootstrap ;) Uli On 07.02.2012 13:04, Barry Books wrote: > I've committed version 2.0 of Tapestry Bootstrap to Github. > > https://github.com/trsvax/tapestry-bootstrap > > This version supports Twitter Bootstrap version 2.0 > > http://twitter.github.com/bootstrap/index.html > > This is a complete rewrite of the first version and is very early > Alpha.The first version required rewriting some components to create > the HTML structure required by the Bootstrap CSS. After a while this > seemed like a very bad path to head down so I started over. > > This version takes a broader scope. The idea is to support any > existing components and allow multiple CSS frameworks to exist at the > same time. To accomplish this there is one mixin called FW (framework) > that is added to every component via a Worker. This mixin just adds an > element around the body of its component. After the page is rendered a > Visitor finds these elements and rewrites the HTML to the supported > framework if needed. The Visitors are pluggable. This allows the tml > to contain something like: > > > > ComboButtons > Form > NavBar > Table > > > > > > > instead of > > > > > > > Home > > Link > Link > > > > > > because the Visitor adds all the extra elements required by the framework. > > To use the existing Grid component just include the type: > > > > In this case the Visitor converts the HTML output by Grid into the > structure needed by Bootstrap. > > I've got 2 projects currently using the framework so I'll be flushing > out the other components soon. > > To run the samples > > mvn jetty:run > > Thanks > Barry > > - > 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
[Announce] Tapestry-Bootstrap 2.0 early Alpha
I've committed version 2.0 of Tapestry Bootstrap to Github. https://github.com/trsvax/tapestry-bootstrap This version supports Twitter Bootstrap version 2.0 http://twitter.github.com/bootstrap/index.html This is a complete rewrite of the first version and is very early Alpha.The first version required rewriting some components to create the HTML structure required by the Bootstrap CSS. After a while this seemed like a very bad path to head down so I started over. This version takes a broader scope. The idea is to support any existing components and allow multiple CSS frameworks to exist at the same time. To accomplish this there is one mixin called FW (framework) that is added to every component via a Worker. This mixin just adds an element around the body of its component. After the page is rendered a Visitor finds these elements and rewrites the HTML to the supported framework if needed. The Visitors are pluggable. This allows the tml to contain something like: ComboButtons Form NavBar Table instead of Home Link Link because the Visitor adds all the extra elements required by the framework. To use the existing Grid component just include the type: In this case the Visitor converts the HTML output by Grid into the structure needed by Bootstrap. I've got 2 projects currently using the framework so I'll be flushing out the other components soon. To run the samples mvn jetty:run Thanks Barry - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
