Thanks to everyone for the feedback on the form design.  The new design is
working out great, and really keeps things a lot simpler for everyone.

On to a new question:  I've already implemented OnTouchStart, OnTouchMove,
OnTouchEnd, and OnTouchCancel events for all controls, but I'm wondering if
I need to go a little higher level, ala jQuery mobile.  IOW, implement
events similar to OnClick and OnDblClick, such as OnTap, OnDblTap, OnSwipe,
etc.

What do you think ?  Personally, I think that the lower down that I push
this type of functionality, the better.  Right now the "tap" logic is up in
the WebCtrls unit, but I think it should be pushed down into the WebUI unit
and surfaced as new events along the lines of what I mention above.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

>>Right now the "tap" logic is up in
>>the WebCtrls unit, but I think it should be pushed down into the WebUI unit
>>and surfaced as new events along the lines of what I mention above.

Agreed. +1 for WebUI

Tim Young [Elevate Software] wrote:

> On to a new question:  I've already implemented OnTouchStart,
> OnTouchMove, OnTouchEnd, and OnTouchCancel events for all controls,
> but I'm wondering if I need to go a little higher level, ala jQuery
> mobile.  IOW, implement events similar to OnClick and OnDblClick,
> such as OnTap, OnDblTap, OnSwipe, etc.
>
> What do you think ?  Personally, I think that the lower down that I
> push this type of functionality, the better.  Right now the "tap"
> logic is up in the WebCtrls unit, but I think it should be pushed
> down into the WebUI unit and surfaced as new events along the lines
> of what I mention above.

Interesting. I guess it really comes down to what you want touch to do.
My understanding is that it is two-fold. First, reacting to touch
events is faster, in that most browsers (mobile anyway) will pause a
bit before passing on the touch event as a mouse event simulation. So a
basic way to get in before that makes sense.

But one of my applications really uses touch fully, or would do. Right
now, it uses dragging with the mouse, but touch based interfaces can't
work yet as they don't do dragging. If you look at the second screen on
http://www.banxia.com/resources/connect/userguide/index.html?preferencin
g.htm you will see that there are some blobs on the top, and the idea
is that the user just drags them from there to the ideas that they want
to support. Likewise they can move them around too. This works nicely
with the mouse, using the MouseUp/Down/Move events.

What I want then, is the same "easy functionality" as the Mouse code. I
guess having access to the lowest level possible is therefore
important. But the higher level facilities would save a lot of time. I
wonder though if they can be "farmed out" to another component? Sort of
taking what would be in the low level stuff, but you attach a
"GestureControl" to a panel, and it takes over the low level events,
and has its own higher level events. That way I can get the swipe info
from the GestureControl, but am not forced to that way of thinking.
Moreover, I can make a different GestureControl that interacts
differently, or automatically shows a delete button on a panel. Or
something.

I look forward to what you come up with. Thanks!

On 2/20/2015 10:54 AM, Tim Young [Elevate Software] wrote:
> On to a new question:  I've already implemented OnTouchStart,
> OnTouchMove, OnTouchEnd, and OnTouchCancel events for all controls, but
> I'm wondering if I need to go a little higher level, ala jQuery mobile.
> IOW, implement events similar to OnClick and OnDblClick, such as OnTap,
> OnDblTap, OnSwipe, etc.

Not sure if OnTap and OnDoubleTap itself need to be different from
corresponding OnClick etc but would definitely like higher level
functions for the touch specific things.

Especially for more complex cases like all the swipe variations, multi
touch variations (from pinch to zoom to rotate with multi-touch) to the
3 and 4 finger variations etc.

Raul

Matthew,

<< That way I can get the swipe info from the GestureControl, but am not
forced to that way of thinking. >>

I'm not proposing one or the other, but both.  You wouldn't be forced to use
one way or the other, rather you'd have OnTouch*, etc. events *and* the
OnTap, etc. events.  It's just that you wouldn't be forced to *interpret*
the OnTouch* events to get the higher-level events like OnTap.

Tim Young
Elevate Software
www.elevatesoft.com

Raul,

<< Especially for more complex cases like all the swipe variations, multi
touch variations (from pinch to zoom to rotate with multi-touch) to the 3
and 4 finger variations etc. >>

Yeah, I won't have multi-finger touch support in the first 2.x release, but
I will surface it at some point.  The initial release will be exclusively
single-finger touch events.

Tim Young
Elevate Software
www.elevatesoft.com