ingo schuster wrote:
>
> At 20:36 01/31/01, Brian M. Long wrote:
> >hey folks.
> >
> >where does the <skin> tag get generated in
> >/WEB-INF/psml/turbine/homeHTML.psml and the associated
> >/WEB-INF/psml/user/turbine/html/default.psml ?
> >
> >basically what i'd like is for 2 different users to be able to have
> >different skins on their portlets, but every time i use the Customizer it
> >resets the colors to the defaults.
> >
> >any help finding out where this happens? i'm sure it's in an xml / psml
> >file somewhere, but i can't track it down.
> >-bml
> >
>
> Another customizer problem... The customizer saves the portlets using a
> "psml" template (well, it's an template of the respective object tree).
> Don't think you can solve your problem without touching customizer code.
> A customizer redesign is on our ToDo for alpha 2:
>
> > - redesign the customizer
> > * be layout aware
>
Remember that I plan to implement the new layout proposal for alpha 2 also
so the customizer will need to be modified accordingly. But I think it
should be way easier to write a customizer for this layout system because the
configuration structure is much simpler to manipulate.
I think the best course would be that you propose the customizer functional
behavior you'd like to implement to list, discuss this together, make sure
the "content model" APIs enable the customizer to do what it wants and then
go on and implement it.
In case you did not notice it yet, in the new layout proposal we use a pull
methodology, which means jetspeed has *no way* to know how many and which
panes will be included in a given template. I don't think this presents a
major issue but you need to be aware of this...
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
