pride: for android
the current version: r218
May 2013 - March 2014: 7000+ downloadsDownload latest version
A workaround was added to pr_stripImages.sh in order to overcome a bug in Android lint. Lint only identifies the first occurrence of unused resources. So its raw output is insufficient for identifiying all unused images.
Pride combines bash scripts, zenity, ant, ImageMagick, and the Android tools to create a fast and simple POSIX alternative for Android development. It provides all the basic commands (clean, build, release, etc.) of other Android IDEs. But it is primarily a robust and simple injection framework. Injections from methods to clusters of activities are easily created from existing code and can then be injected into any project. Pride can also be used to batch build, load or release multiple projects and can update class and resource files among projects which use the same objects or resources.
the gnu license
Pride is released under the GNU General Public License. Note that this does not affect the licensing of apps which use pride. (I used to work with the lawyers at SUN as a systems engineer.) There is NO REASON not to include GNU files in a paid app. The GNU GPL only affects pride files. If you fix or enhance a pride file, feed it back into the project. If someone asks for your GNU code, which is unlikely, just send it to them. It's a pride file, right? Don't send them your entire app source. ANYTHING outside the pride files comes under your own copyright. All of my apps are released under my personal copyright, all rights reserved. They all use pride code. Want my GNU code? Download pride. Want to see my other code? You'll have to wait until 70 years after I'm dead. Or longer, if my heirs renew the copyright.
the reason pride exists
Pride is for independent developers. It was created as an easy-to-use injection framework because I don't like writing or researching anything twice. Everything you use more than once can be made into an injection. And every injection you create, except original core logic, can be fed back into the project. Keep in mind that most core logic isn't that original. There is lots of my core logic in pride already.
Look for whole activities and for clusters of multiple activities for injections. Object-oriented code is like Lego. Most apps are like little Lego boats and houses. If we combine our work with pride, we will be building apps more like the QE2 and the Taj Mahal. If you are trying to make money with Android apps, you can see the possibilities of pride. But pride won't get there unless we combine our efforts.
Just email your injections to the Contact Email above. I will make sure they build and run. Then I will cut a new release. The potential of pride is the synergy of independent development.
the things pride is not
- Pride is not a new system of Android development. It does everything in the canonical way so that anyone can use it.
- Pride is not a binary. It is a system of Bash scripts using the Android SDK and pride's other dependencies.
- Pride is not a source repository. It is an injection system for anything from methods to clusters of activities with their src and res files.
- Pride is not difficult to use. Only Object injections require new Bash scripts. All other injections require minor setup and edits.
- Pride is not an editor. Use any editor you like with pride.
- Zabri: provided class list for Pride::Import
- Se'b: wrote remove_unused_imports.awk
If your organization, of any kind, would like help in realizing the potential of pride, I am available for consultations, presentations, and training. In my experience, pride is roughly six times more productive than any of the monolithic IDEs and its collaborative potential is unbounded. Any development effort would greatly benefit from the synergy pride makes possible. Contact Email.