Flexible Content Management System


Modules Development CVS open

Once you finish a module, rather: once you *think* you are finished with a module, let me know via email and I will review it and if it's functioning properly and all, I will merge into the "official" modules repository.

I ask that if you do *not* know what you are doing with CVS, you do not go committing or adding things all over the place ;) Instead, send me an email and I will help you get more familiar with CVS and how to properly add and commit :)

Sometime this weekend I will write-up a guide for module authors as to what requirements need to be met to be accepted as "official". As well, I will work on a guide for starting out in making modules :)

New Release -- Last one for a little while!

Some of the things that we are working on next are some added features that we are including that are already released either as full tarballs, or as addons.

First, pkellum's advance block hack is going to be examined in the next alpha release, with his permission. We think that this will greatly expand some of the features that are wanted and needed with our little project.

You can see an example here

The other news is, we are integrating the ML-Nuke (Multi Language) Nuke into Post-Nuke. We think this will be a very big advancement with the system, that all of us could really learn to love.

You can see an example here

Seperating out more of the core and the plugins are on our list. A couple of other things that we are looking at right now is re-examining the current module system. There is some area of opportunity there, that we might be able to exploit. We are also redesigning the admin interface as well, and working out some bugs in that system as well. I wouldn't expect to see either of these at the end of the week, but they are on our list.

There is also going to be some improvement to the codebase as well, as we start to look at merging the authors and the users table. And we are getting very close to examining the database structure in general.

I hope this keeps everyone in the loop for some of our short term plans.

Post-Nuke Scope, Vision, and Goals

I want to explore where we have been, where we are at right now, and where we are going. I feel to get somewhere, we need to know why and how, just like if we were jumping in our car and going out for the week end. We need to know why we are going, what the goals are, and how we are going to get there, maybe by using a map.

<font class="pn-title">Where we have been</font>

This project started sometime in May. I don't know the exact date, sorry. I was frustrated with the direction that I saw PHP-Nuke headed in. I really thought that we weren't making some of the necessary changes to make Nuke a CMS system that was really universal in scope and vision. It seemed to me that the project was continuing down a spiral of self-destruction because of many factors. Some of which I have explained already in the previous posts on the subject, and I see no reason to bring back up.

What was missing in my opinion was the true vision of what could be. Now, I don't claim to be the sharpest guy in the world, nor do I claim to be the best coder. What I do have are ideas on how things can be universally better for all of us.

I made a post on my site, expressing some of my thoughts, desires, and motives. This started the ideas in a few people. About the same time, Francisco Burzi, made his infamous post about open development, and so the ball started rolling from there. From that post, I was fortunate in finding three other like minded individuals, that shared the same concerns, and the dedication needed for a project this big that is released free of charge.

We spent the next month or so planning where we wanted to go. We also worked on some things that we knew could be done in the short term, and tried to get those together while we talked about the project. We also looked at some of the things that others were working on, to get even more ideas. All of this time was spent planning. We would be no where near the point we are now if we hadn't used this time wisely.

We spent quite a bit of time defining what we thought was the core. I wrote something up at the very beginning of the project that I thought was the core, but you know what? I was way off.

<font class="pn-title">Where we are at now</font>

Some of you might recognize that are project development status is Alpha. Some of you might also ask why we are in Alpha when we are forking from a supposed stable version ( PHP-Nuke 5.0 ). We are taking this time in Alpha status to explore some avenues that we can try to reach our goals. So what does Alpha mean to someone that just wants to install this ap on their website, and let it run? Well, it means that at times, we may release something that is not meant to be released. It also means that a feature that we are looking at might not work as well as we had hoped, or it worked worse than in our dev sites.

It also means that you might be inundated with releases. We will make every attempt possible to release code that is sound, but in Alpha status, you have to keep in mind that we are testing things.

We are trying to also build a community. Everyone is welcome here. Although, the current climate might be more suitable for some one that is accustom to a development atmosphere, I think that we are also doing our best to build up the community. Without the support of everyone that reads this document, we could well loose focus of where we want to go, and in the end we would all loose out. We want to build a better website. Obviously you want to see if there is something better on the horizon, or you would never visit.

<font class="pn-title">Where we are going</font>

