From lasso at queensu.ca  Sat Dec 13 16:32:45 2014
From: lasso at queensu.ca (Andras Lasso)
Date: Sat, 13 Dec 2014 21:32:45 +0000
Subject: [Ctk-developers] Info level logging macro in VTK
Message-ID: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>

Hi all,

We are having a discussion with VTK developers about the necessity for a vtkInfoMacro (or vtkGenericOutputMacro) in addition to vtkErrorMacro, vtkWarningMacro, and vtkDebugMacro in VTK [1] . The new macro would offer a standard way of logging non-error messages from VTK-derived application classes, tests, and examples. For example, you would not need to specify a separate application-specific LOG_INFO macro in your application for logging non-error messages while using the VTK standard vtkErrorMacro and vtkWarningMacro for errors.

The next step would be asking for moving the log message formatting from the VTK logging macros to the vtkOutputWindow class. That would allow getting rid of the ugly multi-line VTK error messages, because in a custom vtkOutputWindow class the application could format the fields (message, line number, etc.) in any way or it could send the info to the application logger (there would be no need to parse the VTK error messages anymore to extract the fields).

It would help the discussion on the VTK list a lot if we know the opinion, needs of more application developers:
* Do you find the current VTK error/warning/debug logging convenient for your application?
* Would you use INFO level logging in VTK-based classes in your application?
* Would you like to have customizable formatting of VTK error/warning messages? (e.g., have compact, single-line messages; or be able to have the message, line number, file name, etc. separately so that you can send it to your application's logger)

Thanks in advance.
Andras

[1] http://public.kitware.com/pipermail/vtk-developers/2014-December/031102.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20141213/e021b4bb/attachment.html>

From bill.lorensen at gmail.com  Sat Dec 13 16:58:24 2014
From: bill.lorensen at gmail.com (Bill Lorensen)
Date: Sat, 13 Dec 2014 16:58:24 -0500
Subject: [Ctk-developers] Info level logging macro in VTK
In-Reply-To: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>
References: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>
Message-ID: <CADZJ4hPO9tfbOuEK538Bd57hx0Sq75mMMB9bqj=GCY7ecxXkjg@mail.gmail.com>

Personally, I do not like macros. For this functionality I would
prefer a logging class like we have in ITK.

Bill


On Sat, Dec 13, 2014 at 4:32 PM, Andras Lasso <lasso at queensu.ca> wrote:
> Hi all,
>
>
>
> We are having a discussion with VTK developers about the necessity for a
> vtkInfoMacro (or vtkGenericOutputMacro) in addition to vtkErrorMacro,
> vtkWarningMacro, and vtkDebugMacro in VTK [1] . The new macro would offer a
> standard way of logging non-error messages from VTK-derived application
> classes, tests, and examples. For example, you would not need to specify a
> separate application-specific LOG_INFO macro in your application for logging
> non-error messages while using the VTK standard vtkErrorMacro and
> vtkWarningMacro for errors.
>
>
>
> The next step would be asking for moving the log message formatting from the
> VTK logging macros to the vtkOutputWindow class. That would allow getting
> rid of the ugly multi-line VTK error messages, because in a custom
> vtkOutputWindow class the application could format the fields (message, line
> number, etc.) in any way or it could send the info to the application logger
> (there would be no need to parse the VTK error messages anymore to extract
> the fields).
>
>
>
> It would help the discussion on the VTK list a lot if we know the opinion,
> needs of more application developers:
>
> * Do you find the current VTK error/warning/debug logging convenient for
> your application?
>
> * Would you use INFO level logging in VTK-based classes in your application?
>
> * Would you like to have customizable formatting of VTK error/warning
> messages? (e.g., have compact, single-line messages; or be able to have the
> message, line number, file name, etc. separately so that you can send it to
> your application?s logger)
>
>
>
> Thanks in advance.
>
> Andras
>
>
>
> [1]
> http://public.kitware.com/pipermail/vtk-developers/2014-December/031102.html
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>



-- 
Unpaid intern in BillsBasement at noware dot com

From lasso at queensu.ca  Sat Dec 13 17:09:06 2014
From: lasso at queensu.ca (Andras Lasso)
Date: Sat, 13 Dec 2014 22:09:06 +0000
Subject: [Ctk-developers] Info level logging macro in VTK
In-Reply-To: <CADZJ4hPO9tfbOuEK538Bd57hx0Sq75mMMB9bqj=GCY7ecxXkjg@mail.gmail.com>
References: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>,
 <CADZJ4hPO9tfbOuEK538Bd57hx0Sq75mMMB9bqj=GCY7ecxXkjg@mail.gmail.com>
Message-ID: <B6FC5543F5C41E479B8B89158B0C58FF31E1CBD3@QU-MBX02-PRD.AD.QUEENSU.CA>

The only reason for using macro is to be able to get the line number and file name. The rest is handled by output window and logger classes.

Andras
________________________________
From: Bill Lorensen<mailto:bill.lorensen at gmail.com>
Sent: ?2014-?12-?13 16:58
To: Andras Lasso<mailto:lasso at queensu.ca>
Cc: ctk-developers at commontk.org<mailto:ctk-developers at commontk.org>
Subject: Re: [Ctk-developers] Info level logging macro in VTK

Personally, I do not like macros. For this functionality I would
prefer a logging class like we have in ITK.

Bill


On Sat, Dec 13, 2014 at 4:32 PM, Andras Lasso <lasso at queensu.ca> wrote:
> Hi all,
>
>
>
> We are having a discussion with VTK developers about the necessity for a
> vtkInfoMacro (or vtkGenericOutputMacro) in addition to vtkErrorMacro,
> vtkWarningMacro, and vtkDebugMacro in VTK [1] . The new macro would offer a
> standard way of logging non-error messages from VTK-derived application
> classes, tests, and examples. For example, you would not need to specify a
> separate application-specific LOG_INFO macro in your application for logging
> non-error messages while using the VTK standard vtkErrorMacro and
> vtkWarningMacro for errors.
>
>
>
> The next step would be asking for moving the log message formatting from the
> VTK logging macros to the vtkOutputWindow class. That would allow getting
> rid of the ugly multi-line VTK error messages, because in a custom
> vtkOutputWindow class the application could format the fields (message, line
> number, etc.) in any way or it could send the info to the application logger
> (there would be no need to parse the VTK error messages anymore to extract
> the fields).
>
>
>
> It would help the discussion on the VTK list a lot if we know the opinion,
> needs of more application developers:
>
> * Do you find the current VTK error/warning/debug logging convenient for
> your application?
>
> * Would you use INFO level logging in VTK-based classes in your application?
>
> * Would you like to have customizable formatting of VTK error/warning
> messages? (e.g., have compact, single-line messages; or be able to have the
> message, line number, file name, etc. separately so that you can send it to
> your application?s logger)
>
>
>
> Thanks in advance.
>
> Andras
>
>
>
> [1]
> http://public.kitware.com/pipermail/vtk-developers/2014-December/031102.html
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>



--
Unpaid intern in BillsBasement at noware dot com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20141213/58f1301e/attachment-0001.html>

From pieper at isomics.com  Sat Dec 13 17:41:55 2014
From: pieper at isomics.com (Steve Pieper)
Date: Sat, 13 Dec 2014 17:41:55 -0500
Subject: [Ctk-developers] Info level logging macro in VTK
In-Reply-To: <B6FC5543F5C41E479B8B89158B0C58FF31E1CBD3@QU-MBX02-PRD.AD.QUEENSU.CA>
References: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>
 <CADZJ4hPO9tfbOuEK538Bd57hx0Sq75mMMB9bqj=GCY7ecxXkjg@mail.gmail.com>
 <B6FC5543F5C41E479B8B89158B0C58FF31E1CBD3@QU-MBX02-PRD.AD.QUEENSU.CA>
Message-ID: <CADkb7uNQiVEGo31HdT6u6=rjLv_CEfKsRfE_ivaKqC5yY51nAA@mail.gmail.com>

Hi Andras -

I'm on record from previous discussions on the vtk developer list that I'd
like to make vtk smaller (e.g. move vtkChemistry, GeoVis and similar things
into their own add-on libraries [1]).  But on this one I actually agree
with your argument that VTK really should have a provision for this rather
than leaving it to each application to develop a custom solution.  Berk
seems to have dug in his heels though, so maybe just add the feature to
CTK?  Or leaving it in Slicer is okay by me too.

-Steve

[1]
http://vtk.1045678.n5.nabble.com/Driving-away-your-existing-developers-td5728448.html


On Sat, Dec 13, 2014 at 5:09 PM, Andras Lasso <lasso at queensu.ca> wrote:
>
>   The only reason for using macro is to be able to get the line number
> and file name. The rest is handled by output window and logger classes.
>
> Andras
>  ------------------------------
> From: Bill Lorensen <bill.lorensen at gmail.com>
> Sent: ?2014-?12-?13 16:58
> To: Andras Lasso <lasso at queensu.ca>
> Cc: ctk-developers at commontk.org
> Subject: Re: [Ctk-developers] Info level logging macro in VTK
>
>   Personally, I do not like macros. For this functionality I would
> prefer a logging class like we have in ITK.
>
> Bill
>
>
> On Sat, Dec 13, 2014 at 4:32 PM, Andras Lasso <lasso at queensu.ca> wrote:
> > Hi all,
> >
> >
> >
> > We are having a discussion with VTK developers about the necessity for a
> > vtkInfoMacro (or vtkGenericOutputMacro) in addition to vtkErrorMacro,
> > vtkWarningMacro, and vtkDebugMacro in VTK [1] . The new macro would
> offer a
> > standard way of logging non-error messages from VTK-derived application
> > classes, tests, and examples. For example, you would not need to specify
> a
> > separate application-specific LOG_INFO macro in your application for
> logging
> > non-error messages while using the VTK standard vtkErrorMacro and
> > vtkWarningMacro for errors.
> >
> >
> >
> > The next step would be asking for moving the log message formatting from
> the
> > VTK logging macros to the vtkOutputWindow class. That would allow getting
> > rid of the ugly multi-line VTK error messages, because in a custom
> > vtkOutputWindow class the application could format the fields (message,
> line
> > number, etc.) in any way or it could send the info to the application
> logger
> > (there would be no need to parse the VTK error messages anymore to
> extract
> > the fields).
> >
> >
> >
> > It would help the discussion on the VTK list a lot if we know the
> opinion,
> > needs of more application developers:
> >
> > * Do you find the current VTK error/warning/debug logging convenient for
> > your application?
> >
> > * Would you use INFO level logging in VTK-based classes in your
> application?
> >
> > * Would you like to have customizable formatting of VTK error/warning
> > messages? (e.g., have compact, single-line messages; or be able to have
> the
> > message, line number, file name, etc. separately so that you can send it
> to
> > your application?s logger)
> >
> >
> >
> > Thanks in advance.
> >
> > Andras
> >
> >
> >
> > [1]
> >
> http://public.kitware.com/pipermail/vtk-developers/2014-December/031102.html
> >
> >
> > _______________________________________________
> > Ctk-developers mailing list
> > Ctk-developers at public.kitware.com
> > http://public.kitware.com/mailman/listinfo/ctk-developers
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20141213/a8ddb91e/attachment.html>

From jchris.fillionr at kitware.com  Sun Dec 14 20:43:05 2014
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Sun, 14 Dec 2014 20:43:05 -0500
Subject: [Ctk-developers] Info level logging macro in VTK
In-Reply-To: <CADkb7uNQiVEGo31HdT6u6=rjLv_CEfKsRfE_ivaKqC5yY51nAA@mail.gmail.com>
References: <B6FC5543F5C41E479B8B89158B0C58FF31E1CAF7@QU-MBX02-PRD.AD.QUEENSU.CA>
 <CADZJ4hPO9tfbOuEK538Bd57hx0Sq75mMMB9bqj=GCY7ecxXkjg@mail.gmail.com>
 <B6FC5543F5C41E479B8B89158B0C58FF31E1CBD3@QU-MBX02-PRD.AD.QUEENSU.CA>
 <CADkb7uNQiVEGo31HdT6u6=rjLv_CEfKsRfE_ivaKqC5yY51nAA@mail.gmail.com>
Message-ID: <CANLz8R7kxtU5d=6iiWkaQ5POj-rjTo16EFDY3_gmAFM4h6JJbA@mail.gmail.com>

Hi Folks,

To get the full picture, within CTK, we have the following classes:

* ctkErrorLogModel [1]:  Centralize messages captured by message handlers.

* ctkErrorLogWidget [2]: Present the messages from the model into a view



Message handlers:

* ctkErrorLogStatusMessageHandler [3]: Capture and log messages displayed
in the status bar

* ctkErrorLogStreamMessageHandler [4]: Capture and log messages "printed"
on std::cout and std::cerr

* ctkErrorLogQtMessageHandler [5]: Capture and log messages "printed" using
qWarning/qDebug/...

* ctkErrorLogFDMessageHandler [6]: Capture and log messages "printed" on
stdout and stderr file descriptor

* ctkITKErrorLogMessageHandler [7]: Capture and log messages "printed"
using ITK macros

* ctkVTKErrorLogMessageHandler [8]: Capture and log messages "printed"
using VTK macros



Thanks
Jc



[1]
https://github.com/commontk/CTK/blob/master/Libs/Widgets/ctkErrorLogModel.h

[2]
https://github.com/commontk/CTK/blob/master/Libs/Widgets/ctkErrorLogWidget.h

[3]
https://github.com/commontk/CTK/blob/master/Libs/Widgets/ctkErrorLogStatusMessageHandler.h

[4]
https://github.com/commontk/CTK/blob/master/Libs/Core/ctkErrorLogStreamMessageHandler.h

[5]
https://github.com/commontk/CTK/blob/master/Libs/Core/ctkErrorLogQtMessageHandler.h

[6]
https://github.com/commontk/CTK/blob/master/Libs/Core/ctkErrorLogFDMessageHandler.h

[7]
https://github.com/commontk/CTK/blob/master/Libs/ImageProcessing/ITK/Core/ctkITKErrorLogMessageHandler.h

[8]
https://github.com/commontk/CTK/blob/master/Libs/Visualization/VTK/Core/ctkVTKErrorLogMessageHandler.h


On Sat, Dec 13, 2014 at 5:41 PM, Steve Pieper <pieper at isomics.com> wrote:
>
> Hi Andras -
>
> I'm on record from previous discussions on the vtk developer list that I'd
> like to make vtk smaller (e.g. move vtkChemistry, GeoVis and similar things
> into their own add-on libraries [1]).  But on this one I actually agree
> with your argument that VTK really should have a provision for this rather
> than leaving it to each application to develop a custom solution.  Berk
> seems to have dug in his heels though, so maybe just add the feature to
> CTK?  Or leaving it in Slicer is okay by me too.
>
> -Steve
>
> [1]
> http://vtk.1045678.n5.nabble.com/Driving-away-your-existing-developers-td5728448.html
>
>
> On Sat, Dec 13, 2014 at 5:09 PM, Andras Lasso <lasso at queensu.ca> wrote:
>>
>>   The only reason for using macro is to be able to get the line number
>> and file name. The rest is handled by output window and logger classes.
>>
>> Andras
>>  ------------------------------
>> From: Bill Lorensen <bill.lorensen at gmail.com>
>> Sent: ?2014-?12-?13 16:58
>> To: Andras Lasso <lasso at queensu.ca>
>> Cc: ctk-developers at commontk.org
>> Subject: Re: [Ctk-developers] Info level logging macro in VTK
>>
>>   Personally, I do not like macros. For this functionality I would
>> prefer a logging class like we have in ITK.
>>
>> Bill
>>
>>
>> On Sat, Dec 13, 2014 at 4:32 PM, Andras Lasso <lasso at queensu.ca> wrote:
>> > Hi all,
>> >
>> >
>> >
>> > We are having a discussion with VTK developers about the necessity for a
>> > vtkInfoMacro (or vtkGenericOutputMacro) in addition to vtkErrorMacro,
>> > vtkWarningMacro, and vtkDebugMacro in VTK [1] . The new macro would
>> offer a
>> > standard way of logging non-error messages from VTK-derived application
>> > classes, tests, and examples. For example, you would not need to
>> specify a
>> > separate application-specific LOG_INFO macro in your application for
>> logging
>> > non-error messages while using the VTK standard vtkErrorMacro and
>> > vtkWarningMacro for errors.
>> >
>> >
>> >
>> > The next step would be asking for moving the log message formatting
>> from the
>> > VTK logging macros to the vtkOutputWindow class. That would allow
>> getting
>> > rid of the ugly multi-line VTK error messages, because in a custom
>> > vtkOutputWindow class the application could format the fields (message,
>> line
>> > number, etc.) in any way or it could send the info to the application
>> logger
>> > (there would be no need to parse the VTK error messages anymore to
>> extract
>> > the fields).
>> >
>> >
>> >
>> > It would help the discussion on the VTK list a lot if we know the
>> opinion,
>> > needs of more application developers:
>> >
>> > * Do you find the current VTK error/warning/debug logging convenient for
>> > your application?
>> >
>> > * Would you use INFO level logging in VTK-based classes in your
>> application?
>> >
>> > * Would you like to have customizable formatting of VTK error/warning
>> > messages? (e.g., have compact, single-line messages; or be able to have
>> the
>> > message, line number, file name, etc. separately so that you can send
>> it to
>> > your application?s logger)
>> >
>> >
>> >
>> > Thanks in advance.
>> >
>> > Andras
>> >
>> >
>> >
>> > [1]
>> >
>> http://public.kitware.com/pipermail/vtk-developers/2014-December/031102.html
>> >
>> >
>> > _______________________________________________
>> > Ctk-developers mailing list
>> > Ctk-developers at public.kitware.com
>> > http://public.kitware.com/mailman/listinfo/ctk-developers
>> >
>>
>>
>>
>> --
>> Unpaid intern in BillsBasement at noware dot com
>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at public.kitware.com
>> http://public.kitware.com/mailman/listinfo/ctk-developers
>>
>>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at public.kitware.com
> http://public.kitware.com/mailman/listinfo/ctk-developers
>
>

-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20141214/ae4a2aad/attachment-0001.html>

From nasil122002 at yahoo.de  Wed Dec 24 04:06:00 2014
From: nasil122002 at yahoo.de (Yusuf OEZBEK)
Date: Wed, 24 Dec 2014 09:06:00 +0000 (UTC)
Subject: [Ctk-developers] service-based plugin communication
Message-ID: <2021237534.975087.1419411960619.JavaMail.yahoo@jws11168.mail.ir2.yahoo.com>

Hello dear CTK developers!
How can I call a function in a plugin from another plugin via service-based communication? Or rather it is even possible?

The situation is as following:I have two different plugins A and B. 
The plugin A contains a GUI and a qPushButton on it. If I click on the button it should call a function in plugin B.
The plugin B provides a service which includes the name of the function (via an interface class (void function(); ) in plugin B) that should be called from plugin A and register itself.The plugin A catch any other modifications in service but if I call the function over? service then I get: symbol lookup error: /pluginA.so: undefined symbol: _ZN16interface14functionEv



Mit freundlichen Gr??en
Yusuf ?ZBEK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20141224/060d4c4b/attachment.html>