Skip Navigation

Text Only/ Printer-Friendly

Current and Upcoming Development Projects

The project list has not been in active use for some time - The google code issue tracker is the primary location now for Reason project tracking.

Browse by project_type/client:

Contextual help

Edit this project

  • Description: Deveop a system for providing contextual help for Reason users
  • Current State: Assigned
  • Deadline: Not currently defined
  • Project Lead: mryan, nwhite
  • Scale: medium
  • Initiation Date: Jul 17th, 2006
  • Detailed Info:
    • [ 17 Jul 2006 ] We have a certain amount of help/tutorial information on Carleton's webgroup pages ( http://apps.carleton.edu/campus/webgroup/training/ ), but we don;t have a good way to provide that information (or links to it) in the context of the tasks it is sopposed to help with. We need to work on a system to make access to relevant help information easier and quicker. -- mr

Project Types

Edit this project

Order by: Deadline | Current State | Project Lead | Priority Level | Scale | Initiation Date

Other Projects

  • Improve Date/Datetime Form Elements
    • Description: The date and datetime form elements are somewhat clumsy to use. It would be nice to rework the way they are handled.
    • Deadline: Not currently defined
    • Scale: small
    • Initiation Date: Dec 21st, 2006
  • Attempt to extract content from assests for full-text searchability
    • Description: We haven't been able to affter great searching for assets because the content of the assets isn't in the database. Reason ought to be able to attempt to yank textual content out of common file formats and store it for searching purposes.
    • Deadline: Not currently defined
    • Project Lead: mheiman, mryan
    • Scale: medium
    • Initiation Date: Jul 23rd, 2006
  • Rework String Escape Method(s)
    • Description: Reason uses a hodgepoge of methods to escape strings for use in SQL queries. For security and compatibility reasons, it would be a good idea to standardize the way we are escaping these values.
    • Current State: In Planning
    • Deadline: Not currently defined
    • Project Lead: mryan
    • Scale: medium
    • Initiation Date: Apr 16th, 2007
  • Tool for importing non-reason images copied into page content
    • Description: Migrating content can be a royal pain, and the biggest headache is that, when people copy a web page into a Loki field, images appear to have been moved over -- but they really haven't. I envision a script that scours a Reason page, imports any images that are not already in Reason, and changes the src attributes of all the images to point to the newly imported images.
    • Current State: In Planning
    • Deadline: Jun 1st, 2006 -- overdue
    • Project Lead: mryan
    • Scale: small
    • Initiation Date: Jan 15th, 2006
  • Entity Cloning Toool
    • Description: Build a robust, flexible tool for cloning entities. It must respect the various flags regarding allowable relationship connections, and be able to be modified on a type-by-type basis.
    • Current State: In Progress
    • Deadline: Jun 9th, 2006 -- overdue
    • Project Lead: mryan
    • Scale: medium
    • Initiation Date: May 29th, 2006
  • Contextual help
    • Description: Deveop a system for providing contextual help for Reason users
    • Current State: Assigned
    • Deadline: Not currently defined
    • Project Lead: mryan, nwhite
    • Scale: medium
    • Initiation Date: Jul 17th, 2006
  • Improve word html/character cleanup
    • Description: Tidy currently does a good job of getting stuff pasted in from Word to be XHTML compliant, but we are not yet doing a great job of zapping some of the finer issues, like ugly "MsoNormal" classes and -- this is probably the #1 complaint of Reason users -- the non-standard wonky characters that get rendered as question marks by most browsers (this does not include curly quotes, etc -- those seem to be handled OK by Reason's UTF-8 approach -- instead, it includes just plain old gremlins like ascii value 26.)
    • Current State: In Planning
    • Deadline: Not currently defined
    • Project Lead: mryan, nwhite
    • Scale: medium
    • Initiation Date: Not entered
  • Improve UTF-8 handling and work around php5 htmlspecialchars bug
    • Description: There are a number of related issues regarding utf-8 handling, some of which are specific to php5:
      1. in php5, htmlspecialchars() returns an empty string if passed a string containing an invalid utf-8 character (Bug report.) The workaround is apparently to not pass the function the encoding parameter.
      2. There may still be some places where Reason is mangling UTF-8, because there are still odd invalid character glyphs that pop up from time to time. unhtmlentities() is a suspect, but it appears to only be used when prepping strings for use in headering. We should follow a string from userland to the database on the Reason backend and make sure there are no iffy steps
      3. We should be enforcing UTF-8 validity in more locations. The most important ones seem to me to be in the database (which is does not recognize the data as being UTF-8 encoded at the moment) and at the application perimiter, as part of ensuring that the data is in good shape in the first place (this is something of a security issue, as IE6 has a bug in handling invalid UTF-8)
    • Current State: In Planning
    • Deadline: Not currently defined
    • Project Lead: mryan, nwhite
    • Scale: medium
    • Initiation Date: Feb 27th, 2008
  • Improve Reason Installation Experience
    • Description: Improve Reason Installation Experience. Less pain.
    • Current State: In Planning
    • Deadline: Feb 1st, 2007 -- overdue
    • Project Lead: mryan,nwhite,mbockol,mheiman
    • Scale: medium
    • Initiation Date: Dec 8th, 2006
  • Simplify deletion mechanism by removing content_post_deleters
    • Description: We have a confusing, overlapping deletion mechanism -- content_deleters can do what content_post_deleters do (we think) but both systems exist in a weird overlapping way (see the finish action of deleteDisco in admin/admin_disco.php).
    • Current State: Assigned
    • Deadline: Not currently defined
    • Project Lead: nwhite
    • Scale: small
    • Initiation Date: Apr 26th, 2006
  • Enumerate Allowable Relationship Types
    • Description: There are several broad types of allowable relationships: normal, owns, archive, and parent. There may be more as time progresses (like pending.) Right now we are finding/identifying these relationships by their names, sometimes using "like" matching -- which is potentially slow, and definitely iffy. I propose that we add an enum field to the allowable relationships table to allow us to specify this key piece of data more reliably.
    • Current State: In Planning
    • Deadline: Not currently defined
    • Project Lead: nwhite
    • Scale: medium
    • Initiation Date: Jun 5th, 2006
  • JavaScript Thor Form Creator
    • Description: The form content manager in Reason uses a flash based form creation tool that is not extensible and needs to be replaced with a JavaScript based tool.
    • Current State: In Planning
    • Deadline: Not currently defined
    • Project Lead: nwhite
    • Scale: medium
    • Initiation Date: Not entered
  • Give users a chance to save before leaving a Reason form
    • Description: Check for changes on form elements when user tries to follow a link to another module, and provide an easy way for user to save (or decide not to save) before continuing with the action he/she wanted to do
    • Current State: On Hold
    • Deadline: Not currently defined
    • Project Lead: nwhite, mryan
    • Scale: small
    • Initiation Date: Jun 5th, 2006
  • Redo Page Types Scheme
    • Description: Issues: 1. The current page_types.php file is fragile and requires code modification to add/change/remove page types. 2. All sites currently share the same default page type, and allowing each site to have its own default page type would solve a number of issues. 3. We have scanty metadata about each page type -- nice english descriptions, understanding of what its primary Reason types are, help documentation, developer documentation, etc.
    • Current State: Assigned
    • Deadline: Not currently defined
    • Project Lead: nwhite, mryan
    • Scale: large
    • Initiation Date: Jul 14th, 2006
  • Add additional data to relationships
    • Description: There are a variety of areas where being able to add additional data to relationships would be very useful -- for example, it would be nice to be able to recaption an image on a particular page. This project aims to provide a framework for managing that sort of data.
    • Current State: Assigned
    • Deadline: Not currently defined
    • Project Lead: nwhite, mryan
    • Scale: medium
    • Initiation Date: Jul 11th, 2007