Zine

Re: Plugin DB: Progress Update

From:

LeafStorm

Date:

2010-01-19 @ 17:35

Subject:

Re: Plugin DB: Progress Update

On Tue, Jan 19, 2010 at 1:41 PM, Armin Ronacher
<armin.ronacher@active-4.com> wrote:
> Haven't had the time to review that in detail, but I noticed the syntax
> for the categories.txt file.  Could you use the same syntax as
> metadata.txt for the i18n support?
>
> Eg:
>
>  [themes]
>  title: Themes
>  description: Change the appearance of your blog.
>  title[de]: Titel
>  description[de]: Ändere die Darstellung deines Blogs.
>  title[ru]: Тема
>  description[ru]: Изменить appereance вашего сайта

The main reason I wrote a custom format is because the metadata.txt
syntax was not particularly suited for having multiple entries with
separate metadata in the file. (The "[themes]" isn't in the standard
metadata.txt file - I would have to have modified the metadata parser
to support it.) The categories.txt does actually support
internationalization - all entries (including the English one) are
prefixed with a language code (though that might have been hard to
tell since the language I used as an example was 1337 sp33k) - so the
categories.txt format is more compact than metadata.txt since it
doesn't (yet) have to deal with arbitrary data fields.

On the subject of categories, I looked at the standard plugins and
drew up a draft listing of plugin categories in the
"resources/categories.txt" file in the repo. Could you check and see
if I got everything (or at least, everything theoretically possible
with current Zine code)? I'm not too fond about the naming of "Post
Helpers" or "Services", or how I judged what constitutes a "Services"
plugin.

-- LeafStorm
"There are 10 types of people in the world - those who understand
binary and those who don't."



On Tue, Jan 19, 2010 at 1:41 PM, Armin Ronacher
<armin.ronacher@active-4.com> wrote:
> Hey,
>
> Am 17.01.2010 21:23, schrieb LeafStorm:
>> The specification I come up that details how I want it to work is on
>> the wiki for the Bitbucket repository at
> Haven't had the time to review that in detail, but I noticed the syntax
> for the categories.txt file.  Could you use the same syntax as
> metadata.txt for the i18n support?
>
> Eg:
>
>  [themes]
>  title: Themes
>  description: Change the appearance of your blog.
>  title[de]: Titel
>  description[de]: Ändere die Darstellung deines Blogs.
>  title[ru]: Тема
>  description[ru]: Изменить appereance вашего сайта
>
> And so forth.
>
>
> Regards,
> Armin
>

Hi,

Am 19.01.2010 18:35, schrieb LeafStorm:
> The main reason I wrote a custom format is because the metadata.txt
> syntax was not particularly suited for having multiple entries with
> separate metadata in the file. (The "[themes]" isn't in the standard
> metadata.txt file - I would have to have modified the metadata parser
> to support it.)
Yes.  I just propose to modify that parser to support sections :)  I
just don't like the idea of having lang:key:value :)


Regards,
Armin

On Tue, Jan 19, 2010 at 4:25 PM, Armin Ronacher
<armin.ronacher@active-4.com> wrote:
> Yes.  I just propose to modify that parser to support sections :)  I
> just don't like the idea of having lang:key:value :)

That is understandable. I thought it looked a bit awkward myself, but
couldn't really come up with anything better. In addition to being
able to add more info to categories later, being able to put multiple
sets of k/v pairs in a metadata.txt may have other uses as well. (One
benefit is that I won't have to maintain another parser and I won't
have to write a custom class to hold the category information in an
internationalized form.) I'll see if I can modify the parser tonight.

-- LeafStorm
"There are 10 types of people in the world - those who understand
binary and those who don't."