|
|
| 2003-01-20 |
PyDS now supports TopicExchange |
|
The Python Desktop Server now has integrated TopicExchange support. You can fetch the list of topics, select some topics for your use and on posting in categories, you can select topics that should be pinged with your posting! And it shouldn't include HTML tags now, as they should be stripped. This might leave ugly formatted text, but who cares, it's only an excerpt ... |
|
posted at 19:26:08
#
|
| |
RSS rendering factored out |
There will be an abstract RSS rendering API, so that tools can quite easily implement RSS rendering using the standard RSSFeedRendering.tmpl. You just have to implement the following three methods:- getRSSTitle should deliver your feeds title
- getRSSDescription should deliver your feeds description
- getRSSItems should deliver your items as hashes with the RSS tags as keys (all lowercase!)
Just have a look at the WeblogTool to see how that works out, or look into the StoryTool for another implementation (yes, stories now have an RSS feed!) As a side effect of this changes is that the RSSFeedRendering.tmpl has changed, so throw your local copy away when upgrading! |
|
posted at 16:53:36
#
|
| |
abstract RenderTool for rendering content |
|
In CVS now there is an abstract rendering framework. The RenderTool is only a background thread with hooks, where you can hook in your tool to get background rendering with only little effort. StoryTool, MacrosTool and NuggetsTool use it to render their items and the index page. Nuggets and Macros are only rendered if a publish flag is set to yes. Stories now are only rendered if a draft flag is set to no. The pyds.css file has changed to add styles for h4-h6 and structured text starts now at h4 level for headlines (so you have 3 levels of headlines in a text, this should be enough for most purposes). |
|
posted at 15:15:28
#
|
| |
|
|
The current version now has structured text as promised. Works out quite nice, I think. There are some reworkings of inner parts in the queue, but I think the version will stabilize quite soon. And then I will release a 0.2 Alpha. My versioning scheme will be as follows: - 0.x versions are beta
- x.even numbers are stable
- x.odd version numbers are development
The project will stay in Alpha mode as long as functionality is still to be expanded. As soon as no massive new functionalty changes are planned, I will go Beta. In Alpha, all internal APIs can change without prior notice and so templates and stuff like that might be reworked and changed. With Beta mode I expect to have at least stable APIs, only the server itself might be changed and stabilized. Later with released versions, the development versions will be the area where big changes are done and the stable release will be exactly that, stable. Hopefully  |
|
posted at 10:59:28
#
|
|
|
This is the Python Desktop Server weblog.
 (Donations will be used by the author to buy stuff, fullfill selfish wishes or do other silly recreational things. You have been warned.).
The PyDS is
|
