On Thursday, Oct 9, 2003, at 14:00 Europe/Rome, Geoff Howard wrote:
Bertrand Delacretaz wrote:
...
I like access="private" and access="public".
- Which is the default if none is specified? (public)
it would be back incompatible, but defaulting to private would be better from an evolutionary perspective.
I was thinking of back compatibility too, but come to think of it which old version of Cocoon with block polymorphism do we have to worry about?
;)
Hmmm, on second thought,
uri access : @internal-only block access : @access
are these two orthoganal concepts named deceptively in the case of pipelines?
...
If
we never envision anything other than private/public would something like block-private="true" convey more meaning? block-access="private" might do the same but leave freedom for other than private/public.
random though, but you could think of "protected" as exposed to extending blocks but not outside that extending block (maybe to allow a different style of wrapping), while "private" is not exposed to extending blocks and public
so, leaving block-access="" (on both components and pipelines) is probably a better idea.
Sounds good - not sure if we'll need or want those kind of distinctions but it's hard to predict now.
Geoff
