Odk collect cloning cookbook

Is there a documented process for cloning "Collect". I assume that
those that have "cloned" have done so to have an application that
doesn't collide with the actual Collect. For instance I'd like to set
something up that was named something different and uses a different
path than "odk" to keep stuff in. Is that an easy or hard thing to
do? I found where one could make a clone but I really don't know what
to do with it after that. (I realize I may be at the stage of "If you
have to ask you aren't qualified to try. :slight_smile:

-steve-

hey steve,

most people clone so they can add extra functionality to their version
of collect. they usually keep the paths the same, but changing the
path is easy and it shouldn't break anything.

the real thing to be aware off is that android distinguishes
applications by the java package specified in the manifest. if you
don't change the package, you can't install your version side-by-side
with the stock version.

yaw

ยทยทยท On Mon, Jun 27, 2011 at 14:53, Steve Roberts wrote: > Is there a documented process for cloning "Collect". I assume that > those that have "cloned" have done so to have an application that > doesn't collide with the actual Collect. For instance I'd like to set > something up that was named something different and uses a different > path than "odk" to keep stuff in. Is that an easy or hard thing to > do? I found where one could make a clone but I really don't know what > to do with it after that. (I realize I may be at the stage of "If you > have to ask you aren't qualified to try. :-) > > -steve- > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >