Damnit Tim, can't you just let me be right for once?

Horacio:

Much as I agree with what you've just said, I think you might have misinterpreted most of what was being said here - Tim and I, for example, were having a friendly debate and jokingly taking the piss out of one another!

No arguments in this thread!

Gareth

I have to agree with Seven on a lot of the issues with PostNuke - I have used both and decided to stick with Xoops.

PostNuke also seems to be distributed with many superfluous modules, an abundance of stuff you'll never be likely to use. And whereas the XOOPS community seem to develop practical applications, the PN community creates a lot of modules that are either duplicates of one another, or of very limited practical use.

I've not tried E107 to be honest - there was something about it that didn't appeal to me, though I'd already found XOOPS so I probably didn't give it the time it deserved.

Quote:

My sentiments exactly!

Quote:

Dunno, she looks like a bit of a bitch.

Quote:

I said, STOP greasing!

Quote:

Ah - welcome to the club!

Quote:

Maybe not everyone replies via the forums... I myself contacted Horacio by email and am one of the all new, four strong documentation team.

Tom:

Quote:

Then please accept my humble apologies.

Quote:

I was in fact raising issues - stimulating thoughtful debate and stating my opinion, not making criticisms. So there! And put your tongue away, it doesn't attract me in the slightest.

Quote:

Stop greasing

Quote:

You got it!

By the way - don't you ever sleep either then?

mvandam:

That's TWICE I've been beaten to it today - damn you all!

Though I have to admit, your explanation was probably a lot better than mine!

Hi,

I don't quite know what's led you to believe you'd want to edit any of the files in templates_c, but I certainly can't see a reason for it. The templates_c directory is just a cache directory, so editing any of the files in there has no constructive purpose.

Gareth

mvandam:

You yourself raise valid points, which I must concede I agree with. I also agree that through my experiences of other CMS systems, XOOPS is definately one of the better and has in fact become my CMS of choice. This is, in part, because despite it's shortcomings I can see active devlopment within the comunity and a real ear from the devlopers' on user requests.

I also agree that XOOPS has an extremely friendly community which, I must admit, is in part a positive reflection on the way that these forums are run. And I definately agree that some recent posts have been entirely disrespectful attacks on the product and those who devote their time to it's development.

vB3Dev:

Please remember that by comparison to the likes of PHP-Nuke and PostNuke, XOOPS is a very young CMS. For it's age, I think it is a very mature and well managed system with an excellent community and bags of potential.

The lack of a written roadmap does not necessarily indicate a lack of a structured development plan. Quite the contrary in fact. Were the product to have a strict roadmap in place, I feel the community themselves would have less input into the development of XOOPS and suffer as a result - we create and edit the roadmap on a daily basis through feedback.

Y'all keep smiling now!

In the last 12 hours alone, I've seen three seperate threads get locked by forum moderators because a debate was starting to get heated. Agreed, we don't want xoops.org to become a boxing ring, but users are all entitled to their opinions on the XOOPS product, and on others.

Granted: foul language, insults aimed at other users and generally unethical conversation needs to be moderated, but I see little gain in locking conversations in the way it has happened today. If users really want to continue their debate, they'll simply open up another thread in which to do it, until that one gets locked whereby they'll open another.

I also noticed that Tom took a final swing at vB3Dev 4 minutes after ackbarr had called time on the browser debate, which to me appears to be a little unfair. If the topic is closed, it is closed to ALL, and those with forum admin privileges shouldn't use those to take a swipe at a user they know can't swing back.

If the moderators have a problem with the way somebody is conducting themselves within the forums, they should consider suspending or banning the individual and not closing a topic to all. By closing topics at a whim, you are simply conceding to the offender(s) and in effect handing THEM power over YOUR site. The browser debate, while temporarily taking a turn for the worse, would have been a good platform in which to discuss style sheet standards and the fundamental differences in the ways browsers handle Xoops. This in turn would lead to better, more advanced and more informed template development.

And remember - when two creative people get together they often have completely different ideas about how to do things. Each thinks that their idea is better than the others, and from the resulting argument evolves a third solution, better than either of the original two.

And before anybody starts to think I'm having a go at them, I'm not criticising anybody in particular. In fact, the way today has gone, I'd be scared of criticising anybody at all for fear of retribution. I simply want to point out that there are perhaps better ways of handling an argument, and sometimes it's best to just let the argument evolve and wear itself down.

That said - I'm going to continue work on a new theme... update in the morning (UK time)!