I've ended up with a 'build' project which is merely a set of symbolic
links to 'real' projects. This approach works perfectly for me :)
On Dec 10, 9:30 pm, Mark Murphy mmur...@commonsware.com wrote:
Well, in this case you have to go java way:
getClassLoader().getResourceAsStream(name it
How do you manage resources between the various subsystems they are
in?
On Dec 11, 2:39 pm, Andriy Tsykholyas andriy.tsykhol...@gmail.com
wrote:
I've ended up with a 'build' project which is merely a set of symbolic
links to 'real' projects. This approach works perfectly for me :)
On Dec 10,
On Dec 11, 9:53 pm, WoodManEXP woodman...@gmail.com wrote:
How do you manage resources between the various subsystems they are
in?
Quite simply:
1) Each project is compilable and installable on its own. But not
necessary runnable ;)
2) If both project A and B have the resource files with the
I have been successful breaking out common classes into separate
Eclipse projects and exporting them as .jar files, and referencing
the .jar files in other Eclipse projects, as long as they do not
reference resources. If they need to reference resources, well, it
just seems it is not possible at
Mark,
thanks for your answers.
On Dec 10, 3:12 pm, Mark Murphy mmur...@commonsware.com wrote:
* In short:
Is it possible to reuse classes and resources from A.apk in B.apk?
Classes, no. Resources, sorta, but I'm not sure it's a good idea, since
you have no way of ensuring that each device
On Dec 10, 3:28 pm, WoodManEXP woodman...@gmail.com wrote:
If they need to reference resources, well, it
just seems it is not possible at this point.
That's what I was afraid of :(
For the parts of the
Android code that reference resources I am pretty much just copy/
pasting between
Yes I would like to avoid the copy/pasting as well!
Other Java environs, eg NetBeans, have a concept of embedding
resources in .jar files (that are needed by the jar file). Apparently
the Google team has not has time to implement such a thing for Android
world. They have this technique to
According to
http://developer.android.com/guide/publishing/versioning.html
B can check if A is installed. It can even check which version of A is
installed :)
Which gets you little, since you cannot force the user to install A.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android
It seems to me that approach 2 (Make a third project which consists of
symbolic links to classes
and resources of those two projects) is simplest. So, I'm proceeding
with it :)
On Dec 10, 3:58 pm, WoodManEXP woodman...@gmail.com wrote:
Yes I would like to avoid the copy/pasting as well!
Other
On Dec 10, 4:29 pm, Mark Murphy mmur...@commonsware.com wrote:
According to
http://developer.android.com/guide/publishing/versioning.html
B can check if A is installed. It can even check which version of A is
installed :)
Which gets you little, since you cannot force the user to install
Which gets you little, since you cannot force the user to install A.
But you can:
1) Notify user the A is missing. And disable B completely or partially
(depending on effect of missing A).
Which will irritate your users.
2) Ask user if she wants to install A. If she agrees, then:
Intent
On Dec 10, 4:49 pm, Mark Murphy mmur...@commonsware.com wrote:
Which gets you little, since you cannot force the user to install A.
But you can:
Which will irritate your users.
I agree :)
Hence, I stand by my assessment that, while there are ways for B to access
A's resources at
On Dec 10, 2:58 pm, WoodManEXP woodman...@gmail.com wrote:
Yes I would like to avoid the copy/pasting as well!
Other Java environs, eg NetBeans, have a concept of embedding
resources in .jar files (that are needed by the jar file). Apparently
the Google team has not has time to implement
Well, in this case you have to go java way:
getClassLoader().getResourceAsStream(name it what you like)
will pick up whateher you like from jar files on classpath ( though
not as
convenient as android APIs )
Moreover, that'll just give you a stream. It won't work for anything that
needs a
14 matches
Mail list logo
