[geeklog-devtalk] geeklog-devel digest, Vol 1 #357 - 5 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. Re: 1.3.10 to do list (Vincent Furia)
   2. Re: 1.3.10 to do list (Tom Willett)
   3. Re: 1.3.10 to do list (Tony Bibbs)
   4. Re: 1.3.10 to do list (Dirk Haun)
   5. Re: 1.3.10 to do list (Tony Bibbs)

--__--__--

Message: 1
Date: Mon, 26 Jul 2004 13:00:55 -0400
From: Vincent Furia <vfuria at gmail.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

I've just started work on the comment bar.  I still need to work on
design and dig a bit into the code before I know how much work it will
take.  This is a pretty low priority, and only important from an
ascetics perspective when viewing comments from comment.php.  I would
not cry if this got pushed off to a later release.

Here is a list of things that we had discussed or I made up (some
going back pretty far) as things to consider for 1.3.10:
* Improve search engine speed
* Improve general performance (read: reduce page generation time)
* Clean up usage of $_GROUPS, $_RIGHTS
   - basically these aren't' being used consistently, I have an idea
to clean this up, but at this point it should probably be pushed back
to the next release.
* Replace use of $topicsql with COM_getTopicSQL (a new function by Dirk)
   - Many places in geekog generate "topic sql" for topic permissions.
 From a maintainability perspective using Dirk's function is much
better.  Again, this can (and probably should) be pushed off a release
* Fix the comment bar
   - In work, see note above

Also, if people could spend some time testing the new comment system
to make sure there aren't any bugs.  Also, test the upload script and
make sure it doesn't take a ridiculous amount of time.

Also, if anyone can install 1.3.9 and the current cvs side by side and
do some performance comparisons it would be appreciated.  I'm curious
as to how big a performance difference some of the optimizations I
made (quite a while ago now) has caused.

I think that's it for me,
Vinny

On Mon, 26 Jul 2004 17:58:51 +0200, Dirk Haun <dirk at haun-online.de> wrote:

> 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: 2
From: "Tom Willett" <tomw at pigstye.net>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] 1.3.10 to do list
Date: Mon, 26 Jul 2004 20:33:00 +0000
Reply-To: geeklog-devel at lists.geeklog.net

I was supposed to change the spamx plugin to use sql tables rather than 
files.  I am almost done with that and will get it to Tony in the next 
couple of days.

--
Tom Willett
tomw at pigstye.net

---------- Original Message -----------
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Sent: Mon, 26 Jul 2004 11:51:00 -0500
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

------- End of Original Message -------


--__--__--

Message: 3
Date: Mon, 26 Jul 2004 15:45:24 -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

I'll get it in as soon as I get it.

--Tony

Tom Willett wrote:


>I was supposed to change the spamx plugin to use sql tables rather than 

>files.  I am almost done with that and will get it to Tony in the next 

>couple of days.

>

>--

>Tom Willett

>tomw at pigstye.net

>

>---------- Original Message -----------

>From: Tony Bibbs <tony at tonybibbs.com>

>To: geeklog-devel at lists.geeklog.net

>Sent: Mon, 26 Jul 2004 11:51:00 -0500

>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

>>    

>>

>------- End of Original Message -------

>

>_______________________________________________

>geeklog-devel mailing list

>geeklog-devel at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devel

>  

>


--__--__--

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

Tony,

just noticed that the PDF conversion isn't even listed in the changelog
yet. Could you add a word or two, please?

Also, do we need some additional documentation for this? I guess the
various settings (like TTL, Tidy support, ...) aren't always too obvious
and could benefit from some explanations.

bye, Dirk


-- 
http://www.haun-online.de/
http://geeklog.info/


--__--__--

Message: 5
Date: Mon, 26 Jul 2004 16:23:54 -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

Sure, will do.  Give me a few days.

--Tony

Dirk Haun wrote:


>Tony,

>

>just noticed that the PDF conversion isn't even listed in the changelog

>yet. Could you add a word or two, please?

>

>Also, do we need some additional documentation for this? I guess the

>various settings (like TTL, Tidy support, ...) aren't always too obvious

>and could benefit from some explanations.

>

>bye, Dirk

>

>

>  

>



--__--__--

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


End of geeklog-devel Digest