Status Update
Comments
aa...@gmail.com <aa...@gmail.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.
sh...@gmail.com <sh...@gmail.com> #3
I have this same issue and am not using dagger. We do use roboguice though.
ca...@gmail.com <ca...@gmail.com> #4
It seems that there may be an incompatibility between Dagger and Jacoco. In my project I am attempting to use the jacoco gradle plugin directly. What I am seeing is that Dagger generates java and class files with 2 consecutive dollar-signs in the name such as:
MyModule$$ModuleAdapter.java
MyModule$$ModuleAdapter.class
MyModule$$ModuleAdapter$ProvideBusProvidesAdapter
etc.
Jacoco however, seems to be looking for names with single dollar signs:
.../build/classes/debug/com/gravitymobile/haburdio/dagger/MyModule$ModuleAdapter$ProvideBusProvidesAdapter.class (No such file or directory)
MyModule$$ModuleAdapter.java
MyModule$$ModuleAdapter.class
MyModule$$ModuleAdapter$ProvideBusProvidesAdapter
etc.
Jacoco however, seems to be looking for names with single dollar signs:
.../build/classes/debug/com/gravitymobile/haburdio/dagger/MyModule$ModuleAdapter$ProvideBusProvidesAdapter.class (No such file or directory)
mi...@corp.badoo.com <mi...@corp.badoo.com> #5
any sooner will gonna get this feature available? =)
ss...@gmail.com <ss...@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
ch...@gmail.com <ch...@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
ch...@gmail.com <ch...@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?
ca...@gmail.com <ca...@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.
aa...@gmail.com <aa...@gmail.com> #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.
ma...@gmail.com <ma...@gmail.com> #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.
xa...@android.com <xa...@android.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.
xa...@android.com <xa...@android.com> #16
ma...@gmail.com <ma...@gmail.com> #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
xa...@android.com <xa...@android.com> #19
thanks, montgomery, for the link to the channel api talk. looking forward to try using it.
we...@gmail.com <we...@gmail.com> #20
Waiting for a simple websocket API in GAE.
si...@gmail.com <si...@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.
m....@gmail.com <m....@gmail.com> #23
ss...@gmail.com <ss...@gmail.com> #24
Just to let you know, I've put together another patch which enables the current GAE SDK 1.3.6 to use TyphoonAE's Web Socket API. It also adds a simple Web Socket Service backed by tornado web. It supports the hixie-75 and hixie-76 specification. Therefore, it can be used with Chrome 5, Safari 5 and Firefox 4.
http://code.google.com/p/typhoonae/wiki/WebSockets
I wonder if I should port the Channel API to use Web Sockets...
I wonder if I should port the Channel API to use Web Sockets...
va...@gmail.com <va...@gmail.com> #25
Is this on the way?
Description
while developing Android applications (Emulator, DDMS, Eclipse support,
ant scripts...). Use the Developer templates for issues with Android
itself.
Please describe the problem in detail, with the following information (if
applicable)
Host OS: Ubuntu 14.04
SDK tools version (available in the "About" section of the 'android' tool
UI): 22.6.3
Android Studio version: 0.5.7
Platform targeted by your project: 19
Version of the platform running in the emulator: 18
STEPS TO REPRODUCE:
0. Have project that uses Dagger and Android Gradle plugin 0.10+
1. Add 'testCoverageEnabled true' to testing build type
2. Run ./gradlew cC
EXPECTED RESULTS:
Tests should run and get a coverage report in build/reports/coverage.
OBSERVED RESULTS:
Test crashes with
Tests on Nexus_7_4.3(AVD) - 4.3 failed: Instrumentation run failed due to 'java.lang.VerifyError'
03:35:46 E/Device: Error during Sync: Remote object doesn't exist!
null
java.io.IOException: com.android.ddmlib.SyncException: Remote object doesn't exist!
at com.android.builder.testing.ConnectedDevice.pullFile(ConnectedDevice.java:114)
at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:158)
at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:42)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: com.android.ddmlib.SyncException: Remote object doesn't exist!
at com.android.ddmlib.SyncService.pullFile(SyncService.java:314)
at com.android.ddmlib.Device.pullFile(Device.java:849)
at com.android.builder.testing.ConnectedDevice.pullFile(ConnectedDevice.java:107)
... 8 more
:connectedAndroidTest FAILED
ADDITIONAL INFORMATION:
Attached sample project.