New version of the Android Testing Support Library
The release includes two major additions: Espresso-Intents: a Mockito-like API that enables hermetic inter-activity testing by allowing test authors to verify and stub outgoing intents. Test Rules: a set of Junit4 rules that replace ancient framework APIs like ActivityInstrumentationTestCase2 and ServiceTestCase.
All samples have been updated and a set of Espresso-Intents samples has been added to help you get started.
Of course, we have also squashed some reported bugs and addressed minor feature requests from android-test-kit. See release notes and javadoc for details.
#Dartlang is dropping its idea of having a VM inside of Chrome. This is either the death of Dart, or they are going to totally redo how they generate JS. According to Seth Ladd 1.9 (released tomorrow) will have lots of cool stuff. But then he promised me a 200K Dart Angular Hello World app at least 6 months ago... that didn't turn out well! (Last time I checked it was still around 800K. The Angular team has moved to #TypeScript.)
We work with many teams, inside and outside of Google, that use Dart every day to build business-critical apps. Their feedback is consistent: they love working with the Dart language, libraries, and tools, and they compile Da...
Note, it's even bigger than that... It turns out that Polymer is also rather fat... your best path to material design on the web is AngularJS. (For a significant MD app, AngularJS s about 1/4th the size of Polymer, better featured and has better backwards compatibility.) Current Typescript works acceptably with AngularJS 1. (I.E. numerous people deploy the two together in production apps.)
I have made a package that will give you the benefits of #WebComponents without the need to have all that new browser functionality like you need for #Polymer . It is slightly less elegant than the Polymer solution, but it doesn't interfere with you using your favorite framework/event handler/templating and data-binding solutions.
Welcome! This is a discussion area for the Google Developer Groups in Northern Colorado.
We have meetings usually the first week of the month on topics ranging from Android to web apis and frameworks.
We're hoping to have primarily GDG members from the area, but we welcome other surrounding GDGs and even far flung GDG members to participate!
Microsoft is making it incredibly easy for you to put nearly unmodified Android apps on Windows (Phone, Tablet and Desktop). They go to great lengths to make the resulting app behave properly under Windows. This won't be shipping until Windows 10, but you can experiment with it now. https://dev.windows.com/en-US/uwp-bridges/project-astoria
As Google I/O quickly approaches we are hard at work getting everything ready for a great I/O Extended.
A few days before I/O for the past few years a huge gathering of GDG Organizers from all over the world takes places in Mountain View. Every year there is an awesome shirt design that wins. This year GDG Chicago is proud to be able to put up a shirt design.
If we win I'll have some of these shirts to give away to the people of GDG Chicago. So +1 this if you like free shirts! +1 this if you like the awesome design +Virginia Poltrack created! or just simple +1 this post!
The more +1's we get on this post the better off we are so please reshare and ask others to +1 this post as well. #gdg#io15#shirt
It turns out that Dart 1.9.1 is available today. With the news I posted in the link below ( #Google saying that #Dartlang is "for the Entire Web") I decided to take it for a spin.
I feel compelled to say it is a complete and total joke. While I had sometime ago raised the JS generation issue with the Dart folks, after I had clearly and thoroughly made my point, I decided to back off... but things are simply in no way better than before. Google needs to either put up or shut up.
They still don't have a production ready UI library. Let this soak in: Dart was originally intended to be for client-side apps and 1 and 1/2 years after going to version 1.0, they still don't have a viable UI library. If that doesn't say defeat, I don't know what does. Polymer + Dart has been in "early development" for all of that 1 and 1/2 years. The Angular folks gave up and are using #TypeScript (which is what I did as well).
The Polymer ToDoMVC app (sort of their Hello World), generates 550K of JS (328K its own JS, 105K Webcomponents.js, 123K polymer.js). Any serious Paper app would take well over a meg of JS, just for Dart+Polymer overhead. These are the minimized sizes. The app takes 4 seconds to reload from a local dev server in Firefox.
How can #Google possibly be saying it's for "the Entire Web". It took, TEN MINUTES, to build a minimized JS version of the ToDoMVC app on a Haswell-core-i5 laptop. (The 10 minutes is not an exaggeration, it actually took a bit longer than that.)
If this is the state of Dart 1 1/2 years in, why should I ever believe it will be viable?
Sorry, +Seth Ladd, but the only way #dartlang is for the "entire web" is if you want to give the web some comic relief. And if you want to dispute this, I have only one thing to say... show me the working, released code, Google is no longer credible when it comes to promises about Dart.
Sometimes it is easy to forget just how many great things #Google has done! The number of open sources projects is truly phenomenal. (And this list, as large as it is, really doesn't capture everything). even deserves credit for encouraging stodgy places like #Microsoft (TypeScript, F#, even .NET) to adopt open source.
Today, I'd like to share with you some remarkable open-source projects the chromium team has been contributing to over the years. This non-exhaustive list is divided into chromium-owned projects and those the team has contributed to.
The world's first-ever Go Challenge starts off on 1st March 2015. Matt Aimonetti is setting the first challenge.
Nathan Youngman has agreed to set the guidelines for evaluation. Jacques Fuentes, Jiahua Chen, Jyotiska NK, Niket Patel, Nishant Modak, Piyush Verma and Pravin Mishra have all agreed to go thro' all the submitted solutions of a challenge. They will comment and rank these solutions.
We need more Gophers interested in evaluating the submitted challenge solutions.
Even if Polymer goes 1.0 next quarter, it probably isn't appropriate for real commercial use. The linked-to article explains a lot. I've also seen Mozilla raise concerns about Shadow DOM. I really think it very unlikely that Shadow DOM will fly in its current form. #Google is putting shockingly little thought into the future effect of some of the mechanisms it is proposing.
One simple example, the /deep/ combinator. They use this 46 times on the 'html' element in the "layout.html" that is part of Polymer. What that means is that ANY style change to ANY element in your DOM will have to be checked against all 46 rules. Now imagine several packages using that facility in every page in every tab. It's likely a bad idea.
I still believe that Web Components are a good idea, but Polymer is much too ill-thought out for me to buy-in. Major parts are unlikely to make it through the standards process.
The same guy also wrote this article: http://developer.telerik.com/featured/web-components-ready-production/ It basically says that document.registerElement is ready for use. This is what lets you make custom tags. (IE 9+ needed.) You probably want to use the alternate polyfill for it, rather than the one that comes with webcomponents.js. (He explains why in the article.) If you want to make web components now, this is probably your way forward.
Web components are the new hotness. And now that a complete web components implementation landed in Chrome 36, we finally have stable, unprefixed, unflagged version to try out. But, although web components are certainly something to be excited about, and a technology worth experimenting with, that doesn’t mean that they’re ready to use in your …
Hello everyone, I wanted to share this resource to you if you are someone who is interested in learning to build apps for Android, this youtube channel will contain all of my lecture note videos for the in-person class. Over the next 8 weeks I will post several various Android tutorials from beginner to intermediate topics. https://www.youtube.com/channel/UCg-xihUyTn6FnBZfVmaJisA