Assigned
Status Update
Comments
am...@google.com <am...@google.com> #2
Specially being able to talk to our XMPP bots via GTalk like:
var ws = new WebSocket("ws://talk.google.com ")
Possibilities are endless for instant communication, social games, real-time
monitoring, etc.
var ws = new WebSocket("ws://
Possibilities are endless for instant communication, social games, real-time
monitoring, etc.
ho...@gmail.com <ho...@gmail.com> #3
Hi,
Thank you for the quick response.
Link to sample project:
https://drive.google.com/file/d/0B-Rwk6WHJMz2OWlUQlJrSGRIMXM/view?usp=sharing
Observed behavior: When I scroll to the top and bottom of RecyclerViews (or any other scrollable views) I see the theme-colored "bubble" that comes up from the edge I'm scrolling toward, and wiggles to follow my finger. I understand this to be the "over-scroll" that corresponds with android.view.view getOverScrollMode(). When I set the overscroll mode of a support library RecyclerView (android.support.v7.widget.RecyclerView) to be OVER_SCROLL_IF_CONTENT_SCROLLS, even if the RecyclerView is empty or does not need to scroll, the overscroll UI still appears.
Expected behavior: The documentation states:
public static final int OVER_SCROLL_IF_CONTENT_SCROLLS
Allow a user to over-scroll this view only if the content is large enough to meaningfully scroll, provided it is a view that can scroll.
Based on this documentation, I would expected that if I set my RecyclerView to this overscroll mode, then if the RecyclerView was empty, or was small enough to not meaningfully scroll (i.e. all its views were visible without scrolling), then the overscroll UI would not display.
Device: Huawei Nexus 6P
Build: Android 6.0.1, API 23
compileSdkVersion: 23
RecyclerView support library: com.android.support:recyclerview-v7:23.1.1
Steps to reproduce the issue with my apk:
1. Start application
2. The descriptive text view describes the state and expected behavior at each step.
3. In the first state, the recycler view contents are smaller than the screen (1 item only) and the overscroll mode is set to NEVER. Therefore, there should be no overscroll UI -- and indeed there is not.
4. Press NEXT STATE
5. In the second state, the recycler view contents are smaller than the screen (1 item only) but the overscroll mode is set to ALWAYS. Therefore, the overscroll UI should appear -- and it does.
6. Press NEXT STATE
7. Now, the recycler view contents are too large to all fit on the screen at once (50 items). And, the overscroll mode is set to IF_CONTENT_SCROLLS. Therefore, I would expect the overscroll UI to appear -- and it does.
8. Press NEXT STATE
9. In this last state, the recycler view contents are smaller than the screen (1 item only) and the overscroll mode is set to IF_CONTENT_SCROLLS. Since the recycler view cannot meaningfully scroll, I would therefore expect the overscroll UI to not be shown. But, it is shown. This is a bug, in my understanding.
Thank you.
Thank you for the quick response.
Link to sample project:
Observed behavior: When I scroll to the top and bottom of RecyclerViews (or any other scrollable views) I see the theme-colored "bubble" that comes up from the edge I'm scrolling toward, and wiggles to follow my finger. I understand this to be the "over-scroll" that corresponds with android.view.view getOverScrollMode(). When I set the overscroll mode of a support library RecyclerView (android.support.v7.widget.RecyclerView) to be OVER_SCROLL_IF_CONTENT_SCROLLS, even if the RecyclerView is empty or does not need to scroll, the overscroll UI still appears.
Expected behavior: The documentation states:
public static final int OVER_SCROLL_IF_CONTENT_SCROLLS
Allow a user to over-scroll this view only if the content is large enough to meaningfully scroll, provided it is a view that can scroll.
Based on this documentation, I would expected that if I set my RecyclerView to this overscroll mode, then if the RecyclerView was empty, or was small enough to not meaningfully scroll (i.e. all its views were visible without scrolling), then the overscroll UI would not display.
Device: Huawei Nexus 6P
Build: Android 6.0.1, API 23
compileSdkVersion: 23
RecyclerView support library: com.android.support:recyclerview-v7:23.1.1
Steps to reproduce the issue with my apk:
1. Start application
2. The descriptive text view describes the state and expected behavior at each step.
3. In the first state, the recycler view contents are smaller than the screen (1 item only) and the overscroll mode is set to NEVER. Therefore, there should be no overscroll UI -- and indeed there is not.
4. Press NEXT STATE
5. In the second state, the recycler view contents are smaller than the screen (1 item only) but the overscroll mode is set to ALWAYS. Therefore, the overscroll UI should appear -- and it does.
6. Press NEXT STATE
7. Now, the recycler view contents are too large to all fit on the screen at once (50 items). And, the overscroll mode is set to IF_CONTENT_SCROLLS. Therefore, I would expect the overscroll UI to appear -- and it does.
8. Press NEXT STATE
9. In this last state, the recycler view contents are smaller than the screen (1 item only) and the overscroll mode is set to IF_CONTENT_SCROLLS. Since the recycler view cannot meaningfully scroll, I would therefore expect the overscroll UI to not be shown. But, it is shown. This is a bug, in my understanding.
Thank you.
am...@google.com <am...@google.com> #4
Hi,
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
xp...@gmail.com <xp...@gmail.com> #5
any sooner will gonna get this feature available? =)
jp...@gmail.com <jp...@gmail.com> #6
It is currently not on the timeline yet, however we have acknowledge that this would be
a useful feature. If you cannot wait, here is one alternative:
http://groups.google.com/group/google-appengine-
python/browse_thread/thread/a12350c582d32ea4
a useful feature. If you cannot wait, here is one alternative:
python/browse_thread/thread/a12350c582d32ea4
de...@gmail.com <de...@gmail.com> #7
Just to let you know, I've implemented a tiny sample app. It's actually running in two locations:
http://hybrid.typhoonae.org
http://typhoonae-hybrid.appspot.com
fu...@gmail.com <fu...@gmail.com> #8
i tried on firefox 3.5 it does not support websocket? . ur code written in python?
any demo in java?
any demo in java?
jo...@gmail.com <jo...@gmail.com> #9
@8
According to
http://wiki.whatwg.org/wiki/Implementations_in_Web_browsers#Web_Sockets
Web Sockets are only implemented in Chrome dev channel (4.0.238.0 or later), although
there are efforts to implement it in Firefox and Safari/WebKit.
According to
Web Sockets are only implemented in Chrome dev channel (4.0.238.0 or later), although
there are efforts to implement it in Firefox and Safari/WebKit.
[Deleted User] <[Deleted User]> #10
Una de las vías de fomentar html5 es dar las herramientas adecuadas para su desarrollo,
GAE funciona sobre jetty, y este ya tiene una implementación de un servlet para
websockets, entiendo entonces que si Google apuesta por el html5 también apuesta por
websockets, por lo que esto es algo que debería implementar en GAE.
GAE funciona sobre jetty, y este ya tiene una implementación de un servlet para
websockets, entiendo entonces que si Google apuesta por el html5 también apuesta por
websockets, por lo que esto es algo que debería implementar en GAE.
[Deleted User] <[Deleted User]> #11
I'm using Websckets already with FlightGear flightsimulator to update google maps on
Chrome.
This would be wonderful to have.
Chrome.
This would be wonderful to have.
as...@gmail.com <as...@gmail.com> #12
WebSockets is going to be very handy for our products is we could host them on GAE
instead of using thrid-party hosts.
instead of using thrid-party hosts.
am...@google.com <am...@google.com>
lb...@gmail.com <lb...@gmail.com> #13
It would make sense to implement this as it'll result in a much lower load on the servers instead of having to deal
with constant pull requests
with constant pull requests
ya...@gmail.com <ya...@gmail.com> #14
Hi,
I'm so excited to see it implemented into GAE! For me, it's a true web's revolution.
RL, France.
I'm so excited to see it implemented into GAE! For me, it's a true web's revolution.
RL, France.
be...@gmail.com <be...@gmail.com> #15
Safari 5 now implements Web Sockets (http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol-75 ). Go for Web Sockets! http://typhoonae-hybrid.appspot.com and http://hybrid.typhoonae.org uses the same protocol but will support the newer version http://www.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-00.txt soon.
Looking forward to the new Chanel API using Web Sockets.
Looking forward to the new Chanel API using Web Sockets.
lb...@gmail.com <lb...@gmail.com> #16
am...@google.com <am...@google.com>
[Deleted User] <[Deleted User]> #17
Firefox 4 now supports websockets so lets get a jump on this!
[Deleted User] <[Deleted User]> #18
I'm using cron job to poll an url to emulate a push service, websockets is the natural solution and replacement to this kind of work around
sa...@google.com <sa...@google.com>
lb...@gmail.com <lb...@gmail.com> #19
thanks, montgomery, for the link to the channel api talk. looking forward to try using it.
ad...@google.com <ad...@google.com>
sa...@saket.me <sa...@saket.me> #20
Waiting for a simple websocket API in GAE.
as...@gmail.com <as...@gmail.com> #21
naval.duddoria : its already in 1.3.5 SDK (channel API) .. I am just waiting for a python example and its entries in the documentation.
Description
I have a layout like this:
<FrameLayout
xmlns:android="
xmlns:tools="
android:layout_width="match_parent"
android:layout_height="match_parent"
android:clickable="true">
<android.support.v7.widget.RecyclerView
android:id="@+id/settingsOptions"
android:layout_width="match_parent"
android:layout_height="wrap_content"/>
</FrameLayout>