Riedl Juergen wrote: > First of all, WML awareness of 1.3a2: > o yes, you can configure the anon/wml/default.psml as such, > also wml/top.vm and wml/bottom.vm > > What does it lack: > o no login > o even when registering as a new user there is no default > wml/default.psml attached to the user > o the customiser does not regard wml > > What we did: > o port of the html login to wml login > o with each new login user a wml/default.psml is written > > Next steps: > 1) make the customiser wml aware as it shall be possible > from the webpage to select your desired wml portles > (it seems to be foreseen with the HompageCustomizer.vm > whis is not used to our investigations)
The Customizer has no real reason to be "WML aware" because what the customizer manipulates is the PSML resource which is content-type agnostic (ie a PSML page can used to produce any kind of content is the controllers/controls/portlets defined inside are correct for the expected media-type). However, it does need some additionnal work to be fully WML compatible: - provide a UI to allow the user to select the PSML resource he wants to edit. This resource may either be an existing resource got through Profiler.list() or a new resource for a Registry-known media-type. [ 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. ] - implement some customizable controls/controllers that correctly operate in WML mode > 2) having a wml customiser thus one can select from wml > his wml portlets as well > To implement this, you need at least to write WML templates for the Customizer portlets and the controllers customization templates. I'm not sure this would give you a very user friendly WML customizer though... > 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) > Sorry about the state of documentation, I'm very bad at documenting things ; I tend to think sometimes that reading the code is enough :( > Juergen > > >>-----Urspr> �ngliche Nachricht----- >>Von: David Sean Taylor [SMTP:[EMAIL PROTECTED]] >>Gesendet am: Mittwoch, 10. Oktober 2001 21:17 >>An: [EMAIL PROTECTED] >>Betreff: RE: Bug Reports 1.3a2 >> >>1.3a2 is WML aware, however the customizer is not. When you say that you are >>'extending 1.3a2 to make it WML aware', are you extending the customizer? >> >> >> >> >>>-----Original Message----- >>>From: Riedl Juergen [mailto:[EMAIL PROTECTED]] >>>Sent: Wednesday, October 10, 2001 1:40 AM >>>To: '[EMAIL PROTECTED]' >>>Subject: AW: Bug Reports 1.3a2 >>> >>> >>>Does this mean, that WML as of 1.3a1 is excluded? We are >>>curently extending the 1.3a2 to make it WML aware. >>> >>>Thanks >>> >>>Juergen >>> >>> >>>>-----Urspr> �ngliche Nachricht----- >>>>Von: David Sean Taylor [SMTP:[EMAIL PROTECTED]] >>>>Gesendet am: Dienstag, 9. Oktober 2001 19:43 >>>>An: [EMAIL PROTECTED] >>>>Betreff: Bug Reports 1.3a2 >>>> >>>>We are closing in on releasing Jetspeed 1.3a2. >>>>If you know of any bugs in 1.3a2, could you please send a >>>> >>>short description >>> >>>>of the bug(s) to this mailing list so we can get them fixed >>>> >>>before the >>> >>>>release. >>>> >>>>Thanks >>>> >>>>David >>>> >>>> >>>> >>>> >>>> >>>> >>>--------------------------------------------------------------------- >>> >>>>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] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Raphael Luta - [EMAIL PROTECTED] Vivendi Universal Networks - Paris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
