[clam-devel] iPyCLAM

[David García Garzón]

Nice fix!

Let's now get ride of the index and the type as stored attributes and 
constructor parameters in Connector. Let's ask them to the proxy just when 
required.

Next step, the Network object and instrospecting its processings. That is:
net = Network(proxy)
net.proc1
net["proc1"]
net. [tab] to get the available processings (__dir__)

You already did that for ports, configs and so on so it will be quite straight 
forward, i guess, and we can move on quickly and start modifying the network 
(adding, removing, renaming, connecting, disconnecting...)

David.


On Thursday 17 February 2011 20:36:46 Xavier Serra wrote:
> Hi guys,
> I'm commenting a fix here. This is mostly for David, but since he told me
> to now discuss design related questions here in the list I'll be posting
> it here.
> 
> We talked about PeerConnectors and the need to invert direction when
> creating a peer. This is not needed because when we ask for the peers of,
> for example, Processing2.Inport1 we specify in the constructor that we
> want a Connector.Port + Connector.Out and we save this information.
> 
> I became aware of this when I switched to dynamic asking of the index of a
> Connector, it generated an error because it was asking the connectorInfo
> of a Processing1.OutPor1 as a Connector.In
> 
> I'll commit the fix soon when I'm done switching all the tests for deleting
> the index property and the type property used in the Connector constructor
> 
> Bye!
> 
> On Feb 16, 2011, at 12:24 AM, David García Garzón wrote:
> > On Wednesday 16 February 2011 00:12:50 David García Garzón wrote:
> >> We moved the development of ipyclam from Xavi Serra's private repository
> >> to CLAM's. We invite other developers to check it out and play with it.
> >> 
> >> import TestFixture
> >> from Processing import Processing
> >> p = processing("Processing1", TestFixture.proxy())
> >> p.[tab] and start to explore
> >> 
> >> Until now Xavi focused on network introspection and he is about to start
> >> to do manipulation. Even though it still relies on dummy network
> >> definitions, it has quite a good shape. Auto completition for
> >> discovering seems a quite powerfull feature. On big traits, missing
> >> aspects are:
> >> - top level network objects
> >> - manipulation: adding/deleting processings, connecting and
> >> disconnecting - implementing a network proxy that is based on CLAM (not
> >> dummy) - adding a ipyclam console to the NetworkEditor
> >> 
> >> But all that seems quite straight forward and Xavi is working hard on
> >> it.
> >> 
> >> David.
> > 
> > I did several typos in that code. The corrected one:
> > 
> > import TestFixtures
> > from Processing import Processing
> > p = Processing("Processing1", TestFixtures.proxy())
> > p.[tab] and start to explore
> 
> _______________________________________________
> clam-devel mailing list
> clam-devel at lists.clam-project.org
> http://lists.clam-project.org/listinfo.cgi/clam-devel-clam-project.org