Re: [Pyblosxom-devel] Supporting comments, etc.

[Wari W. <wa...@ce...>]

* Blake Winton <bl...@ph...> [030205 00:51]:
> > Responding to some comments from Wari, Our Glorious Leader:

Glorious? :)

> And some day I'll remember to not hold down the Control key when I hit
> enter.  Anyways, what I wanted to say was:
> 1) Does this fulfill all of our needs in terms of storing and
>    retrieving comments/trackbacks/pingbacks/etc?

Yes, it does fulfill all of the above :) It doesn't have a delete() or
modify() though. Think of it this way, if you were to design a webui (or
any UI) for that matter, managing comments, what would you need?

> 2) Is it easy enough to use, or can it be made easier?

A commentID would be nice I guess (makes delete and modify easier).

> 3) Is it reasonable to implement, or nigh impossible?

Not sure until it's done :)

> I think most of the trickyness would come in writing filters.  Oh, and
> there's currently no simple way to sort the data, but if we returned
> the bit of data as a tuple containing the type, and whatever else we
> could parse out, then a sorter would be fairly simple to write.

With a commentID (assuming it's actually a time int() at least) you can
sort them 2 ways, ascending and descending. Unless we're slashdot or
something like that, timestamps would give us a nice unique number
between comments, btw, if you are slashdot, you can use a real data
base, then the commentID can be an integer generated by the database,
you know those autonumber types. Actually, if you are slashdot, you'd be
using threaded discussions :) Comments for blogs does not need to be
threaded (though it can break fluidity in comments).

How about a dump() and load() so that you can migrate between storage
implementations. Though not used by pyblosxom, but could be used by a
utility.

-- 
Regards: Wari Wahab
Senior R&D Engineer
Celestix Networks
http://www.celestix.com/