Yes, all of this.
I agree the in-situ privileged user edit-configuration use case is
compelling.
I agree that there's an implementation detail wherein that CONFIG mode
is going to have to actually write back to the portlet definition record
-- and I kind of hope portlets *can't* just arbitrarily do that
currently, that they need some framework help. But I haven't looked in
any depth at how current CONFIG mode implementation actually works.
Sounds like yet another fine thing to look at together @ Camp next week. :)
Eric, you should so come. You know, when you shake free from skiing.
Andrew
On 1/24/14, 10:50 AM, Drew Wills wrote:
Thanks for chiming in.
On 01/24/2014 09:44 AM, Eric Dalquist wrote:
Normal users can never use CONFIG. It is only usable by portal admins
and requires specific permissions to even work for a user. Beyond that,
a portlet might be able to just set CONFIG as the mode on a URL. I never
actually tried that.
Within the Portlet Manager, I know that the things that get
entered/created in CONFIG mode can become a part of the
portlet-definition record -- e.g. text entered in the WYSIWYG editor
for SimpleCMS.
That integration would still need to work. This example is actually
one of the more compelling imho -- allow privilaged users to edit the
content of a SimpleCMS portlet "in situ" (without going through the
Portlet Manager).
drew
--
You are currently subscribed to uportal-dev@lists.ja-sig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
