Convention over configuration is great -- IF it is intuitively obvious,
or well documented and well exposed so people know about it. Otherwise,
it is just more magic ju-ju juice that is confusing as heck for the
newbie. Despite what you might surmise from above, I like convention
over configuration but only if it is done "properly" (a.k.a. not knowing
it doesn't cost me hours of time wondering why something is acting
funky). So my request here, is to make sure the documentation is
clearly updated because I'll never remember this conversation in a month
let alone a year from now. :-)
Regarding the other fragments:
- Authenticated - This just adds the logout and search for an
authenticated user to the header region.
- Resondr vs. NonRespondr - As I recall, this handles the fact that
universality has portlets 'baked' into the theme files, but with
Respondr they are present in the layout as normal portlets instead. We
chose to not change universality at this point because it would be more
difficult for universities that upgrade from 4.0 to 4.1 but stay on
Universality. Not making the change simply meant that you'd get errors
in Respondr in the log saying that the portlets were rendered but not
consumed
I'm not sure what you mean by a meta-fragment. I assume you are
referring to fragments which have content in headers/footers rather than
in content body (e.g tabs)? I don't consider these 'meta' fragments as
special and I'm not sure why they would need to be treated differently.
Please elaborate.
Thanks,
James Wennmacher - Unicon
480.558.2420
On 01/13/2014 09:17 AM, Andrew Petro wrote:
So, the Favorites portlet needs a meta-fragment into which to shove
the user's favorites. The meta-fragment doesn't display as a tab, but
it benefits from all the features of DLM for providing users a default
set of Favorites (not entirely clear that we're actually going to
provide any default favorites here at Wisc, but it's a nice feature
that falls out from using DLM fragments for this.)
I'm attracted to a convention-over-configuration flavored solution of
naming such meta fragments starting with _ and then filtering out such
fragments in non-meta contexts.
I see some other meta-fragments in trunk that I don't yet understand
(Authenticated? Resondr? NonRespondr?). I'll go understand those
better before the end of Favorites, I'm sure.
But: is uPortal already doing something interesting to identify and
filter out meta-fragments? How do others feel about a "meta fragments
start with underscores" approach to make this more convention-driven?
Andrew
--
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
