Added a Ya­hoo! Ui menubar gen­er­a­tor. It turns this:

a
b
c
 1
 2
  x
  y
d

In­to this:

Or this if you are us­ing links:

Or rather in­to this, which ex­plains why it's nec­es­sary (con­sid­er this is a very sim­ple menu!):

<script type="text/javascript">
YAHOO.example.onMenuBarReady = function(p_oEvent)
{
    // Instantiate and render the menu bar

    var oMenuBar = new YAHOO.widget.MenuBar("None",
        {   autosubmenudisplay:true,
            hidedelay:750,
            lazyload:true
        });

    oMenuBar.render();
}

// Initialize and render the menu bar when it is available in the DOM
YAHOO.util.Event.onContentReady("None", YAHOO.example.onMenuBarReady);
</script>
        <div id="None" class="yuimenubar">
            <div class="bd">
                <ul class="first-of-type">
                    <li class="yuimenubaritem first-of-type">a </li>
                    <li class="yuimenubaritem">b</li>
                    <li class="yuimenubaritem"> c
                        <div id="c" class="yuimenu">
                            <div class="bd">
                                <ul>
                                    <li class="yuimenuitem"> 1</li>
                                    <li class="yuimenuitem"> 2
                                        <div id=" 2" class="yuimenu">
                                            <div class="bd">
                                                <ul class="first-of-type">
                                    <li class="yuimenuitem">  x</li>
                                    <li class="yuimenuitem">  y</li>
                                                </ul>
                                            </div>
                                        </div>
                                    </li>
                                </ul>
                            </div>
                        </div>
                    </li>
                    <li class="yuimenubaritem">d</li>
                </ul>
            </div>
        </div>

Still some miss­ing fea­tures, but a neat thingie al­ready.

An­oth­er morn­ing, an­oth­er fea­ture: ar­chive

Now I'm work­ing on the im­age tool, im­port­ing PyD­S's im­ages and up­load­ing to flick­r, etc.

A cou­ple more hours of hack­ing, and the tem­plates are all new, and more func­tion­al then ev­er.

I am mak­ing heavy use of Ya­hoo's UI li­brary, which makes lots of things much sim­pler:

• Lay­out us­ing Ya­hoo Grids

  I spent hours mak­ing the lay­out you see now, and the one with Grids works bet­ter and was done in min­utes. Avoid rein­ven­t­ing the wheel works for we­b­­pages, too.

• Cal­en­­dar us­ing Ya­hoo Cal­en­­dar

  Is­n't it neat? And it work­s, too. Since the link­ing is han­­dled by javascript I may make it so it loads the posts for a month with­­out reload­­ing the page.

• Styling us­ing their re­set.c­ss stylesheet.

  That stylesheet re­­moves all styling from your page. That way, if there's some­thing there, you put it.

  I used that, added a slight­­ly sim­­pli­­fied stylesheet based on Fire­­fox's de­­fault, Re­struc­­tured Tex­t's and Sil­ver­ci­­ty's, and all the cus­­tomiz­ing I need­ed to do to achieve a sim­­ple but func­­tion­al lay­out were 30 lines of CSS, com­­pared to the rather mon­strous py­d­s.c­ss my blog cur­ren­t­­ly us­es.

• Mod­­u­lar thin­­gies.

  I turned all Tech­no­rati/HaloScan/Feed­Burn­er/Talkr thin­­gies in­­­to macros that take as con­­fig­u­ra­­tion your per­­son­al da­­ta (for ex­am­­ple, HaloScan ID) and if nec­es­sary a post.

If the styling was a lit­tle more done and a few bugs were ironed, I may even start up­load­ing the site us­ing bartle­blog in­stead of PyDS soon :-)

I have been post­ing this blog us­ing PyDS for over 4 years now. Sad­ly, the PyDS au­thor seems to have aban­doned it. Which is sad, be­cause it's nifty soft­ware.

How­ev­er, keep­ing it work­ing is get­ting hard­er ev­ery year, and I don't ex­pect to be able to do it soon.

Al­so, the da­ta is in a Metak­it database, which is the most an­noy­ing DB ev­er (no re­al schema! colum­nar in­stead of record ori­ent­ed! gouge my eyes with a bread­stick­!)

So, since I have all the data, and my blog­ging needs are mod­est, and no tool does ex­act­ly what I wan­t, I de­cid­ed to write my own.

I could make it a web ap­p, maybe us­ing Tur­bo­Gears, but what the heck, I haven't done a de­cent GUI app in ... ok, ar­guably, I nev­er have done a de­cent one, and my PyQt4 needs some work, and I am kin­da in a groove for ac­tu­al­ly fin­ish­ing things late­ly (I am rather proud of RaSPF).

And I have a neat name (Bartle­Blog) re­served from an­oth­er abort­ed ap­p.

So, here's the manda­to­ry screen­shot af­ter a cou­ple hours hack­ing:

And here are the goal­s:

• Gen­er­ate stat­ic pages, so it can be used by any­one with a lit­­tle web space (I am a gip­sy)

• Sim­­ple tem­­plat­ing (Us­ing cher­ry­tem­­plate right now, but should be mod­­u­lar)

• Re­struc­­tured Text as in­­put mech­a­nism (a­­gain, mod­­u­lar)

• Good sup­­port for code snip­pets

• Should sup­­port stat­ic pages (like the ones I have in the Sto­ries link)

• In­­te­­grate with Flickr for im­ages

• In­­te­­grate "chunks" in the tem­­plat­ing, where you can do things like set­t­ing the right Haloscan com­­men­t/­­track­­back links eas­i­­ly

• Sim­­ple cat­e­­go­ry mech­a­nis­m, with a reg­ex­p-based au­­to­­tag­ger with­­out cre­at­ing per-­­cat­e­­go­ry copies of ev­ery­thing.

• RSS feed gen­er­a­­tion, glob­al and per-­­cat­e­­go­ry.

• A way to im­­port all my PyDS blog (and maybe my old­er ad­vo­ga­­to things)

• Use sqlite and SQLOb­­ject for sane stor­age.

So far, it's do­ing some things, I can im­port, ed­it, save (by in­stant ap­pli­ca­tion, there is no "save" here).

I can't yet gen­er­ate the site, or cre­ate a new post, and it should take months to make it use­ful, but let's see how it goes.

And you, read­er­s, if you want a slow, not ful­ly func­tion­al PyQt based ad­voga­to (and oth­er blogs) ed­i­tor, then you can use it too, just search for bartle­blog in sf.net.

Now, if I im­ple­ment­ed caching, and cor­rect date for­mat­ting, and a de­cent HTML edit­ing in­ter­face, this could even be a de­cent ap­p.