|
|
| 2003-09-30 |
New debian repository for CVS versions |
|
The hourly snapshot now creates a debian package, too. The packages needed for CVS versions of PyDS are available under http://simon.bofh.ms/~gb/debian-dev/ in the same way as the stable versions. Currently there is PyDS 0.6.0 and docutils 0.3 in debian-dev, while the stable repository still contains PyDS 0.5.2 and docutils 0.2. |
|
This post references topics:
software
|
|
posted at 13:15:12
#
|
|
| |
| 2003-09-29 |
|
|
The linked RSS feed contains interviews by Chris Lydon. It's a very new feed done by Dave Winer. It is broken in at least two aspects:
- it uses chr(13) (carriage-return) instead of chr(10) (linefeed) as line termination
- it reuses GUIDs! Yep, he reuses the same GUID on the continuations, too. So the Python Desktop Server filters out all but the first part, as those are already seen.
Damn. And I thought it would be just easy to write the enclosure stuff. It is easy to write - but not easy to debug, because none of the available feeds really valid and usefull.
The other feed that's linked in the verbatim documentation of the enclosure feature references enclosures that are not accessible any more.
Ok, I just assume that all this would work if the feeds would work, so if somebody uses some enclosure enabled feeds and notices some weirdness to happen, drop me a note and I try to find out who is guilty 
Oh, the complete enclosure stuff is now in CVS, both weblog and aggregator support it now.
Update: Dave has fixed the duplicate-GUID problem in the Lydon feed, so there now is a quite nice feed to test enclosures with!
|
|
posted at 17:24:48
#
|
| |
PyDS can now send enclosures |
|
The Python Desktop Server can now send enclosures. This posting has added the current CVS snapshot as an example. The enclosure must be an HTTP URL, so that the Python Desktop Server can determine it's content type. The server must return both the content type and the content length. The URL is only passed on, the file isn't actually moved. So if you want to do something with enclosures, you have to first upload your file and afterwards put the URL of the file into the postings enclosure field when doing your posting.
To upload (upstream) files to your community server, just save them in ~/.PyDS/www/ or create a special directory below that (for example call it gems or something like that). Watch your event log, you will see when the file is upstreamd and will get the URL for that file there. Copy that URL to the enclosure entry field.
To activate enclosure posting, you need to go to your enclosure preferences and set it to active.
|
|
Enclosure: application/x-tar (537512 bytes)
|
|
posted at 15:34:56
#
|
|
| |
| 2003-09-28 |
|
|
Roberto Alsina is at it again. This time he presents a GUI client for the Python Desktop Server and Advogato - so if you don't like editing stuff through the web, this might be an option for you!
This reminds me of a todo item I have that would - if implemented - enable you to mirror some postings to other weblog systems (so you can post something to your PyDS and mirror it to Advogato or LiveJournal). Much like footbridge for Radio. But it's still a todo item - somebody else interested in doing this little gem? You could use the TopicExchangeTool as a starting point and implement the MirrorTool in much the same way. Keep the external system access code in driver modules, so it becomes extensible.
|
|
posted at 11:30:40
#
|
|
| |
| 2003-09-27 |
|
|
Roberto Alsina wrote a nice article on how to set up the Python Desktop Server for remote access and adds some notes on how to use SSL to access PyDS through a SSL proxy. |
|
posted at 00:21:52
#
|
|
| |
|
|
| |
| 2003-09-24 |
New in CVS: docutils 0.3 support |
|
The CVS version now depends on docutils 0.3. This means that you must upgrade to docutils 0.3 if you want to use the CVS version! Of course, the latest stable release still depends on docutils 0.2, so you must not upgrade to docutils 0.3 if you want to use the latest stable release 0.5.2!
Now lets see how many of you don't get this right and break their installation
|
|
This post references topics:
software
|
|
posted at 16:28:16
#
|
|
| |
| 2003-09-23 |
New in CVS: unicode support |
|
I just pulled in the patch by Yasushi Iwata for unicode support in the Python Desktop Server. If you set the variable documentEncoding in your ~/.PyDS/etc/PyDSConfig.py to utf-8, all your data will be stored utf-8 encoded and delivered utf-8 encoded. This enables you to use the full range of unicode chars. One caveat: if your databases are already filled, your data will be in iso-8859-1 and you would need to convert your data to utf-8. This conversion program isn't yet available, but I think I will create one as time permits. So you are better off with using the unicode stuff only with a new installation of the Python Desktop Server (and since it is CVS stuff, it's bound to break and you really shouldn't use it on your production blog!). |
|
This post references topics:
software
|
|
posted at 00:25:04
#
|
|
| |
| 2003-09-22 |
Back ... |
|
Just to let everyone know why it was silent around here: I was on vacation. I will start on fixing more bugs and integrating pending patches soon. |
|
posted at 11:01:52
#
|
|
|
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
|
