Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I know that you can download the docs in the android sdk but the whole thing is like 300MBs and I figure if the docs had a repo, and why shouldn't they since android is open source, I could get a shallow clone of the docs and then just pull it once in a while to have it updated. That way I don't have to download 300MBs every time there's some update.
That being said, can I do the same with the whole framework?
Yes, you can.
I don't think this approach will save bandwidth, though, as you'll need to sync all changes.
Clone the source repository with repo
repo init -u https://android.googlesource.com/platform/manifest
repo sync -j 10
Build the doc (sac stands for source.android.com)
make online-sac-docs
The whole documentation will be generated in out/target/common/docs/online-sac.
The Android Developer docs are released as part of the AOSP, which is released under the Apache 2.0 License. That means the source code is freely available - Github has a mirrored repo here.
However, just because you can, doesn't mean you should. You will probably be better off downloading the documentation from the SDK manager, as that way you won't have to generate the HTML files from the .jd template files in the repository. You can also configure automatic updates via the SDK manager, which is a lot less error-prone than relying on yourself to regenerate the docs every time the SDK changes. Unless your download speeds are awful, I don't see any reason to go down this road.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I'm writing tests for my android project and since there are more than one developer on my team, we'd like the commits to auto-build when we push our code to Git so we are now thinking of integrating a CI system like Travis or CircleCI. Since there are more than one options available, I'd want to pick one that builds and runs Test cases automatically along-with building the main app so that the team members would be notified if a Test has failed and what changes they need to make in their code. I've tried Travis, its good , (with some headaches while configuring with github repo), i was wondering if any of you guys have tried the three in question here and suggest one for our purpose.
There is a very good comparison made between these three in this stackshare table.
It is community driven too, so it might be a good starting point to decide which one are you going to use.
Travis CI:
Github integration
Free for open source
Easy to get started
Nice interface
Automatic deployment
Tutorials for each programming language
CircleCI
Github integration
Fast builds
Easy setup
Competitively priced
Slack integration
Great customer support
Jenkins
Hosted internally
Free open source
Great to build, deploy or launch anything async
Rich set of plugins with good documentation
Tons of integrations
Has support for build pipelines
I'd like to throw in that Snap CI can also do this. Plus there's also stages to test things incrementally allowing for faster feedback.
Here's a post that brings a little more information to the table.
https://blog.snap-ci.com/blog/2014/07/22/why-snapci-and-travisci-are-not-the-same-thing/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have developed apps on my own, but now I'm working with a mate.
What is the best way for multiple people to work on the same project and submit the changes?
Is this possible without a 3rd party server? Are their plugins for Eclipse that can solve this problem?
There are plenty of tools that will let you accomplish this.
Version control software such as subversion, mercurial, and Git will all accomplish this task. Git is currently the most popular of the three.
Depending in if you care about keeping to code private, the simplest path forward would be to create a repository on GitHub (private repo's cost money) or BitBucket (allows private repos for free accounts).
If you don't want to involve a 3rd party then you'll need to setup a repository on a computer that both you and your collaborator can access.
3rd Party approach
BitBucket is an online hosting site for Git and Mercurial which also offers a hosted wiki, issue tracker and source code. But you asked for an approach without a 3rd party (which I find perfectly reasonable) so here are some pointers
Doing it on your own
For Version Control: Git. "Bare Repositories" allow you to share code w/o a Server as simple as by a shared network directory.
But: Git is quite complex. You might want VisualSVN which is an easy GUI-driven Subversion-Server capable of running on one of your PCs.
For Issue Tracking: JIRA offers a 10$ edition bundled with other useful tools like Bamboo.
A Wiki for Documentation: Many options here.
Turnkey Redmine is a virtual appliance (downloadable image of a virtual machine). Just download and run i.e. inside VirtualBox and you quickly get a Version control, issue tracker, Wiki and other services in short time.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I want to create an open source application for Android that will be available through a repository control version system. The problem is pretty fundamental, I need a tutorial that will cover the basics of licensing & how to properly maintain and create open source project (application).
First of all, find a proper license that suits for your needs.
Maybe you can begin with this : http://en.wikipedia.org/wiki/Software_license and then dig into the different Opensource licenses : there are a lot.
http://www.github.com is a good challenger to host opensource projects. The help is great if you need to learn Git.
You will be the owner of the project and you will be able to accept or refuse contributions. Later, you will be able to give more rights to trusted buddies that will help you building the software (because when success rise, you won't be able to handle all the submissions).
I suggest you create an empty project and pratice on it, alone.
You can delete it when you feel enough comfortable with the interface, actions to do, etc...
Do not start directly with your final project.
You will make mistakes, better to do them on a dummy project.
Good luck :)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
My immediate need is to take a peek at the source for EditTextPreference and see what I need to do to implement support for preferences with more structure. Can I run Git or repo under cygwin perhaps? Is there an easier way?
If you just need to have a look at a single file you can use the web interface at https://android.googlesource.com.
If you want to check out the source tree you can use http://code.google.com/p/msysgit/
You probably want an ide to browse the code, so using the open source Eclipse or the free Intellij Community edition is recommended. In that case they both contain built-in git clients that you can use.
The Source Code is provided by the Android Open Source Project.
Inside the Page (Tab 'Source' -> Left Menu "Browse Source") you find a link to browse the Source. The link will lead you to a git repository. There is a "search" field and I found 'EditTextPreference' using this field with the 'grep' option.
Go to Google Code Search, and search with "android your class"
The first result for "EditTextPreference" is what your looking for.
You can browser the code source of Android's framework with this tool too. (and it works for Linux/Mac/Whatever users too ! ;)
Using Windows I did this by using Ubuntu live CD, and downloading all the source code using the linux instructions here http://source.android.com/.
There are some commands you need to use for the code to be downloaded to your main hardrive. I wrote a blog post about it here: http://udinic.wordpress.com/2011/11/18/the-source-for-all-goodness/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm considering making an existing mobile app into an open-source project. It has an Android and iPhone version.
While I have used open-source projects and submitted feature requests and bug reports, I have never created an open-source project nor contributed with a patch to an existing one.
What are the top things that I should take into account before opening the source of my project? What specific steps do you recommend taking for open-sourcing a mobile app?
You are lucky as when I started to run open source projects I did not realize this great book exists,
http://producingoss.com/
It provides general tips in almost all aspects of running an open source project, and you can add your own for mobile world.
You can publish you code on googleCode, SourceForge or Github, use all the power of theses websites (documentation, notes etc..) will help contributors.
And don't forget to comment your code ;-)
GoogleCode is a good place to upload your project.
There you will have an issue tracker and a wiki to write about it.
For a truely awesome OSS application I would suggest that you use git. Free hosting for git is provided by github. A good starting point for using git is http://learn.github.com/
As far as FOSS development is concerned, its not very different from usual development. But here you will have to don different roles like product manager, developer and tester too.
Other things that you need to take care of.
Since you are the initiator of it, you need to take control of its development.
Your code should be easy to be understood by others. Documentation is of utmost importance for other developers to start off.
Dont be offended if someone creates a fork of your project. Know to protect yourself by putting appropriate license, like, GPLV3 or any other that you find appropriate.