How should we promote features?
Hi guys,
I wanted to touch base and hear opinions about how you would promote features that other libraries do not have but are difficult to notice when playing around for the first time?
There are many of these in the new drag and drop routines, let me give you a few examples:
- If you drag with your mouse out of the browser window and then release the mouse, and move in again, allmost all other libraries (which the exeption of YUI) fail at releasing the draggable again and produce errors. Ours not, in all browsers.
- Most libraries have very agressive methods when trying to make sure you don't select any text on the page when starting to drag. This will result most of the time that you cannot select text anymore at all (in the draggable at least). I invested a lot of time to make sure this still works in both IE and FF.
- Performance: The library has a cursorAt property which determines where the cursor is, relative to the draggable - that means when you pick it, the draggable (or the clone) does not stay where you picked it, but instead moves to the given offset. If you use it (many already asked if cursorAt is used in real-word usage - yes it is, most of the time), the draggable class automatically detects if the helper (the thing you are moving) is under the mouse - if not, dropable detection is extremely fast (it then uses browser events).
These are just a few. I will explain more of them soon.<br clear="all">
--
--
Paul Bakaus
I wanted to touch base and hear opinions about how you would promote features that other libraries do not have but are difficult to notice when playing around for the first time?
There are many of these in the new drag and drop routines, let me give you a few examples:
- If you drag with your mouse out of the browser window and then release the mouse, and move in again, allmost all other libraries (which the exeption of YUI) fail at releasing the draggable again and produce errors. Ours not, in all browsers.
- Most libraries have very agressive methods when trying to make sure you don't select any text on the page when starting to drag. This will result most of the time that you cannot select text anymore at all (in the draggable at least). I invested a lot of time to make sure this still works in both IE and FF.
- Performance: The library has a cursorAt property which determines where the cursor is, relative to the draggable - that means when you pick it, the draggable (or the clone) does not stay where you picked it, but instead moves to the given offset. If you use it (many already asked if cursorAt is used in real-word usage - yes it is, most of the time), the draggable class automatically detects if the helper (the thing you are moving) is under the mouse - if not, dropable detection is extremely fast (it then uses browser events).
These are just a few. I will explain more of them soon.<br clear="all">
--
--
Paul Bakaus
Topic Participants
Paul Bakaus
gilles0181
nileshp.com