[Paraview] help: problem about message passing in paraview

[Berk Geveci]

The paraview architecture is a wee bit to complicated to describe in
an e-mail. The ParaView Guide explains it some. In short:

1. The gui elements make calls on an (C++) API called "server manager"
2. The server manager translates these into a stream that can be sent
over the network
3. An interpreter receives these streams, parses them and converts
them into C++ calls.

Instead of using something like CORBA, we developed a very simple and
light layer that is automatically generated at compile time (generated
pretty much the same way Tcl, Python and Java wrappers are generated
for VTK automatically).

-Berk

On 5/30/05, Nancy <haifang_zhou at 163.com> wrote:
> Hi, all,
>      I am reading the source code of paraview, and want to understand the message passing scheme in paraview.
> For example, when I push a button or choose an item in the menu on the client GUI, how this event is passed to the final related processing Class object?
> I can only find the begin end of the source code (e.g. create a menu item) and the final class of processing (e.g. a reader/source class), but I can not track the message passing process between the begin end and final methods of related class.
>     Who can give me an answer?   Thanks for any help!
> 
> Best,
> Nancy
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
> 
> 
>