Hi Stefan,

Many thanks for your reply. I have a better understanding now.

I have experimented with the template project and have created a custom
perspective, a custom view and I guess the
"awesomeproject.renderwindoweditor" from the template can be used to create
custom editors, right? I mean I can use this to create the 6-window editor
I'm looking for?

If this is the right thing to do, I have a problem with displaying the
custom editor once my MITK application is launched. I read about how
plugins (views) are not dependent on the default 4-window editor any more.
So, I think my custom plugin is not activating the default 4-window editor
and I'm not sure how to link the custom editor to my created plugin (view).
Can you please give me some hints on this too? I have created a custom
perspective that should show the view on one side and the custom editor on
the other side.


All the best
Dora

On Tue, Oct 27, 2015 at 2:16 PM, Kislinskiy, Stefan <
s.kislins...@dkfz-heidelberg.de> wrote:

> Hi,
>
>
>
> that’s a whole bunch of questions that would require long answers for
> details so let’s start with some hints and see, if further guidance is
> really necessary or the documentation is enough. :) Anyways, you should
> read our developer manual and concept pages in the doxygen documentation,
> which will answer many questions that will arise when developing with MITK.
>
>
>
> 1.     Yes, usually you write your own custom plugin. The actual
> functionality/algorithms should be implemented in a custom module
> (AwesomeLib in the default project template). This way you can access this
> functionality from multiple plugins, which contain just the “View” part of
> your code.
>
> 2.     You can use the Qt styling mechanisms like a CSS/QSS file to style
> the application. See also “Preferences -> General -> Themes” in the MITK
> Workbench. From there you should find the code/mechanisms you are
> interested in.
>
> 3.     By default, we show our 4-window-editor called
> “QmitkStdMultiWidgetEditor”, located in the
> org.mitk.gui.qt.stdmultiwidgeteditor plugin. You can write your own
> “editor” with 6 views and provide it in a custom plugin. Use the previousöy
> mentioned plugin as a template to quickly achieve results.
>
> 4.     If it’s just the plugin buttons that you want to get rid of, you
> just have to disable the according plugins in CMake (by setting the
> MITK-build directory as build directory, (subfolder of MITK-superbuild,
> which is a subfolder of the MITK-ProjectTemplate-superbuild directory).
>
> Best regards,
> Stefan
>
>
>
> *From:* Admin Uniapp [mailto:contactuni...@gmail.com
> <contactuni...@gmail.com>]
> *Sent:* Freitag, 23. Oktober 2015 15:03
> *To:* mitk-users@lists.sourceforge.net
> *Subject:* [mitk-users] How to start editing the MITK template project
>
>
>
> Hi to all,
>
>
>
> My question has been probably asked before but I've had no luck finding an
> answer. So, sorry about this!
>
>
>
> I've managed to install MITK and the template project and I can add and
> remove the default plugins to/from the main application but my question is
> how I would take this further and start modifying the template project to
> make it into an application useful in solving a particular problem?
>
>
>
> - Do I need to create a new custom plugin for the purpose? and add this to
> the default project?
>
> - If so how do I change the looks (user interface) of the default
> application?
>
> - how can I change the default 4 window view? I will need 6 windows to
> display images, plots etc.
>
> - how can I remove the unnecessary plugins buttons from the default
> workbench top bar?
>
>
>
> I have looked at the tutorials but they seem to be describing how to write
> small programs using the MITK functionalities.
>
>
>
> Any clarification will be highly helpful.
>
> Many thanks.
>
> Dora
>
------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to