Related
Beta Version is HERE (Beta1).
looking for developer to write an Album Application (OpenGlEs?) and utilize the SDK to enable pinch-to-zoom on resistive screens.
Greetings,
Wow right!
finally i was able to perform a dual touch on our resistive screens and you can find the dll in the attachements along with a demo app!
NOTE TO EVERYONE :
Please don't report the 1 finger bug, it's well known and it will be eliminated (BTW, Zoom in is possible with 1 finger but zoom out is not)
this demo app is simply a demo app and only to show that the SDK is functional, it WILL NOT zoom to focus the pinched area! if you can develop a demo application and you have a graphics development experience please be my guest and i will help you with the SDK. the current demo only resizes the image and doesn't relocate it. i can do a proper one but this will mean taking time from the real project.
thank you
documentation will NOT be available as this is a preAlpha and it's just to get you excited
here is the demo
Video
http://www.youtube.com/watch?v=ld_kIpLWa3Y
Notice :
i'm not responsible for anything might happen to your phone (Even though i'm sure there is nothing to go wrong but just in case).
This is just a pre-alpha, and there is no garantee to go beyond this version. i'm doing this for the community for free and as a proof of concept only. i will continue to work on this on my free time but please don't rush!
you are not allowed to to ask people to pay for this SDK.
you are not allowed to disassemble the SDK or reverse engineer it.
you are not allowed to post the attachement(s) below to any other website. you can always link to this tread.
if you are going to use it in your application, you MUST put a link in your application/offical website that reffers to this XDA thread.
i reserve the right to make this a paid SDK at any point of time.
i reserve the right to relocate this SDK to another website or even take it offline.
that was long right?!
ok, let's go to business!
Demo Attached
To Use the demo, place 1st finger on the image, then place the 2nd finger also on the image and slide your second finger in or out!
Requres .Net Compat Framework 3.5,
Tested on
- Touch Pro 2 (HTC Rhodium)
- Touch HD (HTC Blackstone)
- Xperia X1
Regards,
Adel R. Al Zubeir (Anaadoul)
Documentation
How to use the SDK!
create an instanse of the class,
the object wich will detect the mouse clicks MUST have mouse down, up and move.
for example in the demo above the code is as following and i use picturebox
publicpartialclassForm1 : Form
{
DualTouchSDK.DualTouchSDK SDK = new DualTouchSDK.DualTouchSDK();
privatevoid Form1_Load(object sender, EventArgs e)
{
SDK.Zooming += new DualTouchSDK.DualTouchSDK.MultiTouchEventHandler(SDK_Zooming);
}
void SDK_Zooming(DualTouchSDK.MultiTouchEventArgument e)
{
// Do the zooming here e.ZoomRatio returns a value which is the % of the zoom < 1 = zoom in, > 1 zoom out.
}
privatevoid pictureBox1_MouseDown(object sender, MouseEventArgs e)
{
SDK.SetMouseDown(e.X, e.Y);
}
privatevoid pictureBox1_MouseMove(object sender, MouseEventArgs e)
{
SDK.SetMouseMove(e.X, e.Y);
}
privatevoid pictureBox1_MouseUp(object sender, MouseEventArgs e)
{
SDK.MouseUp();
}
}
Known Bugs (V0.0)
- Single Finger sliding causes zoom IN (notice that you CANNOT zoom OUT).
First of all, nice try. As developer I kind of (think to) know the technique involved processing this and for most part this could work. However since WinMo 6.5.x has it's own overlay I must admit it's not working properly on build 28008 (and 28002).
Actually it does work if you don't release the screen, but once you do, it's completely useless. You can't do anything but scroll, this probably because of the kinetic scrolling overlay. (This only happends if the image is larger than the screen ofcourse, everything else works as advertised!)
Second, may I add a suggestion (something I once tried in an application but never finished)? If you place your finger on the photo and then place the second finger the application imediately zooms in to like 400% (depending on the place your finger is placed), This makes it hard to pinch-to-zoom out, since you actually have to place the two fingers on the same position.
My idea is this. Whenever your first finger is placed down (and the coordinates are stored) and you place the second finger on the screen, the app would recognize this as a movement of the first finger but in 0 milliseconds. It might be possible to make a sort of minimum time required to move from 'a' to 'b', so the initial position of the two fingers can be 'stored'.
I hope I made myself clear enough for you to understand, as I do not have too much time to explain it better. If you like I can explain it better, but that would be later tonight, for now got to run!
Maybe this is due to the kenetic scrooling, i hope you can watch the video, the zoom will take effect only when you move your 2nd finger not after placing it!
anyway this requires alot of testing and alot of improvements as it's still pre pre pre alpha.
i tested it and it's working good enough on my TP2 and a WM6.5.0 ROMs
Agreed the video is what I had in mind, I'm sorry I should have watched it (though it wasn't up yet when I started replying). Anyway (still being here) this is not what I get, probably due to my build being different. As soon as I place my second finger on the screen it zooms in about 400% or 500%. I actually can pinch to zoom out if I place my fingers in de top-left and bottom-right corner, and move inwards... since the distance is larger than the amount of zooming done initially I can zoom out. Fact remains that everything only works as long as the image isn't larger than the screen, but all this is rather a Windows Mobile error than yours!
Good work, hope to include it into my projects some day!
Stil forgot to mention some required debuggin information (so you can keep track of things if you want)! I use a Touch HD (BlackStone) T8282 (Original Model). I use homecooked ROMs and now running WinMo 6.5.3 build 28008. Besides the regular HTC stuff I have no applications installed (as most is cooked in). I have no Manila 2.5 running and ... that's it.
anaadoul said:
Maybe this is due to the kenetic scrooling, i hope you can watch the video, the zoom will take effect only when you move your 2nd finger not after placing it!
anyway this requires alot of testing and alot of improvements as it's still pre pre pre alpha.
i tested it and it's working good enough on my TP2 and a WM6.5.0 ROMs
Click to expand...
Click to collapse
pocketnow.com is paying attention - congrats, and I can't wait to see more
http://pocketnow.com/tweaks-hacks/multitouch-coming-to-resistive-screens
Val
Anyone know how to make opera Zoom through an external app?
maybe sendmessage API or something similar?
It probably has a lot to do with sensitivity.
For me, resting one finger and using the other to do the gesture works the best. The key is to make sure the resting finger doesn't jitter much.
gotta try this!!!
Wow it's just awesome!
you can just use 1 finger and move it over the image. it works almost the same
pensoffsky said:
you can just use 1 finger and move it over the image. it works almost the same
Click to expand...
Click to collapse
it seems it registers a second press when you drag! but it works in an unpredictable way!
anyway i will look into it and eliminate this bug!
This is awesome so far! I love the progress. If you need any help with testing at all, let me know.
Nice, had this idea for a while but never felt like doing much work with it.
Demo app works fine on Fuze
I have a Verizon Samsung Omnia i910. It works for the most part here, only complaint is the "dragging" zoom issue that has already been reported. This is a great breakthrough, I'm really impressed! I will be following this thread for updates!
excellent work! i really hope you and the other devs pursue this. this way we can have some basic multitouch apps, defeat the last stronghold of the iphone, and claim victory lol.
Wow, this is an amazing piece of work you've created! I'd love to see this further developed, to either support existing apps (like google maps, Opera Mobile, Pocket Internet Explorer, photo viewers, other apps with zooming, etc.). Also, I'd love to see this refined further to support full pinching to zoom instead of only one finger moving, if that's possible. Regardless, I'd like to say thanks for all your hard work, and thanks for sharing this groundbreaking development with us!
great work...
بارك الله فيك و جزاك خيرا...
God bless you brother !!! Thanks a lot
Microsoft Innovation Centre in Singapore has their hands on a developer LG Panther running WP7. They have a lot of pictures but better then that they have a video of the phone first booting and the setup you go through when you do so. I have to admit that it looks likes WP7 is running very smoothly! Hit the link and scroll down to see for yourself!
http://innovativesingapore.com/2010/05/windows-phone-7-spotted/
Silverlight required!
Not seeing the video anywhere in your link
Yeah It looks like they took the video off the page.
heres a youtube link of it
http://www.youtube.com/watch?v=_JqAnhYVeZs
really cool video guys...
man .. too much on scrolling on time-zone
can these guys innovate an easy way to pick a time zone?? can they just provide a map and and an initial spot where we can select the time-zone also once the spot has been tapped, it will zoom out to a more specific time zone in the current GMT??
how's that for change?
loving the flick and scroll too much is sometimes we forget to think of better way.
I would hope that you could just start typing the name of the city. A side scroll bar would be nice too for those really long lists. But I guess that's too Windows Mobile looking.
How about set the time zone by GPS automatically?
Hi Folks,
I had an Omnia 7 in my labs some time ago to write an article - back then, I cannot remember the machine working in landscape mode.
I now got another one from a friend who is higher up at a carrier, and it can do landscape mode in Messaging, Calendar and various other apps (but not the tile list).
Am I just forgetting things, or is this machine weird?
Do you mean you can read the text messages in landscape or you can see the list of texts in landscape?
Well I'm pretty sure all retail WP7 devices have landscape support in the areas you mentioned.
certain things have landscape support such as the ones you mentioned, and certain things don't, such as the start screen/app list, and panorama controls.
it's not that they can't support it, it's just sometimes it doesn't make sense to. for example, look at the xbox hub, imagine trying to use the panorama control in landscape mode. it quite quite difficult. I'm developing an application at the moment and am trying the both mode support for pilot controls (the one where you see each page's headers next to each other, rather than a whole page jump), and though it works, the landscape support looses a lot of visible content because the headers take up quite a bit of space. but in saying that, there may be requirements for having it.
why did i give that example? well it's up to the dev's discretion whether it's needed or not. but yea, things like messaging, email, calendar, web browser, they all have it at least. which are probably the most important ones.
To my mind, it's not very natural to hold a phone in landscape orientation, so I would only do so where the content needed it - videos, big HTML emails, web browsing, photos, games etc. WP7 covers all that so I'm happy. I think people can sometimes obsess over things like this and need to chill a bit.
OGCF said:
Do you mean you can read the text messages in landscape or you can see the list of texts in landscape?
Well I'm pretty sure all retail WP7 devices have landscape support in the areas you mentioned.
Click to expand...
Click to collapse
Hi Folks,
sorry to take so long for responding. Yes, we can see the list of texts AND the texts themselves in landscape mode.
In addition, we have full landscape support in:
x) Settings (!!!)
x) Alarms
x) Calendar
...
The ROM version is stated as
OS rev 7.0.7004.0
Firmware revision: 2424.10.9.9
I can do all that with my HD7 aswell, I think every device can do so.
Dear developers,
As we develop more and more apps, and as the Windows Phone marketplace hit 10,000 apps, I noticed an increasingly annoying trend: Abuse of panoramic hubs.
Yes, I understand that our latest greatest app may be our first important app, but as a user, the app is only one of my many tools in my toolbox, not the center of the universe.
And I understand that a lot of us want our app to be the hub above all other apps, however, let's face it - it's unlikely any third party hubs will be as important as Microsoft's hubs.
While the 6 major hubs in Windows Phone 7 presents some sort of extensibility, a lot of 3rd party hubs don't really do much except the function it is confined to.
A panoramic hub lets developers put different types of list controls in the same page, often for the purpose of showcasing the many depths of the app. However, some apps don't really have much depth, and the usage of panorama in this case feels like 40 pages for table of contents for a 20 page book.
If the app only displays one type of data, a pivot suits a lot better.
And panorama views usually come with a gigantic title, which takes up lots of precious screen space.
Sometimes I noticed that some developers will try to use a background in an app. However, if the app does not have a strong reason to have a background, e.g. dynamic content, I think it's a lot better to let users decide their background colors in their own theme settings. This can save us a lot of Photoshop time, and save users from a lot of text legibility problems.
Just something I'd like to share as both an app developer/designer and a user. Thanks for reading. Peace.
I agree with the fact that the panorama is overused where the pivot is in 99% of cases more appropriate.
I definitely don't agree with the background image thing. Two simple points: Brand Image and Individuality. From a developer standpoint you need something that sticks in users' brains - nothing does so more than product branding. And images are an integral part of that. Since a mobile device doesn't have room for giant logos, the best thing to do is move it to the background and let the text sit on top of it.
I agree that the developer should always offer a choice of background and ensure the text is fully legible in all - but Marketplace rules forbid text not to be legible anyway.
Second, for every application in the Marketplace there are 10 more identical in functionality. So why get the user to use your app over the other 10? Make it look better. And you can't make it look better when it's using the same colour scheme and layout.
pakkei said:
And panorama views usually come with a gigantic title, which takes up lots of precious screen space.
Click to expand...
Click to collapse
Modifying panorama's header template u can do whatever you want with the title (even delete!). Also, most important feature of panorama control is a nice looking slightly scrolling background image (that, I believe so, MS borrowed from Android's home screen).
Panorama != Hub
There is currently no way for a third-party developer to create a hub. Just because an app has a panorama view does not make it a hub.
I do agree though, the panorama view is overused.
I'd be interested if you could give an example of an app over using it as I really enjoy it when used well.
Purely from a developers perspective, I'm slightly worried that I may fall in the category of overuse.
emigrating said:
I do agree though, the panorama view is overused.
Click to expand...
Click to collapse
I disagree.
I think panorama apps are great. Instead of clicking and then having to go back you just swipe.
Best example for me was 1800pocketpc app which was a panorama/hub.
And then apps like facebook that are purely panorama are much easier to navigate cause you never need to reach for the back key
I love the panorama apps i have , its unique to our phones and what makes it great!
evolutionqy7 said:
I disagree.
I think panorama apps are great. Instead of clicking and then having to go back you just swipe.
Best example for me was 1800pocketpc app which was a panorama/hub.
And then apps like facebook that are purely panorama are much easier to navigate cause you never need to reach for the back key
Click to expand...
Click to collapse
I mean that the Panorama is overused because the Pivot is a much neater way of displaying data imo. I think it separates it out nicely.(Pivot being the Outlook-style swiping to sections)
However, some apps do the panorama justice. Faebook, IMDb, etc. However 3rd party developers rarely use it right.
Sent from my OMNIA7 using Board Express
Don't get me wrong - I love the Panorama view, but some [a lot] apps do misuse it.
I have seen plenty of apps which rather than having a "settings" button to open a new view will create their settings page (and about page) as part of the panorama. That is, IMO, not how you should utilize Panorama.
The same goes for apps where you may search for something to add to your "library", placing the search page on your panorama is wrong. It doesn't belong there.
A panorama should, again IMO, be used to display information that belongs together.
Example. You have a DVD collection app; The app is more than welcome to use a panorama as the main page, perhaps it can display "all", "new" and "favorites" on different pages of the panorama. That's all fine. However, adding more pages to display settings, about, search, changelogs etc just gives an awful UX. Add settings/about/changelog as a pivot on it's own page, accessible by a settings button. Add search as a button, either opening a completely new page or an popping up an overlay on the panorama.
Interesting point, and am inclined to agree Panarama views shouldn't be padded with search and settings screens. After all, doesn't the phone sport a physical search button that would be more consistent and allow you to combine your app settings within the phones' main settings for added convenience?
Sent from my HD7 T9292 using XDA Windows Phone 7 App
emigrating said:
A panorama should, again IMO, be used to display information that belongs together.
Example. You have a DVD collection app; The app is more than welcome to use a panorama as the main page, perhaps it can display "all", "new" and "favorites" on different pages of the panorama. That's all fine. However, adding more pages to display settings, about, search, changelogs etc just gives an awful UX. Add settings/about/changelog as a pivot on it's own page, accessible by a settings button. Add search as a button, either opening a completely new page or an popping up an overlay on the panorama.
Click to expand...
Click to collapse
The above is actually incorrect. A pivot should be used when the data of all screens are based on the same underlying data source. Outlook is the perfecet example, as you have all, new, unread which is just filters or views based on the same source: your inbox. The above where you have DVDs should be a pivot as well, since all, new and favorite are based on the single source of your DVD collection.
This is actually where people are making common mistakes with the use of a Panorama control, when it should really be a pivot control. Most users really won't know the difference between the two controls, but developers should to keep the user experience consistent across applications.
The use of a Panorama for a main screen to offer different sections of you applications is a good idea. Be careful to not have too many though. Once you have more than 4-5 sections in a Panorama, the user has the ability to get lost. And remember unlike pivots, the header of each Panorama is seperate from the others (a pivot combines them giving a better hint of the other pages).
Some things to ponder would be in a multi-page settings setup should you use a pivot or a panorama? Since its really not based on data, it should be a Panorama, but a pivot might give a better user experience.
spokanedj said:
The above is actually incorrect. A pivot should be used when the data of all screens are based on the same underlying data source. Outlook is the perfecet example, as you have all, new, unread which is just filters or views based on the same source: your inbox. The above where you have DVDs should be a pivot as well, since all, new and favorite are based on the single source of your DVD collection.
Click to expand...
Click to collapse
I wouldn't say it's incorrect. A pivot may have been a better choice, but it was based on an existing app I have installed where the panorama view isn't completely wrong.
I also believe your argument falls when we step into movie details - this should clearly be displayed as a panorama even though it's based on the same data.
spokanedj said:
Some things to ponder would be in a multi-page settings setup should you use a pivot or a panorama? Since its really not based on data, it should be a Panorama, but a pivot might give a better user experience.
Click to expand...
Click to collapse
A settings page should, IMO, always be a pivot (if more than one screen is really necessary - often it is better to have a scrollable listview instead). That said, if you manage to keep your settings on a single page, using a panorama view would still work to display the about/support/etc screens.
emigrating said:
I wouldn't say it's incorrect. A pivot may have been a better choice, but it was based on an existing app I have installed where the panorama view isn't completely wrong.
I also believe your argument falls when we step into movie details - this should clearly be displayed as a panorama even though it's based on the same data.
Click to expand...
Click to collapse
Here is a video from MS that clarifies this. Pivots should be used when displaying different views or filters or data. For the Movie details if you look at the "bad pano" example, around 11:00 it explains why you woulnd't want to do that. Just because another app is using it, doesn't mean you should.
http://channel9.msdn.com/blogs/jaime+rodriguez/windows-phone-design-days-pivot-and-pano
spokanedj said:
Here is a video from MS that clarifies this. Pivots should be used when displaying different views or filters or data. For the Movie details if you look at the "bad pano" example, around 11:00 it explains why you woulnd't want to do that. Just because another app is using it, doesn't mean you should.
http://channel9.msdn.com/blogs/jaime+rodriguez/windows-phone-design-days-pivot-and-pano
Click to expand...
Click to collapse
?
I pretty much agreed with you that it I presented a bad example. That said, it still works and was nowhere near as bad as many of the apps in the marketplace today.
As for movie details, let's just agree to disagree. Displaying movie details (as opposed to movie listings as discussed above) in a pivot is somewhat counter intuitive and gives a far worse UX than a panorama - I know, I've tried (and had it useability tested by the actual target audience).
Hi there,
Some of you might have already noticed our project, a ball shaped camera you can throw into the air to capture a fully spherical panorama. We are currently running an Indiegogo crowd funding campaign to raise the funds needed. We see that many campaigns nowadays launch with apps, usually only iOS and most of them don't really put much effort into their apps. We want to go a different way as I am a long member of xda-devs and include the community into the app development. As the camera is supposed to be used with a smart phone or tablet, the app is essential for the Panono.
So what does our app actually do? Well, you can re-experience the situation captured with the Panono camera by navigating the 360x360 panoramas by moving your phone/tablet like a window into the captured moment. If my English failed to make it understandable, please have a look at the video starting from 1:22.
We are facing a problem with our app which is caused by the different implementation of the gyroscope sensor reading in different phone models. Unlike on iOS, only few Android phones have a correct algorithm to calculate the current device orientation. The result is a shaky experience in our app. We are trying our best in optimizing our app to work with all devices. To address this issue, we are also having a talk at droidcon in Stockholm right now.
So what help are we seeking right now?
We need people who have a android phone with built-in gyro test the app. The following feedback would be interesting:
Device model: (e.g. Samsung S4)
Shakyness: (e.g. image is jumping around but the orientation is correct)
Lag: (e.g. it takes a while until the correct orientation is displayed)
Jumps: (e.g. the orientation jumps into some random direction for a few frames and returns to the right direction afterwards)
You can get the app here: https://play.google.com/store/apps/details?id=com.panono.panonoviewer
If you have any question about the Panono as the next-gen accessory for your android device, you can also post here, of course.
Thanks!