Clan x86

AdvancedContent has moved on and given way to Digital Text CMS.
AdvancedContent was based on the theory of providing the user with basic things (downloads, forum, etc.) as opposed to doing what I wanted it to do...manage content.

Digital Text will have this ability. You will be able to add pages (static HTML for the most part) and moduels (dynamic stuff).

AdvancedContent used it's own template engine which wasn't too shabby but it was a bit restrictive and made things over complicated.
Digital Text uses Smarty (smarty.php.net) an awesome template engine which makes templating easy and FLEXIBLE for the user. (Instead of me organizing the output of say an array of news entries, the user can himself using built in things to loop through arrays passed to the template)-- this results in a GREAT increase in flexibility to the designer and less hassle to the programmer.

The big advantage I think this will have is it's compact size. Since none of the things in AdvancedContent (forums, downloads, news, pm) are implemented into the core the CMS keeps a small size which allows it to be easily adapted to any purpose.

A live demo (live meaning being worked on) is availible at: www.advancedcontent.net/demo (As of now it is not very interactive just some output)

Quote from: Warriorx86] link=topic=4009.msg42433#msg42433 date=1133690588]
Digital Text uses Smarty (smarty.php.net) an awesome template engine which makes templating easy and FLEXIBLE for the user.

Copier (http://www.sidoh.org/test/scms/index.php/news/full/60).

Ersan told me about this a while back. Actually smarty is pretty easy to use on all servers, you just plop it in a dir (/lib) and instantiate the class Smarty (include Smarty.class.php)

Hmm got a lot of planning to do with how things will interact with each other, going to sleep on it.

Quote from: Warriorx86] link=topic=4009.msg42438#msg42438 date=1133690841]
Ersan told me about this a while back. Actually smarty is pretty easy to use on all servers, you just plop it in a dir (/lib) and instantiate the class Smarty (include Smarty.class.php)

I'm using it, noob.  :P

That entire CMS (www.sidoh.org/test/scms) uses Smarty.  I've extended the smarty engine slightly to fit the way I want my CMS to work.  It's not very significant, but it saves time and keystrokes.

By the way, it's better to just 'plop' a /smarty directory somewhere within your CMS.  Installing it otherwise would be too much of a hassle.

Quote from: Sidoh on December 04, 2005, 05:10:48 AM

Quote from: Warriorx86] link=topic=4009.msg42438#msg42438 date=1133690841]
Ersan told me about this a while back. Actually smarty is pretty easy to use on all servers, you just plop it in a dir (/lib) and instantiate the class Smarty (include Smarty.class.php)

I'm using it, noob.  :P

That entire CMS (www.sidoh.org/test/scms) uses Smarty.  I've extended the smarty engine slightly to fit the way I want my CMS to work.  It's not very significant, but it saves time and keystrokes.

By the way, it's better to just 'plop' a /smarty directory somewhere within your CMS.  Installing it otherwise would be too much of a hassle.

Haha same here, I wrote a class which extends smarty and implemented an abstraction layer of sorts because I am a control freak. Like yours not very vital significant changes (maybe automating a few things here+there, nothing big)

Well yea by "plop" I meant in a dir within your CMS, oops.

Quote from: Warriorx86] link=topic=4009.msg42442#msg42442 date=1133691257]
Haha same here, I wrote a class which extends smarty and implemented an abstraction layer of sorts because I am a control freak. Like yours not very vital significant changes (maybe automating a few things here+there, nothing big)

Well yea by "plop" I meant in a dir within your CMS, oops.

I wasn't aware that /lib was a common DocumentRoot.  :P

I use it anyway.

/demo/lib/smarty
/demo/templates
/demo/templates_c
/demo/cache
/includes

Everything with the CMS no special installation no hassle :)

Quote from: Warriorx86] link=topic=4009.msg42467#msg42467 date=1133716683]
I use it anyway.

/demo/lib/smarty
/demo/templates
/demo/templates_c
/demo/cache
/includes

Everything with the CMS no special installation no hassle :)

