From dirk at haun-online.de  Mon Jun  1 10:55:43 2009
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 1 Jun 2009 16:55:43 +0200
Subject: [geeklog-devel] Introducing the Plugin Toolkit featuring the
 Plugin Generator
In-Reply-To: <8319e2d60903171150h7763d1b1sfdb1c10ee9663d51@mail.gmail.com>
References: <20090315131635.1808091327@smtp.haun-online.de>
	<db993b420903160245m7c5c90bubfa57d6d012b524d@mail.gmail.com>
	<20090316191152.1753075090@smtp.haun-online.de>
	<8319e2d60903171150h7763d1b1sfdb1c10ee9663d51@mail.gmail.com>
Message-ID: <20090601145543.835609677@smtp.haun-online.de>

Vincent Furia wrote:

>For plugin functions that are "optional" to implement, I'd suggest creating
>them commented out.

Given that we have 60+ plugin API functions[1], I decided against that,
as it would only clutter the functions.inc file. I did pick a few common
ones (search, autotags, menu items), though.

Let me know if you feel some others should be in there, too. But for the
rest, I'd say we should provide sample implementations on the wiki
(eventually - for now I would be happy with functions being documented
in the first place ...).


>This could apply to the SQL file
>too, as not all plugins necessarily have SQL tables.

Creating SQL files is now an option. It generates a dummy table that has
an index and the usual owner_id, etc. fields, but no actual content.

    http://www.geeklog.net/filemgmt/index.php?id=941

bye, Dirk

[1] <http://wiki.geeklog.net/index.php/Plugin_API>


-- 
http://www.geeklog.net/
http://geeklog.info/



From vfuria at gmail.com  Tue Jun  2 00:49:56 2009
From: vfuria at gmail.com (Vincent Furia)
Date: Mon, 1 Jun 2009 22:49:56 -0600
Subject: [geeklog-devel] Fwd: MSSQL Class - SQL Coding
In-Reply-To: <0KKH005N0223AP40@mta2.srv.hcvlny.cv.net>
References: <063B8B70CB9DA141B2FC1DB483561B9F26A956@nex-pluto.nextide.ca>
	<20090530191112.733514496@smtp.haun-online.de>
	<0KKH005N0223AP40@mta2.srv.hcvlny.cv.net>
Message-ID: <8319e2d60906012149g445674a7tadb8935d0a214381@mail.gmail.com>

On Sat, May 30, 2009 at 1:29 PM, Joe Mucchiello <joe at throwingdice.com>wrote:

> Use of the array notation (see above) is recommended instead of checking
>> the content of $_DB_dbms when writing DBMS-specific SQL request.
>>
>
> I still don't like this for one reason. The code for both (and soon all
> three) array values executes but only one of the results is needed. This is
> the other reason I think a set of functions would work better.


I don't think this is going to be as big an issue. While mysql, mssql, and
pgsql (and other dbs as well) all have special notation that can be used, if
we migrate to standard ANSI sql we can use a single query for all the
databases and save ourselves the overhead of writing seperate queries for
each db. I suggested to Stan that as he finds queries that can be done in
ANSI sql shared by all dbs, he should use the ANSI sql and remove the per
datbase arrays.

-Vinny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20090601/07201542/attachment.html>

From joe at ThrowingDice.com  Tue Jun  2 01:51:02 2009
From: joe at ThrowingDice.com (Joe Mucchiello)
Date: Tue, 02 Jun 2009 01:51:02 -0400
Subject: [geeklog-devel] Fwd: MSSQL Class - SQL Coding
In-Reply-To: <8319e2d60906012149g445674a7tadb8935d0a214381@mail.gmail.co m>
References: <063B8B70CB9DA141B2FC1DB483561B9F26A956@nex-pluto.nextide.ca>
	<20090530191112.733514496@smtp.haun-online.de>
	<0KKH005N0223AP40@mta2.srv.hcvlny.cv.net>
	<8319e2d60906012149g445674a7tadb8935d0a214381@mail.gmail.com>
Message-ID: <0KKL00KT8K8AXO60@mta3.srv.hcvlny.cv.net>

