You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2003/01/12 11:28:35 UTC
Re: [morphos] [PATCH] some funcionality
Tomasz Pik wrote:
> Hi all,
>
> Attached patch contains most of the funcionality discussed
> here: http://nagoya.apache.org/eyebrowse/ReadMsg?listId=15&msgNo=20440
>
> Nicola, please, review it and let me know your opinion.
Ok, all good. Committed. Please check if all is ok.
Thanks :-)
The next step I want to do is to make it possible to use Cocoon Blocks
in it as a components drop-in system.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [morphos] next steps was Re: [morphos] [PATCH] some funcionality
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Tomasz Pik wrote:
> Nicola Ken Barozzi wrote:
>
[...]
>> The next step I want to do is to make it possible to use Cocoon Blocks
>> in it as a components drop-in system.
>
>
> It's not so clear to me :-(
>
> As always, problem with project dependencies.
> 1) Morphos depends on Cocoon?
> 2) Cocoon (in the future) depends on Morphos;
>
> ad 2 - I cannot find something like 'cocoon api'. Just huge
> set of javadocs with everything inside. I'm not too good in
> Cocoon internals so I don't know where to look for... :-(
The idea is that both remain as separate as possible in the framework,
but that for implementations Morphos depends on Cocoon.
This means that Morphers should be written IMHO as Cocoon Components,
that are Generators, Transformers, Serializers, Readers.
So Morphos implementations will use Cocoon blocks and depend on Cocoon.
I'm going to write in more depth about it real soon.
> Right now I'm working (in free time, so I'm not too fast)
> on JAXP-related classes.
Cool! :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[morphos] next steps was Re: [morphos] [PATCH] some funcionality
Posted by Tomasz Pik <pi...@ais.pl>.
Nicola Ken Barozzi wrote:
>
> Tomasz Pik wrote:
>
> Ok, all good. Committed. Please check if all is ok.
Thanks, I've found a typo somewhere in docs but I'll fix
it next patch.
> Thanks :-)
>
> The next step I want to do is to make it possible to use Cocoon Blocks
> in it as a components drop-in system.
It's not so clear to me :-(
As always, problem with project dependencies.
1) Morphos depends on Cocoon?
2) Cocoon (in the future) depends on Morphos;
ad 2 - I cannot find something like 'cocoon api'. Just huge
set of javadocs with everything inside. I'm not too good in
Cocoon internals so I don't know where to look for... :-(
Right now I'm working (in free time, so I'm not too fast)
on JAXP-related classes.
--
Regards
Tomek Pik
pikus@ais.pl
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [morphos] [PATCH] some funcionality
Posted by Jeremias Maerki <de...@greenmail.ch>.
Nicola,
it seems like this patch hasn't made it in fully. For example, the
BasicMorpherFactory doesn't contain all the code that Tomasz Pik had in
his patch. Would you please have another look at it? Thanks!
I've finally got some time and reason to have a closer look at Morphos.
I'll try to come up with a Morpher for FOP to get a feel for it.
On 12.01.2003 11:28:35 Nicola Ken Barozzi wrote:
>
> Tomasz Pik wrote:
> > Hi all,
> >
> > Attached patch contains most of the funcionality discussed
> > here: http://nagoya.apache.org/eyebrowse/ReadMsg?listId=15&msgNo=20440
> >
> > Nicola, please, review it and let me know your opinion.
>
> Ok, all good. Committed. Please check if all is ok.
>
> Thanks :-)
>
> The next step I want to do is to make it possible to use Cocoon Blocks
> in it as a components drop-in system.
Jeremias Maerki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>