Haha.  I installed it in /<DocumentRoot>/test/scms/classes/smarty.  Also, why wouldn't you set up /demo/configs given your naming pattern?

I havn't used them, I plan to use them though for multi language support possibly.

Quote from: Warriorx86] link=topic=4009.msg42496#msg42496 date=1133721910]
I havn't used them, I plan to use them though for multi language support possibly.

Hehe, that's a great use of them.

Smarty's really nice, but it's hard to know when to use PHP for your core instead of using Smarty for templates.  It's difficult to seperate layout from core like that in some respects.  I think I was talking to iago about this a while ago.  He said he thought the whole idea of templates was so you could keep the graphic designers away from your code, but Smarty actually encourages them to interact with the code.  I suppose that's a positive and negative thing, really.

I suggest you create a "features" section of your site containing links to code, and build in the "obtain feature list" function that gives the ACP a list of available features, with links to click to install said features. That way people can install the basic core, and customize it later (IE: Adding PM with the click of one link, etc.)

I don't know I plan to take a simplistic approach at this. I read anything in the /mod folder and mark it as a possible module.
A module to be loaded must communicate with the core and identify itself. I guess I can perhaps mark them as "Loaded" or "Non Loaded" to get the effect of starting and stopping it. Maybe.

I'm still cleaning up some things in the core and writing my authentication class to do stuff with templates.

Quote from: Quik on December 04, 2005, 03:27:36 PM
I suggest you create a "features" section of your site containing links to code, and build in the "obtain feature list" function that gives the ACP a list of available features, with links to click to install said features. That way people can install the basic core, and customize it later (IE: Adding PM with the click of one link, etc.)

Taking this sort of approach for this kind of project wouldn't work all that well, assuming he's using the templating method I'm imagining.  It would be hard to implement a plugin-like interface if everything is going to be templated.  You'd have to develop templates for all of your plugins.  :\

Quote from: Warriorx86] link=topic=4009.msg42521#msg42521 date=1133728874]
I don't know I plan to take a simplistic approach at this. I read anything in the /mod folder and mark it as a possible module.
A module to be loaded must communicate with the core and identify itself. I guess I can perhaps mark them as "Loaded" or "Non Loaded" to get the effect of starting and stopping it. Maybe.

I'm still cleaning up some things in the core and writing my authentication class to do stuff with templates.

Hehe, I'm thinking about doing something like that for the CMS I'm starting to write now too.  We'll see... Like I've already mentioned, making everything templated using this structure's going to be a challenge.

Why don't you two just team up?  You're doing very similiar things...

Quote from: Blaze on December 04, 2005, 04:26:22 PM
Why don't you two just team up?  You're doing very similiar things...

I, for one, am doing this for experience.  I have no intention for this to become some popularly used CMS or anyting.  Warrior, on the other hand, seems to want to release this (multilanguage support! :)).

I normally wouldn't mind teaming up with him (regardless of my past statements), but I'm in a bind with the amount of time I've had lately.  My school schedules in addition to the craze of applying for colleges and scholarships have been driving me up the wall lately.

Well I'm trying to find a medium between widely used and not so widely used. Not trying to have this be supper dazzling. Just a simple solution to the everyday problem of building a good website.

Quote from: Warriorx86] link=topic=4009.msg42542#msg42542 date=1133734722]
Well I'm trying to find a medium between widely used and not so widely used. Not trying to have this be supper dazzling. Just a simple solution to the everyday problem of building a good website.

Seeing as how I don't plan on releasing my CMS, I'm tailoring it around my personal wants. :]

One of you should custom-tailor one for my personal needs. ;)

Quote from: Quik on December 04, 2005, 08:04:51 PM
One of you should custom-tailor one for my personal needs. ;)

I was thinking the same thing.  :o

The way I'm programming this, it wouldn't be too hard for the user to custom tailor it to his old needs via modifications made to modules and static pages created. This thing is fully themeable and with the use of smarty for the designer you can control how your output will look in the smallest ways.

