I wrote a very simple server for reStructuredText files quite a while ago. Also I did look into S5 quite a while ago including the option to write the presentation in ReST and convert it to S5 HTML with docutils. The somehow logical conclusion (which I failed to see for quite a while as well…)was to adjust the restserver to actually output S5 directly. So S5server got released today. Mainly as a friend at work needed to write an S5 presentation and this makes it very simple and to be able to concentrate on the writing and not any conversion, scripting etc…
If there is also such a thing let me know, hardly worth having two of the same things around.
Maybe a bit over the top to give the S5server its own release but on the other hand it looked useful just on its own.
I am currently using at least 3 different types of Wiki markup at work: JSPWiki markup, REST (reStructuredText) and another Wiki of which I don’t know its name. I have been using REST for personal projects too and I guess am biased a bit being a Python “fan”.
Anyway, I found the http://www.wikimatrix.org from an article on O’reillynet. Not bad for decision making although REST markup is not checked. (A quick googling showed at least MoinMoin seems to handle REST.)
After my experiences until now I still find REST the most readable. Maybe it is just me (and my designer background) but I find REST (just like Python sourcecode) the most pleasing and therefore also the most usable format.
(BTW, I know I should not do any bashing but that’s exactly why I think Perl is unusable – its ugly syntax [besides the do-it-5-different-ways philosophy]…)
just found the release of docutils 0.4. Guess I need to check if my own restserver does still work. It worked with 0.3.10 (never actually released) so it should do but one never knows…
I wanted to do a (tiny new) release of the restserver anyway, so a good time…
did the first steps of the TurboGears wiki tutorial. Looks very neat and I noticed it used docutils as well as kid which I already knew.
A problem I had but it was easily overcome: I have MySQL installed and needed the MySQLdb lib. Quite simple to find out but I guess it should be mentioned as probably quite a few people are using MySQL (e.g. when they come from a PHP background).
Otherwise it all looks new but very easy.
Not special for TurboGears I guess but I do like the ez_setup (eggs? need to look into that a bit more) which is really convinient. Something Python needed for a very long time.
Well, need to do some more tomorrow, too late already…
There is an new mailing list about my favourite schema language (not that I have used many and thoroughly but anyway), the RelaxNG user list.
A current topic is schema documentation. When I wrote my first bigger set of RelaxNG schemas I actually thought about that quite a bit as I had to do at least some kind of docs for the client and also the programmers of the framework using that specific XML format described by the schema. For now I simply used simple comment and basic annotations (“
# comment” or “
## annotation” in the compact syntax which I prefer). People accustomed to DTDs probably understand the compact syntax without knowing RelaxNG, at least the more simpler parts of it. I also used Oxygens RelaxNG diagrams to give a visual overview of the XML format.
I did notice however that a better documentation with maybe examples and more stuff would be handy, even a simplified version for people actually using the grammar and not building on the grammar would be quite useful at times. Therefor at first I though of simply adding a RelaxNG part to my own XSLdoc app which does about the same for XSLT what Javadoc does for Java. In documentation for RelaxNG (having a compact syntax by itself) would actually be quite nice to use the Python Docutils wiki like syntax I use for my XSLT documentation.
I do know the [ ] syntax for structuring Relax annotations but I think I’d prefer a simple and much more readable wiki like syntax to a more explicit-markup like syntax like relax  stuff.
From a Docutils documented RelaxNG schema it would be easy to generate a set of XHTML documentation (or other formats of course) like the ones Javadoc generates. I still quite like that docs even that I do not use Java that much. They come in handy when using a Java library from e.g. Jython or simple to look what a particular lib does. Actually I prefer Javadocs to most Python documentation as it is much more standardized.
I think using wiki-like markup is easier for most people than actually using more explicit markup like XML or HTML.
Well, at least a very interesting new mailing list which I guess I will follow quite regularly. (BTW, all XML related mailing list seem to have only a small set of people actually using it, you see the same names all over again. Wonder what other people use to keep informed and ask questions…)
At Xtech 2005 I noticed quite a few of speakers used S5 presentations.
I did notice S5 some time before that and actually had the chance to use it for a small workshop in the company I work for. Favoring reStructuredText of the Python Docutils project I was very happy to find the RST2S5 converter script which is just great. This way I am able to simply write a presentation which almost autoconverts to an S5 presentation with a simple batch script even with working HTML examples which this particular workshop was actually about. I always tried to stay away from PowerPoint anyway (Impress is not that much better I guess), but now there’s a real alternative…
Adjusting the S5 template to fit what I wanted was another thing though. Being quite fluent with CSS I thought it easier but 4 different stylesheets which are sometimes not very logically divided which one defines what was a bit tricky. And I disabled the “click-for-next-page” functionality which I noticed during most talks just irritates most speakers who try to show or select a part of a page to highlight it.
But anyway, a very fine tool…
Started to blog again but now with a new system.
Before I used PyDS but as my provider has no Python support and I wanted to check out a blog on my own site I choose WordPress which seemed to be used by quite a few people (and is used in the company I work for, too). Installation really was VERY simple. This is a stark contrast to PyDS. I work on Windows and was not even able to install PyDS on my new computer which I got about a few weeks ago now. I quite likes PyDS, one being a Python thing and also the system was quite nice, but WordPress seems to have a few things which are really polished already:
- full XHTML/CSS compliance
- tags (categories)
- simple installation (I am no pro but no beginner either but still don’t want to spend some hours to install a now basic thing as a weblog
- the ability to send a new entry as an email seems nice. I have not tried it yet though
The one thing I do miss is the reStructuredText input mode of PyDS. I use docutils quite frequently now and would like to use it for a blog too. There seems to be a similar thing coming from a Perl thing but I don’t want to use another similar markup again.
So, the new name “second step in blogging” maybe made a bit more clear, hope I get around to really post more stuff than on the first try…
Maybe I’ll copy some stuff from the first try here but at least intend to write new stuff too