Hi Felix, First, welcome to the MITK community!
Unfortunately, you run straight into a bug concerning the logo handling... sorry for that. With commit 0488beafcac6dc3b197fbac7c0901279ed69d8c0 the preferences handling logic in QmitkStdMultiWidgetEditor changed in a way that broke the mechanism how custom logos have usually been set. I modified the preference key look-up logic here https://github.com/MITK/MITK/commit/6afcd10c6b288c10eccbe7278d63d497818b3f57 and added a convenience method in mitkWorkbenchUtil.h which encapsulates the details of the logo setting code. Please have a look at the changes in the following commit, which set a custom logo in the MITK-ProjectTemplate project: https://github.com/MITK/MITK-ProjectTemplate/commit/4261663c9d31f26b059378fd34c4b4719d417d31 If you are playing with the ProjectTemplate, please note that the changes above need to be "activated" by un-commenting the following line: https://github.com/MITK/MITK-ProjectTemplate/blob/master/Apps/AwesomeApp/AwesomeApp.cpp#L46 Now for your questions, please see my comments inline below. On 09/26/2012 02:11 PM, Félix C. Morency wrote: > Hi, > > Thanks you both for your answers. I was still not be able to change > the logo. I discovered that most of the GUI creation is handled in the > org.mitk.gui.qt.ext plugin and not in org.mitk.gui.qt.extapplication. > To help me understand, I tried to change the logo of the MITK > workbench directly from the MITK source code but without luck. Can you > point me out to where I should place the code of my previous message > to modify the logo of the plain MITK workbench and most importantly, > why there? i'm having difficulties understanding the workbench > architecture (org.mitk.qt.ext.plugin VS > org.mitk.gui.qt.extapplication, etc). The place suggested originally by Miklos for setting the logo was correct. the "extapplication" plug-in customizes the MITK workbench by providing workbench advisor classes. The org.mitk.gui.qt.ext plug-in contains some actions and workbench advisor classes containing code which is usually the same for all MITK applications. Plug-ins providing an extension for the "org.blueberry.osgi.applications" extension point in their plugin.xml file (like org.mitk.gui.qt.extapplication does) usually re-use the advisor classes from org.mitk.gui.qt.ext and either inherit from them or just configure them in specific ways. If you would like to get started with plug-in development in MITK, I would suggest to start here: http://docs.mitk.org/nightly-qt4/NewPluginPage.html and let the generator create a complete project stub for you. You can of course also copy the MITK-ProjectTemplate project and adapt it to your needs. Custom workbench advisors are already an advanced topic and it might help to familiarize yourself with the MITK Workbench concepts first. Thanks, Sascha ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
