Same features that currently exist in iportalx but the main difference is a new backend.
Over the last few years i have been slowly working on a new project that allows me to code in a more OOP style using asp classes. This new "core" (or backend) allows me to shortcut most tedious coding so its much easier and faster to code. It also allows things to be completely seperate yet work together. For example. The entire new portal is HTML template driven. I have one class that does news, another that does themes, another that does the menu module, etc. This allows custom mods to be completely separated so its much easier to keep things updated from a users stand point (their mods never get over written). Each class is a seperate file and is only ran if added to a certain folder (so add a file with a mod, its automatically executed).
It sounds really complicated but turns out to be much easier to code around when trying to make things more modular and easier in the long run. Im currently working on getting a few things added to
www.aspinvision.com to show off these new features. The site itself is running this new core and has been running it for over a year now.
In short, imangine a portal system that is completely template driven, and NOT coded around webwizforums or any other app, and completely modular so you can code one file to change anything without having to mod other files.
Here are some example files:
class_menu.asp
<% Class MenuClass Public Sub Core_Initialize() Core.Requires( "Portal" ) End Sub Public Sub Core_Terminate() End Sub
Public Sub Requirements_loaded() With Portal.Template .enable("Menu")
.blockNew("Menu Item") .blockVar("Link") = "/" .blockVar("Name") = "Home" .blockSave()
.blockNew("Menu Item") .blockVar("Link") = "/forum" .blockVar("Name") = "Message Board" .blockSave()
.blockNew("Menu Item") .blockVar("Link") = "/wiki" .blockVar("Name") = "Wiki" .blockSave() End With End Sub End Class %>
|
template menu.html
[!Menu] <li class="module welcome"> <div class="dTable"> <div class="tHeader"> <h3>Welcome!</h3> </div> <div class="module-body"> <div class="tiHeader"> <h3>Navigation</h3> </div> <div class="tRow"> <div class="inner"> <ul class="navigation"> [!Menu Item] <li class="item"><a href="%MenuItemLink%">%MenuItemName%</a></li> [Menu Item!] </ul> </div> </div> <div class="tRow mT3"> <div class="inner cen" style="padding: 10px;" id="site-controls"> <noscript> <div>Enable Javascript<br />for Site Controls!</div> </noscript> </div> </div> </div> </div> </li> [Menu!]
|
When class_menu.asp is ran it takes the menu.html file and parses it so its a complete menu. The templates also support If statements and a few other niffy things.