Profile cover photo
Profile photo
Jeffrey Smith
About
Posts

While it looks like support for JuiceSSH has withered, I wanted to report a bug just in case someone is listening.
When a background color has been set (by terminal control sequence), and a CRLF causes scrolling, the new line should immediately be painted with the set background color. JuiceSSH does not do so until a character is printed on the line. One result of this is that scrolling down one line at a time in vim results in blank lines not matching the background color of non-blank lines.
I have screen-captures and minimal demonstration code if anyone could make use of them.

TLDR: After 18+ months warning, a class of plugins has been disabled in Chrome 42.  Some plugin developers still haven't responded.

  Got a message from a digital sheet music company I have used in the past. They say changes in Chrome 42 prevent the Scorch browser plugin they depend on from working. This is surely because of "NPAPI" plugins being disabled.
  I saw this coming 1+1/2 years ago ( http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html ). Google has provided guidance for developers, and has gradually been tightening the screws in Chrome, so surely the Scorch maintainers knew.  There actually is a way for advanced users to re-enable it, but even that will go away in a few months.
  It appears that someone dropped the ball with Scorch, and I wonder how it will all shake out. Some people may switch to Firefox, but that's not an answer for many people. It would be great if they would build a more cross-browser/cross-platform solution, but I won't hold my breath.
Add a comment...

Post has shared content
Oh my!
Man I still know people that do this... so sad :(
Photo
Add a comment...

Post has attachment
Yay for Android Studio 1.0 being released!  As I understand it, most everything that was working with ADT should be working with Android Studio except for NDK stuff.  Whether or not you've switched to it, make sure you take the survey. 

Post has shared content
Add a comment...

+Xavier Ducrohet I made some patches to the SDK back 4 months or so ago, based on the idea133 branch, but that never got pulled in.  Since the idea133 branch is obsolete, and I saw a recommendation against "random contributions in studio-1.0-dev", I rebased them to studio-1.1-dev.  Now I see that practically no one else is basing off of studio-1.1-dev.  Was I right to choose studio-1.1-dev, or should I move them to studio-1.0-dev?

Post has shared content
This isn't usually the case with me, but I have had my moments... days... weeks...
Photo
Add a comment...

+Xavier Ducrohet I'm trying to make improvements to the android comand-line tool (sdkmanager.jar)... specifically for the command 'android create project --gradle'.  A few days ago I submitted changes against the idea133 branch for this.  Since this is related to the command-line tool, not Android Studio, should I submit it against the master branch?

Post has attachment
I published my first Android app today.  #android #babysteps  
Add a comment...
Wait while more posts are being loaded