View All Screenshots
Loading File Manager ...
|
Find out dates of each version |
Since the day I got my first Apple IIc computer at age 10 and started learning Apple Basic I have always attempted to develop the same type of applications, content management systems. I really don't know why but I have always had a desire to catalog everything in my life in digital form. Perhaps it's because I feel I have a poor memory, or perhaps, being the insane technology nerd that is mreschke, I am constantly filling my mind with every form of advanced technology that I can get my hands on. Whatever the reason, my personal programming projects have always been centered around the input and delivery of content, usually text content of my own authoring.mReschke 2011-04-14 |
This topic contains a very basic mrcore revision history. Up until mrcore version 4.0 I did not keep records of my releases, so pre 4.0 documentation is very sparse. This is just a basic overview of the main revision numbers along with a few screen shots of all the different theme changes (that I have kept track of). The full revision and SVN source control history is contained in my personal Trac website. |
The original mrcore was a frame based, multiuser (by subdomains) PHP framework for building web content. The system was designed to be multiuser. Each user could have their personal site with their own skin and their own content. The url to their site was their username.mreschke.com. So each user was a subdomain (or profile as they were called). The default (blank profile template) application consisted of a blue header frame with the mReschke logo in the left corner. There was a blue left frame, below the header which had a 'home' and 'login or logout' link, along with a very cool, but very poorly designed, javascript tree view of definable links and folders/subfolders. I could control which treeview links every user had by modifying the default.mreschke.com profile. In the default treeview links, there was a 'File Manager' and 'Link Manager' link. These were the two primary applications contained in mrcore. The link manager allowed the user to modify their treeview links and folders. You could create/rename/delete/move folders, and create/rename/delete/move links. You could also specify a custom icon for each link, and its link targer (_top, _blank...). You could also set folders or links to public (the world) or private (only you). The File Manager looked very similar to the link manager, but managed the files in the profiles home directory, rather that the mr_links MySQL database table. Each profiles home directory was web accessible (via IIS as the original time) through their subdomain. So by using the filemanager to edit their index.php file, they could modify their username.mreschke.com home page. Basically, mrcore 1.0 was a web based filemanager, and a very simple "core" frame layout with authentication functions.I was not very familiar with wikis or blogs at that time, nor was I knowledgeable enough to code one.The original mrcore did not contain a wiki system, it basically a user editable website which could be customized per subdomain. It was very basic and frame based, written sometime in 2004 - 2005. It was a multiuser system. Each user, or profile as they were called, was also the subdomain. So mreschke.com was the main site, linux.mreschke.com was another site, utilizing the same core (hence the name, mrcore) application. Each subdomain (profile/user) had its own skin and base directory. This allowed me to easily create various site with customized content, though at the time, I had absolutely no content. I built a content management framework with no content to put in it :). Later I realized that I didn't have content because mrcore 1.0 was not efficient or adequate enough for me to waist time writing content.During the same period as mrcore 1.0 (still original frame based code) I realized that what I really needed was a wiki system, something better than just creating HTML files.To create content, I built a PHP filemanager, and each user had his own home directory within that domains directory. Using the filemanager, one could create test.html and the page would be accessible at mreschke.com/test.htmlblah, blah, fixme |