• Mon­keyStu­­dio is a rather neat Qt4 IDE.

• Kat­a­pult is a pret­­ty launch­er (but I won­der if it could dis­­­play more than one match as I type­­?).

I will try to write more de­tailed re­views in my co­pi­ous free time

As a re­sult of my play­ing with mootools and cre­at­ing pow­er­point-style slideshows on web­pages from re­struc­tured tex­t, I am pret­ty much de­cid­ed about turn­ing this in­to a stan­dalone, re­al ap­pli­ca­tion.

I am do­ing a PyQt4 fron­tend, and re­struc­tured text ad­dons to gen­er­ate the slides.

The na­tive file for­mat is re­struc­tured text it­self, and it sup­ports ba­sic tran­si­tions be­tween slides.

It still needs a ton of work, but here is a video show­ing how it looks af­ter a cou­ple of days hack­ing. You can see the cur­rent UI, a doc­u­men­t's source, and a demon­stra­tion us­ing fire­fox (on­ly be­cause Kon­qy does­n't sup­pose opac­i­ty, the rest of the tran­si­tions work even bet­ter on Kon­queror)

It's Og­g/The­o­ra and 3MB (thanks openo­my.­com!): the video

Now, I don't know if this is use­ful, but I do think it's way neat.

In­spired by S5, rst2s5, and mootools I took an hour (or two) and hacked this neat lit­tle slide tool.

The goals dif­fer from S5 in that I in­tend to write a fron­tend, so that you have a sort of very-poor-­man's pow­er­point, but al­so in that the out­put should be sim­ple to em­bed in oth­er pages so that I can even­tu­al­ly make this a part of bartle­blog.

Check it out (click to go to next slide, move mouse to the top of the slideshow for con­trol­s):

from base64 import *
def myFirstFunction():
      print b64decode ('YnllIHdvcmxkIQ==')

.. flickr:: myPhotoTitle

There may be an ar­ti­fact when you slide out the syn­tax-high­light­ed box­es, but I have no idea how to fix it.

Al­so, I have not test­ed it at all in IE, so if it fails there, don't wor­ry, that's to be ex­pect­ed!

Next time I speak in pub­lic, I may use this :-)

And, as a teas­er... this is the source for the pre­sen­ta­tion you just saw:

Why use BartleBlog
==================

(If you are a nerd)
~~~~~~~~~~~~~~~~~~~

:author: Roberto Alsina <ralsina@kde.org>

It's nerd-oriented
------------------

It's trivial to display source code, with
proper syntax highlighting.

.. code-block:: python

  from base64 import *
  def myFirstFunction():
        print b64decode ('YnllIHdvcmxkIQ==')

Even for things like shell sessions.
Dammit, I am a nerd, I will try to add every nerd
feature I deem cool.


It does things simply
---------------------

Wanna show a flickr photo?

.. code-block:: rst

  .. flickr:: myPhotoTitle

How about using openomy.com to share your files?
And whatever else you can think of, it probably
**can** be done.

It's very easy to extend
------------------------

Really. It's simple python code.

* The module to do syntax highlighting has 41 lines.

* The module to do dynamic animated menus has 103.

* The module to do calendars has 72.

If there is a python module or web service to do what you
want, hooking it into BartleBlog is simple.

And it has kickass features
---------------------------

Like online, embedded, animated slideshows! Like this one!
Done with 65 lines of simple almost-plain-text markup!
Ok, it's not fully implemented yet, because it needs some manual
code, but the hard part is done!

Or automatic SVN changelog display ( I admit that's *somewhat niche* ;-))

Now, who else has that kind of thing?

Now that the back­end is still iffy but gen­er­ates a blog, I fi­nal­ly start­ed show­ing some love to the UI.

Here's the brand new post ed­i­tor:

The far-right two but­tons should let you choose your flickr pho­to/openo­my file re­spec­tive­ly and add the link/thumb­nail eas­i­ly (the UI is not done yet).

The for­mat to write is Re­struc­tured Text or HTML (non wysi­wyg) but oth­er things like Tex­tile or wi­ki markup should be easy to ad­d.

The main win­dow us­es a Qt mod­el to cre­ate the tree with views (right now) by date, but with al­ter­na­tive or­ga­ni­za­tions soon.

A lot of new fea­tures go­ing on, like openo­my based file up­load­ing and links that work like sim­ple rst di­rec­tives:

.. openomy:: my-file.ext

And you should get a link to the file, stored in the 1GB the openo­my guys kind­ly pro­vide.

Al­so, you can ac­tu­al­ly see how the test site looks at //ralsi­na.me/we­blog (us­ing the ex­act same da­ta as this one).

I ac­tu­al­ly up­load al­most ev­ery change I do, so it breaks of­ten ;-)