A few updates: The core now properly handles errors thrown by the page loader.
                      I have implemented an authentication class which sets a variable in the template so that users can see if you are logged in.
                     Now as Sidoh said there are some issues with what should be a template, what should be a module, and whatever.
                     I'm thinking about having the "bare" essentials as part of the core such as Authentication and User registration. But another issue comes to mind like managing user information and how to extend that with the use of modules. Perhaps write a module to dynamically fetch rows and things to update as they are added. Dunno just scribbling some thoughts down.
                    I have also started implementing my modules subsystem into the core. So far it just reads the modules directory and locates all the files needed and if it is not found then it throws and error to the core (most likely will be a fatal one too). 


Todo list:
             Design some user interfaces for when a user logs in, maybe have modules marked as "List only when logged in" or something I'll think more into this
             Fidn a way to isolate all the cores function from the modules since currently I am exposing the entire core. Perhaps create sort of a "Communication pipeline" as in Module grabs Core's anttention Module does the requested data and Module closes stream. This could be overcompliating things but whatever.

 

Update:
Implemented simple modules by simple I mean VERY simple but effective. I might stick with this to maintain my simplistic approach to things.

I have a few bugs to fix on my todo list (No exploits just goofs) but I'm too tired to do it.
I'll post a source code section tomorrow as soon as I get home from school.

Quote from: Warriorx86] link=topic=4009.msg43097#msg43097 date=1133933513]
Update:
Implemented simple modules by simple I mean VERY simple but effective. I might stick with this to maintain my simplistic approach to things.

I have a few bugs to fix on my todo list (No exploits just goofs) but I'm too tired to do it.
I'll post a source code section tomorrow as soon as I get home from school.

Dude, reply to the PM I sent you.  Fag.

I did, the site must not be sending them again omfg. Anyways @ the PM: Sure.

Quote from: Warriorx86] link=topic=4009.msg43109#msg43109 date=1133935647]
I did, the site must not be sending them again omfg. Anyways @ the PM: Sure.

Ugh, that's so gay.

Alright, thanks.  :)

After around 20 minutes of coding I fixed the navigational bug(s) and implemented a simple login module (To be extended on later) I'm doing some more thinking on things relating login and how other things in the future will work but that's for another time

Anyhow here's some example code of how I fixed it:


if ($DB->GetRowCount($query) == 0)
{
$Disp->assign("Nav_Count", 0);
} else {
$nav_array = array();
$i = 0;

while ($result = $DB->FetchArray($query))
{
$nav_array[$i]['name'] = $result['Name'];
$nav_array[$i]['link'] = "index.php?page=" . $result['Name'];
$i++;
}

$query = $DB->PerformQuery("SELECT ModName FROM site_mods");

while ($result = $DB->FetchArray($query))
{
$nav_array[$i]['name'] = $result['ModName'];
$nav_array[$i]['link'] = "index.php?mod=" . $result['ModName'];
$i++;
}

$Disp->assign("Nav_Count", count($nav_array)); // FIXED invalid number count
$Disp->assign("Nav_Item", $nav_array);
}

$Module->SetModule($mod);

$Disp->Show();


And here is the templating code:


{if $Nav_Count}
{foreach from=$Nav_Item item=nav}
<a href="{$nav.link}">{$nav.name|capitalize}</a><br />
{/foreach}
{/if}


As a suggestion, you may want to consider the possiblity of someone supplying an image as a link ($nav.name) as opposed to a plaintext one.  I don't suppose this would matter much since capital "<" is just "<", but I don't know if you'd want to do any additional parsing for something like this.

$nav.name is the name of the module eg. "test" -> "Test" (I think this is what you mean)

Anyhow I've learned the helpfulness of globals (Passing objects from core to module :D)

Quote from: Warriorx86] link=topic=4009.msg43347#msg43347 date=1134025900]
$nav.name is the name of the module eg. "test" -> "Test" (I think this is what you mean)

Anyhow I've learned the helpfulness of globals (Passing objects from core to module :D)

Haha, yeah.

Globals are nice, but I wish that PHP would have an implements method for its OO capability, that'd make things so much cleaner...

