[geeklog-devtalk] geeklog-devel digest, Vol 1 #356 - 4 msgs

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. 1.3.10 to do list (Dirk Haun)
   2. Re: 1.3.10 to do list (Tony Bibbs)
   3. Re: 1.3.10 to do list (Blaine Lang)
   4. Re: 1.3.10 to do list (Blaine Lang)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Mon, 26 Jul 2004 17:58:51 +0200
Organization: Terra Software Systems
Subject: [geeklog-devel] 1.3.10 to do list
Reply-To: geeklog-devel at lists.geeklog.net

Okay, I think I have pretty much implemented everything that I wanted to
go into 1.3.10. Now it's on to the usual stuff (bug fixes, documentation
and language file updates, testing, ...).

Not sure if I'll have a go at the Admin Toolbox we've talked about or
leave it for the next version. I may give it a try if I have a mood swing
or something ...

Then there are a few other open issues:

Inclusion of the SpamX plugin - what's the status here? We probably need
a new plugin API function so that plugins can filter or reject comments
before they will be saved. Also, a method to make it easier to package
plugins with Geeklog would be nice, e.g. by making the install script
read the SQL for the plugin from some predefined directory (if we do
that, it also needs to be able to handle plugin updates).

Vinny, you wanted to do some work on the comment bar. What's the status /
plan here?

PDF: Currently, the PDF-related files all produce XHTML, which is
inconsistent with the rest of Geeklog which produces plain ol' HTML. From
the documentation, the PDF add-on doesn't understand XHTML either (but
only HTML 3.2), so I don't see the need for this. Tony? Anything else
that needs to be done on the PDF support?

A few features have been mentioned in the past as being possibly ready to
go into the next release. Most notably spell checking and archiving of
old stories. Tony, Blaine - any updates?

Anything else?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.tinyweb.de/


--__--__--

Message: 2
Date: Mon, 26 Jul 2004 11:51:00 -0500
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] 1.3.10 to do list
Reply-To: geeklog-devel at lists.geeklog.net



Dirk Haun wrote:


>Inclusion of the SpamX plugin - what's the status here? We probably need

>a new plugin API function so that plugins can filter or reject comments

>before they will be saved. Also, a method to make it easier to package

>plugins with Geeklog would be nice, e.g. by making the install script

>read the SQL for the plugin from some predefined directory (if we do

>that, it also needs to be able to handle plugin updates).

>  

>

I say add something like the following:
PLG_preSaveComment_<pluginName>
PLG_postSaveComment_<pluginName>
PLG_preSaveStory_<pluginName>
PLG_postSaveStory_<pluginName>

The first one is the one we needed the most.  I figured adding a 
postSaveComment would complete the cycle, though, I can't think of an 
immediate use for it now.  I also added the two story-related methods as 
I don't think it would be a stretch to think someone may want those at 
some point.  Just a suggestion...we can simply add the one and worry 
about the rest as needed...I just figured we might try being a bit more 
proactive by adding a few more.


>PDF: Currently, the PDF-related files all produce XHTML, which is

>inconsistent with the rest of Geeklog which produces plain ol' HTML. From

>the documentation, the PDF add-on doesn't understand XHTML either (but

>only HTML 3.2), so I don't see the need for this. Tony? Anything else

>that needs to be done on the PDF support?

>  

>

Agreed, I misunderstood that much.  With that, nothing else is really 
needed then.


>A few features have been mentioned in the past as being possibly ready to

>go into the next release. Most notably spell checking and archiving of

>old stories. Tony, Blaine - any updates?

>  

>

Count the spellchecker out.  I've dusted it off and have a few fairly 
big bugs that will take some time...not worth holding off the .10 release.

--Tony

--__--__--

Message: 3
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] 1.3.10 to do list
Date: Mon, 26 Jul 2004 12:57:41 -0400
Reply-To: geeklog-devel at lists.geeklog.net

I would like to add the Story Archive and can do so this week.
- Option to set a date where the story will be moved to a "defined" archive
topic or delete automatically.
- It's also possible to use a new set of template files for the archive
topic

