01/22/2013, 11:58 AM
|
#1 (permalink) |
|
Member
![]()
Posts: 13
|
Hi,
at first, sorry for my bad english, I'm from Spain and I am a big webos fan. I think in a possibility to replace de back gesture and on this way replace de virtual gesture area. Simply We have to move our finger from de screen to botton bizel. Would be a opposite gesture of card view (from bottom bize to the screen). In this form, We will gain more sreen space and with only two gestures, We will do all the actions. P.S. I'm sorry again for my very bad english |
01/22/2013, 12:33 PM
|
#2 (permalink) |
|
Member
Posts: 2,090
|
I see a problem with that. What if you're scrolling up a document? It's easy to drag your finger all the way to the bottom of the screen. A counter-argument can be made for scrolling up, but you don't start from the screen, so you could say there is no document under your finger. In any case, you'll probably be able to change the DPI setting to make more space if you want to.
There's also a forward gesture in webOS. What would you do with that?
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. |
01/22/2013, 01:31 PM
|
#3 (permalink) |
|
Member
![]()
Posts: 13
|
I don't know if it is technicaly possible. In the touchpad We can enter in the card view without gesture area. I don't if I explained well what I want to say, my propose is a "quickly" (this is important) gesture that starts at the botton of the screen and finish on the botton bizel. It is important that the Os can recognize (?) a page scroll (slowly) and my proposed back gesture (quickly)
------------ (Screen) Gesture start ¥ ----------- ¥ Gesture finish P.S. I know, is a terrible explain |
01/22/2013, 02:51 PM
|
#4 (permalink) |
|
Member
Posts: 2,090
|
Could work, though I'm not sure if there will be trouble interpreting the gesture. There could be buttons down there too, and it's quite likely for someone to swipe down while pressing the button. If you're using that area for a gesture, might as well make the entire area for gestures, since there won't be any ambiguity.
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. |
01/22/2013, 04:40 PM
|
#5 (permalink) |
|
Member
Posts: 1,840
|
I always thought a back gesture on the screen would be faster than going to the gesture area at bottom. It could possibly work in browser, but in email for example one would end up trying to swipe to delete
Last edited by laingman; 01/22/2013 at 05:05 PM. |
01/22/2013, 05:39 PM
|
#6 (permalink) |
|
Member
Posts: 2,090
|
Hmm... Maybe a three finger swipe can be implemented, similar to how it works on multi-touch touchpads these days?
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. |
01/22/2013, 06:24 PM
|
#7 (permalink) | |
|
Member
Posts: 159
|
Quote:
Here's the OwebOS settings App with the virtual gesture area: Enyo Bootplate App It works very nicely on the TouchPad |
|
01/22/2013, 06:46 PM
|
#8 (permalink) |
|
Member
![]()
Posts: 13
|
I believe that a virtual gesture area is not a good solution and is not in order of webos Ui philosofy.
The virtual gesture area bad waste an important part of The screen Only to emulate a single gesture (back) because other gesture can be implemented without it. P.s. Really understood anything of I wrote? |
01/22/2013, 11:59 PM
|
#9 (permalink) |
|
Member
Posts: 1,840
|
Multiple fingers on phone I'm sure would be worse than using the real gesture area, I think.
For one it would require two hands and more thnking.): We need to be careful not to waste the time and resources of our tlented developers fixing something that not broke. Trying to figure out how to get the virtual keyboard not to crash in landscape would be much better project in my opinion |
01/23/2013, 12:05 AM
|
#10 (permalink) | |
|
Member
Posts: 2,090
|
Quote:
(Anyone know whether or not Android phone ports of webOS will use the existing hardware buttons for gestures? Most (if not all) phones have a home and back button.) Edit: Talking about hardware buttons, the original proposal would, for example on my Galaxy S2X, be unusable. I'll always be hitting one of the hardware touch buttons, and they'll always do something I don't want them to do. Plus I'll always be hitting my case. For a counter-problem, I only manage to work the gestures in Chrome half the time, since in portrait the bezel is too thin, and in landscape I'll hit the buttons most of the time.
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. Last edited by GMMan; 01/23/2013 at 12:11 AM. |
|
01/23/2013, 12:36 AM
|
#11 (permalink) |
|
Member
![]() ![]() |
Well, my personal opinion is, that most of the gestures in WebOS are very much ok and very logical. "Back" and "Forward" gestures are ok for me.
What is a bit unlogical is, that after the "swipe up" to get to the app launcher, there is no "swipe down" to hide it again. Instead you need to swipe up again... But this is about the only discepancy I can see in the gestures. But that's just my 2 cents
__________________
War doesn't prove who's right, only who's left... |
01/23/2013, 01:09 AM
|
#12 (permalink) | |
|
Member
Posts: 159
|
Quote:
Did you even test the virtual area as implemented on webOS Ports? It's very thin , I dont really know how much space you'll gain there. swipping from the screen to the bottom, for me, is way too similar to the way you pull and throw away the cards especially if you're running Luna CE with big cards. But after all webOS is open source now, you can go with your solution, the community will pick up what suit better. |
|
01/23/2013, 01:16 AM
|
#13 (permalink) | |
|
Member
Posts: 159
|
Quote:
|
|
01/23/2013, 04:53 AM
|
#15 (permalink) |
|
Member
![]()
Posts: 13
|
I'm not really criticizing the virtual gesture area, simply I do not like. When I say that is not in keeping with the philosophy of UI OpenWebos I want to say that WebOS try to avoid unnecessary buttons replacing them with gestures. If we put a virtual gesture area, we are putting a great virtual button, then it ceases to be useful because a virtual back button is much more comfortable (a back button on the screen as the touchpad) or directly a physical gesture area (as Palm phones). Nor do I mean to impose my idea but I think it would be important to agree on a solution over the next ports to be performed. But we can find inconsistencies or even fragmentation.
And back to my idea, I still think that a gesture down from the screen is possible. If the touchpad can do backwards without interfering with the buttons or icons at the bottom of the apps, you could do the same in reverse (quickly). In another post it was said that it could be done laterally, from the inside of the screen to the left frame. It is a good solution that it could generalize in any direction. A gesture that is just within the screen from out of the frame. What do you think? P.S: hieroglyphic sponsored by google translator |
01/23/2013, 09:35 AM
|
#16 (permalink) |
|
Member
Posts: 2,090
|
I reiterate what I said above. The current phones that have been ported to are not bona fide webOS devices, hence no physical gesture area. If there is a real webOS phone there will be a physical gesture area.
I still see a problem with gesture anywhere. What if you're looking at a map? You could be scrolling in any direction off the edge. How about scrolling long lists? I know in Android, I have to flip through pages of posts on TweetDeck because it lacks a "top" button, and I usually flick really fast from top of the screen to the bottom and let its physics do some work. The thing is any time you're in a document you could also experience unwanted scrolling because you're beginning from a document frame. Either that or unresponsive scrolling.
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. |
01/25/2013, 02:32 AM
|
#17 (permalink) |
|
Homebrew Developer
![]()
Posts: 461
|
The current solution is to reserve a part of the screen for gesture area. If you look at the Galaxy Nexus port that works quite well... actually the modern Android Phones are good for that approach, because they got rid of the bottom hardware buttons and replaced them with "soft buttons", i.e. a part of the screen reserved for buttons... we are doing the same, just not with buttons but with our beloved gesture area.
![]() I don't like gesture everywhere... In fact I tried some of the more advanced gesture hacks in LunaCE and had to disable them... it was too confusing at times, when the device misinterpreted a not so clean scrolling on my part as swipe to switch app or do other fancy stuff. Additionally, especially for mobile phones (i.e. small devices I carry around, using while walking through the city or stuff) multi touch gestures are about the worst thing to rely on. The phone has to be usable with the thumb only, so you can use it and have your other hand free for something else (for example carrying shopping bags). For a tablet this is different... but I still would refrain from requiring multi touch gestures. |
02/13/2013, 05:23 PM
|
#18 (permalink) |
|
Member
![]()
Posts: 13
|
I found this:
Close apps easily with swiping down (You can toggle this on and off now, but will be on by default now) ( http://www.zdnet.com/blog/cell-phone...-keyboard/6881 ) Is a feature of meego's update (pr 1.1). Swiping down, it closes the current aplication. |
02/13/2013, 06:12 PM
|
#19 (permalink) |
|
Member
![]()
Posts: 13
|
I found this:
Close apps easily with swiping down, now on by default ( http://www.overclock.net/t/1163181/t...dy-to-download ) It is a feature on meego's update. Swiping down closes the current App. We can port this solution to OpenWebos. |
02/13/2013, 08:37 PM
|
#20 (permalink) |
|
Member
Posts: 2,090
|
We've already got card view. Why would we want that? Plus it'll break swiping to open menus (swipe a bit off or too far and you'll close your app).
__________________
Contact: @GMMan_BZFlag (me on Twitter) | webOS onTap | @webOSonTap webOS Releases: Change your App Catalog country: TouchPad/PC | TouchPad/webOS Resources | Search suggestion patch for browser | Cycling Email Notifications | Don't Doctor! Make a good support request. | How to post logs | webOS Charge Monitor I will be busy, so I may not be able to provide private support. |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|



