Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Panel
borderStyle
borderColor#ccc
bgColor#FFFFCE
titleBGColor#F7D6C1
borderStyledashed
titleDRAFT NOTESdashed

Note: Apologies for UK spellings (wink) Feel free to edit!

...

AL - quite a few people using Aggregated Layouts - a couple using simple layouts. Lot of interest in terms of Distributed Layouts - supposed to be a simpler migratation path to DLM than ALM from simple layouts. Also DLM is a bit more flexible.
Problems pushing layout fragments via AL damaging layouts if the user is logged in. Memorial running push fragments when the portal is down.

ALM / DLM - DLM has more flexibility in terms of being able to edit tabs with pushed content on it. DLM not quite production ready yet.

...

  • Personalisation handled pretty well with ALM and DLM, but customisation is not very good at all.
  • Personalisation is pretty hard via fragments.xml and we wouldn't like to see this in a user preferences style thing either. Not good from either a user or administrator side of things.
  • UC Berkeley would like to be able to push fragments to different groups and allow users to remove/edit some channels, but not others. They would also like to be able to create editable pulled fragments, which users can select to receive only if they are interested in the subject matter. Finally, they would like to be able to ensure that if a pushed fragment changes, users receive any channels added or updated, but retain any other changes they've made to the fragment. It might be nice to have a setting that allows portal managers to decide whether they want to merge user changes into an updated fragment or not. And of course it will be necessary to have a UI that allows users to manage their fragments in a coherent manner.

Actions:

  • Need Documentation of conventions, standards and requirements
  • Tutorial style guidance to illustrate common usage, styles, design intentions
  • Need a Standing Committee / Interest Group / Discussion Group to continue discussion and keep focus around UI. If anyone can devote any time to this- let Jason Shao know

Immediate short terms goals for 2.6

  • Jason Jason taking the Rutgers theme, ripping out the logos and adding to possibly 2.5.1. and 2.6
    • standards compliant version of SLM
    • css driven for layout.
    • improvements mostly 'cosmetic', less markup being moved around, quicker rendering, prettier!
  • B. Collier Jones @ VT will contribute the VT theme - with icons ripped out etc
  • Sarah Arnott modeless integratedModes
  • Duffy Gillman at Arizona - can add in some tree-controls type layouts.

...