--
Message: 1
Date: Fri, 25 Aug 2006 22:05:21 +0300
From: Janne Hietam?ki [EMAIL PROTECTED]
Subject: Re: [Wicket-user] Applying Style Sheets to Wicket Portlet
Components?
To: wicket-user@lists.sourceforge.net
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
On 25.8.2006, at 8.17, David Russell wrote:
Hi,
I am currently trying to build some Wicket based Portlets. The sample
portlet provided works great. Now I'm trying to convert the sample
TabbedPanel application found in wicket.example.compref into a
PortletApplication.
So far the tabbed page mechanism is working in my portlet, however, I
can not see how to pick up the style sheets effects on the tabs within
the portlet.
The html template page for the TabbedPanel WebApplication includes the
following markup:
head
link rel=stylesheet type=text/css href=style.css /
/head
As it is not permitted to include head information in the html
template page for a portlet I can not see how I can associate
style.css
with my portlet html template page.
Can anyone explain how to apply stylesheets to Wicket portlets?
Thank you for your help,
David
Hi,
I haven't really tested it, but stripping away the head-tags should
work (even if it is against the html spec), and use the bare link tag
in the beginning of the PortletPage html. Another way is to stick the
css inline into the html code.
I'm going to do a automated way to do this, so components having
header contributions really work automagically, but that is a work in
progress and I'm going to do it next week.
Janne
Hi Janne,
I had tried using the bare link tag (having stripped out head/) but
the style sheet effects were not applied as hoped.
Your auto-magic solution for portlets would be great, it would be nice
to be able to use the same html markup for both WebPage and PortletPage.
This is what you have in mind I assume?
I've also been experimenting with a number of other Wicket components in
my portlets. I can not get any of the Javascript dependent components to
work in my portlets, such as the DatePicker extension for example. Have
you tried and verified these work yourself? Perhaps there are known
limitations in the current implementation that would cause such problems?
I know Wicket support for portlets is new so teething problems are to be
expected. Currently I'm trying to evaluate if Wicket based portlets are
feasible for a large development project. If what was available to
Wicket Web applications was available to Wicket Portlet applications I'd
be very happy. That does not seem to be the case today. It would be a
great help to me if you could provide any details on what portlet
support works now, perhaps more importantly what does not yet work and
finally what new support coming in the near future.
Thanks,
David
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
