[Pieforms-commit] SF.net SVN: pieforms: [280] pieforms-php5/trunk/doc
Status: Alpha
Brought to you by:
oracleshinoda
Menu
▾
▴
[Pieforms-commit] SF.net SVN: pieforms: [280] pieforms-php5/trunk/doc
|
From: <ora...@us...> - 2008-01-03 10:59:27
|
Revision: 280
http://pieforms.svn.sourceforge.net/pieforms/?rev=280&view=rev
Author: oracleshinoda
Date: 2008-01-03 02:59:30 -0800 (Thu, 03 Jan 2008)
Log Message:
-----------
Added TODO file in the documentation with a non-exhaustive list of stuff I want to do on Pieforms.
Added Paths:
-----------
pieforms-php5/trunk/doc/html/dev/
pieforms-php5/trunk/doc/html/dev/todo.html
pieforms-php5/trunk/doc/rst/dev/
pieforms-php5/trunk/doc/rst/dev/todo.rst
Added: pieforms-php5/trunk/doc/html/dev/todo.html
===================================================================
--- pieforms-php5/trunk/doc/html/dev/todo.html (rev 0)
+++ pieforms-php5/trunk/doc/html/dev/todo.html 2008-01-03 10:59:30 UTC (rev 280)
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+<html xmlns=http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="generator" content="Docutils 0.4.1: http://docutils.sourceforge.net/" />
+<title>Pieforms TODO List</title>
+
+<link rel="stylesheet" type="text/css" href="../style.css" />
+</head>
+<body>
+<div class="document" id="pieforms-todo-list">
+<h1 class="title">Pieforms TODO List</h1>
+<p><div id="breadcrumbs"><a href="http://pieforms.sourceforge.net/">Pieforms Home</a> » <a href="../">Documentation Home</a> » <a href="">Pieforms TODO List</a></div></p>
+<table class="docutils field-list" frame="void" rules="none">
+<col class="field-name" />
+<col class="field-body" />
+<tbody valign="top">
+<tr class="field"><th class="field-name">Author:</th><td class="field-body">Nigel McNie</td>
+</tr>
+<tr class="field"><th class="field-name">Contact:</th><td class="field-body"><a class="reference" href="mailto:nigel@catalyst.net.nz">nigel@catalyst.net.nz</a></td>
+</tr>
+<tr class="field"><th class="field-name">Copyright:</th><td class="field-body">This document has been placed in the public domain</td>
+</tr>
+</tbody>
+</table>
+<div class="section">
+<h1><a id="more-form-elements" name="more-form-elements">More Form Elements</a></h1>
+<p>To start with, a "WYSIWYG" element bundled with Pieforms makes sense. After that, I guess it's up to popularity.</p>
+</div>
+<div class="section">
+<h1><a id="data-processing-before-validation" name="data-processing-before-validation">Data Processing Before Validation</a></h1>
+<p>E.g. running submitted values through <tt class="docutils literal"><span class="pre">strtoupper()</span></tt>, <tt class="docutils literal"><span class="pre">trim()</span></tt> etc. before applying validation. A useful addition.</p>
+</div>
+<div class="section">
+<h1><a id="multipage-forms" name="multipage-forms">Multipage Forms</a></h1>
+<p>The idea here is that you have one pieform per "page", but yet it's easy to go
+back and forth between the pages.</p>
+<p>In theory, validation is checked each time a page is submitted, and the final
+'submit' happens when the last page is submitted.</p>
+<p>This needs planning.</p>
+</div>
+<div class="section">
+<h1><a id="forms-with-a-tabbed-interface" name="forms-with-a-tabbed-interface">Forms With a Tabbed Interface</a></h1>
+<p>This could probably be done with fieldsets + javascript, or some other fancy trickery.</p>
+</div>
+<div class="section">
+<h1><a id="i18n-ise-error-messages" name="i18n-ise-error-messages">I18n'ise Error Messages</a></h1>
+<p>Currently they're in English only. I'm kind of OK with this.</p>
+</div>
+<div class="section">
+<h1><a id="i18n-system-improvements" name="i18n-system-improvements">I18n System Improvements</a></h1>
+<p>Use some kind of positional parameters or separate the data from the string
+itself in some way so messages can be translated naturally.</p>
+</div>
+<div class="section">
+<h1><a id="make-plugins-have-a-class-based-interface" name="make-plugins-have-a-class-based-interface">Make Plugins Have A Class Based Interface</a></h1>
+<p>See <a class="reference" href="http://sourceforge.net/tracker/index.php?func=detail&aid=1695539&group_id=182497&atid=901456">bug 1695539</a>. This would remove some hacks, especially in the textarea
+element and multicolumntable renderer (although the latter may be removed from
+pieforms at some stage anyway).</p>
+</div>
+<div class="section">
+<h1><a id="remove-the-dependency-on-mochikit" name="remove-the-dependency-on-mochikit">Remove The Dependency On MochiKit</a></h1>
+<p>There are two ways this could be done - one is to write all the javascript
+"raw", so to speak. The other is to rewrite the parts that are in MochiKit in
+JQuery instead. See <a class="reference" href="http://sourceforge.net/tracker/index.php?func=detail&aid=1863018&group_id=182497&atid=901453">bug 1863018</a>.</p>
+</div>
+<div class="section">
+<h1><a id="read-only-mode-for-form-display" name="read-only-mode-for-form-display">Read-Only Mode for Form Display</a></h1>
+<p>Given Pieforms has now switched to AHAH, this will actually be quite easy. This
+is planned for 0.4.0.</p>
+</div>
+<div class="section">
+<h1><a id="documentation-improvements" name="documentation-improvements">Documentation Improvements</a></h1>
+<p>Are ongoing. APIs are still in flux at the moment, making things tricky.</p>
+</div>
+<div class="section">
+<h1><a id="test-suite" name="test-suite">Test Suite</a></h1>
+<p>Would be nice to have one of these. I will have to investigate PHP test suites,
+but I get the feeling selenium will play a significant part here as well, given
+the nature of what is being tested.</p>
+<p><div id="breadcrumbs"><a href="http://pieforms.sourceforge.net/">Pieforms Home</a> » <a href="../">Documentation Home</a> » <a href="">Pieforms TODO List</a></div></p>
+</div>
+</div>
+
+<div id="footer">Pieforms by <a href="http://nigel.mcnie.name/">Nigel McNie</a> and <a href="http://pieforms.sourceforge.net/about#authors">others</a>,
+© 2006 - 2008 <a href="http://www.catalyst.net.nz/">Catalyst IT Ltd</a>. Pieforms is released under the <a href="http://gnu.org/licences/gpl.html">GNU GPL</a></div>
+</body>
+</html>
Added: pieforms-php5/trunk/doc/rst/dev/todo.rst
===================================================================
--- pieforms-php5/trunk/doc/rst/dev/todo.rst (rev 0)
+++ pieforms-php5/trunk/doc/rst/dev/todo.rst 2008-01-03 10:59:30 UTC (rev 280)
@@ -0,0 +1,83 @@
+====================
+ Pieforms TODO List
+====================
+:breadcrumbs:`Documentation Home > Pieforms TODO List`
+
+:Author: Nigel McNie
+:Contact: ni...@ca...
+:Copyright: This document has been placed in the public domain
+
+More Form Elements
+------------------
+
+To start with, a "WYSIWYG" element bundled with Pieforms makes sense. After that, I guess it's up to popularity.
+
+Data Processing Before Validation
+---------------------------------
+
+E.g. running submitted values through ``strtoupper()``, ``trim()`` etc. before applying validation. A useful addition.
+
+Multipage Forms
+---------------
+
+The idea here is that you have one pieform per "page", but yet it's easy to go
+back and forth between the pages.
+
+In theory, validation is checked each time a page is submitted, and the final
+'submit' happens when the last page is submitted.
+
+This needs planning.
+
+Forms With a Tabbed Interface
+-----------------------------
+
+This could probably be done with fieldsets + javascript, or some other fancy trickery.
+
+I18n'ise Error Messages
+-----------------------
+
+Currently they're in English only. I'm kind of OK with this.
+
+I18n System Improvements
+------------------------
+
+Use some kind of positional parameters or separate the data from the string
+itself in some way so messages can be translated naturally.
+
+Make Plugins Have A Class Based Interface
+-----------------------------------------
+
+See `bug 1695539`_. This would remove some hacks, especially in the textarea
+element and multicolumntable renderer (although the latter may be removed from
+pieforms at some stage anyway).
+
+.. _bug 1695539: http://sourceforge.net/tracker/index.php?func=detail&aid=1695539&group_id=182497&atid=901456
+
+Remove The Dependency On MochiKit
+---------------------------------
+
+There are two ways this could be done - one is to write all the javascript
+"raw", so to speak. The other is to rewrite the parts that are in MochiKit in
+JQuery instead. See `bug 1863018`_.
+
+.. _bug 1863018: http://sourceforge.net/tracker/index.php?func=detail&aid=1863018&group_id=182497&atid=901453
+
+Read-Only Mode for Form Display
+-------------------------------
+
+Given Pieforms has now switched to AHAH, this will actually be quite easy. This
+is planned for 0.4.0.
+
+Documentation Improvements
+--------------------------
+
+Are ongoing. APIs are still in flux at the moment, making things tricky.
+
+Test Suite
+----------
+
+Would be nice to have one of these. I will have to investigate PHP test suites,
+but I get the feeling selenium will play a significant part here as well, given
+the nature of what is being tested.
+
+:breadcrumbs:`Documentation Home > Pieforms TODO List`
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
