phpblosxom-devel

[Phpblosxom-devel] Introduction, offer, and need advice

[Jim N. <ji...@xm...>]

Hi, all

I've been working with blosxom (2.0) for a while, and am fairly familiar
with the concepts. I run a few MovableType sites as well, so I have a pretty
good understanding of that.

My "day job" involves coding in Java, Perl and PHP.

I'm giving up on blosxom largely because I can't get mod_rewrite to work
correctly with my ISP, and I'd rather have /index.php/foo than
/cgi-bin/blosxom.cgi/foo in my URLs.


For php-blosxom to be useful to me, I need the following:

- support for meta-creation-date: <date> fields in the "header" of posts.
From what I see, getting this to work will involve patching php-blosxom to
place the logic for sorting entries by date AFTER the "raw_entry" callback
is invoked, unless there's some way for a plugin providing that callback to
manipulate the list of dates.

- A port of textile2. Most of my site is done with textile.

In good ADHD style, since these are essential, I've chosen to begin my work
on something else. :) That is this: I want to add support for blosxom themes
(a la the themes plugin) that will let us keep all of the theme HTML
elements in a single file. (it makes them easier to edit and deploy).

I'd also like to work on getting the category plugin to produce a variety of
category trees (vertical, indented, maybe even javascript-menu style).

= Jim

-- 

Re: [Phpblosxom-devel] Introduction, offer, and need advice

[Magnus N. <ma...@no...>]

Jim Nicholson wrote:

>Hi, all
>
>I've been working with blosxom (2.0) for a while, and am fairly familiar
>with the concepts. I run a few MovableType sites as well, so I have a pretty
>good understanding of that.
>
>My "day job" involves coding in Java, Perl and PHP.
>
>I'm giving up on blosxom largely because I can't get mod_rewrite to work
>correctly with my ISP, and I'd rather have /index.php/foo than
>/cgi-bin/blosxom.cgi/foo in my URLs.
>
>
>For php-blosxom to be useful to me, I need the following:
>
>- support for meta-creation-date: <date> fields in the "header" of posts.
>From what I see, getting this to work will involve patching php-blosxom to
>place the logic for sorting entries by date AFTER the "raw_entry" callback
>is invoked, unless there's some way for a plugin providing that callback to
>manipulate the list of dates.
>
>- A port of textile2. Most of my site is done with textile.
>
>In good ADHD style, since these are essential, I've chosen to begin my work
>on something else. :) That is this: I want to add support for blosxom themes
>(a la the themes plugin) that will let us keep all of the theme HTML
>elements in a single file. (it makes them easier to edit and deploy).
>
>I'd also like to work on getting the category plugin to produce a variety of
>category trees (vertical, indented, maybe even javascript-menu style).
>
>= Jim
>
>  
>
Hi,
I'm not really sure what it is that you want, however I will give some 
comments on the things that you have listed.

- support for meta-creation-date

Why do you need that? You could alter the real creation date with the 
UNIX-command touch. There will be support to change the dates using the 
upcoming webadmin plugin.

- A port of textile2.

 From what I've seen it looks like a standard postformatter, shouldn't 
be too hard to implement.

The category plugin right now is quite a bit short handed.
Any work on that is appreciated.

There is much going on right now.

Currently making is
- An installation script.
- A web based administrative tool.
- Support for trackback
- Support for XML-RPC
- Support for RSS and Atom-feeds.

New in version 0.2 (which is not yet released) is that all modules will 
be, not required to, but encoraged to register themselves, and which 
configuration-keys they use in a $moduleinfo-array. This will be used to 
enable web based configuration of the modules.

Look at for example comments.module in the CVS.

Since you didn't really ask any questions, I can't really answer any :)

Magnus Nordlander

Re: [Phpblosxom-devel] Introduction, offer, and need advice

[Jim N. <ji...@xm...>]

On 8/27/04 10:28 AM, "Magnus Nordlander" <ma...@no...> wrote:

> Hi,
> I'm not really sure what it is that you want, however I will give some
> comments on the things that you have listed.
> 
> - support for meta-creation-date
> 
> Why do you need that? You could alter the real creation date with the
> UNIX-command touch. There will be support to change the dates using the
> upcoming webadmin plugin.
> 

