[kepler-dev] Kepler specific Director and ComponentEntity classes and _addIcon()

Edward A. Lee eal at eecs.berkeley.edu
Tue Apr 18 21:37:33 PDT 2006

At 09:17 PM 4/18/2006, Matthew Brooke wrote:
>If I understand you correctly, you guys are saying we should use the 
>*Icon.xml system - is that right? If so, I don't think that's going 
>to work for Kepler; basically, we have about 130 (and counting) 
>icons already defined as standard SVG files - do you mean we'd need 
>to write a *Icon.xml file (which is not SVG, but is ptii-specific) 
>for each one? I'm not entirely sure I'm understanding you correctly, 
>so let me know if I'm on the wrong track...
>(keeping up the "train wreck" theme ;-)

This is not my suggestion...

What I'm suggesting is that we co-opt the mechanism that supports
the *Icon.xml technique in PtII.

Specifically, a Kepler-specific icon loader would be registered with
the MoMLParser using a static method (see previous email).  That
icon loader would populate each object that could have a *Icon.xml
file (does this currently include directors?) with a Kepler-specific
subclass of EditorIcon.  That subclass would access your existing
SVG data in whatever form it currently exists and provide the


Edward A. Lee
Professor, Chair of the EE Division, Associate Chair of EECS
231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal  

More information about the Kepler-dev mailing list