[geeklog-devtalk] geeklog-devel digest, Vol 1 #320 - 2 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. Comment Links (Vincent Furia)
   2. Geeklog on PHP-Magazin-CD (Dirk Haun)

--__--__--

Message: 1
Date: Thu, 20 May 2004 14:56:15 -0400
From: Vincent Furia <vmf at abtech.org>
To: geeklog-devel at lists.geeklog.net
Subject: [geeklog-devel] Comment Links
Reply-To: geeklog-devel at lists.geeklog.net

I've just submitted to CVS a method to link to comments directly.  You 
can link to a comment directly by:

<site_url>/comments.php?mode=view&cid=<commentid>

There are still some issues to work out.

Currently it is set up to display the comment specified by <commentid> 
and its children (if any and when not in flat comment mode).  This 
brings up a question:

1.  How should the comment default mode be determined.  Right now I have 
  it that you can add an optional parameter to the url 
format=<commentmode> (where commentmode one of: threaded, nested, flat) 
and a default to threaded.

Should a user's preferences be used?  Should the site default be used? 
I'm not sure all the purposes this linking will be used for so I'm not 
sure what a good default (or way of determining default) would be.


The comment bar really sucks for the display of comments like this.  Any 
changes made to options using the comment bar pushes you back to 
article.php.  So...

2.  Should we overhaul the comment bar, remove it when displaying a 
direct link to a comment, or remove it for all uses in comment.php (i.e. 
linking to pid's using mode=display as well)?


One last thing to think about.  What template variables should we add 
now that this is available.  One obvious variable is adding a 
{permalink} to the comment.thtml.  Another is adding a link to the 
comment for Dirk's reporting of comment abuse.  Any others?  Note: I 
haven't added any yet (not even the obvious ones).

In any case I'm not sure how much time I'll have to work on this in the 
next week.  I have some big chores to take care of around the house and 
then I have to travel for business.  Once I'm back I'll try to fix up 
these problems taking into account any feedback.

-Vinny

--__--__--

Message: 2
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Thu, 20 May 2004 22:18:19 +0200
Organization: Terra Software Systems
Subject: [geeklog-devel] Geeklog on PHP-Magazin-CD
Reply-To: geeklog-devel at lists.geeklog.net

I almost forgot ...

The current edition of the German PHP Magazin, <http://www.phpmag.de/>,
features a "market overview" of 80 CMS, including Geeklog. 30 of those
CMS are on the CD that's included with the magazine. Again, Geeklog 1.3.9
is one of them.

The interesting bit is that I forgot to ask them to include it on the CD

:-) They sent a reminder to update the entry for the online version of

that "market overview", <http://www.phpmag.de/cms/>, which I did. Listing
groklaw.net as a reference site may have helped a bit here ...

bye, Dirk


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



--__--__--

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


End of geeklog-devel Digest