Metadata
- Source
- FLUID-893
- Type
- Sub-task
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Allison Bloodworth
- Reporter
- Jonathan Hung
- Created
2008-07-11T18:37:09.000-0400 - Updated
2013-04-11T17:31:17.975-0400 - Versions
-
- 0.1
- 0.3
- 0.4beta1
- 0.4
- Fixed Versions
- N/A
- Component
-
- OSDPL
Description
OSDPL Design Pattern format - add the following sections:
- "Related Fluid Design Patterns"
- "Examples" section with "Example Fluid implementations" and "Similar Implementations" sub-sections
- "References" (sources used to create this pattern)
- "Related patterns" (relationships to other patterns within our DPL)
- "Design Advice"
o CSS tips, Variations of the design, advice on when to implement each variation
o e.g. Inline Edit: when to have an explicit Save button
o Design advice on what's outside of the component e.g. Uploader: "make sure the newly uploaded files are in focus" --> should be included in the "How" section, and just distinguish what's in the component and what's not. (Anastasia)
We feel there should be a section that describes tasks the implementing designer or developer needs to do to ensure the seamless integration of the component. For example, the Uploader component deals strictly with uploading of files, however, the designer should highlight or indicate which files have been uploaded after transitioning from the Uploader back to their work context.
Question: what should the title of this section be?
- "Transition", "Component Integration"
Iteration14
Comments
-
Allison Bloodworth commented
2008-07-16T20:57:13.000-0400 Let's hold off on this task for now as we need to finalize the list of design pattern elements as a group, either on the mailing list or at our next OSDPL meeting on July 23rd.