'Look Inside' (was Re: [kepler-dev] Re: Ptolemy II 4.0.1 is available for download)
Edward A Lee
eal at eecs.berkeley.edu
Fri Aug 6 05:10:58 PDT 2004
The principle being followed is that "Look Inside" reveals whatever
defines the functionality of the actor...
I think it would be confusing to have two versions of look inside,
but I don't feel too strongly about this.
A knowledgeable user can use the tooltip info (which reveals the full
class name of the actor) to find the source code.
I like the idea of Properties display... In fact, we could probably
consolidate a bunch of functionality into that...
At 12:57 PM 8/5/2004 -0700, Tobin Fricke wrote:
>On Thu, 5 Aug 2004, Bertram Ludaescher wrote:
> > In the mid/long run, I think it will be good to have a set of higher
> > order actors (as mentioned before, e.g. by Edward).
>Something tangentially related: On most actors, the 'Look Inside'
>function will give you the Java source to that actor. But on some actors,
>like PythonScript and some of the higher order actors, 'Look Inside' will
>show you the python code or the encapsulated model. That's fine, but as
>far as I can tell, it means that you can't tell what the actor actually is
>without looking at the MoML file!
>Perhaps it would be appropriate to have separate 'Look Inside Java Actor'
>and 'Look Inside...' options so that the user can indicate what degree of
>dereferencing is desired.
>Other possibilities would be to have a 'Properties...' context menu option
>that would give us the name of the underlying Java class (with "See
>code..." and "See Javadoc..." buttons) and/or the MoML code used it
>kepler-dev mailing list
>kepler-dev at ecoinformatics.org
Edward A. Lee, Professor
518 Cory Hall, UC Berkeley, Berkeley, CA 94720
phone: 510-642-0455, fax: 510-642-2739
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal
More information about the Kepler-dev