I also have a similar feature for Blocks - where you can set the show until
time then it gets disabled.

Another item I have is a change to the advanced search results. I just need
to complete a bit more testing on that one.
I will aim for this week as well to get that in.

Blaine
----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 11:58 AM
Subject: [geeklog-devel] 1.3.10 to do list


Okay, I think I have pretty much implemented everything that I wanted to
go into 1.3.10. Now it's on to the usual stuff (bug fixes, documentation
and language file updates, testing, ...).

Not sure if I'll have a go at the Admin Toolbox we've talked about or
leave it for the next version. I may give it a try if I have a mood swing
or something ...

Then there are a few other open issues:

Inclusion of the SpamX plugin - what's the status here? We probably need
a new plugin API function so that plugins can filter or reject comments
before they will be saved. Also, a method to make it easier to package
plugins with Geeklog would be nice, e.g. by making the install script
read the SQL for the plugin from some predefined directory (if we do
that, it also needs to be able to handle plugin updates).

Vinny, you wanted to do some work on the comment bar. What's the status /
plan here?

PDF: Currently, the PDF-related files all produce XHTML, which is
inconsistent with the rest of Geeklog which produces plain ol' HTML. From
the documentation, the PDF add-on doesn't understand XHTML either (but
only HTML 3.2), so I don't see the need for this. Tony? Anything else
that needs to be done on the PDF support?

A few features have been mentioned in the past as being possibly ready to
go into the next release. Most notably spell checking and archiving of
old stories. Tony, Blaine - any updates?

Anything else?

bye, Dirk


-- 
http://www.haun-online.de/
http://www.tinyweb.de/

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


--__--__--

Message: 4
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] 1.3.10 to do list
Date: Mon, 26 Jul 2004 12:58:38 -0400
Reply-To: geeklog-devel at lists.geeklog.net

I say add something like the following:
PLG_preSaveComment_<pluginName>
PLG_postSaveComment_<pluginName>
PLG_preSaveStory_<pluginName>
PLG_postSaveStory_<pluginName>

I like these API's as it would be a good way to add any custom tags that may
provide advanced formatting control.

Blaine
----- Original Message ----- 
From: "Tony Bibbs" <tony at tonybibbs.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Monday, July 26, 2004 12:51 PM
Subject: Re: [geeklog-devel] 1.3.10 to do list




Dirk Haun wrote:


>Inclusion of the SpamX plugin - what's the status here? We probably need

>a new plugin API function so that plugins can filter or reject comments

>before they will be saved. Also, a method to make it easier to package

>plugins with Geeklog would be nice, e.g. by making the install script

>read the SQL for the plugin from some predefined directory (if we do

>that, it also needs to be able to handle plugin updates).

>

>

I say add something like the following:
PLG_preSaveComment_<pluginName>
PLG_postSaveComment_<pluginName>
PLG_preSaveStory_<pluginName>
PLG_postSaveStory_<pluginName>

The first one is the one we needed the most.  I figured adding a
postSaveComment would complete the cycle, though, I can't think of an
immediate use for it now.  I also added the two story-related methods as
I don't think it would be a stretch to think someone may want those at
some point.  Just a suggestion...we can simply add the one and worry
about the rest as needed...I just figured we might try being a bit more
proactive by adding a few more.


>PDF: Currently, the PDF-related files all produce XHTML, which is

>inconsistent with the rest of Geeklog which produces plain ol' HTML. From

>the documentation, the PDF add-on doesn't understand XHTML either (but

>only HTML 3.2), so I don't see the need for this. Tony? Anything else

>that needs to be done on the PDF support?

>

>

Agreed, I misunderstood that much.  With that, nothing else is really
needed then.


>A few features have been mentioned in the past as being possibly ready to

>go into the next release. Most notably spell checking and archiving of

>old stories. Tony, Blaine - any updates?

>

>

Count the spellchecker out.  I've dusted it off and have a few fairly
big bugs that will take some time...not worth holding off the .10 release.

--Tony
_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel



--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


End of geeklog-devel Digest