On Dec 30, 2007 5:35 PM, Reinhard Poetz <[EMAIL PROTECTED]> wrote:
> ... o make Cocoon pipelines/sitemaps ready for the usage in OSGi
> environments...
The Sling project would very probably be interested in this. We're not
there yet, but once we start working on different output renderings in
S
Sylvain Wallez wrote:
Jeroen Reijn wrote:
Reinhard,
sounds like a good thing. I guess not only Indoqa will get a benefit
out of this. Put it in the whiteboard, so if needed and possible other
people can help out and perhaps join the discussion?
+1 !
+1
Michael
Sylvain
Carsten Ziegeler wrote:
How is this related to a final 2.2 release? Are we planning to release
2.2 soon?
Yes, I want to work on the final release in the second week of January again. I
can't say how much time I can dedicate to the release work, but I guess that we
can ship the release by the
How is this related to a final 2.2 release? Are we planning to release
2.2 soon? Before you start your work? Or is it the intension to put this
into a final 2.2 as well?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
Jeroen Reijn wrote:
> Reinhard,
>
> sounds like a good thing. I guess not only Indoqa will get a benefit
> out of this. Put it in the whiteboard, so if needed and possible other
> people can help out and perhaps join the discussion?
+1 !
Sylvain
--
Sylvain Wallez - http://bluxte.net
Reinhard,
sounds like a good thing. I guess not only Indoqa will get a benefit out
of this. Put it in the whiteboard, so if needed and possible other
people can help out and perhaps join the discussion?
Good luck!
Regards,
Jeroen Reijn
Reinhard Poetz wrote:
We at Indoqa have started to
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
My idea is that profiling should only be an aspect on pipeline processing.
In 2.1/2.2 you have to use a different pipeline implementation for
profiling - I think we can do better.
Ahh, got it. If we architect API of pipelines well we will be ab
Reinhard Poetz pisze:
>
> My idea is that profiling should only be an aspect on pipeline
> processing. In 2.1/2.2 you have to use a different pipeline
> implementation for profiling - I think we can do better.
Ahh, got it. If we architect API of pipelines well we will be able to provide
profilin
Grzegorz Kossakowski wrote:
Ralph Goers pisze:
Use the whiteboard. The only areas of concern I have is with regard to
sub-sitemaps and resources. But I reserve judgment on that until I see what
you come up with.
Hi Ralph,
When it comes to resources, we have a replacement for that already. So
Grzegorz Kossakowski wrote:
o aspect-oriented profiling of pipelines
Could you elaborate on this? I may not know all fashionable terminology. :-)
My idea is that profiling should only be an aspect on pipeline processing. In
2.1/2.2 you have to use a different pipeline implementation for prof
Ralph Goers pisze:
> Use the whiteboard. The only areas of concern I have is with regard to
> sub-sitemaps and resources. But I reserve judgment on that until I see
> what you come up with.
Hi Ralph,
When it comes to resources, we have a replacement for that already. Something
similar to old Vir
Use the whiteboard. The only areas of concern I have is with regard to
sub-sitemaps and resources. But I reserve judgment on that until I see
what you come up with.
Ralph
Reinhard Poetz wrote:
We at Indoqa have started to think about working on a slimmed down
version of Cocoon 2.2 ("Micro-C
Reinhard Poetz skrev:
We at Indoqa have started to think about working on a slimmed down
version of Cocoon 2.2 ("Micro-Cocoon"). By doing this we pursue a couple
of goals:
o increase the maintainability of Cocoon
(Cocoon 2.2 is already a big improvement but still too complicated
in s
Reinhard Poetz pisze:
>
> We at Indoqa have started to think about working on a slimmed down
> version of Cocoon 2.2 ("Micro-Cocoon"). By doing this we pursue a couple
> of goals:
>
> o aspect-oriented profiling of pipelines
Could you elaborate on this? I may not know all fashionable termino
We at Indoqa have started to think about working on a slimmed down version of
Cocoon 2.2 ("Micro-Cocoon"). By doing this we pursue a couple of goals:
o increase the maintainability of Cocoon
(Cocoon 2.2 is already a big improvement but still too complicated
in some areas)
o optimize C
15 matches
Mail list logo