Riedl Juergen wrote:
> I doubt, that for a first shot it is neccessary to support any functionality of the
>ProfileLocator. In my opinion the functionality of 1.3a1 is the first step:
> o one can select and deselct WML portlets
>
The ProfileLocator functionality is already implemented in the Profiler service,
you just need to use it.
IMO, The process flow for customization should be the following:
- user connects to Jetspeed using media type 1, ex HTML
- based on request information and media-type, Profiler selects the "best"
PSML configuration resource available for this user.
- the user wants to customize Jetspeed:
(- user selects one of his existing resources he wants to customize or creates
a new PSML resource tied to a specific media-type, media type 2 ex WML)
- based on selected resource media-type, customizer brings a GUI for the
current PSML, the Customizer portlets delegate the customization layout
and rendering to controls and controllers found inside the PSML resource, so
for this to work any controller supporting media-type 2 must also support
the customization interface in media 1 (In the current impl of the controllers
this is achieved through Velocity templates)
- upon saving, the PSMLManager service will use the ProfileLocator handle to
determine where to save the object which should always be in the user specific
dataspace.
The best thing about this process is that it's completely independant of the
real media-type considered and thus can easily be extended to other new medias,
you basically just need to implement the controllers for your targetted media
and their customization templates for all the media on which you plan to actually
interact with the customizer.
> What are we going to use it for?
> o pure WML pages to add (like in html the Sun Java Dev page)
> o pure WML pages which will be obtained remotely and than
> automagically reworked as if locally thus the user remains
> in the portal and not at the wml adress
> o for the demonstration of the power of cocoon: one XML text
> two appearences using either WML and HTML xsl.
>
>
> However, I welcome any discussion, review and advise how the strategy for
>development of jetspeed is. I would appreciate when you and the other big
>maintainer/programmer can share it with the community.
>
> Juergen
>
>
>>-----Urspr> �ngliche Nachricht-----
>>Von: David Sean Taylor [SMTP:[EMAIL PROTECTED]]
>>Gesendet am: Donnerstag, 11. Oktober 2001 18:17
>>An: [EMAIL PROTECTED]
>>Betreff: RE: AW: Bug Reports 1.3a2
>>
>>
>>> As an aside, I don't think the current process of creating
>>>PSML resources
>>> on user creation is a good idea. The architecture of the
>>>Profiler and Customizer
>>> is such that when a newly created user connects he would
>>>get the default
>>> anonymous home page (because of the Profiler fall-back
>>>mechanism) and he can try
>>> to customize it, but when saving the customized page, the
>>>Customizer does
>>> (or should) automatically set the User object in the
>>>ProfileLocator used for
>>> saving thus writing the customized resource in the user
>>>specific storage.
>>>
>>> The main benefit of this is that all your users get your
>>>current default page
>>> (even if you modified it after they were created) unless
>>>they specifically did
>>> customizations to the page.
>>>]
>>>
>>Yes, that is different from how it works.
>>I think this approach is one basic solution on how to assign the default
>>psml page to a user.
>>
>>As for customizing WML or any page besides the default html, the customizer
>>will need a lot of work.
>>It will need a selection page, allowing the user to select which page they
>>want to customize.
>>And what about deleting pages, or creating new pages for all the
>>combinations of ProfileLocator parameters....
>>
>>Do we want to consider adding all this functionality to 1.3a2?
>>
--
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
