Thanks for the comments, Kevin. Within.
On 10 June 2014 20:28, Kevin Meyer - KMZ <[email protected]> wrote: > > > > This implies that the DnD > > viewer will be retired. > > By the way: A DnD viewer can be later re-implemented, if so desired. > > Indeed, probably on of the RO API. > > > 4. Improved support for Shiro > > > > The discussions I've had and heard regarding other application > development suites lead me to believe that this would be an extremely > useful add-on! I'd almost like to request that this be the first thing > worked on, before any of the fundamental changes listed above. > > But that's just my wish. > > Jeroen has already started on this, because Estatio needs a solution here too. We'll try to build something that can then be retrofitted into Isis "proper", and which plays nicely (somehow) with users/roles being also managed in LDAP. > > > > 6. Profile Store > > > > The profile store is a component of the framework that is not supported > by > > either the Wicket or Restful Objects viewers, but whose functionality is > > broadly superceded by the UserSettingsService. > > When the UI becomes user-configurable (re-arranged, pallete change, > etc) this should be demo'd. > > Where are user preferences (e.g. UI language, timezone, etc) currently > stored? Do we have demo code? > > There are two points here... where to store preferences, and how/what within Isis should consume them. For the former, we have the UserSettingsService (part of applib); in the JDO applib there is an entity-based implementation, For the latter, nothing in Isis particularly consumes these. For timezones we tend to use LocalDate which gets around the issue to some extent; but you are right that the UserProfile class (in the profilestore) does hold this Localization class; that needs surfacing out as a first-class concept somehow. So perhaps ProfileStore should live on, but not as a component, but instead as a separate service. In all, I see three related subdomains: [Shiro security] -> [Isis user profile (i18n etc) service] -> [Isis user settings service] I'll raise a ticket to capture this thinking so far. > > > > 8. Wicket Viewer > > > > We will also probably rename it. "Wicket" is merely the implementation > > technology; its name should represent what it's role is. Possible names > > are the "default viewer", or the "standard viewer" (preferences? > > alternatives?) > > Thinking about it further, I would probably prefer to keep "Wicket" in the > name somewhere, as the viewer *is* dependent on Wicket, and those > who wish to extend (I want to add some additional view components), > need to know Wicket. But I guess that other names may also be more > appropriate.. > > Hmm, perhaps you are right. Not sure. Don't feel very strongly either way, really, so maybe the "colloquial" name of Wicket viewer will suffice for the foreseeable. > Don't forget about opportunities to show off Isis in "rapid app" dev > competitions. Jeroen, you mentioned one in the Netherlands?? > Perhaps Isis can become the disruptive change from a surprising > direction! > > Thanks for the reminder. Cheers Dan
