Thanks, that's the info I was looking for

Quote:

Ok, if I understand you correctly: the OO is "inside" XOOPS and is not meant to be used by users who build websites with XOOPS? Let me put it another way: you only "see" the OO when you develop the XOOPS base system, but not if you are just "implement" websites?

What I'm looking for is a CMS where you (=the user) can define classes whose instances form the buildings blocks of the website, like you have a class "Text" and an instance "All about XOOPS" and a class "News" and an instance "XOOPS News", and each of these classes have methods and variables and classes can inherit from other classes.

As the documentation is not too exhaustive - if I understand it correctly:
- I can extend these abstract classes, but can I also extend existing classes (i.e. types)? For example, can I extend XOBJ_DTYPE_INT to, say, XOBJ_DTYPE_SHORTINT?
- how can I add methods and variables to newly defined classes?
- and where's polymorphism, encapsulation and abstraction?

...what I mean: there's (much!) more to object orientation than just having 2 abstract classes...I was hoping to find a CMS that does have "real" OO onboard. Or maybe I'm just missing something here?

Hi,


I stumbled upon XOOPS while googling for object-oriented CMS...I just browsed around the site but didn't find any in-depth information about the object-oriented character of XOOPS. So, could anyone explain how and where XOOPS is OO?

Particularly, I didn't find any clue for essential OO features like:
- classes and instances
- methods in classes/objects
- inheritance upon classes, polymorphism
- encapsulation and abstraction

I'm sorry if I didn't dive into XOOPS enough to discover these features...*provokingly* or is the "OO" in XOOPS not really justified?


Thanks in advance,
Patrick