I'll take a stab at this.  The UI manager appears to be for, in theory,
skinning your presentation.  I.E. if you want to change your
forground/background/font-size/images you can do it via the config file
instead of in a Cascading Style Shee or the HTML.  That having been said, I
haven't really delved too deeply into it and it seems like it's basically
the same thing as a CSS except the output ends up in your HTML instead of
stripped out into another file.  Actually, I'd liken it to server side CSS
or something like XSL.  Using a tool like that has advantages and
disadvantages and I'll give you my opinion on those.

Advantages:
  Consolidates User Interface (UI) look and feel data to a central location
  Allows UI data to be rolled directly into HTML without recoding in 100
different places
  Potentially obviates CSS incompatibilities between browser and seperate
file caching issues

Disadvantages:
  Look and feel is in a different place and in a different format from
almost all other web stuff
  Disallows caching of look and feel (LAF) data on the client
  Not terribly well documented (I haven't seen any, but, I haven't really
looked)



> -----Original Message-----
> From: Chris Rafuse [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 03, 2003 12:27 PM
> To: Turbine User Mailing List; TDK User List
> Subject: UI Manager and Skins
>
>
> Can anyone provide a good explanation of:
>
> 1) What does UI mean?
> 2) What is the UIManager's purpose (it seems to manage html elements,
> but a more detailed explanation would be great)
> 3) What are considered UI elements ?
> 3) How do skins work? ie. What is a skin? Are they loaded for each page?
> What is the directory hierarchy for skins?
>
> Thanks alot,
>
>
>
> Chris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to