I am introducing a tangent to PHPortal, Mini-PHPortal.
This application is a standalone one-time build of many PHPortal concepts and JSP/Java Ideas in PHP. What will be added to and changed will be the component libaries themselves.
Mini-PHPortal uses my Xpc Templator (http://4arrow.com/test/t/) and PHPortal (http://sf.net/projects/xpc/) Concepts.
The first release will be the last release (as far as I can tell right now) of the core code.
Here is the abstract:
Mini-PHPortal is a Hybrid of PHPortal.
Mini-PHPortal combines the structure of Java Beans, with the interface of JSP Custom tags, and the simplicity of PHP in a completely transparent and utterly modular virtual web intreface middleware for the easy use and production of re-usuable software components.
The basic idea is that we use the PHPortal virtual URIs and map them to a local template file directory structure that maps the URIs being requested. Therefore, all URI requests get sent through the main Mini-PHPortal handler.
Once the Link is requested and handled Mini-PHPortal maps the request to a flat file directory structure.
The template is then called and any accompanying macro files that template builds with.
The template and macro files are then parsed for special Xpc tags. These tags are references to the applications that are then called an acted upon.
These applications follow a specific code structure. Any application that is referenced whether that is a caching application, administrative, Template editor etc.. all come from the same libraries directory and follow the same patterns.
The directory structure is as follows:
Sends all URI requests to the index.php file below
Handles all URI requests sent from the .htaccess file, calls the core libs to do the code run on the URI request.
General and global configs. Per site/domain setup is not built-in like PHPortal it would be a separate application in the 'libraries' directory.
The core classes that are executed on each URI request.
All the applications that are referenced within template tags reside here.
The virtual file directory that matches the URI request and has template tag calls to the libraries applications.
The central idea is that everything is a class library that is called by a template tag reference. This would include the actual template editor, template caching, access rights, and the general administration itself.
Besides the above mentioned tools I will try to build before the initial release I will also try to port the Xpc content type transformations but not necessarily as a core class but instead as a component class. Since it is probably bigger than most it will be a good test case to see what to do in large component type application situations.