Hello,
I would like to write a network broker to make the bridge between a GUI and
the Orocos components. My first idea was to use the ControlTaskProxy to get
a pointer to each TaskContext :
TaskContext* myRemoteComponent = ControlTaskProxy::Create("MyComponent);
However, after looking at the KTaskBrowser, I saw that it directly uses the
CORBA interface RTT::Corba::ControlTask_var. What's the best way to
communicate with Orocos component in a GUI and what are the pros/cons of
each solution?
Thank you!
Philippe Hamelin
GUI Design Pattern
On Apr 23, 2009, at 09:22 , Philippe Hamelin wrote:
> Hello,
> I would like to write a network broker to make the bridge between a
> GUI and the Orocos components. My first idea was to use the
> ControlTaskProxy to get a pointer to each TaskContext :
>
>
>
> However, after looking at the KTaskBrowser, I saw that it directly
> uses the CORBA interface RTT::Corba::ControlTask_var. What's the
> best way to communicate with Orocos component in a GUI and what are
> the pros/cons of each solution?
We use the ControlTaskProxy approach above. An outline is actually in
a unit test case I submitted, so you can see it at
http://orocos.org/forum/orocos/orocos-users/corba-connection-problem-if-...
(check the attachments to the second post). Despite that posting, this
works well for us in actual GUIs and is very simple to use.
As Peter has mentioned a few times, using the insides of the
TaskBrowser or Deployer can be a bad idea ... I think he doesn't like
some of his previous code ... ;-)
HTH
S
GUI Design Pattern
You did it exactly the way I was planning to do so. Thank you to reassure me
in this choice :-).
Philippe Hamelin
2009/4/23 S Roderick <kiwi [dot] net [..] ...>
> On Apr 23, 2009, at 09:22 , Philippe Hamelin wrote:
>
> Hello,
>> I would like to write a network broker to make the bridge between a GUI
>> and the Orocos components. My first idea was to use the ControlTaskProxy to
>> get a pointer to each TaskContext :
>>
>>
>>
>> However, after looking at the KTaskBrowser, I saw that it directly uses
>> the CORBA interface RTT::Corba::ControlTask_var. What's the best way to
>> communicate with Orocos component in a GUI and what are the pros/cons of
>> each solution?
>>
>
> We use the ControlTaskProxy approach above. An outline is actually in a
> unit test case I submitted, so you can see it at
>
>
> http://orocos.org/forum/orocos/orocos-users/corba-connection-problem-if-...
>
> (check the attachments to the second post). Despite that posting, this
> works well for us in actual GUIs and is very simple to use.
>
> As Peter has mentioned a few times, using the insides of the TaskBrowser or
> Deployer can be a bad idea ... I think he doesn't like some of his previous
> code ... ;-)
>
> HTH
> S
>