Profile cover photo
Profile photo
Thomas Broyer
1,519 followers
1,519 followers
About
Thomas's posts

Post has shared content
Showing off some quick techniques you can use to audit your site for accessibility. Check it out! https://goo.gl/rXajVD

Post has shared content

Post has shared content
Guava 20.0 released

Guava 20.0 final is now available in Maven Central as com.google.guava:guava:20.0.

This release includes quite a few new things, including a brand new package: com.google.common.graph. For GWT users, note that this release supports, but also requires, GWT 2.8.0. See the release notes (https://github.com/google/guava/wiki/Release20) for more information on what's in this release.

As always, if you encounter any issues you can report them to us on GitHub (https://github.com/google/guava/issues/new), and if you have questions about how to do something, we recommend using StackOverflow (http://stackoverflow.com/questions/ask?tags=guava).

Enjoy!
- +Colin Decker

Post has attachment
Watch out if you want to use Dagger‡ in your GWT project: make sure you don't put dagger-compiler in the classpath when running GWT (compiler, devmode, codeserver, tests, etc.), as both bring Eclipse ECJ/JDT with different versions.

https://github.com/gwtproject/gwt/issues/9447

If you're using Maven, use maven-compiler-plugin with version 3.5.1 (at a minimum, but it's currently the latest) and put dagger-compiler in the annotationProcessorPaths (note that there are a few downsides to that: http://blog.ltgt.net/maven-is-broken-by-design-2/ but it should be ok 99% of the time).

If you're using Gradle, simply put dagger-compiler dependency in the compileOnly configuration (might not work with the gwt-gradle-plugin, but should work with the fr.putnami.gwt plugin) or, better, use the net.ltgt.apt plugin and put it in the apt configuration.

Post has shared content
The European Commission is drafting new cybersecurity requirements to beef up security around so-called Internet of Things (IoT) devices such as Web-connected security cameras, routers and digital video recorders (DVRs).

https://krebsonsecurity.com/2016/10/europe-to-push-new-security-rules-amid-iot-mess/

Post has attachment
Looks like my Rubik's cube has a problem…
Photo
Photo
08/10/2016
2 Photos - View album

Post has shared content
What this all means is that the IoT will remain insecure unless government steps in and fixes the problem. When we have market failures, government is the only solution. The government could impose security regulations on IoT manufacturers, forcing them to make their devices secure even though their customers don't care. They could impose liabilities on manufacturers, allowing people like Brian Krebs to sue them. Any of these would raise the cost of insecurity and give companies incentives to spend money making their devices secure.

http://motherboard.vice.com/read/we-need-to-save-the-internet-from-the-internet-of-things

Post has shared content

Post has shared content
That also means you shouldn't use PushButton or CustomButton, stick to Button (and SubmitButton if you use forms), and possibly Checkbox and RadioButton if you need to toggle state. Use CSS to do the rest.
Thinking of making a fancy custom button? ✋

Just use <button>

Post has shared content
Number #1 error with GWT and build tools¹ is treating your app as a "monolith": your client and server parts are two distinct components that communicate over an unreliable network.

You wouldn't use the same Maven module or Gradle project² for your server and an Android app, so why trying to do it for your server and GWT (client) app? And if you share code, then use a shared library module/project.


¹ ok, maybe not #1, but still pretty high in the list; same would probably be true of all isomorphic tools too.
² this is less true for Gradle, due to its flexibility, but it would unnecessarily complicate your build script; one of the idea behind that client vs. server separation also being dependency segregation: don't put server-side dependencies in your GWT Compiler/DevMode classpath, and don't put GWT in your server-side classpath (except for the server/jvm-dedicated libraries).
Wait while more posts are being loaded