objective c - How to manage the code of multiple, very similar Xcode projects -

-

greetings stackoverflow community,

i have taken on task of 'unifying' 4 mobile iphone apps share 95% of code , differ in 5% (this of over-simplification, never mind). each of apps has own hefty set of resources (media files).

after 'unifying' 4 apps, adding new functionality apps, functionality apps share.

i appreciate hearing opinions on what's best way manage code of these apps. here approach i'm taking @ moment.

  1. i'm maintaining 1 xcode project includes functionality of 4 apps. functionality not shared among apps enclosed in condition such as: if (appname == 'x')...

  2. each app has own info.plist file, have 4 of such files: infox.plist, infoy.plist, ...

  3. before build app, 2 things done: a. in build settings, specify name of info.plist use. b. ensure app's resources (media files) in project. delete other apps' resources.

as apps 95% similar in code, having "one app rule them all" ensures when code gets upgraded, apps enjoy upgrade. can assume apps remain similar in code.

as apps' media files large , many, i'm keeping them off git repository.

how sound?

many thanks!

there better ways:

a. move framework

it depends on how generic common parts of apps. should think putting parts of in separate project framework. can link 4 apps against framework. but, of course, not go there.

b. have different targets

for sure should have 4 different targets. xcode let set build settings each setting commonly per project or specially per target. additionally can customize build phases (including copy of media files) on per target base. not have rename or delete , insert anything. select target, want build.

c. project tree

xcode allows have subprojects common code. maybe things common "foundation" classes of app. can have different projects each app in single workspace, using subproject.

probably best way combination, depending on subject. start b. , add other techniques, if needed.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more