I'm afraid this page of the documentation is outdated and does not match the current directory structure anymore. Thanks for the hint. I already created a task to get this fixed: https://phabricator.mitk.org/T27818
Best, Stefan ________________________________ Von: Ramazan Ergüder Bekrek <e.bek...@yandex.com> Gesendet: Sonntag, 4. Oktober 2020 14:31 An: mitk-users Betreff: Re: [mitk-users] Moving BlueBerry Framework from MITK towards CTK making it independant of the massive MITK setup While browsing MITK's documentation at this link : https://docs.mitk.org/nightly/DirectoryStructurePage.html#DirectoryStructurePageBlueBerry it is written that there is a BlueBerry folder which contains all code related to the framework that can be used totally independently from MITK. I realized the intention was good but in MITK's root source code directory there is no BlueBerry folder. Instead the BlueBerry folder's content is scattered in https://github.com/MITK/MITK/tree/master/Plugins folder with all the org.blueberry.* listing. >From my understanding BlueBerry cannot be used independently from MITK because >it is deeply rooted in the Plugins folder. Am I understanding it wrong? Let me know if there is another repo location where the BlueBerry folder is present then it will save a lot of my time trying to use it with CTK. Best regards 04.10.2020, 00:41, "Ramazan Ergüder Bekrek" <e.bek...@yandex.com>: Greetings to all again! So I tried to follow Stefan's advice to get BlueBerry out from MITK and put it somewhere else where it would become more appropriate. That's how I came up with this CTK version where I think it is better to put BlueBerry because MITK is way bigger then CTK and not everyone who wants to use CTK & BlueBerry necessarily want to become dependent to MITK which is itself depending on ITK&VTK. BlueBerry is nice for people who are coming from Eclipse background and are used to work with extensions and RCP Plugin development. CTK is nice for modularity but lacks any UI capability framework that's why BlueBerry should be part of CTK and not MITK. Also moving BlueBerry from MITK to CTK would also allow MITK to still continue use it without having anymore the need to handle it in its CMake configuration. I am not 100% sure that all I have come up with is actually making total sense and you are more than welcome to correct my disillusion. So now what I am asking you guys is SUPPORT because I cannot go any way further because of my lack of CMake skills and not really understanding MITK's complicated CMake structure and architecture. What I have achieve up until now is purely based on reversed engineering of function/macro names and CMake basic variable definitions. From that I just followed the bread crumbs up until it all stopped making sense in my brain and I got really tired :D Please bear with me if this looks like a noob's work because I am a noob :D Link to the repo : https://github.com/al-sabr/CTK/tree/ctk-blueberry-framework P.S. Hey BlueBerry's creator I don't know who you are but I am dreaming about you every night that you will come with your night's armor and horse to save me from the arms of CMake. Best Regards _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/mitk-users
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
