Guide
![[WWW]](/wiki/classic/img/moin-www.png){kind=small}
to the Meeting Area code. "marea" 1. The 7-Frame Interface
Navigating to POD_URL_ROOT/marea loads frameset.php. The entire meeting area interface remains in the same downloaded framset the whole time. It lays out the browser window with 7 frames like this:
name=blabla is the HTML FRAMESET NAME tag, which is also the javascript identifier for the frame. The php files listed are the possible files which may appear in that frame during use.
banner, foliotb, msglisttoolbar and curmsgtoolbar all rarely reload during use. Changes to their text are accomplished via DHTML routines. (Exception: foliotb must reload to get an updated navigation listing of the folio items in the meeting area)
msglist.php's highlighting and jumping around, is accomplished through DHTML. However, all the message headers are written via php; thus, it must reload to show new messages. msglist.php controls the display in msglisttoolbar via javascript calls.
curmsg.php reloads for every new message. curmsg.php controls the display in curmsgtoolbar via javascript calls.
workspace reloads for every new view, of the folio index, and of each folio item.
2. Meeting Area Popups
Popups for the meeting area – for creating new folio items and messages – actually are framesets with one big frame that does all the actual work. The external frame exists to provide a javascript object ('opener') referring back to the original 7-frame frameset window,even after the main working frame requests new pages, wiping clean its javascript memory.
3. Other marea Notes
All php pages designed to be requested by the user, are one subdirectory below POD_URL_ROOT and POD_FILE_ROOT. This means, the universal way to get at the group root is '..' xMSx xMSx xMSx xMSx
