Documentation Wiki

Site Tools


roadmap:glfusion130

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
roadmap:glfusion130 [2011/05/27 21:18]
Mark [Images in stories]
— (current)
Line 1: Line 1:
-======= glFusion v1.3.x Development Roadmap / Design Ideas ======= 
- 
-The purpose of this page is to document the features planned for glFusion v1.3.0. The release time frame has yet to be determined.  ​ 
- 
-====== Dropping Support for PHP v4 **COMPLETE** ====== 
-Support for PHP v4 is dwindling. The PHP group stopped supporting PHP v4 in December 2007. Several glFusion plugins now require PHP v5. So if you haven'​t made the jump to PHP v5 yet, please start planning to do so soon. Starting with glFusion v2.0 we will no longer support PHP v4. 
- 
-The minimum version of PHP that will be required will be PHP v5.2.0. 
- 
- 
-====== JavaScript Libraries ====== 
-The current production release of glFusion utilizes MooTools v1.11 to provide a JavaScript foundation. ​ This release of MooTools is now several versions behind their current production release.  ​ 
- 
-After much discussion, the development team has decided to move to [[http://​jquery.com/​|JQuery]]. ​ This decision was based on several factors, but primarily that JQuery offers many more opportunities to easily integrate other tools / projects into glFusion.  ​ 
- 
-The goal is to duplicate all the current functionality we offer with MooTools v1.11 in the new JQuery implementation. 
- 
-====== Rewrite Authentication System ====== 
-The current system for authenticating users is fragmented and does not allow for growth. ​ What I propose is to design a more modular system that doesn'​t care whether you are authenticating locally or remotely. Instead, local password authentication will simply be one of the methods. ​  This could possibly require some modifications to how user data is handled and stored. 
- 
-The primary goal of rewriting the authentication system is to allow easier integration of new methods. Facebook and Google authentication is now very popular. ​ Having a modular authentication system will also much quicker and easier integration of these technologies. 
- 
-====== Social Networking Service Integration ** COMPLETE ** ====== 
-Our goal is to provide features which allow for the tighter integration of glFusion sites and the related content that is offered with social networking environments such as Facebook, LinkedIn and Twitter.  ​ 
- 
-To enable these features, it will be necessary to allow users to link their existing glFusion accounts to social networking services, or as an option, allow users to utilize these social services as remote authentication methods for glFusion itself. 
- 
-This work is highly interdependent upon the authentication system rewrite, however the near-term goal will be to allow users to login to glFusion using their social networking account. ​ Facebook, LinkedIn and Twitter will be supported. **Initial integration of Facebook, LinkedIn, and Twitter authentication is complete.** 
- 
-====== Comment Integration Enhancements ====== 
-The current comment engine is OK, but we would like to see some 
-improvements in how comments integrate with the system. ​ There are 
-several features missing: 
- 
-  * integrated comment form (show at the bottom of an item such as a story or media item) 
-  * comment subscriptions (ability to subscribe to a specific comment thread, see item #6 below) **COMPLETE** 
-  * comment RSS feeds - RSS feed for specific comment threads 
- 
-Other things to consider would be moderated comments, where an admin must approve the post before it is made public. 
- 
-====== Date Handling **COMPLETE** ====== 
-Currently, there are several areas in the code where dates are handled by PHP functions, so localization is up to the PHP configuration. ​ We would prefer to see glFusion own all date handling functions and provide localization. 
- 
-====== Autotag Permissions **COMPLETE** ====== 
-Currently, there are no controls in place to handle when or where autotags can be used. Autotags are a extremely powerful tool, but there needs to be some controls in place to ensure that autotags are used properly. 
- 
-An autotag permission system will be implemented. ​ The permission system will not follow the traditional glFusion permission model, i.e.; permissions by user.  Instead, the autotag permission system will control where autotags can be used.  For example, the **showblock** autotag is probably not appropriate for a comment. ​ The autotag permission system will allow to you enable / disable tags based on where they can be used.  This allows you to disable tags like **showblock** in the comment area or the user signature. 
- 
-====== General Tweaks ====== 
- 
-===== Fix RSS path ===== 
-The current configuration setting for RSS feed path must include a filename, which is just confusing. ​ Rework that configuration setting to only require the path. 
- 
-===== Path Handling ===== 
-There are literally a dozen paths you have to specify when installing / configuring glFusion. ​ Several plugins also have their own paths as well.  This make moving a site very difficult. 
- 
-This proposal is to simply have 2 paths: 
- 
- - path to private ​ 
- - path to public 
- 
-That's it!  Everything else, including plugins will simply tack on whatever they need to the end.  ​ 
- 
-The drawback to this approach is that it will make it a bit less configurable. ​ For example, in the Forum plugin, the path for post attachments cannot be changed. 
- 
-===== URL Parsing ===== 
-The current Forum plugin has the ability to automatically find and parse embedded URLs in a post. It will turn **<​nowiki>​www.glfusion.org</​nowiki>​** into http://​www.glfusion.org automatically. ​ There are several other areas in glFusion where this happens, but each one has it's own custom code to handle.  ​ 
- 
-This proposal will create a standard URL parsing API that can be used both by the core glFusion implementation and all plugins. ​ 
- 
-===== Theme Cleanup ===== 
-Remove unused templates (storybodytext.thtml / 
-featuredstorybodytext.thtml / archivestorybodytext.thtml). ​ Create a better documented and easier to follow style.css. 
- 
-====== Features to Remove ====== 
-There are some features in glFusion that we do not think bring much value any longer. ​ We would like to consider removing the following: 
- 
-===== Editor Implementation ===== 
-Editor Implementation - We would like have an open discussion about the need to be able to switch between text / html / wysiwyg anytime the '​advanced editor'​ (which I want to rename to WYSIWYG editor) is enabled.  ​ 
- 
- 
-===== Digg Integration ===== 
-Remove Digg implementation - let this be handled by things like the AddThis plugin or possibly a new ShareThis plugin. 
- 
-===== Wiki Formatting for Stories **COMPLETE** ===== 
-The code is very old and hasn't been maintained in years. ​ This feature will be removed from the code base. 
- 
- 
- 
  
roadmap/glfusion130.1306549083.txt.gz · Last modified: 2015/07/11 17:18 (external edit)