HTML Table |
---|
style | Wiki Markup |
---|
{table:style=background-color: #eee; margin: 15px 0 0; text-align:left; border-collapse:collapse; | Table Row (tr) |
---|
| style | }
{tr: style=text-align:center Table Head (th) |
---|
style | }
{th:style=width:50%; border-right:1px solid #000
---|
Problem | Table Row (tr) |
---|
Table Cell (td) |
---|
style | }
h2. Problem
{th}
{th}
h2. Solution
{th}
{tr}
{tr}
{td:style=padding:5px; width:50%; border-right:1px solid #000 }
*Problem Statement:* Currently most web applications use the standard {{http}} file browse and upload service provided with the {{<input type="file">}} form field.
* Only one file can be selected at a time for upload.
* Interface is inconsistent from browser to browser even down to the labels on the _browse_ button.
* The application can not specify the file type or types that are accepted in the current context.
* The browser does not provide meaningful or consistent feedback on the upload process. Table Cell (td) |
---|
style |
{td}
{td:style=padding:5px 10px; width:50%; Wireframes What does the Uploader look like and how does it behave? Storyboards: How, when, and where would the user use an Uploader? Design Pattern Upload design pattern}
*Wireframes* What does the Uploader look like and how does it behave?
* [Uploader Wireframes (Design Iteration)]
*Storyboards:* How, when, and where would the user use an Uploader?
* [Uploader Storyboard - Simple Upload]
* [Uploader Storyboard - Upload with Error]
* [Uploader Storyboard - Batch Upload with Metadata]
* [Uploader Storyboard - Add more]
*Design Pattern*
* [fluid:Upload design pattern]
{td}
{tr}
{table}
|