Mouse

Page history last edited by Richard D. Worth 1 year, 1 month ago

type: utility

release: 0.0

status: complete

documentation: N/A

demo: N/A

1 - Description:

Base component for all mouse-interactions and widgets, eg. Draggable or Slider.

Existing Plugins

http://threedubmedia.com/ - jquery.event.drag, jquery.event.drop

2 - Visual Design:

none

3 - Functional Specifications/Requirements:

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

$.ui.mouse

[general description, here or on a seperate page]
_mouseInit

_mouseDestroy

_mouseDown

_mouseMove

_mouseUp

_mouseDistanceMet

_mouseDelayMet

_mouseStart

_mouseDrag

_mouseDrop

_mouseCapture

defaults

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

Need to pull in touch normalizing from jQuery Mobile: jquery.mobile.vmouse.js, ask Kin Blas if you have questions (he wrote it)
Need to build in scroll support that's currently in draggable (and perhaps others)
Need to add touch support which will mean renaming mouse

Comments (3)

Adding support for touch events doesn't seem to complicated: http://dev.jsui.de/test/ipad.html

My understanding is the core interaction plugins are getting a rewrite / refactor and I'm keen to know whether you still intend to use the mouse widget pattern or are in fact looking into the use of the special event API for drag, dragstart, dragend etc?

As, whilst I think the mouse widget is a clever approach, I feel the special event API is more suited in that it would a) be using a consistent and familiar API and b) because it could be used outside the context of the widget factory developers would get more utility out of it.