<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Patrick,<br>
<br>
There is an example in the ptII development tree that uses Python
for GUI work.<br>
Bob Weber sent me a model that I folded in as<br>
$PTII/ptolemy/actor/lib/python/demo/RecordManipulation.xml<br>
I've attached the model.<br>
<br>
The Ptolemy II development tree also includes a draft system for
laying out components<br>
in a runtime window. In the Ptolemy II development window, View
-> Interface Window brings<br>
up a run control panel that is editable.<br>
<br>
We stopped work on this when we submitted changes to the underlying
package and the author<br>
said he was moving to Eclipse RCP.<br>
<br>
To access the Ptolemy II development tree, see<br>
<a class="moz-txt-link-freetext" href="http://chess.eecs.berkeley.edu/ptexternal">http://chess.eecs.berkeley.edu/ptexternal</a><br>
<br>
For information about Kepler and Python, see<br>
<a class="moz-txt-link-freetext" href="https://kepler-project.org/developers/reference/python-and-kepler">https://kepler-project.org/developers/reference/python-and-kepler</a><br>
<br>
There is also a thread at<br>
<a class="moz-txt-link-freetext" href="http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2011-November/002044.html">http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2011-November/002044.html</a><br>
about Kepler and Python.<br>
<br>
_Christopher<br>
<br>
On 6/8/12 5:44 PM, Edward A. Lee wrote:
<blockquote cite="mid:4FD29C59.4040703@eecs.berkeley.edu"
type="cite">
<br>
As I said before:
<br>
<br>
They aren't as limited as you think...
<br>
If a parameter contains an attribute that subclasses
<br>
ParameterEditorStyle, then that attribute controls
<br>
how the interaction with the parameter is done.
<br>
See the
<br>
$PTII/ptolemy/actor/gui/style directory.
<br>
<br>
In addition, you can completely customize the
<br>
dialog that Configure Actor opens.
<br>
See EditorFactory and its subclasses for examples.
<br>
<br>
For an example, the PythonScript actor in the library
<br>
opens a text editor when you select Configure Actor.
<br>
<br>
Edward
<br>
<br>
On 6/8/12 2:14 PM, Rohan Sadler wrote:
<br>
<blockquote type="cite">Hi Patrick,
<br>
<br>
I was thinking the same thing today, and was having a look at
wxPython. However, I am in the early days and so can't help you
re: experience.
<br>
<br>
At this point in time I am almost tempted to run Kepler from the
command line:
<a class="moz-txt-link-freetext" href="https://kepler-project.org/developers/reference/executing-kepler-from-the-command-line">https://kepler-project.org/developers/reference/executing-kepler-from-the-command-line</a>.
The python/java GUI buttons would simply change default object
assignments in the kepler/java script before running the
project. There though should be a better way, as it would not be
computationally smart to have two interpreters stacked on top of
each other.
<br>
<br>
re: other toolkits. The forthcoming book
<a class="moz-txt-link-freetext" href="http://www.amazon.com/Programming-Graphical-Interfaces-Chapman-Series/dp/1439856826">http://www.amazon.com/Programming-Graphical-Interfaces-Chapman-Series/dp/1439856826</a>
also enables learning GUIs for R.
<br>
<br>
I agree with you. The bottom line is that there is a need for
custom interfaces for endusers of the kepler workflow, as soon
as the workflow gets complex. Most of my endusers are familiar
with excel and that is it when it comes to software, and don't
want to venture too far out. For example a technician typing in
soil and plant parameters, before getting a soil water balance
from Kepler. Something like RExcel means they can plug in
numbers in a spreadsheet, and get their outputs. In a workflow
this would mean that:
<br>
1) Run the workflow in Kepler,
<br>
2) An excel styled spreadsheet would pop-up, pre-populated with
default parameters, and perhaps some pre-specified data [e.g.
swing pulldown to source locally held weather station data].
<br>
3) End user would type in their numbers, then press 'done'
<br>
4) Kepler would continue to execute with the new information.
<br>
<br>
Regards
<br>
Rohan
<br>
<br>
Senior Scientist
<br>
Astron Environmental Services
<br>
<br>
Adjunct Senior Lecturer
<br>
School of Agricultural and Resource Economics
<br>
The University of Western Australia
<br>
<br>
________________________________________
<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:kepler-users-bounces@kepler-project.org">kepler-users-bounces@kepler-project.org</a>
[<a class="moz-txt-link-abbreviated" href="mailto:kepler-users-bounces@kepler-project.org">kepler-users-bounces@kepler-project.org</a>] On Behalf Of Patrick
Janssen [<a class="moz-txt-link-abbreviated" href="mailto:patrick@janssen.name">patrick@janssen.name</a>]
<br>
Sent: Tuesday, 5 June 2012 8:54 AM
<br>
To: <a class="moz-txt-link-abbreviated" href="mailto:kepler-users@kepler-project.org">kepler-users@kepler-project.org</a>
<br>
Subject: [kepler-users] component gui
<br>
<br>
The GUI creation tools under the 'Configure Actor' (for creating
custom interfaces for setting actor parameters) are limited (for
example, no sliders, no drop down lists, no tabs, no free text,
no layout constraints, etc). In particular, I find this an issue
when defining complex Python actors with lost of different
parameters. As a result, the interface can end up being a bit
unfriendly for the end users of my actors.
<br>
<br>
I am wondering - what is the best way of overcoming this? Has
anyone had any experience creating custom GUIs for actors using
either Java or Python, for example using Swing or other
toolkits?
<br>
_______________________________________________
<br>
Kepler-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Kepler-users@kepler-project.org">Kepler-users@kepler-project.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users">http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users</a>
<br>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kepler-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kepler-users@kepler-project.org">Kepler-users@kepler-project.org</a>
<a class="moz-txt-link-freetext" href="http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users">http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Christopher Brooks, PMP University of California
CHESS Executive Director US Mail: 337 Cory Hall
Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
ph: 510.643.9841 (Office: 545Q Cory)
home: (F-Tu) 707.665.0131 cell: 707.332.0670 </pre>
</body>
</html>