At 12:49 AM 6/2/2009, Vincent Furia wrote:
>I don't think this is going to be as big an issue. While mysql, 
>mssql, and pgsql (and other dbs as well) all have special notation 
>that can be used, if we migrate to standard ANSI sql we can use a 
>single query for all the databases and save ourselves the overhead 
>of writing seperate queries for each db. I suggested to Stan that as 
>he finds queries that can be done in ANSI sql shared by all dbs, he 
>should use the ANSI sql and remove the per datbase arrays.

That would be great. But I don't think there are standards for stuff 
like NOW() or UNIXTIME(). That's why I was suggesting creating 
functions to hide that kind of thing:

$sql = 'SELECT id, title, etc, ' . DB_fieldAsTimestamp('created') . ' 
FROM ' . $_TABLES['foo'] . ' WHERE created > ' . DB_now() . ' ORDER 
BY created DESC';

mysql: SELECT id, title, etc, UNIXTIME(created) FROM gl_foo WHERE 
created > NOW() ORDER BY created DESC
mssql: SELECT id, title, etc, DATEDIFF(s, '19700101', created) FROM 
gl_foo WHERE created > GETDATE() ORDER BY created DESC

Although UNIXTIME is a poor example since mysql is just about the 
only database engine that supports it. Still dates are always a 
problem. pgsql and mssql don't handle big text fields like mysql. I'm 
sure mssql users would like to have stories with greater than 4k of 
text. pgsql users will have the same issue.

----
Joe Mucchiello
Throwing Dice Games
http://www.throwingdice.com 



No virus found in this outgoing message
Checked by PC Tools AntiVirus (6.0.0.19 - 10.004.038).
http://www.pctools.com/free-antivirus/


From chopinou at choplair.org  Wed Jun  3 17:06:28 2009
From: chopinou at choplair.org (Choplair)
Date: Wed, 3 Jun 2009 23:06:28 +0200
Subject: [geeklog-devel] Dedicated website for the GSoC OpenID project
Message-ID: <8e35836f0906031406s783b7a91jb89414f5ddd12e75@mail.gmail.com>

Hello.

For the one who don't know, I am Choplair, the student selected to
achieve full OpenID v2.0 library creation and integration into
Geeklog.

This requirement of coding an entire new OpenID implementation in PHP
is the big part of the job, and since being reusable by potential
other interested projects would be a good point, I directly chose to
perform this library's development in an rather independent way.

I thus gave the project a name[1] and opened its own account on Source
Forge, with, in particular, a dedicated website to allow anyone to
follow progress, obtain information, get documentation, and access to
the latest source code in a fast, simple, centralized way.

Here is the address : http://gggoooiiippp.sf.net/

It's a fresh Geeklog install without a lot of content right now, but
I'm gonna add various stuffs during the coming days.

Those stuffs to add includes access to a Mercurial repository.
Indeed, as an old shool addict I've been working with CVS for so long,
but I dived into Mercurial since you selected for your SoC project,
and now I love this system ! So please let me just some time to set up
something nice to put online, and you'll have access to source code.
:)

And I'll "push" my commit on both (mine and Geeklogs's) project's
Mercurial repository at the same time. :)

Hope you are OK with it.

Regards,
Choplair

[1] Which is GGGOOOIIIPPP, standing for "Geeklog GNU GPL Object
Oriented Opend ID Implemention In Pure PHP Project". I know this
acronym looks horrible, but I wanted something different from borry
"PHP OpenID" or "OpenID v2 library". The good points with GGGOOOIIIPPP
is that it's a unique name that help project being easily found using
search engine, and that it's actualy easy to remember : triple G,
triple O, triple I, triple P.
There is also a shorter version "GOIP" for "Geeklog OpenID project"
but such a 4 letter acronym is already used by loads of things.
Anyway, it's just a name, it's not very important ATM and if you
really hate it, renaming it would take some seconds. :p

