[geeklog-devel] 1.3.10 to do list

[Vincent Furia]

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
>