Perhaps you could provide here a paragraph or two describing what it does?
"Web portal framework" doesn't tell me much.
| [reply] |
The portal files are kind standard functions for member management login, logout, register new member with some Ajax, password reminder, private messenger Ajax version, admin area, member list, database page view with security levels and Ajax, member profile view/edit/delete, Search, rank is a member XP game that is mainly gained though the Forum.pm in the /lib/modules folder.
The modules folder has Chat, simple wiki, simple faq, Image Gallery, RSS Feeds module, Clock that uses GD and was from some web site...., Error log which shows logged warnings and die error from the system w/delete, Forum is a combo of a Forum/Articles/Polls, server info is a Perl Digger script only works for *nix OS's
There is a Capcha module that a few codes use like login and register.
Before you even get to the some of the codes above there is ban, anti-spam which is experimental along with /lib/TG.pm, stats log - logs user activity, member authentication is a session.
A lot of the development went into the SQLSubLoad.pm file in /lib. The method in that file can help you put subroutine where you want them though out parts of the theme and before the theme loads.
Also uses the AUBBC module i made for a lot of the html tag substitutions and to secure form inputs to the database. A wiki entry in the sql.txt was left about the AUBBC module. It has a lot of tag the portal supports.
Other capability it offers is a tag converter for URL paths to the cgi-bin an none cgi folders. That can be used in the main & member menu and theme editor. sub eval_theme_tags in /lib/theme.pm
Plus a few more thinks that makes life easier.
| [reply] |
I haven't looked at your code yet, but do you mean something like the Everything Engine?
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] |
The description of there system sounds very simpler to what I'm doing. I think they may have took theres a step further with there Template Toolkit. but this is the first time i have heard of Everything Engine and kinda want to install it to check it out.
| [reply] |
The Everything Engine is the basis of our Monastery, although the present incarnation of it in our hallowed halls will probably bear little resemblance to the original!
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
| [reply] |
