Forum OpenACS Development: Response to user preferences - a new package?

Collapse
Posted by Ben Adida on
Michael: sure, you can do that. Build packages that provide certain services (you can call them objects) without a UI, allowing the services to be used by other packages. Credit Card Processing, for example (although you might have a generic management UI there).

"Cramming them into the core" is a tad misleading. There are two issues:
1) what should be distributed as OpenACS core and 2) what pieces become de-facto core since many other packages use them.

Going back to something Don and I were talking about a while ago, the right thing to do is probably to distribute a very minimal core, and each package individually. Then, we need an easy way to create vertical-specific applications that mix and match the right packages. This makes it flexible for developers, and functional for users.