I guess it depends on what you mean by work. I'd like to be able to use
existing components like grid and have them display like a Bootstrap table
instead of Tapestry table. In my first attempt I wrote bsGrid, bsBeanEdit
etc but after a few of them it seemed like the wrong direction. In the
second version I use a visitor to modify the DOM output of existing
components. I also played with subclassing the components and providing a
different template. All three have drawbacks but at least modifying the DOM
does not require understanding how the component works. 

So ideally you just add bootstrap to your pom file and your done.
Realistically you'll need to modify your layout.tml unless you already have
something as simple as

    <body>
    <div class="container">
      <t:body/>
    </div>
    </body>

Currently I'm working on two new sites and one existing one. The new ones
are easy and the existing one worked pretty well after just changing the
layout.

I can understand not wanting to modify the existing components by default.
Unfortunately you can't really mix the Tapestry CSS and the Bootstrap CSS. I
suspect this is true of any framework type CSS.  They just fight with each
other consequently I think you are stuck with the all or nothing approach.
If you have other ideas I'd be happy to hear them.

As far as removing the got5-jQuery requirement I'm on the fence. While
Bootstrap will work without jQuery important things like dropdown menus
don't work without it. So again realistically I think you may be stuck with
the all or nothing approach. I have tried to make sure it will work with
both Prototype and jQuery so you don't have to throw out any Prototype code.

As far as the download I was thinking about Less but now that they have the
zip download I think I'm going to support that. I'll provide a default but
the idea is you just download the zip file and drop it in your project. You
don't even unzip it. You could also use Less if you like.

So the simple answer is I'd like it to just work but realistically you will
need a new Layout.tml.

While I've had issues (I'm looking at you @SupportsInformalParameters) the
fact that you can replace the entire presentation framework and only have to
change the Layout.tml really shows the flexibility of Tapestry.



--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Got5-Jquery-compatibility-with-Grid-and-BeanEditForm-Tapestry-Bootstrap-tp5584806p5587937.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

Reply via email to