Changes between Version 12 and Version 13 of TracPluggableModules

Timestamp:

Jan 11, 2005, 6:10:56 PM (19 years ago)

Author:

Christopher Lenz

Comment:

Comments on todays code drop

TracPluggableModules

@@ -136 +136 @@
 Plug-ins should also be able to not only hook into the web-interface, but also into TracAdmin. The approach for this would be similar to the one discussed above, meaning that modules should be able to contribute commands.
 
+== Status ==
+
+I'm currently working on this code locally, and uploading tarballs as attachments to this page. The code is in prototype state, i.e. it is fully functional but is far from doing the stuff Trac can do. There isn't even database access yet.
+
+The tarball from 01/11/2005 has the following:
+ * A working plug-in system as described above, minus the configuration of which plug-ins are to be loaded.
+ * A new (and as of yet incomplete) abstraction layer between the Trac web-application and the web-server. Unlike the current {{{trac.core.Request}}} class, it provides separate request and response objects. It is based on [http://www.python.org/peps/pep-0333.html WSGI] with a simple adapter for CGI. ''This doesn't really have much to do with the plug-in system, it's just another refactoring that I'm playing with in the same sandbox.''
+ * An interactive shell that allows testing the Trac web-app from the command-line (in {{{trac/web/testserver.py}}}).
+ * A new abstraction layer on top of the ClearSilver templating engine. It allows populating the HDF using native Python data structures such as lists and dicts.
+ * ClearSilver templating is a plug-in ({{{trac/web/clearsilver.py}}}), request dispatching is a plug-in ({{{trac/web/dispatcher.py}}}) and building the web-site chrome (e.g. the navigation) is another plug-in ({{{trac/web/chrome.py}}}). Hooking into HTTP authentication is also a plug-in ({{{trac/web/ext_auth.py}}}). The idea with the latter is that we could provide an alternative plug-in that would do form-based authentication. 
+ * Plug-in stubs for the ticket, changeset, timeline and search modules.
+
+For testing the code, you'll need a normal Trac 0.8 environment set up. The easiest way then is to use the interactive shell:
+
+{{{
+$ cd trac-pluggable_20050111
+$ PYTHONPATH=. python trac/web/testserver.py /path/to/projenv
+> import trac.web.clearsilver
+> import trac.plugins.timeline
+> get /timeline
+}}}
+
+That last command will simulate an HTTP request, and you should get the response printed to the console. To get the HDF of a response, type:
+
+{{{
+> get /timeline?debug=1
+}}}
+
+You can import any plug-in you want using the {{{import modulename}}} command, the plug-ins will need to be on the Python path of course.
+
 == Your Ideas Wanted ==