"(better)portalML" -- define the user's customized portal layout and what they can choose from
-
define available objects and layout (number of columns etc. generalizes ideas in Flow,..,GridBag Object layouts in Java AWT)
-
e.g. <portal name="" ><columns=3/><portalobject mode="forced" source=""><placeat layout="flow1" position="1" > ......
-
placement of component objects on pages and specification of their parameters and location e.g. access weather object for suchandsuchcity with suchandsuch sensor overlay
-
choice of nifty JavaScript or Java index
-
rendering preferences such as resolutions and "universal access"
-
borders, backgrounds etc.
|