[Brian Luft wrote]
>  One other piece I'd like to see is some sort of API to the Komodo
>  application itself.  You see a lot of the successful projects these days
>  exposing interfaces to Python and other dynamic languages so that the user
>  community can easily customize the application itself.   I think Komodo
>  would benefit greatly by documenting and exposing an API.  My understanding
>  is that some customization is possible if you dig through the Komodo program
>  directories.  

The Komodo macro system does document some of the exposed APIs. However,
a lot of functionality enabled by the macro system is undocumented and
APIs are definitely unstable. In future versions we hope to nail down
and document much more of the API and provide a system for making
plugins for other parts of Komodo (e.g. syntax checking, file status
info, etc.)

    http://aspn.activestate.com/ASPN/docs/Komodo/3.1/komodo-doc-macroapi.html

A fair amount of customizing is possible with the Toolbox and Projects
(custom menus, toolbars, commands, templates, macros, etc.). These can
be exported and imported with "Komodo Packages".

Cheers,
Trent

-- 
Trent Mick
TrentM@[...].com
_______________________________________________
Komodo-discuss mailing list
Komodo-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/Komodo-discuss