Hi guys, I'm planning to use bootstrap in a project using Wicket and I also think that https://github.com/l0rdn1kk0n/wicket-bootstrap requires some work before to be adopted. I outlined some thoughts about how it can be improved at https://github.com/l0rdn1kk0n/wicket-bootstrap/issues and would value your input on the matter.
Cheers, Pedro Santos 2012/5/29 Martin Grigorov <[email protected]> > On Tue, May 29, 2012 at 3:40 PM, Martijn Dashorst > <[email protected]> wrote: > > On Tue, May 29, 2012 at 2:24 PM, Martin Grigorov <[email protected]> > wrote: > >>> - [...] should we provide a development mode integration with wro4j > >>> for less css? (I'd suggest using the maven plugin for deployment) > >> > >> what do you mean by "development mode integration" ? > >> the maven plugin compiles from less to css at build time and at > >> runtime you just refer to the css files > > > > Having a Wicket resource loader that integrates wro4j sounds more > > Wicket-y rather than depend on a maven plugin to run side-by-side. I > > haven't used wro4j myself, so I might be off base, but I figure that > > running Wicket in development mode, and having a Wicket resource > > loader that recompiles on changes and adjusts headers/caching etc > > accordingly gives us more control. As I hear that wro4j is quite slow, > > this wouldn't be my deployment mode of operation, but I can imagine > > that people also want to deploy with a Wicket wro4j resource loader. > > I see. > This will work. > Wro4J uses Rhino, that's why it is slow and memory consuming. > > > > > Martijn > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com >
