What is still to come?

Soon a new templates section will emerge beholding free and payed themes/templates for use in Wordpress or ImpressCMS websites. A section with only static Html templates will also be present.

So, just sit back and make sure you visit us regularly. See you soon.

Getting the archive

Although Manon has been busy doing non internet related things lately, we decided to move her archive from the .nl website into the main .org domain. The downside however is that the blog posts are in Dutch but will be translated later on. Have fun!

Old Core74 layout

Great things are going to happen to Core74. Soon we may present and welcome our new logo meaning the start of a concept we worked hard and long on. A concept that isn’t a revolution, but more a search into our hearts. We’ve planned to enjoy the web once again and embrace new technology, movements and wild ideas.
First, we are going to say goodbye to a content management system we’ve loved for a long time, for us it’s time to move on and explore the cms world once again, and we have found a new love, but more of that later.

Second, we’re going to create a virtual statue of all the people that have influinced us in all of our work, which will be,..well interesting to read, and may be a good start for beginning web artists.

Thirdly,.we are going to promote our hosting facilities. Born from the needs from design clients, grown as a stable platform and gateway towards internet.

Four. We again going to build free and commercial themes and templates. Themes for a diversity of content manegement systems, and the lower priced (x)html templates.

So visit us regularly, have a nice cup of coffee and we’ll speak to you soon;)

Normally we use the famous famfamfam icon set to spice things up, but for the priority buttons we could not find an equal match, so, we made some of our own.

Set I

priority small set I:

priority big set I:

priority print small set I:

Download the full zipped set I package here!

Set II

priority small set II:

priority big set II:

priority print small set II:

Download the full zipped set II package here!

Just copy the image files into the /path/to/xhelp/images directory. For your own sake, make sure you backup your old images(!), you have been warned.If you use these images, it’’s always a nice thing to link to us. You may use these images for personal or commercial use, alter them or send them to a friend as a present, but you may not sell them in anyway.

Why?

Well, it seems a lot of important people of the Xoops community aren”t able to work together anymore, so it’’s almost logical that this would happen. I don”t want to go into the political details, because I really don”t care about the Xoops-politics, I only care that there is a production of many tools that will make me, my clients, and all other contributors happy in “any way what so ever”.

So you are part of the fork?

Yes, after talking to some friends about the switch I can tell you that I also will try to contribute my knowledge to ImpressCMS.

Does this mean you”ll stop supporting Xoops?

Not at all, I will carry on designing websites for Xoops, I just have extended my base of content management systems. Furthermore, I will keep supporting the Dutch Xoops Community in all possible manners.Discuss the news post here!

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!

So where are we now?

Well, no where. Our team leader has brought his pencils back to Xoops, an action we have followed as well. The main reason for us to be in the team was because of it’’s leader. A man with a vision who didn”t get the attention he needed to bring Xoops to a higher level. Sad? Well yes. Xoops now missed a chance to be a ”really” great (Design, SEO, functionality, etc wise) cms. Now Xoops never will loose it’’s Phpnuke legacy and remains what it always was, a Phpnuke fork.

Aren”t you too hard?

Yes I am, it’’s more frustration that is talking rather then my rational side. However, we will keep supporting Xoops, just a little less then we intended to.

Should we use or continue using Xoops?

Yes please, I believe among all those Xoops users there are people who are able to push red flagged buttons which will change the face of Xoops forever. It just wasn”t meant to be for us to give something new at this moment.

Final word.

Although we will not communicate our leaving on Xoops.org (we will not feed the sharks, but will fight them if needed), we now officially quit the Design team. We are not going to write about this any further, and look at it as a lesson of life. We wish all official and unofficial teams good luck, and we are sure we will meet once again.