Not yet baked for a pull request, but work-in-progress adding a JSON web
service exposing (appropriate portions of) Marketplace data.
Code:
http://goo.gl/a0GvCO
Kicking out JSON something like this:
https://gist.github.com/apetro/11203163
Jackson is pretty cool.
Andrew
On 4/21/14, 8:01 AM, Andrew Petro wrote:
This MyUW development sprint (ending this Friday) includes stories
about implementing not-logged-in potentially-Google-indexable views on
the Marketplace portlet data.
This may be an opportunity to address some of this, since will need a
solution that doesn't rely on portlet preferences when rendering
outside the context of a portlet.
Figure it's a great idea to let everyone know what's in flight as we
focus towards a 4.1 release...
Andrew
On 4/18/14, 12:27 PM, James Wennmacher wrote:
This sounds reasonable to me.
James Wennmacher - Unicon
480.558.2420
On 04/17/2014 06:46 PM, Andrew Petro wrote:
I agree we need to do something to hide some portlet marketplace
entries from non-admins.
I really like the idea of inventing a VIEW_MARKETPLACE_ENTRY
permission activity that one can be granted targeting portlets (or
portlet categories, of course), requiring VIEW_MARKETPLACE_ENTRY or
MANAGE permission to see an entry for any given portlet in the
marketplace.
And then the business rule of non-portal-administrators do not see
non-categorized portlets could be easily expressed as granting
VIEW_MARKETPLACE_ENTRY on all categories of portlets. If a portlet
is in a category, user would have the permission on it. If it isn't
in any category, wouldn't. And then adopters can go forth nuancing
the experience via permissions -- we think we have requirements here
where users will have permission to see marketplace entries for some
portlets they can't actually subscribe or render, and we definitely
have requirements for users to be able to render some
infrastructural portlets that they don't need to be bothering with
in the Marketplace.
Captured some of these thoughts here:
https://wiki.jasig.org/display/UPC/Marketplace?focusedCommentId=67371619#comment-67371619
I'm thinking of this kind of fix as a "bugfix" that we could accept
in the RC march to uPortal 4.1. So, like, polish up Favorites and
Marketplace and dynamic skin to work well, but too late to bring in
my glorious to do list portlet [1] or other new functionality for
uPortal 4.1.
Andrew
[1]: That's kind of an inside joke. I don't actually have a
glorious to do list portlet. But what I mean to evoke by this is,
no new features! :)
On 4/17/14, 5:50 PM, Drew Wills wrote:
I'm looking at the Portlet Marketplace in a local dev environment
today, now that it's in the master branch -- nice work!
One item of feedback: I think it really should honor the feature
whereby non-categorized portlets are hidden from browsing and
direct access.
drew
--
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
