1CMS - Version 1.0 Demonstration Domain - By Steph Benoit - So many desires to go forward (not sideways); yet, so little time!

Navigation

· Home
· Advertising
· AvantGo
· Credits
· Downloads
· FAQ
· Feedback
· Forums
· Journal
· Private Messages
· Recommend Us
· Reviews
· Search
· Statistics
· Stories Archive
· Submit News
· Surveys
· Top 10
· Topics
· Web Links
· Your Account

Advertising

1CMS: So many desires to go forward (not sideways); yet, so little time!

After being gone for a year (my first post since last October), let me begin by mentioning that this is more of a blog post of my thoughts than anything else though I'll start a discussion thread on this topic in my forums

I am presently in the (probably) not-so-unique position of pondering exactly where I should be going in terms of moving forward with CMS Software Development.

While it is appealing to work with others on releases with promise, it leaves a bad taste in my mouth to work on any solutions that are (in any way) bound to "nuke" for a variety of reasons, most of which I have written about extensively in other posts, at other times, on other sites (as well as my own).

I don't claim to be anything great in terms of PHP5 coding. My main abilities have simply revolved around fixing existing coding problems relative to nuke's construction (most recently in Nuke 7.8) and implementing 100% W3C Compliant CSS, HTML 4.01 Transitional and XHTML 1.1 Transition standards as well as compliance for all output formats including RSS, XML and a first for Nuke, Atom feeds.

In baseline alone, this was a huge (400+ hours) undertaking. Last year, I simply stopped working on my compilation after November 2005, when going back to work for the Government. I just didn't have the time or inclination to work on my CMS solutions given other serious responsibilities, but I want to emphasize that what this solution became (because of this process) was something, 'beyond nuke'. For a variety of reasons, I kept the code to myself. I'll go into some of the reasons for that later.

After returning this week to scene I've looked around and discovered that there continues to be a number of "packaged nuke" solutions being evolved by many of the same major nuke players of old; however, as has been evident for the past 5 several years the various, "serious" nuke coders have failed to join together in a concerted effort to address the core problems with the application in favor of either earning a living (from advertising and donations on their sites when offering their individual band-aides for the many core faults of EACH AND EVERY VERSION of Nuke), and/or individuals are evolving what they call, "better packages" with some fixes, but all based on that same, flawed baseline code.

To a certain degree, this is where "after-patch" began to part ways with Nuke. I began questioning the assumed norms and concentrated on recoding infrastructure features to work the way they were originally intended as well as finish things that (even after many supposed "final" updates) failed to be finished, all the while concentrating on compliance and removing certain, "assumptions" on how things are handled.

One reason I chose to spend so much time on 7.8 was that there were some core modifications that began to pave the way for input filtering, though on the other hand; a terrible and faulty implementation and extremely poor integration of the TinyMCE editor. While I remain in favor of editor integration, only when the core features have been thoroughly configured, tested and only after new documentation has been created to describe how to import, export, and otherwise manipulate data in those fields. As is typical with "final" versions from phpnuke.org, attention to any kind of detail was completely ignored, leaving new users with unsecured operations and at best partially functional features. Anyone, "upgrading" would discover quickly that old features and functions that had been patched, would no longer work. Once again an official, "final" version of Nuke was released that had more holes and faults than the version before.

This circular issue, where bugs are identified, yet never fixed, where the solution is never actually "evolved", and where everyone must visit 3 other sites just to obtain patches, security fixes and other utilities intended just to secure baseline code are the primary reasons why I believe it a complete waste of time to continue on with anything called, "nuke".

So where is the community now? In my humble opinion, just as fractured as it was before I left. A few individuals have good ideas and directions with promise, but I find myself asking what it would take to get the more serious coders of the community together to start work on a new baseline, where these serious problems won't continuously (with each new so-called, "upgrade") plague the application and those frustrated people trying to use it.

Posted on Friday, October 27, 2006 @ 17:59:08 EDT by 64bitguy

"So many desires to go forward (not sideways); yet, so little time!" | Login/Create an Account | 0 comments

The comments are owned by the poster. We aren't responsible for their content.

No Comments Allowed for Anonymous, please register

Article's Poll

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.