What is e-Xoops?
  • 2003/10/5 23:41

  • Hanan

  • Just popping in

  • Posts: 7

  • Since: 2003/7/31

Just a bit confused. Wahta the different between XOOPS and e-xoops?

Re: What is e-Xoops?
  • 2003/10/5 23:50

  • djsckizo

  • Just can't stay away

  • Posts: 401

  • Since: 2003/5/9 8

This other cms program that doesn't work right and doesn't want to install for me so I say "eat the cheddar!" to it and use XOOPS instead. XOOPS is much easier I assume but since I could never get e-xoops to even load correctly, I have no idea. However, all of their skins appear to be duplicates of the same lame thing and really ugly at that.

Oh, and XOOPS is supported like crazy. There appears to be a lot more going for XOOPS than e-xoops, which was a very original name.

Re: What is e-Xoops?

e-xoops is a branch of XOOPS based upon the old 1.x version of Xoops. The release of e-xoops is not welcomed by the XOOPS developers.

Re: What is e-Xoops?
  • 2003/10/6 0:44

  • djsckizo

  • Just can't stay away

  • Posts: 401

  • Since: 2003/5/9 8

All together, let's fart in their general direction.

Re: What is e-Xoops?
  • 2003/10/6 7:24

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1

Normally not being one to dig up old grudges, but the fact of the matter is that eXoops is a XOOPS1 fork by Half-Dead, who didn't agree on the devs descision to go with Smarty. His disagreement led him to take the CVS code (which is ok), and started his own fork (which is also ok, albeit he didn't do it in a friendly fashion). The grudge the devs hold over e-Xoops is that Half-Dead removed the credits and copyrights of the CVS code, and with little to no adjustments released it as his own... That, by any standard, is plain rude and illegal as well, since the code was released under the GNU-GPL licence.

This was a looong time ago, and XOOPS has moved on, since. The fact remains that a lot of confusion is created by the name eXoops, and the main differences. Personally, I support XOOPS and think that eXOOPS has been left behind when we moved to smarty. But please jedge yourself


Re: What is e-Xoops?
  • 2003/10/6 10:47

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9

thanks for clearing that up for me as i wondered what that was as well...
Maybe this is somethin you should add to a faq somewhere as i've used XOOPS for a while now and had no idea where to look for answers.
On another note what exactly is this smarty term all about.
I kinda guess i've used it as i've done some messing around with themes and stuff but i dont know 'exactly' what it is?

Re: What is e-Xoops?

On another note what exactly is this smarty term all about...?

Smarty is a template cache system that dramatically decreases the number of database queries required to generate a page, helps to separate presentation from content to limit theme parsing overhead, and "remembers" compiled PHP. This improves performance, allowing the benefits of a database-driven site with performance comparable to a static site.

For example, if you cache the forum block with a 10-minute setting, the queries and compiling required to produce the forum block will occur every 10 minutes, instead of every time a user requests a page.

By choosing the Smarty cache system, the developers can focus on XOOPS development without worrying about developing or improving the cache.

More information about Smarty can be found at:

Re: What is e-Xoops?
  • 2003/10/7 7:08

  • djsckizo

  • Just can't stay away

  • Posts: 401

  • Since: 2003/5/9 8

You'd think he could have atleast been original enough to call it 'myphpxoopsnukedgeekloginvisionboardbb'.

Re: What is Smarty? [more data]... (was: What is e-Xoops?)
  • 2003/10/7 9:58

  • Mikhail

  • Just can't stay away

  • Posts: 412

  • Since: 2003/1/19

Resized Image

Smarty is a template engine for PHP. More specifically, it facilitates a manageable way to separate application logic and content from its presentation. This is best described in a situation where the application programmer and the template designer play different roles, or in most cases are not the same person.

For example, let's say you are creating a web page that is displaying a newspaper article. The article headline, tagline, author and body are content elements, they contain no information about how they will be presented. They are passed into Smarty by the application, then the template designer edits the templates and uses a combination of HTML tags and template tags to format the presentation of these elements (HTML tables, background colors, font sizes, style sheets, etc.) One day the programmer needs to change the way the article content is retrieved (a change in application logic.) This change does not affect the template designer, the content will still arrive in the template exactly the same. Likewise, if the template designer wants to completely redesign the templates, this requires no changes to the application logic. Therefore, the programmer can make changes to the application logic without the need to restructure templates, and the template designer can make changes to templates without breaking application logic.

Now for a short word on what Smarty does NOT do. Smarty does not attempt to completely separate logic from the templates. There is no problem with logic in your templates under the condition that this logic is strictly for presentation. A word of advice: keep application logic out of the templates, and presentation logic out of the application. This will most definately keep things manageable and scalable for the foreseeable future.

One of the unique aspects about Smarty is the template compling. This means Smarty reads the template files and creates PHP scripts from them. Once they are created, they are executed from then on. Therefore there is no costly template file parsing for each request, and each template can take full advantage of PHP compiler cache solutions such as Zend Accelerator (http://www.zend.com) or PHP Accelerator (http://www.php-accelerator.co.uk).

Some of Smarty's features:

* It is extremely fast.
* It is efficient since the PHP parser does the dirty work.
* No template parsing overhead, only compiles once.
* It is smart about recompiling only the template files that have changed.
* You can make custom functions and custom variable modifiers, so the template language is extremely extensible.
* Configurable template delimiter tag syntax, so you can use {}, {{}}, <!--{}-->, etc.
* The if/elseif/else/endif constructs are passed to the PHP parser, so the {if ...} expression syntax can be as simple or as complex as you like.
* Unlimited nesting of sections, ifs, etc. allowed.
* It is possible to embed PHP code right in your template files, although this may not be needed (nor recommended) since the engine is so customizable.
* Built-in caching support
* Arbitrary template sources
* Custom cache handling functions
* Plugin architecture

Re: What is Smarty? [more data]...
  • 2003/10/7 11:39

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9

Thats great you guys... it all makes sense now and i can see why you decided to adopt it.
(if it isnt id chuck that in the faq somewhere)
keep up the good work!


Who's Online

53 user(s) are online (32 user(s) are browsing Support Forums)

Members: 0

Guests: 53



Goal: $100.00
Due Date: Aug 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits