[kepler-dev] Re: [SDM-SPA] Re: user library

[Efrat Jaeger]

Currently we incorporate Ptolemy actors and libraries within Kepler by
jarring all the classes and xml files and including the ptolemyjar in the
classpath (this is all specified in the build file). You can possibly do the
same for SPA by including both a ptolemyjar and a keplerjar.

- Efrat

----- Original Message -----
From: "Bertram Ludaescher" <ludaesch at sdsc.edu>
To: "Terence Critchlow" <critchlow1 at llnl.gov>
Cc: "Xiaowen Xin" <xin2 at llnl.gov>; <sdm-dev at sdsc.edu>
Sent: Friday, March 19, 2004 7:05 PM
Subject: Re: [SDM-SPA] Re: user library


>
> Terence, Xiaowen:
>
> That's a good discussion. Should we cross-post such question to
> Kepler-dev since all the Ptolemy folks and other Kepler folks are
> listing in?
>
> I don't have the answers to these questions (while Ilkay might -- but
> she's gone camping I think ..), but I could forward to Kepler-dev if
> you like.
>
> Bertram
>
> >>>>> "TC" == Terence Critchlow <critchlow1 at llnl.gov> writes:
> TC>
> TC> Hi Xiaowen
> >> So if we distributed actors, we'd probably want to create a library
file
> >> with the same format as "user library.xml", and ask the user to import
> >> that.
> TC>
> TC> It seems like there should be a cleaner way to do this. If I
understand
> TC> correctly, in order to use an actor developed by someone else and not
part
> TC> of the official distribution, a user would need to:
> TC> (1) download an actor, for example compiled java code, and store it
somewhere
> TC> (2) download a library file
> TC> (3) update the library file to point to the right location in their
environment
> TC> (4) import the library file
> TC>
> TC> We could eliminate step 3 if we encourage (force) people to place the
file
> TC> in a known location, but I am not sure how well that would work across
> TC> platforms - for example, you don't really have a home directory in
windows
> TC> so I am not sure if ~/.ptolemy is well defined, and relative paths (ie
> TC> ../users/me won't work well if the system is installed in a protected
or
> TC> shared directory. If we can find a way to get around this, it might be
> TC> worth it to see if we can modify the code to look in a designated spot
> TC> (specified in a config file?) for the actors and automatically import
> TC> them.  Just a thought.....
> TC>
> TC> Terence
>