Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
New Proposal Template
This page has been created from a template that uses "zones." To proceed:
  1. Edit the page
  2. Replace sample content within each zone-data tag with your own content
  3. Remove this notice
  4. Save the page
  5. When you are ready for community review, move this page to the Ready for Review section on the edit page.
No placeholders allowed!
Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Filter_ConvertNewlines Component Proposal

Proposed Component Name Zend_Filter_ConvertNewlines
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Filter_ConvertNewlines
Proposers Pawe? Przeradowski
Zend Liaison TBD
Revision 0.1 - 10 August 2008: Initial Draft. (wiki revision: 3)

Table of Contents

1. Overview

Zend_Filter_ConvertNewlines is a filter that handles conversion between various line termination styles used on different architectures.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will be as simple as possible.
  • This component will support Windows, Unix, Mac, Native and custom line terminators.
  • This component will allow to replace newlines with arbitrary text.

4. Dependencies on Other Framework Components

  • Zend_Filter_Interface

5. Theory of Operation

The component operate as each other Zend_Filter_*. It is typically used in filter chains together with other filters. It can also be used alone.

6. Milestones / Tasks

  • Milestone 1: design notes will be published here
  • Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
  • Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
  • Milestone 4: Unit tests exist, work, and are checked into SVN.
  • Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

  • Milestone #: [DONE] Unit tests ...

7. Class Index

  • Zend_Filter_ConvertNewlines

8. Use Cases

UC-01: Converting Mac-style into Windows-style

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.