Kees Jongenburger wrote: > > > > It's good that we break up mmbase in modular pieces, but we should not > > exaggerate, and that we should not use the mere argument that we can 'do > > without' a certain class, because then I fear there will be no end to > > it.... > > I think it's up to the release manager to define what will be standard > in the next release. > jai or image magic, for email and database stuff we don't have that > luxery because > it's all stuffed in the core.
You have the choice. If you don't like the image conversion implementaion you can easily plug in your own (and we offer two), same with email (we offer none in core iirc), and database (we offer a bunch). And the release manager can still define what will be the standard in the database. I don't really understand your point. None of the code which your mentioned is obligatory; even though it is in mmbase.jar, you can choose to not use it. Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
