14
i very much like mambo, and i also like the fact that i've been able to setup a network of sites running off of one installation of mambo, sharing the userbase and forums (SimpleBoard)
there's a couple of nice components for mambo (modules in XOOPS world) that are lacking from the XOOPS community, and vice versa. i like all the 'eye candy' of mambo, because i want a site that will look kickass to my userbase.
but like several have stated, coding for XOOPS seems to be a much better process. file structure/layout is much smarter and organized, and working in the mambo community and whatnot seems to be a bit of a hassle for me (their community sites don't seem cohesive enough, seem too broken up, whereas i have no problem going between XOOPS and dev.xoops to find what i need)
there's definitely some things XOOPS needs to learn from mambo tho, such as the eye-candy factor, as well as the wysiwyg, file/image manager, etc.
and the mambots are nice, kinda like hooks i reckon. they work well for me, and it's nice to have a 'mambot' that will replace specified text with whatever i want.
aaaanywho, i've been building that multi-site network that i spoke of, but i'm not sure that i will continue working on it, because i can't find a *good* gallery software that i like, in mambo (Gallery gives me issues when i try to integrate it)
not sure yet, because we've put alot of work into these sites.