Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
[...]
Daniel,
let me repeat: I don't care about precision and elegance and
completeness, I care about usability.
I am thinking at flow users that want to use jav
Vadim Gritsenko wrote:
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Reinhard, how many cocoon users have ever implemented
org.apache.cocoon.xml.XMLPipe?
All users who implemented at least one Transformer.
public interface Transformer extends XMLPipe, SitemapModelComponent {
}
If yo
On 15.10.2005 10:38, Reinhard Poetz wrote:
I only doubt that the proposed way of how to find the classes and
interfaces, that should become part of the public documentation, will
lead to success. Do you guys really think that many people will start to
evaluate ~670 classes and interfaces? And
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
[...]
Daniel,
let me repeat: I don't care about precision and elegance and
completeness, I care about usability.
I am thinking at flow users that want to use java components to do
their
Stefano Mazzocchi wrote:
Reinhard Poetz wrote:
Reinhard, how many cocoon users have ever implemented
org.apache.cocoon.xml.XMLPipe?
All users who implemented at least one Transformer.
public interface Transformer extends XMLPipe, SitemapModelComponent {
}
If you are implementing transfo
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
[...]
Daniel,
let me repeat: I don't care about precision and elegance and
completeness, I care about usability.
I am thinking at flow users that want to use java components to do
their stuff. They should *NOT* ca
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
Daniel Fagerstrom wrote:
To illustrate what I meant I tried to follow the dependencies for the
sitemap component interfaces.
Cocoon API
==
So what is the Cocoon API? All interfaces used in
cocoon-core-sitemap.xconf are part of th
Stefano Mazzocchi wrote:
...
Daniel,
let me repeat: I don't care about precision and elegance and
completeness, I care about usability.
That is great Stefano, you find the the 673 classes and interfaces that
need to be marked public or private, with usability in mind here:
http://wiki.apac
Stefano Mazzocchi wrote:
Daniel Fagerstrom wrote:
[...]
Daniel,
let me repeat: I don't care about precision and elegance and
completeness, I care about usability.
I am thinking at flow users that want to use java components to do their
stuff. They should *NOT* care about org.apache.cocoo
Daniel Fagerstrom wrote:
Daniel Fagerstrom wrote:
...
To illustrate what I meant I tried to follow the dependencies for the
sitemap component interfaces.
Cocoon API
==
...
So what is the Cocoon API? All interfaces used in
cocoon-core-sitemap.xconf are part of the Cocoon API: Gen
Daniel Fagerstrom wrote:
...
To illustrate what I meant I tried to follow the dependencies for the
sitemap component interfaces.
Cocoon API
==
...
So what is the Cocoon API? All interfaces used in
cocoon-core-sitemap.xconf are part of the Cocoon API: Generator,
Transformer, Seria
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon, and the set of classes (components) that an
application programmer need JavaDoc for.
If it ain't public API you ain't need J
Daniel Fagerstrom wrote:
Upayavira wrote:
So, I have created a wiki page:
http://wiki.apache.org/cocoon/PublicAPIClasses
Please go there and mark classes public/private as necessary. As it
says at the top of that page, if you disagree with someone, change it
to "dispute" or D for short. The
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon, and the set of classes (components) that an
application programmer need JavaDoc for.
If it ain't public API you ain't need
Vadim Gritsenko wrote:
Ralph Goers wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon, and the set of classes (components) that an
application programmer need JavaDoc
Ralph Goers wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon, and the set of classes (components) that an
application programmer need JavaDoc for.
If it ain't public
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon, and the set of classes (components) that an
application programmer need JavaDoc for.
If it ain't public API you ain't need
Reinhard Poetz wrote:
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
IMO we need to find two set of interfaces/classes:
the API of Cocoon,
and the set of classes (components) that an
application programmer need
JavaDoc for.
If it ain't public API you ain't need Javadoc for it, period.
--- Daniel Fagerstrom <[EMAIL PROTECTED]> schrieb:
> Upayavira wrote:
>
> > So, I have created a wiki page:
> >
> > http://wiki.apache.org/cocoon/PublicAPIClasses
> >
> > Please go there and mark classes public/private as
> necessary. As it
> > says at the top of that page, if you disagree with
Upayavira wrote:
So, I have created a wiki page:
http://wiki.apache.org/cocoon/PublicAPIClasses
Please go there and mark classes public/private as necessary. As it
says at the top of that page, if you disagree with someone, change it
to "dispute" or D for short. Then it becomes an opportunit
Stefano Mazzocchi wrote:
Upayavira wrote:
So, I have created a wiki page:
http://wiki.apache.org/cocoon/PublicAPIClasses
I would also suggest to add all the other avalon components we ship by
default too (I use the SourceResolver quite a bit and you need to pass
this to the SourceUtil.getS
Upayavira wrote:
So, I have created a wiki page:
http://wiki.apache.org/cocoon/PublicAPIClasses
Please go there and mark classes public/private as necessary. As it says
at the top of that page, if you disagree with someone, change it to
"dispute" or D for short. Then it becomes an opportunity
So, I have created a wiki page:
http://wiki.apache.org/cocoon/PublicAPIClasses
Please go there and mark classes public/private as necessary. As it says
at the top of that page, if you disagree with someone, change it to
"dispute" or D for short. Then it becomes an opportunity for some
healthy
23 matches
Mail list logo
