Taglibs and so forth

[Cantor, Scott]

On 5/12/14, 5:46 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>I'm pretty convinced that getting the jsp taglibs ported over (and hence
>the
>support current login page) is going to be relatively easy and so I'll
>plan
>to get it done for the Alpha.

I figured. I seem to recall we needed to tweak something in the language
handling, I think we didn't include a built-in setting for default
language(s) to use if the browser doesn't supply any matching one.

>FWIW, I have not looked closely at velocity rendering but I'm wondering
>whether the easy way to provide the power to the end user is to create a
>UIContext and add that to the velocity context.  We can populate it with
>the
>usual suspects and allow plugin at this point.  It might well be
>interesting
>to provide some sort of scripting capability.

I don't think there's any question you can create a context with lots of
the relevant data. But beyond that it's very hit or miss if we tried to
leave it up to the macro language to get at information we didn't expose
ourselves.

Which reminds me I forgot to add the string-based navigation I meant to
add to the context tree.

>My first question is what module we want to put this code.  I'm guessing
>that much of it will be needed by the TOU and consent modules.

For the stuff that's metadata-centric, it could go in that idp-metadata
module I guess. Alternatively we could just create an idp-ui module I
guess.

-- Scott