Which one is the best one to use? Because I don’t have VS2008 or .NET3.5 (WPF), nor a multi-touch display (:/) I am unable to try all of these out and decide for myself which has the best features, control set, etc. Are all these just derivatives of TouchLib?
Would all of these work with any multi-touch capable device? I’m looking at the TouchKit (http://nortd.com/touchkit/).
I would like to begin looking into creating multi-touch apps, but trying to pick a starting point seems to confuse me! Especially with the emergence of frameworks like Lux (http://nuiman.com/log/view/lux/) which appear to be cross platform.
http://nuigroup.com/forums/viewthread/1616/
is your best bet for a WPF framework. I haven’t used it yet but it seems pretty good. AdmiralUD should be able to help you with any questions you have.
I haven’t looked at nuiman’s lux ao I can’t comment on that.
I’m also not sure of the best way to approach my plunge into the creation of multi-touch apps with respect to a multi-touch display. Initially I thought that going the wii whiteboard route would be a quick and easy way to jump in. But after some high level digging around, it seems to me that while it is a very cheap way to get a multi-touch surface, the software to translate the gestures into events is quite young and would be limited to DirectX apps. Moving to one of these frameworks (WPF, or cross platform via Lux) seems like a better approach.
Having said that, what display would you recommend? I was looking at TouchKit: http://nortd.com/touchkit/.
There is also MultiTouchVista. What do you think about it?
It uses addin architecture for input. That means any hardware is possible, as long as you implement an interface for this device. Comes with MultipleMice and TouchLib addins.
Input service runs separated from application and can support more than on application at time. Can be run as console application or windows service (any other hosting is also possible).
You can use attached event to respond to use input.
Includes TouchablePanel. Can be used in many controls to interact with items.
Gestures
Ah! Yet another framework to consider underscoring the relevance of the thread topic.
I’m unable to view the videos at the moment, but from what you describe, MultiTouchVista would definitely be a consideration.
Daniel D - 22 May 2008 02:19 PM
It uses addin architecture for input. That means any hardware is possible, as long as you implement an interface for this device.
What multi-touch displays are people using, and at what cost?
Very, very nice Jurbo. Are all these frameworks basically “constructed” in the same way? Fundamentally, what s the difference between your framework and others like MultiTouchVista?
Additional questions on your framework in your thread.
I can say only about MultiTouchVista. It is build with architekture that is very simmilar to wpf input architekture and reuses wpf as much as possible. It is possible to write applications only using xaml without any code. Input service is independent from GUI framework. It runs as separated process and can send input to more than one application at time. Also it can be started as Windows Service.
I have a question to application developers. What features are you awaiting and what you are missing from a Multitouch Framework?
I can say only about MultiTouchVista. It is build with architekture that is very simmilar to wpf input architekture and reuses wpf as much as possible. It is possible to write applications only using xaml without any code. Input service is independent from GUI framework. It runs as separated process and can send input to more than one application at time. Also it can be started as Windows Service.
I have a question to application developers. What features are you awaiting and what you are missing from a Multitouch Framework?
Well my initial response would have to be that a multi-touch framework is only as good as the multi-touch controls that it provides. Yes “enabling” the multi-touch interaction is key to any framework, but it is the multi-touch control set that lets application developers take true advantage.
Do you agree with me if I say that not every control should be multi-touch capable? Main goal of MultiTouchVista is to allow ANY Control to be used with it. That means you can use all standard WPF controls with it.
Do you have any special Controls that you are missing in MultiTouchVista?
Do you agree with me if I say that not every control should be multi-touch capable?
Agreed.
Main goal of MultiTouchVista is to allow ANY Control to be used with it. That means you can use all standard WPF controls with it.
Do you have any special Controls that you are missing in MultiTouchVista?
Hard to say at the moment - I haven’t been able to try out MultiTouchVista for my self and play around with it. Still on the first step in obtaining / constructing a multi-touch display.
Hard to say at the moment - I haven’t been able to try out MultiTouchVista for my self and play around with it. Still on the first step in obtaining / constructing a multi-touch display.
you don’t need multi-touch display to try out MultiTouchVista. just connect additional mice and use them. very helpful for development.
Correct me if I’m wrong. Most framework are usig TouchLib (CsTI), some of them can TUIO.
MultiTouchVista abstracts input using input providers. As for today there is an implementation for CsTI and multiple mice. Also in First Prototype directory there is a provider that was “inspired” by TouchLib (same algorithmes for filters and blob detection).
If you have a device that is not yet supported, you have to implement IProvider interface. Look in Multitouch.InputProviders.sln for details.
