droid-at-screen is a free Java-based app that displays the content of your phone’s display to your computer’s display, when the phone is connected via a USB cable.
Below is a screen snap shot taken from my computer display. At the upper left is the Droid@Screen application running. Droid@Screen is connected to my Nexus 5 phone.
At right is the display showing on my phone, which has been transferred from the phone to my computer over a USB connection. I’ve circled two user interface items – the magnifying glass icon is used to adjust the display size of the phone’s screen. Since the phone has a 1920×1080 display, the initial image is quite large!
Below that is a camera icon. Click on that to take a snapshot of what is on the screen, and then save the screen image to a local file.
At the lower left is the DroidAtScreen .jar file. This is the Java executable program file. Assuming Java is installed on your system, double click the .jar file to begin running Droid@Screen.
Continue reading Using droid-at-screen to see your phone’s display on your computer
The Appril release of Quirky Linux includes the Android SDK (Software Development Kit), Android Studio, App Inventor, Oracle JDK (Java Development Kit), and LiveCode tools, as well as all of their dependencies, together with the JWM (Joe’s Window Manager) and ROX, providing one of the lightest environments for Android app developers.
“The intention is to have out-of-the-box, just-click-and-get-going Android app development, catering for total non-programmers with App Inventor, through intermediate with LiveCode, to hard-core coders with Android Studio,” says Barry Kauler, Puppy Linux creator.
Source: Puppy Linux’s Sister Quirky 7.1 Distro Arrives with Tools for Android App Developers
It actually runs the App Inventor system on the computer – does not require access to appinventor.mit.edu.
Download here (its free, of course). I have not tried this yet but would be interested to hear reports from users!
MIT has begun testing a new App Inventor feature that will enable developers to create their own “extension components”. Extension components are written in Java. Once created and tested, these new components may be shared with other App Inventor developers for use in programs.
What this means: if App Inventor lacks a feature or capability, then a Java developer familiar with App Inventor and its components software development kit will be able to add new features to App Inventor. Over time, the capabilities and power of App Inventor are likely to grow enormously – and rapidly. The ability to extend App Inventor’s features/components is an exciting and tremendously important development for the future of App Inventor!
For now, this feature is in “test mode”.
Source: App Inventor Extension Components available for testing | Explore MIT App Inventor
I posted the following on my App Inventor Facebook page – only a fraction of readers use the FB page so I am cross posting back over this blog. Usually I post items on the blog first, and then those end up on FB.
If you would like to follow the Facebook page, click here and then click on Like and also select “Get Notifications”.
Google will end support for Android Software development using the Eclipse Integrated Development Environment as they migrate development over to Google’s own Android Studio.
See here for details: http://www.androidcentral.com/google-stop-development-and-support-android-developer-tools-eclipse
This does NOT impact MIT App Inventor coders!
Eclipse and Android Studio are used for developing Android apps written in the Java programming language, and relying on the Android Software Development Kit of libraries of code. These tools are used to develop most Android apps as they are capable of using all of the features provided by Android, while MIT App Inventor limits us to a subset.
I just spent several days getting Android Studio up and running and reconfiguring an old project so that it now builds entirely in Android Studio. That Eclipse will be going away was sort of obvious.
I have completed all of the text for my next App Inventor e-book. However, once I finished, I decided to add even more! I am hard at work on one more chapter! I think a lot of people are going to love Volume 3 and I cannot wait to share it with you! However, its the middle of summer and my wife would like us to take an actual vacation so I need to work hard on my vacation skills for a few days before I can wrap up the book!
I hope to share a lot more with you in very early August.
Changes between nb143i and nb144 (June 30, 2015)
- When a component is renamed in the designer, any related collapsed blocks will be properly renamed now.
- Screen1 now has properties that permit you to hide both the top “Status” and “Title” Bars
- The selected item in a ListView is now highlighted
- Activity Starter component now has a “Activity Canceled” event
- Fix to the Player Component so it doesn’t spontaneously start playing after a phone call or other interruption
- Bugfix to Image Sprite rotation which had left screen artifacts on some devices
- Add Math blocks to convert between decimal, Hexidecimal and Binary representation
- Clock Component now permits you to format a date or time arbitrarily. You provide a “format string”
- You can now have both a Background Image and a Background Color and the “right thing” happens
- TextToSpeech: The designer now uses dropdown menus to select Country and Language. Added blocks to fetch the supports countries and languages on a given device
Source: Release Notes for MIT App Inventor 2 (Beta)
Source: MIT App Inventor usage for 2014-2015 Academic Year
As they point out, the cyclical ups and downs in usage suggest App Inventor is primarily used by students – with drop off in usage during school vacation periods.
That suggests an opportunity to expand usage of MIT App Inventor – by insuring that AI2 appeals to a wide audience of potential app developers and not just educational programs!