Stefano Mazzocchi wrote:
So, my proposal is to keep the above semantics, but differentiate
between 'real' and 'virtual' pipeline components, with the existance of
the src= attribute. If missing, the tree processor will consider it a
virtual one and construct it from there.
I like this.
Could we
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
Sorry, not much time to dig into the implementation for now, but I
will :-)
Good :)
In order to have a better opinion on the naming issue (virtual-blah /
special src=... / no src) I started digging in the implementation.
VPCs aren't an easy
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
Sorry, not much time to dig into the implementation for now, but I
will :-)
Good :)
In order to have a better opinion on the naming issue (virtual-blah /
special src=... / no src) I started digging in the implementation.
VPCs
Sylvain Wallez wrote:
What we see here is that VPCs aren't regular components from the way
their configuration is parsed. This configuration isn't parsed by the
component itself, but by the surrounding environment which is the
TreeProcessor.
This can be changed so that VPC create own instance
On Apr 12, 2005 5:50 AM, Sylvain Wallez [EMAIL PROTECTED] wrote:
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
big snip/
So in the end, my opinion is that sitemap fragments for VPCs should be
declared in their own section of the sitemap, just as views, resources
and flows. Components
Peter Hunsberger wrote:
On Apr 12, 2005 5:50 AM, Sylvain Wallez [EMAIL PROTECTED] wrote:
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
big snip/
So in the end, my opinion is that sitemap fragments for VPCs should be
declared in their own section of the sitemap, just as views,
Daniel Fagerstrom wrote:
So I don't see this so much as an implementation question as a
conceptual question. Are we considering the VPCs as sitemap components
or something else, to me they look like sitemap components.
Conceptually, I think VPCs are components first and foremost. So they are
On Apr 12, 2005 9:05 AM, Daniel Fagerstrom [EMAIL PROTECTED] wrote:
Peter Hunsberger wrote:
On Apr 12, 2005 5:50 AM, Sylvain Wallez [EMAIL PROTECTED] wrote:
Daniel Fagerstrom wrote:
Sylvain Wallez wrote:
big snip/
So in the end, my opinion is that sitemap fragments
Daniel Fagerstrom wrote:
...
So I don't see this so much as an implementation question as a
conceptual question. Are we considering the VPCs as sitemap components
or something else, to me they look like sitemap components.
To me, a VPC is a better _resource_: IMHO it should be on the same level.
Peter Hunsberger wrote:
On Apr 12, 2005 9:05 AM, Daniel Fagerstrom [EMAIL PROTECTED] wrote:
snip/
I don't see that there is any harm in separating VPC's into a new
section, but I do see a lot of possible good in the long run.
Might be. But as long as I haven't seen any concrete use cases I
Vadim Gritsenko wrote:
Daniel Fagerstrom wrote:
So I don't see this so much as an implementation question as a
conceptual question. Are we considering the VPCs as sitemap
components or something else, to me they look like sitemap components.
Conceptually, I think VPCs are components first and
Daniel Fagerstrom wrote:
Peter Hunsberger wrote:
On Apr 12, 2005 9:05 AM, Daniel Fagerstrom [EMAIL PROTECTED] wrote:
snip/
I don't see that there is any harm in separating VPC's into a new
section, but I do see a lot of possible good in the long run.
Might be. But as long as I haven't seen
Le 13 avr. 05, à 00:09, Sylvain Wallez a écrit :
...2 - rank each solution from 1 to 4, and choose the one with the
highest sum. Seems good except that it allows people to rank several
choices equally..
I also like this way, but if two solutions come out very close we might
want to rediscuss
Daniel Fagerstrom wrote:
I have continued Vadim's and Sylvain's work and added a first,
hopefully working version of virtual sitemap components (VPCs) to the
trunk.
Good job!
Use
===
To use VPCs one define them in the components section in the sitemap,
e.g.:
map:components
map:readers
Le 11 avr. 05, à 14:41, Sylvain Wallez a écrit :
It seems weird to me to see sitemap statements in the
map:components section. But they're also used as any other
component. Hmm...
What about either:
- leave them in map:components but with special element names, e.g.
map:virtual-generator
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
map:transformers default=xslt
map:transformer name=virtual2
src=org.apache.cocoon.transformation.VirtualPipelineTransformer
map:source param=src2/
map:transform src=vpc-include.xsl
map:parameter name=file
Vadim Gritsenko wrote:
It can be
map:components
map:generators
map:virtual name=a
That's enough information to build it.
I agree with Vadim and I think this is the syntax suggest in the early
discussions about VSC as well.
Carsten
--
Carsten Ziegeler - Open Source
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
I have continued Vadim's and Sylvain's work and added a first,
hopefully working version of virtual sitemap components (VPCs) to the
trunk.
Good job!
Thanks :)
Use
===
To use VPCs one define them in the components section in the sitemap,
e.g.:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
snip/
What about either:
- leave them in map:components but with special element names, e.g.
map:virtual-generator that maps to the VirtualPipelineGenerator class
It can be
map:components
map:generators
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
map:transformers default=xslt
map:transformer name=virtual2
src=org.apache.cocoon.transformation.VirtualPipelineTransformer
map:source param=src2/
map:transform src=vpc-include.xsl
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
map:transformers default=xslt
map:transformer name=virtual2
src=org.apache.cocoon.transformation.VirtualPipelineTransformer
map:source param=src2/
map:transform src=vpc-include.xsl
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
map:transformers default=xslt
map:transformer name=virtual2
src=org.apache.cocoon.transformation.VirtualPipelineTransformer
map:source param=src2/
map:transform
Stefano Mazzocchi wrote:
Vadim Gritsenko wrote:
It can be
map:components
map:generators
map:virtual name=a
That's enough information to build it.
I still like the way we agreed in the past and Daniel implemented, the
fact that a generator is a java class or is a subpipeline should
Daniel Fagerstrom wrote:
I have continued Vadim's and Sylvain's work and added a first, hopefully
working version of virtual sitemap components (VPCs) to the trunk.
Awesome!!!
You (and Vadim) rock!
I'm a happy camper.
Use
===
To use VPCs one define them in the components section in the sitemap,
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
snip/
Good point. So let's go for map:virtual-blah in map:components.
No, what does that buy you? generator means it generates, who cares
how it's implemented?
People that write sitemaps do care. What they want is to write a virtual
component and
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Uh? Are you saying that any map:generator without a class attribute
will be interpreted as a VPC?
Well, a little more complex than this, a generator is virtual if:
1) doesn't have a src attribute
2) his first child is generator
3) contains zero
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
snip/
virtual readers? h, never thought of that one. What does that buy
you? I mean, it's not harmful to have it, but do you see any real use
of that?
Consider an application using graphical buttons. You may want be
Daniel Fagerstrom wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
VPCs are not cacheable yet. Its probably not that hard to add
caching, but it requires that we extend the ProcessingPipeline
interface with some methods that are needed for VPCs. It also
requires
Sylvain Wallez wrote:
Vadim Gritsenko wrote:
It can be
map:components
map:generators
map:virtual name=a
...
Good point. So let's go for map:virtual-blah in map:components.
Note: I never suggested virtual-blah :-)
I prefer map:generator, while map:virtual will be an ok option too.
We
On Lun, 11 de Abril de 2005, 14:06, Leszek Gawron dijo:
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
snip/
virtual readers? h, never thought of that one. What does that buy
you? I mean, it's not harmful to have it, but do you see any real use
of that?
On Lun, 11 de Abril de 2005, 13:23, Daniel Fagerstrom dijo:
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
I have continued Vadim's and Sylvain's work and added a first,
hopefully working version of virtual sitemap components (VPCs) to the
trunk.
Awesome!!!
You (and Vadim) rock!
I'm
I have continued Vadim's and Sylvain's work and added a first, hopefully
working version of virtual sitemap components (VPCs) to the trunk.
Use
===
To use VPCs one define them in the components section in the sitemap, e.g.:
map:components
map:readers
map:reader name=virtual1
32 matches
Mail list logo