Well, here it is in a nutshell of where we want to get to. We want a division of Core to Plugin files ( I'll get to this in a minute ). We want a system that installs without a hitch, that allows you to choose what you want to install to make your website run better and faster. That is what is on our mind. We also want to maintain some semblance to PHP-Nuke in terms of adding abstraction layers to allow you to be able to use all of its add-ons and themes if you so desire.

What's the core?

Quite frankly, the Core is the users system. My original thoughts had the core defined with many things including the content management. However, after our planning and discussions, we concluded that not every site absolutely wants even that. So what does that mean? We are going to shift very soon to focusing on what we have defined as the core of the system, and the rest of the system will be plugin based.

Let's say you want to run a site with just news and links. What we want to do, is allow the core script manage the user portion (which includes your administration functions) and allow you to decide what is right for your website. What is envisioned is that you upload the Core files to your web directory, and then run the install script to install the rest of the plugins. So the install script will install your news files and your link management.

Let's say instead, you want to run a forum, news and reviews. Well then, you will install the Core script, and then run the install file to install the rest. Starting to become clearer to you?

Now there will be other functions that the core will provide, such as the theme for the site, the administration, etc., but as far as managing something, the script will basically manage the users to your website. We want to allow everyone to install a website that is very easy to tailor to your own needs instead of having a ton of extra features that you don't use, or don't even understand why anyone would use them.

So what will this give us? It will give us the ability to have a rock solid stable core to the script, and then focus on the added feature that may not be suited to your needs, but someone else may have. This will allow everyone to enjoy the benefits of a high-end web site application that won't cost a cent to buy. We also hope that by having an open development model, this will speed us to fixing problems, and coming up with solutions to some of the challenges we face.

I hope this shed some light on our focus and objectives. If you have any suggestions or comments, let them be heard.

Stance of phpBB / Phorum and Post-Nuke

We have phorum installed as an experiement more than anything else. We are looking at ways to use the forum plugin to cover the comments sections for every plugin that is offered. Phorum gives us a little easier platform to work on than anything else. That's why it is installed here. It also gives us a chance to have a forum installed with out making everyone either register twice, or installing a buggy integration effort for phpBB. Phorum is also a little easier to work with in a development, because it is a simpler code base. We can make some quick changes, just to see what would happen.

Really, there isn't any conspiracy afoot here. The people that really like Phorum, really like Phorum. The people that really like phpBB, really like phpBB. What is on my mind more than anything else is to give people the choice of what you want to install.

We also understand that phpBB makes sense to have as a plugin, because it was bundled with PHP-Nuke 4.4. As soon as we have some resources free that can look at some of the phpBB integrations around, we will. We will need to implement the CSS, and a few other things to make it much easier for you to deploy, and that's why we need to free up some resources to do this.

We hope to have both a Phorum plugin and a phpBB plugin that gives you a choice. We might actually be a little closer with the phpBB because it has been integrated before, and can allow us to speed development. Eventually, after we have the comments system worked out and an abstract layer in place, we will have a pretty good system in both:)

I hope this makes it a bit clearer as to our intentions.

The GEAR: the *nuke optimization and integration team

our site is not a test one, we'll configure it to make possible a teamwork of my own, with the coders that are creating stuff we'll offer to the post-nuke community.

in the plans, we have a forum... a sure and secure, with extras, and configs that will interest anyone... (multi-threads, last-message icon, private messages, sub-forums, personal avatars, that we'll offer in a future new user.php when your version will be modified, a much better way to configure smilies, etc...

all our tools are made to be used in a folder like /modules/ but we'll call it /gear/ and we'll can our modules via a block or a sideblock... we just wait to see what you want to modify to make possible the call of a addon.php in a block to show it's content (like the chatbox you'll see on our site...)

the IM will be modulated, so if you wish to show the IM as a floating window or a block, admin will have the choice in the install process...

every module or addon we do will have it install process, and everything is configured to use /gear/images/ or /gear/config/ or /gear/emoticons/ ... so you never have to erase or modify any files in your server when you use our stuff... and our icons/emoticons are not the one sent with post-nuke or anyother addon... we have a bank of 1500 emoticons, so we have the choice... mini-emoticons for the blocks, and standard ones in the addon/module.. so it's a better config tho make the block a good size... !!

so be there, we'll make some friends !!!
First Page Previous Page Page 274 / 277 (2731 - 2740 of 2763 Total) Next Page Last Page