-- 
                           C H O P L A I R
                           N E T W O R K

  Copyleft Web, Software & Audio/Video Production
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 EMAIL :                  contact AT choplair DOT net
 PHONE / FAX :      +33 (0)9 72 11 44 69
 POST :            Choplair-Network. 2972 Columbia St.
                         Suite # 4557  Torrance, CA 90503
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 NETWORK :                      http://www.choplair.net
 COMMUNICATION :           http://www.choplair.com
 ORGANIZATION :              http://www.choplair.org
 ENTERTAINMENT UNIT :   http://www.choplair.eu
 FORUMS :                         http://www.choplair.fr
 INFORMAL :                      http://www.choplair.info


From dirk at haun-online.de  Sun Jun 14 07:14:21 2009
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 14 Jun 2009 13:14:21 +0200
Subject: [geeklog-devel] Bugtracker update
In-Reply-To: <20081213221825.26073654@smtp.haun-online.de>
References: <20081213221825.26073654@smtp.haun-online.de>
Message-ID: <20090614111421.1709449552@smtp.haun-online.de>

Dirk Haun wrote:

>FYI: I've installed the latest version of Mantis on project.geeklog.net.
>Let me know if there are any problems.

See above :)

bye, Dirk


-- 
http://www.geeklog.net/
http://geeklog.info/



From dirk at haun-online.de  Mon Jun 15 14:47:14 2009
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 15 Jun 2009 20:47:14 +0200
Subject: [geeklog-devel] [geeklog-cvs] geeklog: Added support for Bcc -
	Blind copy.
In-Reply-To: <hg.3b8700815448.1245074926.1485632861@qs1489.pair.com>
References: <hg.3b8700815448.1245074926.1485632861@qs1489.pair.com>
Message-ID: <20090615184714.299668630@smtp.haun-online.de>

geeklog-cvs at lists.geeklog.net wrote:

>details:   http://project.geeklog.net/cgi-bin/hgweb.cgi/rev/3b8700815448
>changeset: 7122:3b8700815448
>user:      blaine Lang <blaine at portalparts.com>
>date:      Mon Jun 15 10:07:53 2009 -0400
>description:
>Added support for Bcc - Blind copy.

Blaine, any objections if we roll back that change and push it to 1.6.1
instead?

I'm somewhat frustrated with the ever-expanding list of optional
parameters on some functions (COM_mail, COM_siteHeader - there may be
more) and would like us to come up with a better solution instead of
creating facts (and at the last minute) that we then have to support for
all eternity ...

bye, Dirk


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



From devel at portalparts.com  Mon Jun 15 15:03:59 2009
From: devel at portalparts.com (Blaine Lang)
Date: Mon, 15 Jun 2009 15:03:59 -0400
Subject: [geeklog-devel] [geeklog-cvs] geeklog: Added support for Bcc
 -	Blind copy.
In-Reply-To: <20090615184714.299668630@smtp.haun-online.de>
References: <hg.3b8700815448.1245074926.1485632861@qs1489.pair.com>
	<20090615184714.299668630@smtp.haun-online.de>
Message-ID: <BLU0-SMTP5B3B2637CE75C4FEB04EEBC3E0@phx.gbl>

Not a problem - do as you feel best.
I thought it was a change that would not effect anyone and is something 
that was needed but if I have to release a custom mail function as part 
of my new plugin then I will.

Plugins that send out notifications process each email notification 
individually and I wanted to change that to use a single COM_mail with a 
bcc distribution list.

Blaine

Dirk Haun wrote:
> geeklog-cvs at lists.geeklog.net wrote:
>
>   
>> details:   http://project.geeklog.net/cgi-bin/hgweb.cgi/rev/3b8700815448
>> changeset: 7122:3b8700815448
>> user:      blaine Lang <blaine at portalparts.com>
>> date:      Mon Jun 15 10:07:53 2009 -0400
>> description:
>> Added support for Bcc - Blind copy.
>>     
>
> Blaine, any objections if we roll back that change and push it to 1.6.1
> instead?
>
> I'm somewhat frustrated with the ever-expanding list of optional
> parameters on some functions (COM_mail, COM_siteHeader - there may be
> more) and would like us to come up with a better solution instead of
> creating facts (and at the last minute) that we then have to support for
> all eternity ...
>
> bye, Dirk
>
>
>   