I thought PHP5 had this *shrug* that's not widely used anyhow.

I was in an especially tight bind because some of my classes take params in thier constructors which are essential to how it's run (example: $DB = new dtDatabase($settings['dbtype']) and settings is $settings = GetSettings();) and I had no idea how to pass that from config.php to the core to the module so globals worked perfectly here.

I was also faced with a setback because I was previously using array_push() but I don't think it can push associative arrays. Oh well I use a (imho) cleaner method now.

I think most of the major coding of the CMS is done though :)

Quote from: Warriorx86] link=topic=4009.msg43350#msg43350 date=1134026753]
I thought PHP5 had this *shrug* that's not widely used anyhow.

I was in an especially tight bind because some of my classes take params in thier constructors which are essential to how it's run (example: $DB = new dtDatabase($settings['dbtype']) and settings is $settings = GetSettings();) and I had no idea how to pass that from config.php to the core to the module so globals worked perfectly here.

I was also faced with a setback because I was previously using array_push() but I don't think it can push associative arrays. Oh well I use a (imho) cleaner method now.

I think most of the major coding of the CMS is done though :)

RTFM (http://www.php.net/manual/en/language.oop5.php).  Just kidding.  implements is a widely used OO structure in other OOP languages, just look at some of the Java code from JavaOp or something.

Yeah, other than passing them as params (which is really stupid to begin with), globals are the only way I'm aware of to share variables/objects between classes (unless you use a long line of extends classes, which is dumb anyway).

In my opinion, array_push is a pretty useless function.  As I'm sure you're aware, it has the same affect as:


$v = array();

v[] = '0';


Yea. Why would I want to read something on PHP5!? :P.

array_push() was getting annoying so while looking through some old advancedcontent code I saw I did it like this in some places (Saved by my old code!).

I like my current CMS' state it's pretty powerful yet small. I can't see any bugs in it (except some warnings PHP would generate if I do something withought checking another which I'll fix) all that I really lack is the time to sit down and write some modules.

Quote from: Warriorx86] link=topic=4009.msg43356#msg43356 date=1134028076]
Yea. Why would I want to read something on PHP5!? :P.

array_push() was getting annoying so while looking through some old advancedcontent code I saw I did it like this in some places (Saved by my old code!).

I like my current CMS' state it's pretty powerful yet small. I can't see any bugs in it (except some warnings PHP would generate if I do something withought checking another which I'll fix) all that I really lack is the time to sit down and write some modules.

Haha.  Its funny that they'd even have a function that can be replaced with an operator.  It's like having an add() function.  Oh well, haha.

That's what we call "efficient!" :P

Okay I decided to keep my modules in this simplistic format maybe improve on it with some identification abilities (Make them able to inherit a class from thier own probably thier own class spawned on thier creation so they can identify themselves if they'd like but that would allow them to do evil things (Like include themselves endlessly but then again, who'd use a malicious module!?). Yea I'll probably do a little more thinking but for now I think I'll leave it this way.

I'm going to start working on some basic modules to show off the functionality of the core and get around to seeing if theres any optimizations I can make before releasing a stable "beta1"

Quote from: Warriorx86] link=topic=4009.msg43428#msg43428 date=1134074408]
Okay I decided to keep my modules in this simplistic format maybe improve on it with some identification abilities (Make them able to inherit a class from thier own probably thier own class spawned on thier creation so they can identify themselves if they'd like but that would allow them to do evil things (Like include themselves endlessly but then again, who'd use a malicious module!?). Yea I'll probably do a little more thinking but for now I think I'll leave it this way.

I'm going to start working on some basic modules to show off the functionality of the core and get around to seeing if theres any optimizations I can make before releasing a stable "beta1"

If they'd like to?  You're making it sound like they have minds of their own!  Scary.

Haha after rereading it is sorta scary. Anyhow I havn't implemented anything new yet but I was testing my modules and wrote a simple news one, here it is:

