Allen Gilliland wrote:
> I think all of these sound interesting and I definitely think you should
> write up proposals for them so we can talk about them more. A couple
> specific comments inline below ...
>
> [snip]
> This is definitely an idea we would be interested in, but out of
> curiosity, why wouldn't a rating be a direct attribute of an entry
> rather than an association? It seems that way you wouldn't need a new
> table, just a new column.
>
The rating table tracks each rating per user and the time of the rating.
create table roller_weblogentry_rating (
entryid varchar(48) not null,
userid varchar(48) not null,
ratetime timestamp not null default current timestamp,
rating smallint not null default 0,
primary key (entryid,userid)
);
This allows us to easily track the number of ratings for an entry, allow
users to modify their ratings, ensure that users cannot game the system
by rating an entry more than once, etc.
> The other thing is the RatingServlet. If the purpose of that servlet is
> to return some kind of computer consumable output then I think the
> better approach would be to create something like a JsonServlet and make
> part of that servlet capable of getting entries by rating. I know that
> one of the things I definitely think we should add to Roller is some
> ways to make weblog content come out in more formats than just html &
> xml (atom & rss). So if we had a JsonServlet which allowed you to get
> at all the normal data about a weblog directly then that would fulfill
> this need and provide more options to Roller users/developers who want
> to create more tools for weblogs using ajax. i.e. something like ...
>
Yes, this is good. Let me stew on this a bit more and see if I can come
up with something good.
> [snip]
> Sounds good, but is the real purpose of this to go on the homepage or
> somewhere in the authoring UI? since you are required to be logged in
> it seems like this could just be in the authoring UI and displayed on
> (or just off of) the main menu when you login.
>
In our implementation it sits just off the home page. We have a tabbed
interface where one of the options is "My Activity". The way it is
implemented, it could appear either in the authoring UI or homepage theme.
> [snip]
>>
>> Proposal 5: Language Filtering
>>
>> This has not yet been implemented, but we would like the ability to
>> filtering the home page listing of entries by language.
>
> this should already be working, if you go to /<frontpage blog>/<lang> it
> should return entries from just that language.
>
>
Ok, I missed that completely. Thanks.
>>
>> Proposal 6: Atom Threading Extensions support
>>
>> We have added support for the Atom Threading Extensions (RFC 4685)
>> to the Atom feeds produced (entry and comment feeds)
>>
>> Proposal 7: Atom Bidi Attribute support
>>
>> We have added support for the draft Atom Bidi Attribute specification
>> for entries that are marked as "Right-to-Left"... e.g.,
>>
>> <entry dir="rtl">
>> ...
>> </entry>
>>
>> That's it for now. For most of these, we would need to execute a code
>> grant. Before I start that process, however, I need to know if y'all
>> are interested in these.
>
> That's a lot of proposals, are you really going to try doing all of them
> for 4.0? The best thing is probably to just pick the ones you feel sure
> you'll be able to complete in the next month or so and focus on those.
>
Not necessarily for 4.0. Things like the threading extension and bidi
support are very easy. I can submit patches for those for 4.0 quite easily.
Most of this has already been implemented but, like the RatingServlet,
can likely be implemented better. It is not likely that all these can
get done in time for the 4.0 release.
- James
