The core Wicket Bootstrap currently just provides the bootstrap
artifacts. And for the foreseeable future, I don't expect it to go
beyond that too much.
I still am on the fence on:
- whether a Bootstrap component library should be part of Wicket
- whether l0rdn1kk0n's implementation is the way to go
If you need a component library now, you should really use
l0rdn1kk0n's implementation. Currently that project has the freedom to
move at a different pace than Wicket, so that is a benefit. If/whether
that ends up at Apache is unknown.
At €-dayjob we are starting to develop Bootstrap applications and we
are experimenting with building our own component libraries. If they
end up looking like l0rdn1kk0n's bootstrap implementation, we'll
gladly move to that project, and start advocating its adoption as a
wicket core project, or start pointing folks at that particular
implementation.
For now, Wicket's bootstrap is just there to support the new examples
and might be folded into them. I think the wicket examples are a
special case that usually don't have the same requirements for
components as your typical 'enterprise' application, and wouldn't
benefit of l0rdn1kk0n's implementation.
Martijn
On Sun, Oct 21, 2012 at 2:43 AM, Chris Colman
<chr...@stepaheadsoftware.com> wrote:
> We've ported our app to Wicket 6.2 and are now looking to start using
> Twitter Bootstrap.
>
> Is this a correct summary of the current state Twitter Bootstrap support
> in Wicket?
>
> 1. The Wicket experimental does not provide any component
> implementations. It merely provides a class for convenient inclusion of
> the appropriate CSS + JS resources required for Twitter Bootstrap to
> work via doing this in any page class that requires it:
> @Override
> public void renderHead(IHeaderResponse response) {
> super.renderHead(response);
>
> Bootstrap.renderHead(response);
> }
>
> 2. The l0rdn1kk0n Wicket-Bootstrap project (pity about the weird
> name!) has a few Wicket components specialized for Twitter Bootstrap use
> and includes support for some free Bootstrap schemes.
>
> Some questions:
>
> How far off before Wicket bootstrap experimental gets some native wicket
> components?
> Could Wicket bootstrap experimental integrate the work of the
> l0rdn1kk0n, bringing in some of it's components to leverage of existing
> work by that project?
> Will Wicket bootstrap experimental be so radically different to the
> l0rdn1kk0n that porting to Wicket bootstrap experimental will be a
> bothersome task when it's ready?
>
> Chris Colman
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
