project-organization | 易学教程

How to organize unit testing of a library project in Xcode?

阅读更多关于 How to organize unit testing of a library project in Xcode?

问题 I'm not yet a fan of integrated development environments, but I'm trying to overcome my prejudices and learn Xcode. (Eclipse/CDT is next; I couldn't get that to work for me either when I tried last year, but that's a separate issue.) I am writing some new code in a new project that will become (part of) a small library. I want to unit test it, too. How do I explain to Xcode that I'm building a (shared) library, but I also want to use it in a test program, compiled from separate source that

Best practices when Design iPhone Game with MVC?

阅读更多关于 Best practices when Design iPhone Game with MVC?

问题 I have made two games for the iPhone already, the first one was a mess, and the second one is less messy but still, not perfect. I would love to hear if someone had some links that pointed to good class organization advice when creating games using MVC ? 回答1: You controller is the glue that holds everything together, it is the least reusable out of the MVC trio. Your views and models are what you should concentrate on making reusable. The controller handles all of the game-specific

Split Python source into separate directories?

阅读更多关于 Split Python source into separate directories?

问题 Here are some various Python packages my company "foo.com" uses: com.foo.bar.web com.foo.bar.lib com.foo.zig.web com.foo.zig.lib com.foo.zig.lib.lib1 com.foo.zig.lib.lib2 Here's the traditional way to store the source on disk: pysrc/ com/ foo/ bar/ web/ lib/ zig/ web/ lib/ lib1/ lib2/ PYTHONPATH=pysrc But for organizational purposes (different teams, different revision control, etc.), we want to store these as follows: bar/ pysrc/ com/ foo/ bar/ web/ lib/ zig/ pysrc/ com/ foo/ zig/ web/ lib/

how do you organize your namespaces?

阅读更多关于 how do you organize your namespaces?

So I have logical entities (person, country, etc.), GUI elements / controls, data and navigation controllers / managers, then things like quad-trees and timers, and I always struggle with cleanly separating these things into logical namespaces. I usually have something like this: Leviathan.GUI.Controls Leviathan.GUI.Views Leviathan.Entities Leviathan.Controllers (data and other stuff) Leviathan.Helpers (trees and other stuff) Are there any good guides on this? I need to stop this mess. For applications Company.Product.Tier.Sub.Sub where I like to get Tier from Model, View, Controller or other

What project options to use for open source Delphi packages?

阅读更多关于 What project options to use for open source Delphi packages?

I've written some Delphi code I would like to share on GitHub. All code is contained in runtime and designtime packages as required. There are many "Project Options" to set for each project. (Output directories, search paths, compilation options, etc.) I've managed to find some default options that work well for my situation but reading other Q&As here it's clear there are multiple ways of working . What project options should be used to allow the open source packages to easily be incorporated into individual projects? I've recently started using NodeJS. The NPM package manager makes it super

Split Python source into separate directories?

阅读更多关于 Split Python source into separate directories?

Here are some various Python packages my company "foo.com" uses: com.foo.bar.web com.foo.bar.lib com.foo.zig.web com.foo.zig.lib com.foo.zig.lib.lib1 com.foo.zig.lib.lib2 Here's the traditional way to store the source on disk: pysrc/ com/ foo/ bar/ web/ lib/ zig/ web/ lib/ lib1/ lib2/ PYTHONPATH=pysrc But for organizational purposes (different teams, different revision control, etc.), we want to store these as follows: bar/ pysrc/ com/ foo/ bar/ web/ lib/ zig/ pysrc/ com/ foo/ zig/ web/ lib/ lib1/ lib2/ PYTHONPATH=bar/pysrc:zig/pysrc The question is: Are there any issues with this second

C++ project source code layout

阅读更多关于 C++ project source code layout

One of the popular way to organize project directory is more or less like this: MyLib +--mylib_class_a.h mylib_class_a.cpp mylib_library_private_helpers.h mylib_library_private_helpers.cpp MyApp +--other_class.h other_class.cpp app.cpp app.cpp : #include "other_class.h" #include <mylib_class_a.h> // using library MyLib All .h and .cpp files for the same library are in the same directory. To avoid name collision, file names are often prefix with company name and/or library name. MyLib will be in MyApp's header search path, etc. I'm not a fan of prefixing filenames, but I like the idea of

Why and when to create a multi-module Maven project?

阅读更多关于 Why and when to create a multi-module Maven project?

问题 I have a general question about Maven's multi module project. When and why to go for it? 回答1: The answer of @Esko Luontola Splitting the project into multiple modules is useful for example if the modules need to be deployed separately,.. could be misinterpreted. If you have modules which will be deployed separately, it's exactly the opposite. In such case, you should never create a multi-module build. This should be done via simple separate maven projects. The idea of a multi-module build is

Best way to organize the files in my project

阅读更多关于 Best way to organize the files in my project

What is the best way to organize the files in your project? For example do you put all user controls in a separate folder or do you place them in a sub folder? Do you have business logic folder? A helper classes folder? I used to organize my projects like this: Project/User Controls/Module Name/ Project/Classes/Module Name/ Now I am learning more towards something like this: Project/Module Name/User Controls/ Project/Module Name/Classes/ What is the best way? Especially if the project gets really big? What type of folder structure should exist? First the purpose of folder separation is to be

Build server: Best practices managing third party components?

阅读更多关于 Build server: Best practices managing third party components?

问题 I'm maintaining a quite large legacy application. The source tree is a real mess. I'm trying to set up a build server. On the source tree, I've third party component with sources (also in the project's include path). These components are also installed within the IDE. My question is : How to manage those components ? I thought to manage this way: Install the IDE on the build server Install all the third party component Remove the component sources from the project sources tree (and keep them