<?php	global $Disp;	global $DB;		$Display = new dtDisplay("news.tpl");		$action = $_GET['action'];		switch ($action)	{		case "":			$query = $DB->PerformQuery("SELECT * FROM site_news LIMIT 1");						if ($DB->GetRowCount($query) == 0)			{				$Disp->assign("News_Count", 0);			} else {				$news_array = array();				$i = 0;								while ($result = $DB->FetchArray($query))				{					$news_array[$i]['Subject'] = $result['Subject'];					$news_array[$i]['Author'] = $result['Author'];					$news_array[$i]['Message'] = nl2br($result['Message']);					$i++;				}								$Display->assign("News_Count", $i);				$Display->assign("News_Item", $news_array);							}						$Disp->assign("Content", $Display->fetch("news.tpl"));			break;	}?>




<?php	/* LiquidDev		Professional Scripting	   	   @author: Nelson Carrillo	 */class dtModules{		function SetModule($mod)	{				if (!$this->Exists($mod))			$this->Create($mod);				$this->Perform($mod);	}			function Exists($mod)	{		$settings = GetSettings();		$DB = new dtDatabase($settings['dbtype']);		$query = "SELECT * FROM site_mods WHERE ModName='" . $mod . "'";				if ($DB->GetRowCount($DB->PerformQuery($query)) == 0)			return false;		else			return true;	}		function Create($mod)	{		$settings = GetSettings();		$DB = new dtDatabase($settings['dbtype']);				$query = $DB->PerformQuery("INSERT INTO site_mods SET ModName='" . $mod . "'");				// TODO: Check the query.				return;	}		function Perform($mod)	{		include_once("modules/" . $mod . "/index.php"); // TODO: Check to make sure this file exists!	}}?>

<?phpclass module extends dtModules {  function do_this()    ...}?>

<?phpfunction ModuleInit(){	global $SiteCanvas;	$Canvas1 = new DisplaySystem;		// Now for the SiteCanvas you MUST assign {PageContent} with something to draw to it so we do this		$Canvas1->assign("MyVar", "MyVal");	$Canvas1->assign("MyVar2", "MyVal2");	$SiteCanvas->assign("PageContent", $Canvas1->Fetch("whatever.tpl");		return;}?>

<?php// Some constantsdefine('VW_MAIN', 0);define('VW_CREATE', 1);define('VW_EDIT', 2);define('VW_DELETE', 3);// Some errorsdefine ('VW_NOERR', 0);define ('VW_ERRACTN', 1);define ('VW_BADMOD', 2);class MMCore{	var $DB;	var $ModuleName;	var $View;	var $ManagerCanvas;		function HandlePage($view, $name = NULL)	{		if ($name != NULL)		{			if (!$this->Exists($name))				return VW_BADMOD;						$view = VW_EDIT;			$this->ModuleName = $name		}				$this->DB = new DatabaseSystem;		$this->View = $view;		$usingSys = true;		$this->ManagerCanvas = new DisplaySystem($usingSys);				switch ($this->View)		{			case VW_MAIN:				$this->HandleMain();				break;			case VW_CREATE:				$this->HandleCreate();				break;			case VW_EDIT:				break;			case VW_DELETE:				break;			default:				break;		}				return VW_NOERR;	}		function HandleMain()	{			if (!empty($this->ModuleName))		{			$this->ManagerCanvas->assign("SingleModule", true);			// Display information about the module			if (is_array($result))			{			} else {				// Log an error about failing to fetch here				// Display "Unable to Fetch"				$this->ManagerCanvas->assign("ModuleName", $this->ModuleName);				$this->ManagerCanvas->assign("ModuleVersion", "Unable to Fetch");				$this->ManagerCanvas->assign("ModuleAuthor", "Unable to Fetch");				$this->ManagerCanvas->assign("ModuleDescription", "Unable to Fetch");			}		} else {			$this->ManagerCanvas->assign("SingleModule", false);			// Done		}				return VW_NOERR;	}		function HandleCreate()	{		if ($_POST)		{			// Been posted, use sLayer to check it's integrity		} else {			if (!empty($this->ModuleName))			{				// Dont display			} else {				// Display			}		}				return VW_NOERR;	}	}?>