From robg at griffsweb.com  Tue Jun 16 20:32:51 2009
From: robg at griffsweb.com (Rob Griffiths)
Date: Tue, 16 Jun 2009 17:32:51 -0700
Subject: [geeklog-devel] Prevent disabling blocks?
Message-ID: <18073014-A017-4A52-B57B-D28F6F836796@griffsweb.com>

I have a couple of blocks that I'd rather users not be able to disable  
via the Content tab in their prefs. What's the easiest way to do this?  
It doesn't seem to have a UI, nor could I find any sort of hidden pref  
for it. Must I resort to modifying usersetting.php? If so, what's the  
best way to make the change?

thx;
-rob.


From tcsp1900 at hotmail.com  Sun Jun 28 23:23:14 2009
From: tcsp1900 at hotmail.com (Tim Patrick)
Date: Sun, 28 Jun 2009 23:23:14 -0400
Subject: [geeklog-devel] geeklog-devel Digest, Vol 29, Issue 6
In-Reply-To: <mailman.9.1245247202.75869.geeklog-devel@lists.geeklog.net>
References: <mailman.9.1245247202.75869.geeklog-devel@lists.geeklog.net>
Message-ID: <BAY109-W457349099ED20A193A8577D3300@phx.gbl>


Hey Guys,

I have noticed something - In the course of making the repository, I needed a ZIP archive library. However the PEAR version, ARCHIVE_ZIP is now obsolete, now superseded as PHP's ZipArchive class, from the zlib extension.
However, not all hosts support this extension, so there is a problem. Since it is not the best of ideas to write code that works with an obsolete library, writing using ARCHIVE_ZIP is not good. However, writing with ZipArchive effectively leaves the users who do not have this extension enabled and are on shared hosts where they can't out in the dark.

What do you guys think should be done?
I am thinking of writing a library class that uses the maintained ZipArchive if it is supported, else it falls back to using the ARCHIVE_ZIP obsolete package from PEAR.

- Tim

_________________________________________________________________
We are your photos. Share us now with Windows Live Photos.
http://go.microsoft.com/?linkid=9666047
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20090628/6137d049/attachment.html>

From dirk at haun-online.de  Mon Jun 29 01:07:41 2009
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 29 Jun 2009 07:07:41 +0200
Subject: [geeklog-devel] geeklog-devel Digest, Vol 29, Issue 6
In-Reply-To: <BAY109-W457349099ED20A193A8577D3300@phx.gbl>
References: <mailman.9.1245247202.75869.geeklog-devel@lists.geeklog.net>
	<BAY109-W457349099ED20A193A8577D3300@phx.gbl>
Message-ID: <20090629050741.1034857559@smtp.haun-online.de>

Tim Patrick wrote:

>I am thinking of writing a library class that uses the maintained
>ZipArchive if it is supported, else it falls back to using the
>ARCHIVE_ZIP obsolete package from PEAR.

Are we talking about packing or unpacking? For unpacking, there's
already system/classes/unpacker.class.php

bye, Dirk


-- 
http://www.geeklog.net/
http://geeklog.info/



From vfuria at gmail.com  Mon Jun 29 18:41:46 2009
From: vfuria at gmail.com (Vincent Furia)
Date: Mon, 29 Jun 2009 16:41:46 -0600
Subject: [geeklog-devel] Content Security Policy
Message-ID: <8319e2d60906291541ge851e88of9219bb8531e5969@mail.gmail.com>

Mozilla's solution to XSS prevention. Of course, other browsers would have
to pick it up to make implementing it worth our while.

http://blog.mozilla.com/security/2009/06/19/shutting-down-xss-with-content-security-policy/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20090629/08646be3/attachment.html>

From sc1245 at messiah.edu  Tue Jun 30 20:31:09 2009
From: sc1245 at messiah.edu (Sean Clark)
Date: Tue, 30 Jun 2009 20:31:09 -0400
Subject: [geeklog-devel] This week...
Message-ID: <4A4A760D020000CB0001FC76@gwia.messiah.edu>

Hey Dirk,

Right now I'm working my way through lib-common, trying to figure out
ingenious ways to test it - but wanted to make sure I'm on the right track.
Is there anything more specific you want me to work on this week
(evaluations are coming up next week, after all). 

- Sean