The main reason is because my existing blosxom setup uses meta dates instead
of file systems dates. There are several reasons for this, not in any
particular order:

=  if my ISP fails, and I have to restore the blog somewhere else, my
current backup strategy doesn't have accurate file creation dates on the
backup copies of posts, so all the posts would show up on the day they were
restored rather than the day they were entered.

= philosophically, I consider an edit to an existing document to be an edit,
and don't want date-based permalinks to break just because I go in and edit
a file and forget to touch the date back to where it was.

= My blosxom blogs are seeded by a perl script that converts MT export files
into blosxom posts. That script currently sets meta-creation-date rather
than touching the output file.

= Jim

> - A port of textile2.
> 
>  From what I've seen it looks like a standard postformatter, shouldn't
> be too hard to implement.
> 
> The category plugin right now is quite a bit short handed.
> Any work on that is appreciated.
> 
> There is much going on right now.
> 
> Currently making is
> - An installation script.
> - A web based administrative tool.
> - Support for trackback
> - Support for XML-RPC
> - Support for RSS and Atom-feeds.
> 
> New in version 0.2 (which is not yet released) is that all modules will
> be, not required to, but encoraged to register themselves, and which
> configuration-keys they use in a $moduleinfo-array. This will be used to
> enable web based configuration of the modules.
> 
> Look at for example comments.module in the CVS.
> 
> Since you didn't really ask any questions, I can't really answer any :)
> 
> Magnus Nordlander
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Phpblosxom-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpblosxom-devel

-- 

Re: [Phpblosxom-devel] Introduction, offer, and need advice

[Magnus N. <ma...@no...>]

Jim Nicholson wrote:

>
>On 8/27/04 10:28 AM, "Magnus Nordlander" <ma...@no...> wrote:
>
>  
>
>>Hi,
>>I'm not really sure what it is that you want, however I will give some
>>comments on the things that you have listed.
>>
>>- support for meta-creation-date
>>
>>Why do you need that? You could alter the real creation date with the
>>UNIX-command touch. There will be support to change the dates using the
>>upcoming webadmin plugin.
>>
>>    
>>
>
>The main reason is because my existing blosxom setup uses meta dates instead
>of file systems dates. There are several reasons for this, not in any
>particular order:
>
>=  if my ISP fails, and I have to restore the blog somewhere else, my
>current backup strategy doesn't have accurate file creation dates on the
>backup copies of posts, so all the posts would show up on the day they were
>restored rather than the day they were entered.
>
>= philosophically, I consider an edit to an existing document to be an edit,
>and don't want date-based permalinks to break just because I go in and edit
>a file and forget to touch the date back to where it was.
>
>= My blosxom blogs are seeded by a perl script that converts MT export files
>into blosxom posts. That script currently sets meta-creation-date rather
>than touching the output file.
>
>= Jim
>
>  
>
>>- A port of textile2.
>>
>> From what I've seen it looks like a standard postformatter, shouldn't
>>be too hard to implement.
>>
>>The category plugin right now is quite a bit short handed.
>>Any work on that is appreciated.
>>
>>There is much going on right now.
>>
>>Currently making is
>>- An installation script.
>>- A web based administrative tool.
>>- Support for trackback
>>- Support for XML-RPC
>>- Support for RSS and Atom-feeds.
>>
>>New in version 0.2 (which is not yet released) is that all modules will
>>be, not required to, but encoraged to register themselves, and which
>>configuration-keys they use in a $moduleinfo-array. This will be used to
>>enable web based configuration of the modules.
>>
>>Look at for example comments.module in the CVS.
>>
>>Since you didn't really ask any questions, I can't really answer any :)
>>
>>Magnus Nordlander
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
>>100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
>>Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
>>http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
>>_______________________________________________
>>Phpblosxom-devel mailing list
>>Php...@li...
>>https://lists.sourceforge.net/lists/listinfo/phpblosxom-devel
>>    
>>
>
>  
>
OK, I see how this could be useful. If the aquisition of the mtime is 
done with a module overrideable user-function it wouldn't be to hard to 
make what you want possible, would it?

Magnus Nordlander

Re: [Phpblosxom-devel] Introduction, offer, and need advice

[Jim N. <ji...@xm...>]

On 8/27/04 11:49 AM, "Magnus Nordlander" <ma...@no...> wrote:

