Main Xoops website

Most people only know him by name, only a few have actually worked with him.

After some roaring years in the Xoops community, it seems “a great king” has come back to his castle and to his own created community.
Read the return announcement of Onokazu, specially, see the reaction of his people.
Cheers and welcome Back!

Xoops.nl website revision

After a long time of silence we finally (together with Web-M) closed the Xoops.nl website and began installing the new design.
Although we had some initial problems, especially with the old newbb forum, work went very smoothly.Currently the website is online again, but alot of work still has to be done. Pay a visit at Xoops.nl and tell us what you think, in the meantime I”ll keep you posted..

Xoop.nl main navigationXoops.nl frontpage latest forum posts

Xoops.nl frontpage latest forum posts

Xoops.nl main news overview

Xoops.nl forum frontpage

Xoops.nl forum posts overview

Not only will there be a new jacket around all the nice, relevant and important data, but people are re-thinking about the setup in general.
You”re invited to follow the progress about the redesign part and give us your input here, or on the main Dutch Xoops support website.

Ever wondered if the Xoops code tag could look a bit nicer? Instead of using the ordinairy three (!) sets of elements and classes, we found on the internet a nicer way to display code within Xoops with some help from a small javascript.

First we had to make some changes in one of the Xoops core file, namely the module.textsanitizer.php which can be found in the class directory. Go to line 407 and 411 and change it to the same code you find below.

$replacements = "''
''.MyTextSanitizer::codeSanitizer(''$1'').''

''";\r\n//$text =& $this->xoopsCodeDecode($text);\r\n} else {\r\n// image not allowed\r\n$replacements = "''
''.MyTextSanitizer::codeSanitizer(''$1'', 0).''

''";

You might notice the closing of the p element. We use paragraphs to display our news text, using a code element in p is not permitted, so we make sure it closes before the code element is activated. If you look a bit further you”ll see we close the code element and start a new paragraph. Second point of interest is we named the pre element and gave it the class name “prettyprint”. This class will be used as an indentifier for the javascript.

The script:

Go to code.google.com and download the small script. The package beholds two files, one .js and one .css. Copy those files into you theme directory (we use a js directory for scripts and a stylie directory for our stylies) Then make sure you call them in your main theme file (theme.html)

Stylesheet:

Script call:

Thats all, but hey, they still don”t work. Yes, thats true in some cases. Somehow the javascript isn”t doing his job, meaning, isn”t translating the data. We found that if you altering the body element and force the script to load in your theme.html file is more succesfull.

Voila, nice and colorfull code display! Ofcourse you can tweak and style the pre class a bit more. Here”s how our pre class looks like:

pre.prettyprint {
display: block;
padding: 5px;
margin-left: 25px;
background-color: #eee;
border: 1px solid #d3d3d6;
border-left: 5px solid #D6D6D6;
overflow-x: auto;
width: 85%;
font-family: ''lucida console'', ''Courier New'', monospace;
font-size: 1em;
white-space: pre-wrap; /* css-3 */
white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
white-space: -pre-wrap; /* Opera 4-6 */
white-space: -o-pre-wrap; /* Opera 7 */
word-wrap: break-word; /* Internet Explorer 5.5+ */

That kinda rounds it up, leaving you and your fantasy behind!

Here”s a quote from the Sourceforge Xoops developers forum:’, ‘Quote:

Well, while I was kinda frozen I noticed another thread on Xoops.org:Giba Account hacked and removed! What the hell,.has the Xoops world gone mad? Giba, one of the most helpful and kind persons of Xoops has been attacked personally! I currently have no words, sadness fills my mind, time for some rounds of Counterstrike!