AP> Minimized window state will have a styled infocard-like
representation. Title, first bit of the description, icon. Enough
to evoke what it is so you can decide to open it.

AC> Will this be actually rendered portlets or just skin trickery from
marketplace registry?

Likely just theme trickery initially, though selectively growing into portlets 
with interesting minimized window state would be an interesting direction for 
eventual future improvement.

Currently few (none?) portlets are prepared to handle MINIMIZED window state 
appropriately, a lot of them appear to have an interceptor that short-circuit 
no-ops MINIMIZED handling, and anyway I'm pretty sure the theme doesn't even 
give them the chance to render.

Using theme trickery can probably be *very fast* without having to wait for 
portlets to render dynamic minimized window states.  Getting to something that 
renders *very fast* and then circling back and soberly adding features later is 
attractive.  A mobile-first product is first and foremost a product that 
*renders fast*.

Using theme trickery is also an opportunity to make them appear uniform, like 
they're designed to look good and go together in that MINIMIZED form factor.  
Allowing the portlet to render, without taking the time to make sure that what 
the portlet renders works well in this way, is an opportunity to have an ugly, 
slow, unusable home page within the portal.


On 8/7/14, 5:50 PM, "Anthony Colebourne" 
<[email protected]<mailto:[email protected]>>
 wrote:

Andrew,

Thank you for being so open, the community is so much richer for it.

My opinions inline...

On 07/08/14 20:29, Andrew Petro wrote:
   * *Collections of Favorites are gone*, at least for now.  [1]

This is devastating news :-(

   * User-selected *Normal Window State portlets living on the landing
     tab are back in*.  This means that Maximized isn't the only way to
     get at user-selected stuff; portlets are sometimes in Normal Window
     State rather than only Maximized.

Woo Hoo!

   * Favoriting a portlet and adding it to one's Welcome page (the only
     page of multiple portlets) is exactly the same thing. *So, you
     favorite a portlet, and that adds it in Minimized window state right
     on your home screen. * You might then expand it to Normal window
     state, and that expansion will be remembered.

Love the use of minimized window state.

   * *Minimized window state will have a styled infocard-like
     representation.*  Title, first bit of the description, icon.  Enough
     to evoke what it is so you can decide to open it.

Will this be actually rendered portets or just skin trickery from
marketplace registry? I hope its the former, portelts have a lot to
offer. Perhaps it could source and aggregate some marketplace content
too via an API.

   * User *re-ordering of the portlets in the home screen will be
     disabled* to reduce technical risk and support burden.
       Drag-and-drop as trip hazard.  This feature probably comes back in
     on some subsequent release.

Trip hazard?

   * *Search is de-scoped to only search MyUW content*, and we're
     dropping the whole search Portlet Event thing.  No search of dynamic
     content, just search over descriptions and other static portlet
     publication metadata. *This will make search radically faster.*  It
     also probably makes search implementation radically different in
     that, at least for the near term in redesigned MyUW, *Search is just
     another view on Marketplace*.  It's entirely feasible to load the
     entire (filtered-for-the-user) portlet metadata registry down into
     the browser and perform all the search operations client-side.  This
     will make search radically faster.

Couldn't a hybrid solution be found? I believe autocomplete has already
gone this way. Perhaps the initial render can be followed by ajax
loading->loaded content search? (infinite scroller?)

I see personalized federated search as a big selling point of uPortal.
There must be ways we can make this performant (or at least appear so).

We've spoken in the past about including a crawler, I feel there may be
something in this.

Also we spoke about the difficulties of personalized search in the
absence of a PortletRequest :-( .... perhaps ajax is our friend? simple
but effective.


-- Anthony.

--
You are currently subscribed to 
[email protected]<mailto:[email protected]> as: 
[email protected]<mailto:[email protected]>
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


-- 
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

Reply via email to