[kepler-users] problems finding the python actor

[Trina Myers]

Thankyou Matt and Dan for your prompt replies, I look forward to the next
version. 

I had found in the context drop down a 'save in library' option and added a
saved version of Dan's pythonActor (from the demos available) to the local
library, although when using a new instance of it I don't get the full text
window as you get in the examples, only the small edit box available in the
'edit parameters' dialog box. I have tried doing this with the 'instantiate
component' with the same results. The actor works ok, its just a but awkward
scripting in such a small window...

I am sure by the time I am up to speed on using python to script what I am
wanting, the new Kepler version will be availabe :) (actually by that time
we might be 3 versions ahead)

Once again thankyou for such helpful responses,
Trina



-----Original Message-----
From: Dan Higgins [mailto:higgins at nceas.ucsb.edu] 
Sent: Tuesday, 14 October 2008 6:06 AM
To: Matt Jones
Cc: Trina Myers; kepler-users at ecoinformatics.org
Subject: Re: [kepler-users] problems finding the python actor

Hi Matt and Trina,
    Although the PythonScript actor is not in the actor tree of Kepler 
1.0.0, the code for the actor IS included as can be seen by the examples 
that appear in $KEPLER/demos/Python/ directory. You can build a new 
workflow by copying the PythonScript actor from one of the examples 
(e.g. PythonDialogExample.xml). Alternatively, you can use the 
Tools/Instantiate Component menu to create a Python actor using the 
class name "ptolemy.actor.lib.python.PythonScript". Once created you can 
then save it in your local library.

Dan Higgins

-----

Matt Jones wrote:
> Hi Trina,
>
> After looking into it, I found that the PythonScript actor did not 
> ship with Kepler 1.0.0, however we have added it into the current 
> development version, so it should ship with the next release of 
> Kepler.  We're working on making the actors more independent of the 
> workflow engine, so that new actors can be distributed and shared 
> between releases of the workflow engine.  But this is not fully in 
> place for 1.0.0, so we need to look into what the options are.  Chad 
> is going to spend a little time doing this, seeing if he can package 
> up the python actor into a KAR file that you can import into your 
> version of Kepler. Chad should report back to us sometime in the next 
> few days...
>
> Matt
>
> On Sun, Oct 12, 2008 at 8:01 PM, Trina Myers <t.myers at bigpond.net.au 
> <mailto:t.myers at bigpond.net.au>> wrote:
>
>     Hello,
>
>     I am a new user and would like to implement some python scripts
>     into the
>     workflow. However the pythonActor does not seem to be available in the
>     repository included in the installation version (Version:1.0.0 May08,
>     Windows with R). Any help would be appreciated..
>
>     Cheers
>     Trina
>
>     _______________________________________________
>     Kepler-users mailing list
>     Kepler-users at ecoinformatics.org
>     <mailto:Kepler-users at ecoinformatics.org>
>
http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
>
>
>
>
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Matthew B. Jones
> Director of Informatics Research and Development
> National Center for Ecological Analysis and Synthesis (NCEAS)
> UC Santa Barbara
> jones at nceas.ucsb.edu <mailto:jones at nceas.ucsb.edu>                     
>   Ph: 1-907-523-1960
> http://www.nceas.ucsb.edu/ecoinfo
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ------------------------------------------------------------------------
>
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
>