>> [long discussion of why Jim wants meta-creation-date deleted to save
>> bandwidth..]
>>=20
>>  =20
> OK, I see how this could be useful. If the aquisition of the mtime is don=
e
> with a module overrideable user-function it wouldn't be to hard to make w=
hat
> you want possible, would it?
>=20
> Magnus Nordlander
>=20
That would do it for creation date. On the other hand, consider this: Befor=
e
the rawentries call back is invoked, a number of variables exist that
contain the post content and the =B3metadata=B2 for that post =AD the title, the
date, the post pathinfo (the path to the source of the article) etc. If it
were (or maybe =B3is=B2; my php scoping knowledge is rusty) possible to overrid=
e
the values of any of those variables from within the rawentry callback, the=
n
(presumably) any number of extensions could be implemented. Some general
ideas might include:
>=20
* over-riding the display of the article on the main blog index page to onl=
y
include the first paragraph, or the article up to a specific flag within th=
e
article, as the =B3seemore=B2 plugin does for blosxom.
* completely overriding the format specifications for a post file, so that
an entirely different post format could be used to store data. One might
would use this, for example, to write certain posts as XML documents, with
fields for the =B3category=B2, =B3title=B2, =B3publication date=B2, =B3abstract=B2, and
=B3content=B2.=20
* Less ambitiously, implementing something like =B3macro=B2 tags within a post,
so that frequently used markup can be easily entered. (for example, on my
blog I use this to change things in posts like
>>  <media type=3D=B2mp3=B2 filename=3D=B2foo.mp3=B2>Betty=B9s song</media>
> into markup like
>> <div class=3D=B2media=B2><a href=3D=B2/media/foo.mp3=B2><img src=3D=B2/images/mp3.gif=B2
>> border=3D=B20=B2/>Betty=B9s song</a></div>

I=B9m just thinking out loud here, and haven=B9t thought much of this through,
so if it=B9s chasing moonbeams, just bring me back to earth.

=3D Jim



--=20

Re: [Phpblosxom-devel] Introduction, offer, and need advice

[Magnus N. <ma...@no...>]

Jim Nicholson wrote:

> On 8/27/04 11:49 AM, "Magnus Nordlander" <ma...@no...> wrote:
>
>         [long discussion of why Jim wants meta-creation-date deleted
>         to save bandwidth..]
>
>           
>
>     OK, I see how this could be useful. If the aquisition of the mtime
>     is done with a module overrideable user-function it wouldn't be to
>     hard to make what you want possible, would it?
>
>     Magnus Nordlander
>
> That would do it for creation date. On the other hand, consider this: 
> Before the rawentries call back is invoked, a number of variables 
> exist that contain the post content and the "metadata" for that post - 
> the title, the date, the post pathinfo (the path to the source of the 
> article) etc. If it were (or maybe "is"; my php scoping knowledge is 
> rusty) possible to override the values of any of those variables from 
> within the rawentry callback, then (presumably) any number of 
> extensions could be implemented. Some general ideas might include:
>
>
>     * over-riding the display of the article on the main blog index
>       page to only include the first paragraph, or the article up to a
>       specific flag within the article, as the "seemore" plugin does
>       for blosxom.
>     * completely overriding the format specifications for a post file,
>       so that an entirely different post format could be used to store
>       data. One might would use this, for example, to write certain
>       posts as XML documents, with fields for the "category", "title",
>       "publication date", "abstract", and "content".
>     * Less ambitiously, implementing something like "macro" tags
>       within a post, so that frequently used markup can be easily
>       entered. (for example, on my blog I use this to change things in
>       posts like
>
>         <media type="mp3" filename="foo.mp3">Betty's song</media>
>
>     into markup like
>
>         <div class="media"><a href="/media/foo.mp3"><img
>         src="/images/mp3.gif" border="0"/>Betty's song</a></div>
>
>
> I'm just thinking out loud here, and haven't thought much of this 
> through, so if it's chasing moonbeams, just bring me back to earth.
>
> = Jim
>
>
>
> -- 
>
/me gets his lasso and brings Jim back to earth :P

Those things are already possible using post-formatters.

The only reason date needs to be treated separatly, is because posts get 
sorted and selected by date.

Magnus Nordlander