Hi Andrew,
On 22/01/14 15:24, Andrew Petro wrote:
AC> Finally my thoughts in this area lead me to think about a custom
window state like the windows 8 tile.
All that said, I think maybe part of the message of Responsive is that
UIs that respond to their window (or portlet container!) sizes are the
evolution beyond the blunt instrument of telling a portlet how big it is
with its window state. We may not need NORMAL, MAXIMIZED, and TILE
window states (or, at least, can use the very same view implementations
to handle all those) if the portlet UI automagically arranges and styles
itself for the container size it finds itself rendered in.
I agree that we need to get the responsive containers stuff working.
I think that the future of "window states" revolves around the "window
type" that content is going into, not its size.
So a NORMAL window state will require a portlet to wrap all its output
in container with a .portlet class.
A "REGION" window state will require a portlet to abide by rule 3 set
out in https://wiki.jasig.org/display/UPC/Respondr+Regions+Feature
A "TILE" window state might limit a portlet to only outputting a
<section> containing a single <h1> tag and background colour/image.
My other point is that a "dumb" launcher favorite link does not leverage
the unique capabilities of java portlet technology.
-- Anthony.
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
