[Building Sakai] Wicket, Portlets and JSR-168

[Matthew Jones]

Yea, I don't think that staying current is non trivial either,since there
aren't many people in the Sakai community are familiar with wicket either.
I'd hope it's easier than upgrading JSF 1.x to JSF 2 though (even JSF 1.1
to 1.2 is seeming like a huge task). There are just those 2 wicket tools in
core, though delegated access and dashboard are two big tools in contrib.

Though with delegated access being an admin only tool isn't as big a deal
for portlet support, but it seems like we'd want to have something in place
for dashboard and profile2 on mobile. Though if mobile view was the
specific goal, avoiding wicket all together and making a simplified UI
using a different framework or client side render for mobile using direct
might take less time than wicket portlets.


On Mon, Dec 16, 2013 at 1:46 PM, Charles Severance <csev at umich.edu> wrote:

> Thanks Matt and Steve - seems like a non-starter.    But one can dream :)
>
> It is probably more important to stay current than to have portlet support.
>
> /Chuck
>
> On Dec 15, 2013, at 5:57 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> > I was working on the Wicket portlet support a while back but it was far
> too incomplete and unusable, and was dropped (as Matt said). It would be
> interesting to see where this goes for Wicket 6. The current Wicket tools
> should be upgraded to Wicket 6 at some stage. I would not recommend binding
> tools to an older (and unsupported) version of any library, but rather have
> time spent in improving the support going forward if we are interested in
> it.
> >
> > cheers,
> > Steve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131216/f5380dd9/attachment.html