Sylvain Wallez wrote: [good ol' snip]
I don't see a real problem of having InputModule (or whatever their names) being not fully used by the sitemap engine, and I'd like to avoid the conceptual overlap between InputModules and PropertyContainers.
I share this sentiment.
Someone (Chris I think) made a parallel between Modules and Sources : a source acesses (potentially) large data sets, while a module accesses smaller and discrete data.
So, since we have Source, WriteableSource, TraversableSource, etc, why couldn't we have :
- PropertyProvider (I like it more than "PropertyContainer")
- WriteablePropertyProvider (i.e. an input/output provider)
- ListablePropertyProvider (i.e. the current Module, that can list the values it provides)
- ListableWriteablePropertyProvider (extends ListablePropertyProvider and WriteablePropertyProvider)
And require classes used by the sitemap to implement the root PropertyProvider interface.
Thoughts ?
Good idea. I like the shorter name of _PropertySet_ more though. Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
