Re: Jestpeed 1.2: status
At 21:31 2000-12-03, Raphael Luta wrote: Hello, It's been about one month since we started clean-up the Jetspeed source code and implement new features. In this one month, a lot of work has been done and many new ideas were proposed and the project now counts 3 new committers. I think this is a good time for every feature owner to give a little statis report on his different tasks. Here is my status: * Update Jetspeed to the new Turbine User and ACL architecture: done As I wrote in an earlier note, jetspeed now works with latest turbine, but it doesn't take any advantage of the new security model so far. (This is another task on the todo: "Incorporate Turbine ACL features in Jetspeed") I'm not happy with all the enrollment and login screens/actions, but I don't think we should spend much time at this point, as they are gonna be reworked in the templates anyway. * Implement a customizer system for both the Portlets and the Portal Layout Some of my colleagues have been working on this. There was/is much more to do here, as we needed some sort of persistence mechanism in order to write configuration data/psml files back to the disk... Anyway, I understood that this work is almost done. The customizer will be very basic, but still: it works and it is something that does it's job (and can be improved later). I'll explain this to you in more detail in a few days (there are some other high priority jobs for me to first). We should discuss the changes on the list next week so that hopefully I'll be able to commit the changes end of next week or the one after that. I'll start with mine: I've been mainly active this month in the clean-up process of the source code and the integration of services within Jetspeed. I'm currently working on 3 issues: - patching Turbine and Jetspeed in order to be able to distribute a binary WAR - reworking the screens/layouts/navigations to use Webmacro My JSP templates are only layout and navigations, I haven't fully replaced ecs (screens). That's an item on the todo... Raphael, I somewhere read following statement about the jars in turbine's lib directory: "vleocity-0.4.jar: Atemplating engine that will soon replace Webmacro." This was a posting of Cristopher Elkins on 17th, October - I'm not sure if this is agreed upon by all turbine members, but if so, we should probably use velocity instead of webmacro? - implementation of template support in portlets/portletcontrols/ portletcontrollers I think WAR support should be achieved within next week. The 2 other tasks will take between 1 week and 3 weeks depending on the time I have available for working on Jetspeed. That's great! WAR support will solve many installing questions. ingo. During next week, real work will probably prevent me from being very active on the project but I should be able to catch in the following weeks. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
RE: Jestpeed 1.2: status
Raphael, I somewhere read following statement about the jars in turbine's lib directory: "vleocity-0.4.jar: Atemplating engine that will soon replace Webmacro." This was a posting of Cristopher Elkins on 17th, October - I'm not sure if this is agreed upon by all turbine members, but if so, we should probably use velocity instead of webmacro? Yes, Velocity is (will be) replacing WebMacro as far as the Turbine list is concerned. It is pretty stable right now, with a few minor wrinkles to be ironed out. Its parser is WAY more flexible than WebMacro's, and there are already key components in Turbine (such as torque) that heavily use Velocity. -- Gonzalo A. Diethelm [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
"Diethelm Guallar, Gonzalo" wrote: Raphael, I somewhere read following statement about the jars in turbine's lib directory: "vleocity-0.4.jar: Atemplating engine that will soon replace Webmacro." This was a posting of Cristopher Elkins on 17th, October - I'm not sure if this is agreed upon by all turbine members, but if so, we should probably use velocity instead of webmacro? Yes, Velocity is (will be) replacing WebMacro as far as the Turbine list is concerned. It is pretty stable right now, with a few minor wrinkles to be ironed out. Its parser is WAY more flexible than WebMacro's, and there are already key components in Turbine (such as torque) that heavily use Velocity. Yes, but currently there's still some support classes missing for Velocity and most important: the templates are the same so switching for Webmacro to Velocity will just be an issue of changing the default configuration in TR.p. AFAIK, in the latest Turbine, Webmacro is still the default templating system. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
on 12/6/2000 6:52 AM, "Raphael Luta" [EMAIL PROTECTED] wrote: Yes, but currently there's still some support classes missing for Velocity and most important: the templates are the same so switching for Webmacro to Velocity will just be an issue of changing the default configuration in TR.p. AFAIK, in the latest Turbine, Webmacro is still the default templating system. However, in the TDK, Velocity is. We will 120% support WebMacro, but people will be strongly encouraged to use Velocity instead. -jon -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
[EMAIL PROTECTED] wrote: Raphael, thanks for the info. Would the template support in portlets/controls/controllers use nested invocation of templates like in the example below to avoid use of ECS for page generation ? Yes template1 (e.g. controller template) calls template11 (e.g. control template ) calls template111 (portlet template) calls template112 (portlet template) calls template12 (e.g. control template ) calls template121 (portlet template) Something like that yes, although I was also playing with the idea of changing the portal OM, the control would become the display peer of a portlet thus completely hiding the portlet API from the rendering engine. This will allos to evolve the rendering/layout engine independently of the portlet API. I assume that would that also be WebMacro templates ? I like Webmacro :) Maybe we might do something similar based on JSPs also ... Definitely, the framework will be template system abstracted. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
Something like that yes, although I was also playing with the idea of changing the portal OM, the control would become the display peer of a portlet thus completely hiding the portlet API from the rendering engine. This will allos to evolve the rendering/layout engine independently of the portlet API. Seems like a very good idea to me. Best regards, Thomas Thomas Schaeck IBM Pervasive Computing Division Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED] Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen, Germany [EMAIL PROTECTED] wrote: Raphael, thanks for the info. Would the template support in portlets/controls/controllers use nested invocation of templates like in the example below to avoid use of ECS for page generation ? Yes template1 (e.g. controller template) calls template11 (e.g. control template ) calls template111 (portlet template) calls template112 (portlet template) calls template12 (e.g. control template ) calls template121 (portlet template) Something like that yes, although I was also playing with the idea of changing the portal OM, the control would become the display peer of a portlet thus completely hiding the portlet API from the rendering engine. This will allos to evolve the rendering/layout engine independently of the portlet API. I assume that would that also be WebMacro templates ? I like Webmacro :) Maybe we might do something similar based on JSPs also ... Definitely, the framework will be template system abstracted. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
Raphael, it may be that some of your work impacts our work in the areas of WAP support and JSP template support. Can you provide a brief overview on these items ? - reworking the screens/layouts/navigations to use Webmacro - implementation of template support in portlets/portletcontrols/ portletcontrollers Best regards, Thomas Thomas Schaeck IBM Pervasive Computing Division Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED] Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen, Germany -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
RE: Jestpeed 1.2: status
Im working on the profiler service. Starting today and for the remainder of December, I hope to be a lot more active. I am looking at doing this in two phases: first without Turbine security and then the second phase to add the security. I hope to commit the first part of the work by the end of next week, and the second phase 1-2 weeks after. -- David Taylor [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Raphael Luta Sent: Sunday, December 03, 2000 12:31 PM To: JetSpeed Subject: Jestpeed 1.2: status Hello, It's been about one month since we started clean-up the Jetspeed source code and implement new features. In this one month, a lot of work has been done and many new ideas were proposed and the project now counts 3 new committers. I think this is a good time for every feature owner to give a little statis report on his different tasks. I'll start with mine: I've been mainly active this month in the clean-up process of the source code and the integration of services within Jetspeed. I'm currently working on 3 issues: - patching Turbine and Jetspeed in order to be able to distribute a binary WAR - reworking the screens/layouts/navigations to use Webmacro - implementation of template support in portlets/portletcontrols/ portletcontrollers I think WAR support should be achieved within next week. The 2 other tasks will take between 1 week and 3 weeks depending on the time I have available for working on Jetspeed. During next week, real work will probably prevent me from being very active on the project but I should be able to catch in the following weeks. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
Re: Jestpeed 1.2: status
Raphael, thanks for the info. Would the template support in portlets/controls/controllers use nested invocation of templates like in the example below to avoid use of ECS for page generation ? template1 (e.g. controller template) calls template11 (e.g. control template ) calls template111 (portlet template) calls template112 (portlet template) calls template12 (e.g. control template ) calls template121 (portlet template) I assume that would that also be WebMacro templates ? Maybe we might do something similar based on JSPs also ... Best regards, Thomas Thomas Schaeck IBM Pervasive Computing Division Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED] Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen, Germany Raphael Luta wrote: [EMAIL PROTECTED] wrote: Raphael, it may be that some of your work impacts our work in the areas of WAP support and JSP template support. Can you provide a brief overview on these items ? - reworking the screens/layouts/navigations to use Webmacro This is just implementing the screens awith Webmacro templates just like Ingo did with JSP templates so have users have their choice of templating system. - implementation of template support in portlets/portletcontrols/ portletcontrollers I'll send to the list a proposal as soon as I have time. -- Raphaël Luta - [EMAIL PROTECTED] -- -- Please read the FAQ! http://java.apache.org/faq/ To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: http://marc.theaimsgroup.com/?l=jetspeed Problems?: [EMAIL PROTECTED]
