We are very aware of the need for this use case (in-house sharing of
code/resources), and are working on something.
That is good to hear!
OpenIntents might be a good place to host a repository of public
widgets, as there is already a list of open intents and reusable
libraries.
I support
On Mon, Mar 29, 2010 at 9:21 AM, westmeadboy westmead...@yahoo.co.uk wrote:
I'm sure this would be very useful to some/many.
But, personally, I'm specifically interested in sharing in-house
resources-based jars between my own apps.
Currently I'm resorting to a prehistoric copy-paste
I've been holding off on replying to this only because I haven't fully
collected my thoughts. I hope to write up my recommendations for build
approaches, especially for free/paid apps, before really wrapping my
mind around it.
But since that's taking me a while, I thought I should chime in, yes,
But one thought is that making this be a command may not be the best
approach for integration into build systems. I'm thinking that
packaging it as an ant macro in an antlib may be a better approach,
with the underlying technology being a .zip file with the various
pieces.
Then, if you feel
Anyway, if you choose to go the parcel shell route, don't forget a
parcel upgrade command. Personally, If I cannot upgrade easily to a
new version of a library I wouldn't use it.
Yup, it's in there.
Thanks for the input!
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App
I didn't suggest writing any Java code. I didn't suggest writing any
ant tasks in Java.
I said to create an antlib (though I should have said library of ant
definitions to be used with include/), which is entirely in XML.
That's part of why I suggested this approach, as it would avoid the
need
I like the idea and as far as I know this is already possible to some
extend by using the Maven Android Plugin. However this is really a
suboptimal way in terms of component reuse on the device. Ideally it
would even go further and get to a stage where a app could declare a
dependency to a widget,
I am interested - I have the same issues even sharing with my own
libraries - In some ways the an approach might be to simply import
both the code and the resources into the project if that were possible
- The biggest issue I run across is resources which don't seem to get
imported properly when
Hello Mark,
You are absolutely right: support for reusable components other than
pure Java code (and Java resources) is sorely missed. I personally
think Google should step up and add this kind of support to the
Android eclipse plugin.
In my opinion, the problem of lack of tool support is minor
Mark,
I perfectly understand where you are coming from and support the
motion. The 'parcel' shell would be fine, I can see how it will be
welcome amongst Java devs (e.g. Grails does the same). Something I
would like to get more details on is the storage mechanism of parcels
on a local machine
To be honest, I would prefer to be able to specify package
dependencies, much like linux distros do. That way I wouldn't have to
bloat my app with source from other libs and I would make a non open
source app a dependency even.
However, I don't think we can do that without Google getting involved.
I'm sure this would be very useful to some/many.
But, personally, I'm specifically interested in sharing in-house
resources-based jars between my own apps.
Currently I'm resorting to a prehistoric copy-paste approach!
On Mar 29, 4:19 pm, Mark Murphy mmur...@commonsware.com wrote:
Creating
This is a pretty interesting idea.
It's hard to think of where this would be useful, but I can imagine
some people finding a use for it, but you could spend a great deal of
time trying to develop and maintain this and it would have slow take-
up, only after some fairly common parcels start to get
Gaunt Face wrote:
It's hard to think of where this would be useful, but I can imagine
some people finding a use for it, but you could spend a great deal of
time trying to develop and maintain this and it would have slow take-
up, only after some fairly common parcels start to get used by a
I'd be very interested, and willing to lend a hand. I've been
collecting my own library of tricks and widgets and even sharing
within my own apps it's cumbersome.
On Mar 29, 1:41 pm, Mark Murphy mmur...@commonsware.com wrote:
Gaunt Face wrote:
It's hard to think of where this would be
15 matches
Mail list logo
