PureDocs
{5} Assigned, Active Tickets by Owner (Full Description) (3 matches)
will (3 matches)
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #2 | Support zope.interface in Python | plugins | enhancement | 02/04/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Python language plugin should have optional support for creating resources specifically for zope.interface declarations. Alternatively, another Python language plugin, descending from the primary one, should be created with this enabled. I would envision enabling zope.interface support using Options from the plugin, partially as an example of how plugin-specific options are handled, to make the Python language plugin a more complete example of how to write plugins. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #8 | C Language Plugins | base | initial-release | enhancement | 03/05/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We should support C language plugins, in the form of shared libraries that either provide or link against a parser for whatever language. Since a lot of languages out there have C-based parsers already, this should provide a quick and easy way to expand PureDocs language support with less effort than specialized Python parsers. The intention was never to require everything be implemented in Python. The basic idea would be to use the ctypes FFI package included in Python 2.5 (available for previous versions, but not included) to dynamically load specified shared libraries and use a specified API to interact with those libraries. Data-type conversions might be tricky, and it might be necessary to define a C analog to our Python Resource class. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #7 | Make Browser UI use anchor links | plugins | task | 02/11/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The Browser should use anchor links to load the appropriate resources for the anchor link. This way urls that link directly to a specific function, etc, can be used. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||