[kepler-dev] kepler extension points documentation

[Matt Jones]

Yes, that is a great point, and we should have it there.  In the past, we've
generally relied on the Ptolemy documentation for that, so I'll need to
figure out how to provide an appropriate pointer into the Ptolemy PDF files,
or otherwise link directly to the actor API.  Is there an html version of
the actor API around that we could point to, or maybe we could just generate
one from the ptolemy documentation latex files?  Maybe Christopher can
recommend a path for this when he returns from vacation?

Matt

On Fri, Sep 3, 2010 at 7:42 AM, Edward A. Lee <eal at eecs.berkeley.edu> wrote:

>
> This is great!  Should it include a pointer to "Authoring actors"?
>
> Edward
>
>
>
> On 9/2/10 10:52 PM, Matt Jones wrote:
>
>> Hi,
>>
>> A quick notice that I created a new page that improves our description
>> of extension points and APIs that are available to module developers and
>> actor developers in Kepler.  The new page is here:
>>
>>
>> https://kepler-project.org/developers/teams/framework/kepler-extension-points-1
>>
>> It provides a brief description and links to the more detailed page for
>> each extension point.  These pages vary in their quality and clarity,
>> but I f am hoping that collating them in one location will help motivate
>> the people in-the-know to improve them.  If you develop or know of
>> additional extension points that are meant to be used by module and
>> actor developers, please create a page and link it into that list.
>>  Thanks,
>>
>> Matt
>>
>>
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20100903/bd5b00c3/attachment.html>