MidCOM 1.0

Operating systemsOS : Windows / Linux / BSD / Solaris
Program licensingScript Licensing : GPL - GNU Public License
CreatedCreated : Jul 18, 2007
Size downloadDownloads : 3
Program licensing
Thank you for voting...

<i>MidCOM</i> is component framework for PHP running ...

midcom by The Midgard Project is component framework for PHP running on top of the Midgard framework. MidCOM 1.0 provides a full content management system based on a series of components. MidCOM [midcom1.0.exe] users can build their web by "clicking together" a directory hierarchy, each folder being managed by the appropriate component.
MidCOM - 0MB components are distributed as PEAR packages that allows easy installation and maintenance of the environment.
Ideally, a MidCOM 1.0-based web site consists of one or more Components only, though midgard's fundamental design makes it very easy to use MidCOM along with traditional midgard applications or web sites and even with plain file-based web content.
Every Component contains a complete application module: It might depend on other Components to work, but it should fulfil a defined task independently. For example, a MidCOM Component could handle the management and display of a certain article type ("product information", "news item") on a web site. In a web-based application environment, it may contain the whole web frontend of a custom-built CRM system. After all, it is up to the Component author to define how broad or narrow to design its features.
Technically speaking, MidCOM establishes a Model-View-Controller concept within Midgard. This specification primarily defines the outline of component packaging. A component in this sense is the combination of business logic (what to do), default configuration (default data structure, default operation mode) and default style (default presentation information).
A correctly designed component can be deployed to another Midgard installation by simply importing the component's XML file and creating a site-specific style (HTML design) for it. Therefore, the ideal MidCOM Website completely relies on its components having no application-specific logic anywhere else than within the components themselves.
Each component exposes a strictly defined interface to the underlying midcom_framework and Midgard itself. MidCOM uses Midgard's topic tree to link incoming HTTP requests to their corresponding Components, thus controlling a Component's assignment to a certain area of a web site or a certain type of content object. Using the topic tree instead of the page tree - which has the same role in traditional Midgard environments - gives users much more flexibility for providing advanced features. The Component code itself is completely encaspulated in snippets, which makes replication and packaging as easy as possible.
The MidCOM framework passes requests to the Components, provides support for them in several areas (such as building a consistent navigation interface for a complex web site with multiple independent Components) and assembles their data management capabilities into a single administration interface to the user. For example, a secretary managing the news and press sections of her company web site does neither feel nor needs to know that she is working with two different Components as she makes her changes within a consistently designed CMS interface.

MidCOM 1.0 scripting tags: midcom, development tools, default, midcom tools, components, midgard, framework, web, midcom framework. What is new in MidCOM 1.0 software script? - Unable to find MidCOM 1.0 news. What is improvements are expecting? Newly-made MidCOM 1.1 will be downloaded from here. You may download directly. Please write the reviews of the MidCOM. License limitations are unspecified.