Really it depends on what he's got in the original app. Even just a
provider is going to be trouble if he simply turns the whole thing into a
library.
On Wednesday, 13 February 2013 09:05:34 UTC-5, Digipom wrote:
Hi Lew,
Do you kindly have any evidence or documentation to back up your
Hi Lew,
Do you kindly have any evidence or documentation to back up your claims?
I'm just curious. Why can't one just check the library checkbox?
On Tuesday, February 12, 2013 5:13:25 PM UTC-5, Lew wrote:
bob wrote:
Does he really need to create a new library project?
Yes.
Or can
You could do that but you might end up with package name problems if you
want to keep your existing package name for your old application (and a new
package name for the 2nd application).
So you will probable need to rename the package of the library and this
will have some knock-on effects on
On 02/13/2013 09:05 AM, Digipom wrote:
Hi Lew,
Do you kindly have any evidence or documentation to back up your
claims? I'm just curious. Why can't one just check the library checkbox?
I'd say it's better to create a library project for the simple reason
that at some point he may want to
Ok, I was just wondering, as I once turned an app project into a library
project by simply checking the checkbox, kept the old package name for the
library and created a new app project with a different package.
I was just wondering if there was something I might have overlooked or some
bad side
When you say put existing shared code, does this literally mean copy and
paste all the .java and layout files from the one application to the
library project?
On Tuesday, February 12, 2013 3:24:22 PM UTC-5, RichardC wrote:
Create an new Android Library project.
Put all your existing shared
Yes and change the Java package name(s) to match the name of the library
package.
On Wednesday, February 13, 2013 5:17:44 PM UTC, John Merlino wrote:
When you say put existing shared code, does this literally mean copy and
paste all the .java and layout files from the one application to the
Create an new Android Library project.
Put all your existing shared code and resources into it.
Create 2 new Android Projects (one with your old package name and the other
with a new package name), and set them to use your Android Library project.
Put the different resources into the Application
I don't see where it mentions to copy existing code into the library
project. Am I supposed to copy and paste it?
On Feb 12, 3:24 pm, RichardC richard.crit...@googlemail.com wrote:
Create an new Android Library project.
Put all your existing shared code and resources into it.
Create 2 new
For an example look at:
android-sdk\samples\android-n\TicTacToeLib
android-sdk\samples\android-n\TicTacToeMain
On Tuesday, February 12, 2013 8:58:16 PM UTC, John Merlino wrote:
I don't see where it mentions to copy existing code into the library
project. Am I supposed to copy and paste it?
Does he really need to create a new library project?
Or can he just check the Is Library checkbox on his existing project?
https://lh5.googleusercontent.com/-V1ww5FOHONU/URq7qNZ2FxI/AMg/lrxK0vxdDgs/s1600/lib.png
On Tuesday, February 12, 2013 2:24:22 PM UTC-6, RichardC wrote:
bob wrote:
Does he really need to create a new library project?
Yes.
Or can he just check the Is Library checkbox on his existing project?
No.
RichardC wrote:
Create an new Android Library project.
Put all your existing shared code and resources into it.
Create 2 new Android
12 matches
Mail list logo
