On Oct 26, 2006, at 8:03 AM, David H. DeWolf wrote:
I'll probably have some time to finish up the TilesContextFactory configuration today and start doing some work on removing duplication. Once I get through that I'll start putting some container ideas down into code. The first step of that process will be to define the tiles container api. What are those things that we want to expose to the world?
It doesn't seem like much. The majority of what people will do with Tiles is plug it into another architecture, so we need to focus on the points where it interfaces with MVC architectures I think. Beyond that, there will be cases where people want to create, modify, and access definitions and attributes. I'd say keep the public API as small as possible and add to it as requests come in. Antonio may have more input since he's working with some Tiles extensions.
Do we prefer to do the container work in a branch, or continue working on it in the trunk?
Either way is fine with me. I would prefer to just do it in the trunk since it can be done incrementally.
Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
