HtmlToData

Page history last edited by Todd Parker 11 mos ago

 

type: utility

release: 0.0

priority: medium

status: in planning || in development || complete

documentation: url || N/A

demo: url || N/A

 


 

1 - Description:

 

A standardized way to scrape data from html elements for powering widgets with progressive enhancement. For example, a standard html select could be turned into a standardized data object that could be used to populate a slider, date picker, combobox, etc. Or an html table could be transformed into a chart or grid by parsing out the data.

 

A very basic version of the idea of grabbing data from an html table is used here for visualizations:

http://www.filamentgroup.com/lab/creating_accessible_charts_using_canvas_and_jquery/

 

A more robust systemfrom Dojo is probably a closer starting point:

http://dojotoolkit.org/book/dojo-book-0-9/part-3-programmatic-dijit-and-dojo/data-retrieval-dojo-data-0

 

 


 

2 - Visual Design:

 

(Initial wireframe mockup, followed by more detailed designs of the various configurations, options and states.)

 


 

 

3 - Functional Specifications/Requirements:

 

(Detailed descrition of how the script will be structured: defaults, options, architecture, extensibility, etc.)

 


 

4 - Markup & Style:

 

     4.1 Initial markup examples

 

     (Pre-enhanced HTML markup structure that will be transformed into the final widget. There may be multiple possible HTML markup options per widget: for example, for a slider, radiobuttons, inputs or selects could all be used. )

 

     4.2 Recommended transformed HTML markup

 

     (The HTML markup structure and classes that will be used by the scripts in the enhanced version) 

 

     4.3 Accessibility recommendation

 

    (Detailed recommendations for ARIA, HTML markup, CSS and javascript that will contribute to universal access and full section 508 accessibility for screen readers, mobile devices and any other devices) 

 

     4.4 CSS & Theme

 

    (Description of the CSS classes to be used for all states, how custom theming and Themeroller support will work.) 

 


 

5 - Latest version of plugin:

 

(Link to the latest version in the jQuery UI trunk here)

 


 

6 - Open issues being discussed

 

(Use this area to place things that we're hashing out like featuresand options we're not sure we should include, questions about how this fits into UI and relates to other widgets and utilities, known problems, whether features should be broken across multiple releases, etc.)

 


 

 

 

 

Comments (1)

profile picture

Andrew Powell said

at 9:00 am on Mar 11, 2009

Food for thought: The .NET DataSource/DataBind model might be considered for looking at design paradigms for this implementation. It's very robust and very efficient.

You don't have permission to comment on this page.