good structure of the project's code

[aoloe]

• the code should be structure in small classes that are easy to browse.
• one should intuitively find in which class a features is implemented.
• there should not be too many files in a directory and the directories structure should not be too deep.

one idea is to put the main structures and their accessors in the main code.
all actions (import, export, editing, scripting) would then go in plugins.

[aoloe]

how to create sub projects:

• http://stackoverflow.com/questions/10034825/how-do-i-build-a-static-library-and-executable-with-qt
• http://stackoverflow.com/questions/1417776/how-to-use-qmakes-subdirs-template

[aoloe]

how to create shared libraries:

• http://gertverdemme.nl/dev/cpp/qt/build_shared_libraries
• http://www.qtcentre.org/threads/28359-Setting-LD_LIBRARY_PATH-from-Qt-Creator (the part on linux seems to work correctly... it's what i use now for the builds...)

dont forget to export all the symbols you want to let use (http://qt-project.org/doc/qt-4.8/sharedlibrary.html)