Hi Madhavi,
It is possible to add a custom module to your suite. One way of doing
so is to make your new custom module itself into a suite. And then, in
addition to a reference to itself, your module should have a reference
to *kepler-2.1.0. More information on the details of how to do this
sort of thing can be determined by reading the build system
documentation which is available here:
https://kepler-project.org/developers/teams/build/documentation/build-system-instructions
#making-your-own-modules
This documentation should probably answer all of your questions about
dependencies.
In terms of getting your own actors to show up in the canvas, this
should be addressed in sections 10.3 and 10.4 of the Kepler User
Manual which is available here:
ttps://code.kepler-project.org/code/kepler-docs/trunk/outreach/
documentation/shipping/UserManual.pdf
Hope this helps,
David
On Jun 8, 2011, at 11:48 PM, Madhavi Tikhe wrote:
Hi,
I have few questions.
1. My current suite is Kelper-2.1. is it possible to add a custom
module to it? If yes, how?
2. If I create custom suite say foo and it should depend on the
modules already available in suite kepler-2.1. how to establish this
dependency? I would like to use core as well as custom actors
together.
3. I create a custom suite sfoo and a custom module mfoo in sfoo. If
I run kepler from the custom suite sfoo, can I see the actors added
in the mfoo in the left hand side actor's tree in UI? If no, is
there a way to see them so it is easier for users to drag-n-drop
those actors on canvas while creating workflow?
Thanks in advance.
Madhavi
DISCLAIMER
==========
This e-mail may contain privileged and confidential information
which is the property of Persistent Systems Ltd. It is intended only
for the use of the individual or entity to which it is addressed. If
you are not the intended recipient, you are not authorized to read,
retain, copy, print, distribute or use this message. If you have
received this communication in error, please notify the sender and
delete all copies of this message. Persistent Systems Ltd. does not
accept any liability for virus infected mails.
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
