Hi,

I'm fine with html and pretty good with CSS etc - however I'd like to start learning how to make my own XOOPS modules - what exactly should I be looking to learn to do this? Would php, mysql, java etc be the best to learn?!

Where did you learn to make modules! ;)

Just a question - reading the 'roadmap' for XOOPS it states that:

2.3 alpha will be release Jan 2006

2.4 alpha will be release Mar 2006

As we're in March now, does this mean that the imminent release will be for 2.4 and that wil be the end of 2.3?

Is the Mar release for 2.4 still on course or should I not hold my breath for it this summer?

Thanks!

Thanks for the very interesting replies guys & gals!

I think that's the difficulty - there's an awful lot under the bonnet that is impossible to see until you've really used a cms properly - and then it's usually too late!

Joomla's apparently got a 1.1 release coming very soon which is meant to move it totally away from it's mambo-base and redress many issues - there's a bunch of folk raving about it anyway.

And XOOPS has the similar 2.3/2.4 releases coming up!

So I guess I'll just wait and see who delivers the greatest goods and go with my instinct then! ;)

hi Quest,

Yeah it sounds like your motivations towards XOOPS were similar to mine - though the reason I'm asking is that I just had a look over there today and they really have removed a lot of the things that swayed me to XOOPS a while back.

-They're now registered properly as an open-source software company
-Their components section is superb -http://extensions.joomla.org/

Have a look - it's like a hit-list of the annoyances of XOOPS - ie look in 'wysiwig editors' section and you'll find neatly arranged (and working!) versions of the most recent wysiwig editors - look at the documents section and you'll see a range - there's an online 'magazine' module that let's you break out of the template and arrange elements however you want for a magazine look (look at the examples) and so on and so on.

The trouble is I think of the hassle and number of requests it's taken for any sort of movement in having a news article that can even display images in the category listings (ie like the XOOPS homepage question that has been asked a thousand times) and after months and months of these questions we get a limited hack from smdcom that limits us to four categories...

It's these sorts of comparisons that really make my feet itchy - it seems most of the issues that affected joomla have disappeared whereas XOOPS has just kinda stood still.

So I guess what I need to hear is any actual reasons why XOOPS is better - for example are the modules unstable in joomla? (mind you XOOPS ain't the greatest! probably bad example ;))

Is XOOPS more secure? Though, again from your post if the homesite is getting trashed by hackers then that doesn't really bode too well!

I think in terms of the look of website, joomla is two or three years ahead of xoops, but I'd like to know if there's some 'under the bonnet' advantage XOOPS has? Is it quicker?

<sigh>

Ok I've been using XOOPS for around a year, and I'm beginning to get very itchy feet with all the nonsense that's been going on - I'm particularly looking at Joomla which appears to be leaping forward with update after update, plus if you take one look at the kind of websites that are made you can see they really are 'next-generation' cms...

I've recently had to reinstall my entire site after downgrading to 2.0.13 from 2.2.3 after finding out that 2.2.3 was not the most 'stable' version and so you'll need to downgrade in order to upgrade to 2.3 whenever that's out. The 'downgrade script' basically trashed my site, deleted database entries and wiped a load of data. Nice.

Unsurprisingly I'm getting to the end of my tether now - does anyone know of any advantages that XOOPS has over joomla? At least that might ease my itchy feet! ;)

Thanks!