Hi,
if you have to to exclude the bootstrap.css but still want to include the
tree.css, tapestry.css, exception-frame.css and tapestry-console.css i
found an easy solutation that i wanted to share:
// fixing default bootstrap include
@Contribute(JavaScriptStack.class)
@Core
public static void
set
Hi,
you can disable the auto-include of the core stack when you add this to
your AppModule:
public void
contributeMarkupRenderer(OrderedConfiguration
configuration) {
configuration.override("ImportCoreStack", null);
}
then you can add the core stack individually as needed with
@Import(stack="c
On Tue, 08 Oct 2013 23:05:42 -0300, Thiago H de Paula Figueiredo
wrote:
On Tue, 08 Oct 2013 22:21:12 -0300, Barry Books wrote:
I was not a big fan of auto including the core stuff.
Me neither. I think it can be easily disabled by overriding the
"ImportCoreStack" MarkupWriterListener co
On Tue, 08 Oct 2013 22:21:12 -0300, Barry Books wrote:
I was not a big fan of auto including the core stuff.
Me neither. I think it can be easily disabled by overriding the
"ImportCoreStack" MarkupWriterListener contribution to the MarkupRender
service to a dummy implementation. Another o
Problem is you can't get around it really.
Once you start using components such as alert, tree, etc. core can't be omitted,
so not including core won't work in the long term.
On Oct 8, 2013, at 9:21 PM, Barry Books wrote:
> I was not a big fan of auto including the core stuff.
>
>
> On Tue,
I was not a big fan of auto including the core stuff.
On Tue, Oct 8, 2013 at 8:14 PM, Lenny Primak wrote:
> Hence my post :) Every one of these methods is very hack-ish.
> There should be an 'official' ability for Tapestry to do this.
>
> Another JIRA?
>
> On Oct 8, 2013, at 9:11 PM, Barry Boo
Hence my post :) Every one of these methods is very hack-ish.
There should be an 'official' ability for Tapestry to do this.
Another JIRA?
On Oct 8, 2013, at 9:11 PM, Barry Books wrote:
> I think I'm using the version before it was adding automatically. But I
> think you can do what you said (h
I think I'm using the version before it was adding automatically. But I
think you can do what you said (hopefully)
On Tue, Oct 8, 2013 at 8:09 PM, Lenny Primak wrote:
> Yes, but how did you remove the reference to bootstrap.css form the old
> layout?
> Or did you override Tapestry bootstrap loc
Yes, but how did you remove the reference to bootstrap.css form the old layout?
Or did you override Tapestry bootstrap location and import bootstrap from
the new location in the new layout yourself?
On Oct 8, 2013, at 9:06 PM, Barry Books wrote:
> I created a new layout component for bootstrap pa
I created a new layout component for bootstrap pages and left the old one
for old style pages.
On Tue, Oct 8, 2013 at 7:41 PM, Lenny Primak wrote:
> I am upgrading a site to T5.4. The plan is to have 'old' layout for old
> pages and 'new' bootstrap-based
> layout for new pages. For old pages,
I am upgrading a site to T5.4. The plan is to have 'old' layout for old pages
and 'new' bootstrap-based
layout for new pages. For old pages, I would just like to disable bootstrap
loading completely, and internally
substitute it with our old CSS. This doesn't solve beaneditor layout problem,
11 matches
Mail list logo
