Re: AW: AW: AW: Bug Reports 1.3a2
Riedl Juergen wrote: > Raphael, > > thank you for this information. I will review with our developer Andreas how he did >it. > > He reportet to me, that he has one problem with the customizer (we can customize >html and wml separately now): > o since he load the wml default.psml for customising, selecting "Home" > or something else the wml default remains loaded. That means > wml portlets are displayed as $screen_placeholder. > > On monday we will review the call tree how to hande this. If you have a suggestion, >of course, this is highly appreciated. > If he had to change the profile accessible from JetspeedRunData.getProfile() then he probably needs to remove it when it goes out of customization mode and before a request is made to load the Home page (the profile is refreshed at session validation step). Otherwise it's very easy to modify the sessionValidator so that it always refresh Profile objects... -- Raphael Luta - [EMAIL PROTECTED] Vivendi Universal Networks - Paris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: AW: Bug Reports 1.3a2
Raphael, thank you for this information. I will review with our developer Andreas how he did it. He reportet to me, that he has one problem with the customizer (we can customize html and wml separately now): o since he load the wml default.psml for customising, selecting "Home" or something else the wml default remains loaded. That means wml portlets are displayed as $screen_placeholder. On monday we will review the call tree how to hande this. If you have a suggestion, of course, this is highly appreciated. Nice weekend Juergen > -Urspr> üngliche Nachricht- > Von: Raphaël Luta [SMTP:[EMAIL PROTECTED]] > Gesendet am: Freitag, 12. Oktober 2001 14:03 > An: [EMAIL PROTECTED] > Betreff: Re: AW: AW: Bug Reports 1.3a2 > > 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. > [JR] [.. cut ..] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: AW: Bug Reports 1.3a2
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]
AW: AW: Bug Reports 1.3a2
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 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? > > > > - > 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]
Re: AW: AW: Bug Reports 1.3a2
Riedl, Winword is ok. We use a XML base document format that is common to all Jakarta projects, so I will have to do some editing. You may email the document to me directly (paulsp at apache.org). If the document is large, i.e. > 3MB, then compress it with Zip or tar. Thank you, Paul Spencer Riedl Juergen wrote: > > Yes, as soon as we have a package ready (SW + docu) > > What is the preferred document format? I tend to have it in XML using the >toot-o-matic from Doug Tidwell, IBM >(http://www6.software.ibm.com/dl/devworks/dw-tootomatic-p) > Currently it is in Winword. But for the future I will move on this using XML and >cocoon's capabilities > > Juergen > > > -Urspr> üngliche Nachricht- > > Von: Paul Spencer [SMTP:[EMAIL PROTECTED]] > > Gesendet am: Donnerstag, 11. Oktober 2001 13:38 > > An: [EMAIL PROTECTED] > > Betreff: Re: AW: Bug Reports 1.3a2 > > > > Riedl, > > Would you contribute your documentation so it can incorporated into > > Jetspeed? > > > > > > Riedl Juergen wrote: > > : > > : > > > > > > As the documentation in detail is poor unfortunately (so we document what we >did), this took us much time of debugging to get knowledge, how the things work. > > > > > > However, I'm optimistic, that we can implement at least 1) > > > > > > Juergen > > > > > > > > > Paul Spencer > > > > - > > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: Bug Reports 1.3a2
Yes, as soon as we have a package ready (SW + docu) What is the preferred document format? I tend to have it in XML using the toot-o-matic from Doug Tidwell, IBM (http://www6.software.ibm.com/dl/devworks/dw-tootomatic-p) Currently it is in Winword. But for the future I will move on this using XML and cocoon's capabilities Juergen > -Urspr> üngliche Nachricht- > Von: Paul Spencer [SMTP:[EMAIL PROTECTED]] > Gesendet am: Donnerstag, 11. Oktober 2001 13:38 > An: [EMAIL PROTECTED] > Betreff: Re: AW: Bug Reports 1.3a2 > > Riedl, > Would you contribute your documentation so it can incorporated into > Jetspeed? > > > Riedl Juergen wrote: > : > : > > > > As the documentation in detail is poor unfortunately (so we document what we did), >this took us much time of debugging to get knowledge, how the things work. > > > > However, I'm optimistic, that we can implement at least 1) > > > > Juergen > > > > > Paul Spencer > > - > 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]
