I like the callback solution. Requires Tapestry support though :) That wil serve my needs at least (BeanEditor that looks like the 'old' 5.3 BeanEditor :)
On Oct 16, 2013, at 7:30 AM, mailingl...@j-b-s.de wrote: > Hi, > > just my two cents: In general coupling bean editor (and friends) tightly to > bootstrap is strange even I am aware its the de facto standard. Furthermore I > can not believe it will ever produce a layout which makes all of us happy. Is > it not possible to add a additional, optional parameter to support "row > building" or "field grouping" (eg List of List of field names forming > rows/groups) and retrieve/provide css for each field and row/group by > callbacks? Means: by default Tapestry does not care about rows/groups and may > solely set col-xyz-whatever on each field's class to provide a default > responsive layout. Nevertheless by a callback solution its now possible to > easily override "that default css" for a group/row or even individual field. > Due to the fact everything is optional it won't break old code, too. > I can not see how a mixin is able to easily modify css across elements > without any structural hint (rows/groups), but correct me if I am wrong. > > > Jens > > > > Von meinem iPhone gesendet > >> Am 15.10.2013 um 12:46 schrieb Barry Books <trs...@gmail.com>: >> >> If you are building sites that work on mobile the default is correct. If >> you are starting from scratch it's OK also but converting an existing site >> can be a problem. I do have one non mobile site I'm converting so I looked >> at my old 2.3 mixin and the at the example >> >> http://getbootstrap.com/css/#forms-horizontal >> >> I'm not really sure how to support this because each property can have >> different col settings. My first thought is the mixin needs a map of >> propertyName/columnWidth. It might be possible to do this with the message >> catalogue also. >> >> >> On Mon, Oct 14, 2013 at 9:43 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: >> >>> I know of its existence but didn't really use it. I can do it with a >>> visitor, but >>> all of these approaches are clunky. It should be implemented in Tapestry >>> itself. >>> >>> I really don't understand why Bootstrap people didn't make horizontal form >>> the default. >>> I guess because it's harder to get right :) >>> >>>>> On Oct 14, 2013, at 10:28 PM, Thiago H de Paula Figueiredo wrote: >>>>> >>>>> On Mon, 14 Oct 2013 22:29:57 -0300, Lenny Primak <lpri...@hope.nyc.ny.us> >>>> wrote: >>>> >>>>> I have tried to implement this using a mixin, but it gets too >>> complicated for my taste. >>>>> >>>>> The problem is that the each label and component has to be surrounded >>> with <div class='col-md-XX'> (for example) >>>>> which requires really digging around elements with MarkupWriter (error >>> prone) >>>> >>>> Have you checked Tapestry-XPath? It helps so much in finding elements >>> which I think it could be part of Tapestry-core itself. >>>> >>>> -- >>>> Thiago H. de Paula Figueiredo >>>> Tapestry, Java and Hibernate consultant and developer >>>> http://machina.com.br >>>> >>>> --------------------------------------------------------------------- >>>> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
