On 02/12/2014 05:13 PM, Johannes Totz wrote: > On 12/02/2014 13:36, Sascha Zelzer wrote: >> Dear MITK users, >> >> as many of you know, MITK has a long history and has grown tremendously >> over the last ten years. Parts of that history are still reflected in >> the current MITK source tree layout and the naming of directories, >> executables, libraries etc. >> >> We now want to introduce a consistent naming scheme. However, these >> changes will very likely require modifications of the CMake files of >> MITK based projects because some module names will change. >> >> Your own projects naming scheme will of course not be affected but you >> could reuse some of the MITK CMake code to enforce your own naming >> scheme for your MITK modules. >> >> This mail is intended to gather feedback from the community for the >> proposal [1] and as a preliminary announcement. >> >> Thank you, >> >> Sascha >> >> [1] http://mitk.org/Development/NamingConventions > Makes sense. Will you keep the mitk file name prefix, e.g. > "mitkBaseRenderer.h" vs "BaseRenderer.h"?
Yes, no changes will be made to source files or source code itself. - Sascha ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
