From: "Ole Bulbuk" <[EMAIL PROTECTED]> > > I don't get it. "Everything that is reusable should be in > > Commons". Not > > a very practical goal, is it? It'd make SourceForge a lot smaller... > > Not everything that is reusable of course. But maybe everything that is ment > to be used in almost any class/component/... > I call these packages usually horizontal packages.
Call it /aspect/ ;-) > If you decide to use them > for an existing project you would have to rewrite it almost completely. > If such a horizontal package is big enough to be an own project it should do > so (e.g. log4j) and these projects would like to depend only on the > "commons" project. > > More vertical packages that can be used reasonably in a little part of a > project would sit on top of the horizontal ones. > > So it would give clear hierarchy and things could be easier to find. IMO Avalon should concentrate on Interfaces (as it does) and on Facades. In this way it would really become the the reference point for any aspect. The power is in the API, it's what users see. If there was a way of using Avalon interfaces and any other popular implementation, I guess anybody would use the Avalon packages. Avalon Logging is a good thing, but IMO it needs to be more specific on the definition of how the *API* itself works, and how to plug in implementations. Now I want to do a general API for charting, that can make me use any underlying implementation, and one of which is already working (on krysalis now http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/krysalis/krysalis-wings/src/) . What do you think, do you want it on Avalon? Would you help me come up with a good interface+facade? -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
