International Sites:

Hierarchy of Portalsuite Objects

The following illustration shows the pedigree with its most important classes.

As usual in the object-oriented world, the arrows in the illustration always point at the ancestors.

This pedigree is absolutely elementary and you will consult it consistently, because only if you know - for instance - that Pcontentarticle is derived from Pcontent PObjects and this class again is derived from Pobjects, you will be able to use these objects effectively. Each new class you will encounter over time has properties and methods you are already familiar with due to its parentage and root objects. You solely have to get to know the newly accrued properties and methods differing and defining one object from its ancestor.

Being familiar with the objects provided by the Portalsuite in the Portalsuite objects world is an assumption for developing and creating portals and portal applications. There is no such thing as a perfect world and hierarchy in the OOP. It takes some experience as well as acceptance of compromise to decide which object has to get which properties and methods and which object consequently has to spring from which other. You profit from our experience with the Portunity "Portalsuite objects" in developing your own portals and portal applications. Of course the “Portalsuite objects“ is only a vantage point you should use to realize your own functionality and effects with your own classes and objects.

Continue to recommend this article:

Direct links to the new Portalsuite 2002:

- Productinfos
- Download

- Support overview
- Support forum