Oh my god .... Thanks Sascha ...
.... ------------------------------------- Tangi MEYER Virtual and Augmented Reality System and Software Engineer Leuvensesteenweg 325 B-1932 Zaventem - Belgium Telephone: +32 (0) 2 721 54 84 Fax: +32 (0) 2 721 54 44 ------------------------------------- From: "Sascha Zelzer" <[email protected]> To: [email protected] Sent: Friday, 30 April, 2010 3:12:06 PM Subject: Re: [mitk-users] Questions regarding QMitkFunctionnality. Hi Tangi, just a quick guess: Is CamdasstEditor the right class-name (the t looks suspicous)? Check your plugin.xml file that it contains the proper class name for your editor. Best, Sascha On 04/30/2010 03:51 PM, Tangi Meyer wrote: Hello Michael, Thank you for your answer. I finally got some time to get back on track with MITK/BlueBerry. To me it seems a little more complicated than what you said but maybe I'm wrong: - I do understand that we can create specific view plugins inheriting directly from the berry:QtViewPart - I do understand that I have to create my own functionnality so that all my plugins can benefit from the services I want to implement. - However, the dependency to the MultiWidget is not only embedded within the QmitkFunctionnality, the applications (both the ExtApp and CoreApp) are based on the QmitkStdMultiWidgetEditor from org_mitk_gui_qt_common, even the QmitkFileOpenAction at some points dynamic cast in QmitkStdMultiWidgetEditor. - So from what I understand, if I want to get rid of the QmitkStdMultiwidget and replace it for example by a "simple" 3D view, I have to build my own editor and associated application, workbench, etc. So I developped my own camdass.gui.qt.common plugin with all those classes (similar to org.mitk.gui.qt.common). And to test everything, I copied the IGT view and recorder examples plugins and made them inherit from my functionnality. But it seems that my Editor can not be found (see attached snapshot). Does anyone have an idea? Best regards, Tangi ------------------------------------- Tangi MEYER Virtual and Augmented Reality System and Software Engineer Leuvensesteenweg 325 B-1932 Zaventem - Belgium Telephone: +32 (0) 2 721 54 84 Fax: +32 (0) 2 721 54 44 ------------------------------------- From: "Müller Michael" <[email protected]> To: "mitk-users" <[email protected]> Cc: "Zelzer Sascha" <[email protected]> Sent: Thursday, 11 March, 2010 12:25:04 PM Subject: Re: [mitk-users] Questions regarding QMitkFunctionnality. Hi Tangi, the QmitkFunctionality is a convenience class providing methods that are frequently used by nearly all modules in a MITK application. I just gave a short seminar on this class: http://www.mitk.org/wiki/BugSquashingSeminars?action=AttachFile&do=view&target=QmitkFunctionality.pdf However, if you want to contribute view plugins (GUI parts) to a BlueBerry Qt workbench, the only prerequisite is to implement a class which inherits from berry::QtViewPart. Have a look in QmitkFunctionality.h. The class itself is inherited from berry::QtViewPart. So the solution would be to write your own functionality inheriting from berry::QtViewPart. E.g., the DataManager view is a class which does not inherit from QmitkFunctionality because it doesn`t need the MultiWidget. The Bundle Generator generates a QmitkFunctionality-inherited class by default. You may change this afterwards manually, the view itself is exported as berry::IViewPart. As you can see, in BlueBerry it`s all about interfaces ;) Bye, Michael Von: Tangi Meyer [ mailto:[email protected] ] Gesendet: Donnerstag, 11. März 2010 12:27 An: mitk-users Cc: Zelzer Sascha Betreff: [mitk-users] Questions regarding QMitkFunctionnality. Dear All, We are looking for some advices regarding the QmitkFunctionnality principles. Basically, the QmitkFunctionnality is used as a kind of interface for new plugin/view. It provides access to different services and to the QmitkStdMultiWidget (which is also linked with the berry editor). In our approach, we would like our application views: - to have access to our own berry services - to use our own 3D widgets without using the QmitkStdMultiWidget. So the first solution coming to our mind is buidlding our functionnality class that would inherits from the QmitkFunctionnality. However, this would mean embedding the QmitkStdMultiWidget without using it. Also, will the Bundle generator properly handle the dependencies (will try to test it today)? The point is that such a class will be specific to our application and therefore shall not be part of the mitk svn ... Another solution could be to have a more abstracted QmitkFunctionnality class that can be derived in specific applications and that the Bundle generator can take into account. Thank you in advance for your answers! Best regards, Tangi ------------------------------------- Tangi MEYER Virtual and Augmented Reality System and Software Engineer Leuvensesteenweg 325 B-1932 Zaventem - Belgium Telephone: +32 (0) 2 721 54 84 Fax: +32 (0) 2 721 54 44 ------------------------------------- ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users ------------------------------------------------------------------------------ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
