[kepler-users] internally connect actor

[Shawn Bowers]

Yep, that button is a placeholder.  I think some of the pieces are
there to implement it (e.g., the suggest components), but we never got
around to implementing this.

Shawn

On Tue, Jul 14, 2009 at 1:31 PM, Chris Weed<chrisweed at gmail.com> wrote:
> Yea, that "Insert Adapters" button looks like what I want.
> Unfortunately, it seems to be a placeholder.
> Chris
>
> On Tue, Jul 14, 2009 at 11:00 AM, Shawn Bowers<sbowers at ucdavis.edu> wrote:
>> Hi Chris,
>>
>>> I would like to create an actor that when connected to other actors
>>> will inspect the actors it is connected to and show the user the set
>>> of actors that could fulfill this connection based on the Semantic
>>> info.
>>
>> For this, you might look at the "Type Check > Summary" context menu
>> action. This can be found by right-clicking on the workflow canvas.
>> This does both"semantic" and "structural" type checking for a
>> workflow. Like the other semantic type stuff, the UI is a prototype
>> ... but does let you see which channels are mismatched, which are
>> "correct" (everything matches), and which channels do not have enough
>> information (e.g., because the structural or semantic types aren't
>> given). When you click on channels in the tables of the UI, they are
>> highlighted on the canvas.
>>
>> Shawn
>>
>>> The user would be able to select from this set, and the actor would be
>>> internally created in my connector actor and connected to the ports.
>>> Is there an example of an actor that does this internal construction
>>> and connection of actor ports?
>>>
>>> Thanks,
>>> Chris
>>> _______________________________________________
>>> Kepler-users mailing list
>>> Kepler-users at kepler-project.org
>>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>>>
>>
>