• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Task
    • Increase Requirement to PHP 5

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: Increase Requirement to PHP 5

    • Issue Tools
      • View Changes
    1. issueid=2025 October 10, 2010 1:46 AM
      pegasus pegasus is offline
      VaultWiki Team
      Increase Requirement to PHP 5

      Time to make the programming a bit more object-oriented, without having to bloat a global $vault container or remember to load extensions continuously. Instead, we should be able to call our methods and extensions statically on one line. However, this isn't supported by PHP 5. Doing this would make the requirement for VaultWiki 4 be PHP 5.2.0+.

      Have to go back, upgrade the already-written pieces of the core, and organize it somewhat better for MVC.
    Issue Details
    Issue Number 2025
    Issue Type Task
    Project VaultWiki 4.x Series
    Category General
    Status Completed
    Priority 6 - Dev-Related Tasks
    Target Version 4.0.0 Alpha 1
    Resolved Version 4.0.0 Alpha 1
    Milestone VaultWiki 4 Alpha 1
    Software DependencyAny
    License TypePaid
    Votes to perform 0
    Votes not to perform 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. October 11, 2010 1:58 AM
      pegasus pegasus is offline
      VaultWiki Team
      Core updated to PHP 5. This was a bit annoying, but the code itself is quite elegant now. The implementation of MVC had to be loose in certain situations - e.g. for the database class, it would be simpler for developers to call only model('DB'), rather than having to remember which methods are actually in controller('DB').

      While I see the benefits of the MVC architecture for most coding projects, I still am not sure why it is being so widely adopted for PHP software. The problem with MVC is that separating what would have been 1 class into 3 files has the effect of multiplying the number of files by 3. While this is fine for compiled software, PHP scripts do not compile before runtime unless you have additional software installed, which many shared hosts do not allow. This means that the hard disk latency will have 3x more of a slowing effect than a non-MVC application, which is in turn 3x more likely to be noticeable in the user experience for larger applications (like VaultWiki, or an entire forum).
      Reply Reply  
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 10:59 PM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2023 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2023 DragonByte Technologies Ltd.
    Copyright © 2008 - 2013 VaultWiki Team, Cracked Egg Studios, LLC.