From dirk at haun-online.de  Sun Jan  2 13:07:32 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 2 Jan 2011 19:07:32 +0100
Subject: [geeklog-devel] geeklog_1_7_1_1 branch
Message-ID: <6D9D7D1F-7E18-4658-8633-029EFC906F73@haun-online.de>

I hate it when that happens:

> remote: added 8 changesets with 11 changes to 5 files (+1 heads)
> remote: notify: sending 1 subscribers 1 changes
> remote: error: incoming.notify hook failed: 
> remote: 4.7.1 <geeklog-cvs at lists.geeklog.net>: Recipient address rejected: Service temporarily unavailable

Anyway, there is now a geeklog_1_7_1_1 branch in the repository and a geeklog_1_7_1sr1 tag on that branch. Any changes for Geeklog 1.7.x (e.g. the fix for bug #1239) will go into that branch, while development of 1.8.0 will continue on the trunk (branch HEAD) as usual.

For those unfamiliar with named branches in Mercurial, I've added instructions for switching to branches / tags here:

http://wiki.geeklog.net/index.php/Tags_and_Branches#Switching_to_a_branch

The "graph" view may also help:

http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/graph

bye, Dirk



From websitemaster at cogeco.net  Sun Jan  2 17:16:55 2011
From: websitemaster at cogeco.net (Website Master)
Date: Sun, 2 Jan 2011 17:16:55 -0500
Subject: [geeklog-devel] Geeklog Printable Pages and Google
Message-ID: <000001cbaaca$c3acab60$4b060220$@cogeco.net>

Hi all,

I hope everyone has had a good new year so far. My main PC  suffered a
motherboard meltdown last week so I ended up having to get a whole new
computer. I think I am almost finished moving over all my data, applications
and settings.  Uugghh!

Anyways, does anyone have any problems with me added the following meta tag
to the story and staticpage printable templates?

<META name="robots" content="NOINDEX, NOFOLLOW" />

I do not see the point of having these files indexed since the regular
versions are already indexed. I hate when I see in Google my print version
of a story outranking for some reason the actual version of the story. We
could also maybe just use:

<META name="robots" content="NOINDEX" />

To indicate not to index the page but follow the links (though the links
would be on the regular page and followed there so the other example may be
better?).

Does anyone have any thoughts on the matter?

Tom



From cordiste at free.fr  Mon Jan  3 02:07:05 2011
From: cordiste at free.fr (cordiste)
Date: Mon, 3 Jan 2011 08:07:05 +0100
Subject: [geeklog-devel] Geeklog Printable Pages and Google
In-Reply-To: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
Message-ID: <AANLkTi=w5L=xJknp3LRis_B_gzLNTY8hon8iDhOmhg+T@mail.gmail.com>

Hi,

+1 for the NOINDEX. It's a good idea.

Also can we implement a redirect to the regular version in case of a
direct link to the printable version from robots or referers?

Ben

2011/1/2 Website Master <websitemaster at cogeco.net>:
> Hi all,
>
> I hope everyone has had a good new year so far. My main PC ?suffered a
> motherboard meltdown last week so I ended up having to get a whole new
> computer. I think I am almost finished moving over all my data, applications
> and settings. ?Uugghh!
>
> Anyways, does anyone have any problems with me added the following meta tag
> to the story and staticpage printable templates?
>
> <META name="robots" content="NOINDEX, NOFOLLOW" />
>
> I do not see the point of having these files indexed since the regular
> versions are already indexed. I hate when I see in Google my print version
> of a story outranking for some reason the actual version of the story. We
> could also maybe just use:
>
> <META name="robots" content="NOINDEX" />
>
> To indicate not to index the page but follow the links (though the links
> would be on the regular page and followed there so the other example may be
> better?).
>
> Does anyone have any thoughts on the matter?
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From rouslan at placella.com  Mon Jan  3 12:37:25 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Mon, 03 Jan 2011 17:37:25 +0000
Subject: [geeklog-devel] Geeklog Printable Pages and Google
In-Reply-To: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
Message-ID: <1294076245.1787.5.camel@roccivic-pc>

I think that the NOFOLLOW option should go in the link that is pointing
to the printable page (E.g.: <A href="#" rel="nofollow">printable
page</A>). So the robots don't go to that page in the first place. But
then if they find themselves there, they should probably go ahead and
follow the links.
I'm not an expert on the matter though...

Rouslan

On Sun, 2011-01-02 at 17:16 -0500, Website Master wrote:
> Hi all,
> 
> I hope everyone has had a good new year so far. My main PC  suffered a
> motherboard meltdown last week so I ended up having to get a whole new
> computer. I think I am almost finished moving over all my data, applications
> and settings.  Uugghh!
> 
> Anyways, does anyone have any problems with me added the following meta tag
> to the story and staticpage printable templates?
> 
> <META name="robots" content="NOINDEX, NOFOLLOW" />
> 
> I do not see the point of having these files indexed since the regular
> versions are already indexed. I hate when I see in Google my print version
> of a story outranking for some reason the actual version of the story. We
> could also maybe just use:
> 
> <META name="robots" content="NOINDEX" />
> 
> To indicate not to index the page but follow the links (though the links
> would be on the regular page and followed there so the other example may be
> better?).
> 
> Does anyone have any thoughts on the matter?
> 
> Tom
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel




From dirk at haun-online.de  Mon Jan  3 13:38:52 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 3 Jan 2011 19:38:52 +0100
Subject: [geeklog-devel] Geeklog Printable Pages and Google
In-Reply-To: <1294076245.1787.5.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294076245.1787.5.camel@roccivic-pc>
Message-ID: <F7F0BCD2-B7E6-4F5A-BF6B-02C4AC75F332@haun-online.de>

Rouslan Placella wrote:

> I think that the NOFOLLOW option should go in the link that is pointing
> to the printable page

You may want to check that link on existing Geeklog sites ;-)


> On Sun, 2011-01-02 at 17:16 -0500, Website Master wrote:

New year, old name? What happened to Tom? ;-)


>> <META name="robots" content="NOINDEX" />

I think this should be enough. If a spider ends up on a printable page, we want it to find it's way back to the proper pages (and rank those).

From a philosophical point of view: Shouldn't it tell us something that the printable pages rank higher than their "full" counterpart?

bye, Dirk




From websitemaster at cogeco.net  Tue Jan  4 10:21:45 2011
From: websitemaster at cogeco.net (Tom)
Date: Tue, 4 Jan 2011 10:21:45 -0500
Subject: [geeklog-devel] Geeklog Printable Pages and Google
In-Reply-To: <F7F0BCD2-B7E6-4F5A-BF6B-02C4AC75F332@haun-online.de>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>	<1294076245.1787.5.camel@roccivic-pc>
	<F7F0BCD2-B7E6-4F5A-BF6B-02C4AC75F332@haun-online.de>
Message-ID: <000501cbac23$18e36660$4aaa3320$@cogeco.net>

>From a philosophical point of view: Shouldn't it tell us something that the
printable pages rank higher than their "full" counterpart?

In my case most times they don't but the odd one still does. Another reason
to add the meta tag is possible duplicate content issues.

>New year, old name? What happened to Tom? ;-)

It should be switched back now.  I got a new PC and I missed that at first
after installing Outlook.

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: January-03-11 1:39 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Printable Pages and Google

Rouslan Placella wrote:

> I think that the NOFOLLOW option should go in the link that is 
> pointing to the printable page

You may want to check that link on existing Geeklog sites ;-)


> On Sun, 2011-01-02 at 17:16 -0500, Website Master wrote:

New year, old name? What happened to Tom? ;-)


>> <META name="robots" content="NOINDEX" />

I think this should be enough. If a spider ends up on a printable page, we
want it to find it's way back to the proper pages (and rank those).

>From a philosophical point of view: Shouldn't it tell us something that the
printable pages rank higher than their "full" counterpart?

bye, Dirk


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



From rouslan at placella.com  Thu Jan 13 13:18:09 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Thu, 13 Jan 2011 18:18:09 +0000
Subject: [geeklog-devel] New version checker
In-Reply-To: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
Message-ID: <1294942689.3475.19.camel@roccivic-pc>

Hi all,

I found a task on openhatch [1] that involves redesigning the current
version checker page [2]. And so I decided to give it a go. And so I put
together a prototype over the last few days.

I'm looking for some feedback and help testing. So far I only tested on
linux with Firefox 3.6 and Opera 11. (There are a few minor issues with
the timeline image that I'm aware of, but that I haven't fixed yet.
E.g.: some text gets clipped in some situations and PHP is not loading
the fonts that I'm telling it to.)

There are 8 different types of response that one can get from this
script. Here are some examples:

http://www.placella.com/gl/versioncheck/versionchecker.php
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1sr1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.5.2
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.6.1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.3.9
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.8.0hg
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.0rc1



Any thoughts?

Thanks,
Rouslan

[1] https://openhatch.org/+projects/geeklog
[2] http://www.geeklog.net/versionchecker.php




From cordiste at free.fr  Thu Jan 13 16:33:49 2011
From: cordiste at free.fr (cordiste)
Date: Thu, 13 Jan 2011 22:33:49 +0100
Subject: [geeklog-devel] New version checker
In-Reply-To: <1294942689.3475.19.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294942689.3475.19.camel@roccivic-pc>
Message-ID: <AANLkTin=WYzDJYyj5BoQ-K9DHyQa0oz-Yyhjm-L3Kggn@mail.gmail.com>

Very nice work Rouslan. Tested on safari 5.0.3 and chrome 8.0 for windows.

The g logo is a little outdated. We should really change it ;)

Ben

2011/1/13 Rouslan Placella <rouslan at placella.com>:
> Hi all,
>
> I found a task on openhatch [1] that involves redesigning the current
> version checker page [2]. And so I decided to give it a go. And so I put
> together a prototype over the last few days.
>
> I'm looking for some feedback and help testing. So far I only tested on
> linux with Firefox 3.6 and Opera 11. (There are a few minor issues with
> the timeline image that I'm aware of, but that I haven't fixed yet.
> E.g.: some text gets clipped in some situations and PHP is not loading
> the fonts that I'm telling it to.)
>
> There are 8 different types of response that one can get from this
> script. Here are some examples:
>
> http://www.placella.com/gl/versioncheck/versionchecker.php
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1sr1
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.5.2
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.6.1
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.3.9
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.8.0hg
> http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.0rc1
>
>
>
> Any thoughts?
>
> Thanks,
> Rouslan
>
> [1] https://openhatch.org/+projects/geeklog
> [2] http://www.geeklog.net/versionchecker.php
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From websitemaster at cogeco.net  Thu Jan 13 19:34:57 2011
From: websitemaster at cogeco.net (Tom)
Date: Thu, 13 Jan 2011 19:34:57 -0500
Subject: [geeklog-devel] New version checker
In-Reply-To: <1294942689.3475.19.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294942689.3475.19.camel@roccivic-pc>
Message-ID: <005d01cbb382$df063f00$9d12bd00$@cogeco.net>

Looks good.  I also did a quick check using IE 8 and things looked fine.

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Placella
Sent: January-13-11 1:18 PM
To: Geeklog Development
Subject: [geeklog-devel] New version checker

Hi all,

I found a task on openhatch [1] that involves redesigning the current
version checker page [2]. And so I decided to give it a go. And so I put
together a prototype over the last few days.

I'm looking for some feedback and help testing. So far I only tested on
linux with Firefox 3.6 and Opera 11. (There are a few minor issues with the
timeline image that I'm aware of, but that I haven't fixed yet.
E.g.: some text gets clipped in some situations and PHP is not loading the
fonts that I'm telling it to.)

There are 8 different types of response that one can get from this script.
Here are some examples:

http://www.placella.com/gl/versioncheck/versionchecker.php
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1sr1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.5.2
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.6.1
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.3.9
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.8.0hg
http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.0rc1



Any thoughts?

Thanks,
Rouslan

[1] https://openhatch.org/+projects/geeklog
[2] http://www.geeklog.net/versionchecker.php


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



From joe at throwingdice.com  Sat Jan 15 00:46:19 2011
From: joe at throwingdice.com (joe at throwingdice.com)
Date: Sat, 15 Jan 2011 05:46:19 -0000
Subject: [geeklog-devel] OpenID & OAuth Support
In-Reply-To: <009c01cb7707$f37b6da0$da7248e0$@net>
References: <20101014044907.abs5ffjxqzkk8g48@webmail.opentransfer.com>
	<732B1751-FD6B-482D-A8E2-5DCA85A59921@haun-online.de>
	<1287312505.4723.9.camel@roccivic-pc>
	<AANLkTi=Y7yKJLNMAm7MMtqRPyKt89tjjdPX1oaiJpvxS@mail.gmail.com>
	<1287332416.2703.30.camel@roccivic-pc>
	<012e01cb6fb3$25fd7db0$71f87910$@net>
	<1287522704.2650.0.camel@roccivic-pc>
	<015b01cb6fd4$132a24b0$397e6e10$@net>
	<015d01cb72e3$d2016300$76042900$@net>
	<C6554C4F-BD7B-49F8-B5B4-81045DE8ACF4@haun-online.de>
	<01c601cb73e4$4acf2be0$e06d83a0$@net> <88
	<00ed01cb75de$e2ac6710$a8053530$@net>
	<009c01cb7707$f37b6da0$da7248e0$@net>
Message-ID: <01d04e15660132aa22a884bc10283045.squirrel@mustang.hawkhost.com>

> Also currently in the remoteservice column of the users table, the OAuth
> class saves the name of its remote service  as facebook, twitter or
> linkedin. It doesn't mention OAuth and conceivably we could get
> duplications
> if there is more than one way to access your facebook account. Should I
> add
> a column for remote service type?
>
> For example remoteservice would then become oauth and then
> remoteservicetype
> would become facebook

I don't know how you choose this terminology but it sounds backwards. The
RemoteServiceTYPE is OAuth and the RemoveService (provider) is Facebook or
LinkedIn. At least that sounds better to me.

  Joe



From callkalpa at gmail.com  Sat Jan 15 08:12:51 2011
From: callkalpa at gmail.com (Kalpa Welivitigoda)
Date: Sat, 15 Jan 2011 18:42:51 +0530
Subject: [geeklog-devel] Bug #0001216 patched
Message-ID: <AANLkTi=-k_-r+-hJZ+F8WgKkiLeay-pqYfjXFT=aMSwx@mail.gmail.com>

Hi,

I patched bug #0001216. Can someone review and commit it.

-- 
Best Regards,

Kalpa Pathum Welivitigoda
http://kalpapathum.blogspot.com
http://thiraya.wordpress.com
http://www.flickr.com/photos/49383144 at N05/


From dirk at haun-online.de  Sat Jan 15 09:03:04 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 15 Jan 2011 15:03:04 +0100
Subject: [geeklog-devel] Bug #0001216 patched
In-Reply-To: <AANLkTi=-k_-r+-hJZ+F8WgKkiLeay-pqYfjXFT=aMSwx@mail.gmail.com>
References: <AANLkTi=-k_-r+-hJZ+F8WgKkiLeay-pqYfjXFT=aMSwx@mail.gmail.com>
Message-ID: <9539DB84-B315-43CC-823F-603EC7B9AF68@haun-online.de>

Kalpa Welivitigoda wrote:

> I patched bug #0001216. Can someone review and commit it.

I don't see a patch attached to the issue. Did you forget to upload it?

http://project.geeklog.net/tracking/view.php?id=1216

bye, Dirk



From callkalpa at gmail.com  Sat Jan 15 09:10:12 2011
From: callkalpa at gmail.com (Kalpa Welivitigoda)
Date: Sat, 15 Jan 2011 19:40:12 +0530
Subject: [geeklog-devel] Bug #0001216 patched
In-Reply-To: <9539DB84-B315-43CC-823F-603EC7B9AF68@haun-online.de>
References: <AANLkTi=-k_-r+-hJZ+F8WgKkiLeay-pqYfjXFT=aMSwx@mail.gmail.com>
	<9539DB84-B315-43CC-823F-603EC7B9AF68@haun-online.de>
Message-ID: <AANLkTin+0FF2by9yO_F2LMp3At5a8QtxNje5_esvp36S@mail.gmail.com>

On Sat, Jan 15, 2011 at 7:33 PM, Dirk Haun <dirk at haun-online.de> wrote:
> Kalpa Welivitigoda wrote:
>
>> I patched bug #0001216. Can someone review and commit it.
>
> I don't see a patch attached to the issue. Did you forget to upload it?
>

Opps. I've forgotten to attach. I attched it now.

> http://project.geeklog.net/tracking/view.php?id=1216
>
> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>



-- 
Best Regards,

Kalpa Pathum Welivitigoda
http://kalpapathum.blogspot.com
http://thiraya.wordpress.com
http://www.flickr.com/photos/49383144 at N05/


From dirk at haun-online.de  Sat Jan 15 09:59:13 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 15 Jan 2011 15:59:13 +0100
Subject: [geeklog-devel] Bugtracker workflow suggestions
Message-ID: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>

We have quite a few issues in our bugtracker now with an attached patch. However, they aren't easy to find. As a result, they tend to get overlooked. In other words: Many issues in our bugtracker have already been solved - but we don't see it since the existence of a patch isn't easily visible.

There doesn't seem to be an easy way to extend the workflow with an additional state (say, "has patch"). So far, we've tried to work around the problem by setting the status of such an issue to "assigned". But that hasn't happened for all the issues with a patch and it still doesn't help to find all issues with a patch, since you would also get issues that are assigned to people currently working on it.

We do, however, have a third category (besides "bugs" and "feature requests"): "Patches".

Suggestion: An issue for which we have a patch will be changed to category "Patches". That makes them easier to find (use the filters). The only downside is that we're losing the information whether it was a bug or feature request to begin with. But then again that information can still be seen in the issue's history.

Any objections or other suggestions?

bye, Dirk



From callkalpa at gmail.com  Sat Jan 15 10:45:39 2011
From: callkalpa at gmail.com (Kalpa Welivitigoda)
Date: Sat, 15 Jan 2011 21:15:39 +0530
Subject: [geeklog-devel] Bugtracker workflow suggestions
In-Reply-To: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>
References: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>
Message-ID: <AANLkTino--NfHtTdjTbyCwsc4yrtsrhQ6yjV4VvSfj5i@mail.gmail.com>

On Sat, Jan 15, 2011 at 8:29 PM, Dirk Haun <dirk at haun-online.de> wrote:
> We have quite a few issues in our bugtracker now with an attached patch. However, they aren't easy to find. As a result, they tend to get overlooked. In other words: Many issues in our bugtracker have already been solved - but we don't see it since the existence of a patch isn't easily visible.
>
> There doesn't seem to be an easy way to extend the workflow with an additional state (say, "has patch"). So far, we've tried to work around the problem by setting the status of such an issue to "assigned". But that hasn't happened for all the issues with a patch and it still doesn't help to find all issues with a patch, since you would also get issues that are assigned to people currently working on it.
>
> We do, however, have a third category (besides "bugs" and "feature requests"): "Patches".
>
> Suggestion: An issue for which we have a patch will be changed to category "Patches". That makes them easier to find (use the filters). The only downside is that we're losing the information whether it was a bug or feature request to begin with. But then again that information can still be seen in the issue's history.
>
> Any objections or other suggestions?
>

Well, do we do the change of category soon after a patch is uploaded
or once it gets reviewed?

> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>



-- 
Best Regards,

Kalpa Pathum Welivitigoda
http://kalpapathum.blogspot.com
http://thiraya.wordpress.com
http://www.flickr.com/photos/49383144 at N05/


From rouslan at placella.com  Sat Jan 15 13:53:18 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Sat, 15 Jan 2011 18:53:18 +0000
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <1294942689.3475.19.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294942689.3475.19.camel@roccivic-pc>
Message-ID: <1295117598.1787.111.camel@roccivic-pc>

Hi all,

I found another task on openhatch [1] that I would like to have a go at.
Here's its summary:

"Geeklog's plugin 'editor' is mainly a form that displays some
information about a plugin. It really only has options to enable/disable
a plugin and possibly to update it. The main issue with this form,
however, is that unlike all of the other editors in Geeklog, it has the
buttons (save, cancel, ...) at the top of the form. But moving them to
the bottom (for consistency) leaves some ugly blank space at the top of
the form. So the task is to come up with a new design for this form
that's both consistent with the rest of Geeklog and also looks nice."


However I fail to see how the plugin editor is actually useful. All the
information that it displays can be safely moved to the plugin list.
This can be done by either directly inserting information in the table
or by using the new COM_tooltip() function. The "delete" function can
also be inserted in the plugin list table, including the confirmation
function. There would be only one thing left for which the plugin editor
would be useful after the changes that I described above are
implemented: enabling and disabling plugins without the need for
JavaScript to be turned on. But I tackled this last issue in "feature
request #0001243"[2]. So, basically we'd be left at this point with the
same implementation as in glFusion plugin admin ( Can be seen on their
demo site [3] ). So, what do you guys think? Should I do it like that?
Any other ideas / suggestions / recommendations?

Take care,
Rouslan


[1]: https://openhatch.org/+projects/geeklog
[2]: http://project.geeklog.net/tracking/view.php?id=1243
[3]: http://demo.glfusion.org/admin/plugins.php



From websitemaster at cogeco.net  Sat Jan 15 15:18:53 2011
From: websitemaster at cogeco.net (Tom)
Date: Sat, 15 Jan 2011 15:18:53 -0500
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <1295117598.1787.111.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>	<1294942689.3475.19.camel@roccivic-pc>
	<1295117598.1787.111.camel@roccivic-pc>
Message-ID: <00e301cbb4f1$6e486f70$4ad94e50$@cogeco.net>


Your layout ideas make sense.

One thing I thought of is that there are a few projects related to plugins
that you may want to consider with the redesign. These haven't been
implemented yet but at some point we should and when we do they may affect
how the plugins form is laid out:

Plugin Version Control and Dependencies
http://project.geeklog.net/tracking/view.php?id=1154

Plugin Repository
http://wiki.geeklog.net/index.php/SoC_plugin_repository#Plugin_Repository
- See all on this page: Plugin admin panel
- This has been worked on as a GSOC project and I know Dirk had wanted to
finish it up at some point.

Tom


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Placella
Sent: January-15-11 1:53 PM
To: Geeklog Development
Subject: [geeklog-devel] Redesign the Plugin "Editor"

Hi all,

I found another task on openhatch [1] that I would like to have a go at.
Here's its summary:

"Geeklog's plugin 'editor' is mainly a form that displays some information
about a plugin. It really only has options to enable/disable a plugin and
possibly to update it. The main issue with this form, however, is that
unlike all of the other editors in Geeklog, it has the buttons (save,
cancel, ...) at the top of the form. But moving them to the bottom (for
consistency) leaves some ugly blank space at the top of the form. So the
task is to come up with a new design for this form that's both consistent
with the rest of Geeklog and also looks nice."


However I fail to see how the plugin editor is actually useful. All the
information that it displays can be safely moved to the plugin list.
This can be done by either directly inserting information in the table or by
using the new COM_tooltip() function. The "delete" function can also be
inserted in the plugin list table, including the confirmation function.
There would be only one thing left for which the plugin editor would be
useful after the changes that I described above are
implemented: enabling and disabling plugins without the need for JavaScript
to be turned on. But I tackled this last issue in "feature request
#0001243"[2]. So, basically we'd be left at this point with the same
implementation as in glFusion plugin admin ( Can be seen on their demo site
[3] ). So, what do you guys think? Should I do it like that?
Any other ideas / suggestions / recommendations?

Take care,
Rouslan


[1]: https://openhatch.org/+projects/geeklog
[2]: http://project.geeklog.net/tracking/view.php?id=1243
[3]: http://demo.glfusion.org/admin/plugins.php

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



From jmucchiello at yahoo.com  Sat Jan 15 16:10:43 2011
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Sat, 15 Jan 2011 13:10:43 -0800 (PST)
Subject: [geeklog-devel] Redesign the Plugin "Editor"
Message-ID: <60384.97697.qm@web31401.mail.mud.yahoo.com>

Tom points out something important. I don't think getting rid of the "plugin 
editor" is a good idea. It would be nice if plugins could register dependencies 
on other plugins and the place to put that information would be the editor 
screen. If you really want to do something with plugins, find the ~8 year old 
feature request for being able to change the load order of plugins and implement 
it. Geeklog needs that much more than it needs pretty admin screens.

  Joe



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

From rouslan at placella.com  Sat Jan 15 17:20:55 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Sat, 15 Jan 2011 22:20:55 +0000
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <60384.97697.qm@web31401.mail.mud.yahoo.com>
References: <60384.97697.qm@web31401.mail.mud.yahoo.com>
Message-ID: <1295130055.5318.7.camel@roccivic-pc>

On Sat, 2011-01-15 at 13:10 -0800, Joe Mucchiello wrote:
> Tom points out something important. I don't think getting rid of the
> "plugin editor" is a good idea. It would be nice if plugins could
> register dependencies on other plugins and the place to put that
> information would be the editor screen.
Couldn't that information go into a "info" tooltip? Or if it needs to be
changed, it could go directly into the list of plugins.

>  If you really want to do something with plugins, find the ~8 year old
> feature request for being able to change the load order of plugins and
> implement it.
The oldest entry in the bugtracker that I can see is from 2008...

> Geeklog needs that much more than it needs pretty admin screens.
Why?


Take care,
Rouslan




From rouslan at placella.com  Sat Jan 15 17:36:20 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Sat, 15 Jan 2011 22:36:20 +0000
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <1295130055.5318.7.camel@roccivic-pc>
References: <60384.97697.qm@web31401.mail.mud.yahoo.com>
	<1295130055.5318.7.camel@roccivic-pc>
Message-ID: <1295130980.5318.9.camel@roccivic-pc>

On Sat, 2011-01-15 at 22:20 +0000, Rouslan Placella wrote:
> On Sat, 2011-01-15 at 13:10 -0800, Joe Mucchiello wrote:
> > Tom points out something important. I don't think getting rid of the
> > "plugin editor" is a good idea. It would be nice if plugins could
> > register dependencies on other plugins and the place to put that
> > information would be the editor screen.
> Couldn't that information go into a "info" tooltip? Or if it needs to be
> changed, it could go directly into the list of plugins.
> 
> >  If you really want to do something with plugins, find the ~8 year old
> > feature request for being able to change the load order of plugins and
> > implement it.
> The oldest entry in the bugtracker that I can see is from 2008...
> 
> > Geeklog needs that much more than it needs pretty admin screens.
> Why?
> 
> 
> Take care,
> Rouslan

Nevermind Joe, Dirk found it. And I refiled it:
http://project.geeklog.net/tracking/view.php?id=1247
Anyway, I get it and I'll have a look into it.

Take care, Rouslan



From websitemaster at cogeco.net  Sat Jan 15 19:56:37 2011
From: websitemaster at cogeco.net (Tom)
Date: Sat, 15 Jan 2011 19:56:37 -0500
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <1295130980.5318.9.camel@roccivic-pc>
References: <60384.97697.qm@web31401.mail.mud.yahoo.com>	<1295130055.5318.7.camel@roccivic-pc>
	<1295130980.5318.9.camel@roccivic-pc>
Message-ID: <00ea01cbb518$3a5fcab0$af1f6010$@cogeco.net>

Hey Dirk,

You mentioned in a post a while back:

>>I do have the Geeklog side of things in a local Mercurial repository, all
merged with the current development version (including SQL updates etc.). 
>>I haven't pushed it since I ran into a few issues with the actual
Repository
 >>plugin. I've talked to Tim briefly to see if he would be available to
either work on it or help us with it.

>>The Plugin Repository is an important next step in our ongoing quest to
make installation and upgrades easier, so it should definitively be on the
list.

Is this something you think you will get to, or should Rouslan not worry
about it if he goes ahead and updates the plugin interface?

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan
Placella
Sent: January-15-11 5:36 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Redesign the Plugin "Editor"

On Sat, 2011-01-15 at 22:20 +0000, Rouslan Placella wrote:
> On Sat, 2011-01-15 at 13:10 -0800, Joe Mucchiello wrote:
> > Tom points out something important. I don't think getting rid of the 
> > "plugin editor" is a good idea. It would be nice if plugins could 
> > register dependencies on other plugins and the place to put that 
> > information would be the editor screen.
> Couldn't that information go into a "info" tooltip? Or if it needs to 
> be changed, it could go directly into the list of plugins.
> 
> >  If you really want to do something with plugins, find the ~8 year 
> > old feature request for being able to change the load order of 
> > plugins and implement it.
> The oldest entry in the bugtracker that I can see is from 2008...
> 
> > Geeklog needs that much more than it needs pretty admin screens.
> Why?
> 
> 
> Take care,
> Rouslan

Nevermind Joe, Dirk found it. And I refiled it:
http://project.geeklog.net/tracking/view.php?id=1247
Anyway, I get it and I'll have a look into it.

Take care, Rouslan

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



From vfuria at gmail.com  Sat Jan 15 21:19:28 2011
From: vfuria at gmail.com (Vincent Furia)
Date: Sat, 15 Jan 2011 19:19:28 -0700
Subject: [geeklog-devel] Bugtracker workflow suggestions
In-Reply-To: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>
References: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>
Message-ID: <AANLkTikhK2wk+pA3s5rPhFF5d4WCkQAz2O_Z_qq1vwnP@mail.gmail.com>

I think an ideal solution would be something that would be obvious to those
submitting a patch. Changing the category to Patch will work for those who
are familiar with our system, but would be non-obvious for everyone else.
I'm not sure there is a good solution though...

-Vinny

On Sat, Jan 15, 2011 at 07:59, Dirk Haun <dirk at haun-online.de> wrote:

> We have quite a few issues in our bugtracker now with an attached patch.
> However, they aren't easy to find. As a result, they tend to get overlooked.
> In other words: Many issues in our bugtracker have already been solved - but
> we don't see it since the existence of a patch isn't easily visible.
>
> There doesn't seem to be an easy way to extend the workflow with an
> additional state (say, "has patch"). So far, we've tried to work around the
> problem by setting the status of such an issue to "assigned". But that
> hasn't happened for all the issues with a patch and it still doesn't help to
> find all issues with a patch, since you would also get issues that are
> assigned to people currently working on it.
>
> We do, however, have a third category (besides "bugs" and "feature
> requests"): "Patches".
>
> Suggestion: An issue for which we have a patch will be changed to category
> "Patches". That makes them easier to find (use the filters). The only
> downside is that we're losing the information whether it was a bug or
> feature request to begin with. But then again that information can still be
> seen in the issue's history.
>
> Any objections or other suggestions?
>
> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110115/91b5719e/attachment.html>

From vfuria at gmail.com  Sat Jan 15 21:24:00 2011
From: vfuria at gmail.com (Vincent Furia)
Date: Sat, 15 Jan 2011 19:24:00 -0700
Subject: [geeklog-devel] Redesign the Plugin "Editor"
In-Reply-To: <1295130980.5318.9.camel@roccivic-pc>
References: <60384.97697.qm@web31401.mail.mud.yahoo.com>
	<1295130055.5318.7.camel@roccivic-pc>
	<1295130980.5318.9.camel@roccivic-pc>
Message-ID: <AANLkTikgGapW0A6ft-wtfQVYnGxzHcff8NLE=EZmjivF@mail.gmail.com>

On Sat, Jan 15, 2011 at 15:36, Rouslan Placella <rouslan at placella.com>wrote:

> > >  If you really want to do something with plugins, find the ~8 year old
> > > feature request for being able to change the load order of plugins and
> > > implement it.
> > The oldest entry in the bugtracker that I can see is from 2008...
> >
> > > Geeklog needs that much more than it needs pretty admin screens.
> > Why?
>
> Nevermind Joe, Dirk found it. And I refiled it:
> http://project.geeklog.net/tracking/view.php?id=1247
> Anyway, I get it and I'll have a look into it.


It seems we could add ordering to the plugin list (like we have for side
blocks). Then just sort them on the query that pulls plugin names to load
the functions.inc plugin files.

I agree that a good revamping of the plugin list could eliminate the need
for the edit plugin screen and provide a very intuitive way of handling
plugins. Good call Rouslan.

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

From jmucchiello at yahoo.com  Sun Jan 16 00:10:21 2011
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Sat, 15 Jan 2011 21:10:21 -0800 (PST)
Subject: [geeklog-devel] [Fwd: Re:  Redesign the Plugin "Editor"]
In-Reply-To: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
Message-ID: <21889.27328.qm@web31403.mail.mud.yahoo.com>



"Rouslan Placella" <rouslan at placella.com> wrote:
>Couldn't that information go into a "info" tooltip? Or if it needs to be
>changed, it could go directly into the list of plugins.

Do you really think "This plugin requires the social networing plugin active in 
order to work" is the kind of information that belongs in a tooltip? Last summer 
everyone was all up about making plugins that were built off the socnet plugin 
(where ever that is). Well, knowing that if you deactivate the socnet plugin it 
will affect other plugins doesn't sound like something that goes in a tooltip. 
Adding this information to the main plugin list doesn't sound good either. 


What is the motivation to remove the editor screen? Are you going to remove the 
topic editor too? It's kind of sparse. I just think it would confusing to have 
some admin screens that lead to editors and some that are edited in place.

>The oldest entry in the bugtracker that I can see is from 2008...
There was a big crash in 2008. They are older.

>> Geeklog needs that much more than it needs pretty admin screens.
>Why?
Because only admins see pretty admin screens. Making pretty admin screens 
benefits one or two people per geeklog installation and usually only during 
their first few weeks of installation: how often to admins go to the plugin 
screen really? User facing screens getting beautified helps every user at every 
geeklog installation.

The plugin load order fix is as simple as adding a pi_order field to the plugin 
table. Stealing the up/down arrow interface from the blocks admin screen and 
changing the spot where the plugins are initially loaded so that it uses the new 
order field when it loads the plugin list. The request is at least as old as 
Geeklog 1.3.x. And the old bug tracker had a patch lost in the above crash. If 
you can get it into core, more power to you.

  Joe



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

From dirk at haun-online.de  Sun Jan 16 03:57:31 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 16 Jan 2011 09:57:31 +0100
Subject: [geeklog-devel] New version checker
In-Reply-To: <1294942689.3475.19.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294942689.3475.19.camel@roccivic-pc>
Message-ID: <FE72D8AD-CD64-4FE4-AC04-3F4EAC8B5D74@haun-online.de>

Rouslan Placella wrote:

> I found a task on openhatch [1] that involves redesigning the current
> version checker page [2]. And so I decided to give it a go. And so I put
> together a prototype over the last few days.

Looks good to me.

http://www.placella.com/gl/versioncheck/versionchecker.php?version=1.7.1

There's an extra space in "... is out of date ." (i.e. after "date"). That's about the only problem I found :)

Since it requires some extra files (icons, stylesheet): Can you put those into a subdirectory please? We don't really want to dump them into the webroot on geeklog.net

Send it over and I'll put it up on geeklog.net. With an announcement - we need some positive news for a change ;-)

Thanks!

bye, Dirk



From dirk at haun-online.de  Sun Jan 16 06:09:08 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 16 Jan 2011 12:09:08 +0100
Subject: [geeklog-devel] Bugtracker workflow suggestions
In-Reply-To: <AANLkTikhK2wk+pA3s5rPhFF5d4WCkQAz2O_Z_qq1vwnP@mail.gmail.com>
References: <16BA4184-5FA3-45F7-99A5-02D7E6EF45E4@haun-online.de>
	<AANLkTikhK2wk+pA3s5rPhFF5d4WCkQAz2O_Z_qq1vwnP@mail.gmail.com>
Message-ID: <CAB0E6A8-D642-48D7-ABE3-F8D78126C80A@haun-online.de>

Vincent Furia wrote:

> I'm not sure there is a good solution though...

Yep.

I went through parts of the open issues and already identified 20+ patches lurking there. So I'd say anything that helps to make them more visible is a good thing. It must be frustrating for those who submitted those patches in the first place when we let them sit for months.

Help in reviewing the patches is welcome, btw :)

bye, Dirk



From websitemaster at cogeco.net  Sun Jan 16 10:36:16 2011
From: websitemaster at cogeco.net (Tom)
Date: Sun, 16 Jan 2011 10:36:16 -0500
Subject: [geeklog-devel] Open Source Market Share Report
Message-ID: <011301cbb593$1ec24820$5c46d860$@cogeco.net>

For those interested, here is an Open Source Market Share Report for 2010
from Water and Stone. There are no surprises here on who the big 3 are.

http://www.waterandstone.com/book/2010-open-source-cms-market-share-report

Tom



From Randy.Kolenko at nextide.ca  Sun Jan 16 11:33:54 2011
From: Randy.Kolenko at nextide.ca (Randy Kolenko)
Date: Sun, 16 Jan 2011 11:33:54 -0500
Subject: [geeklog-devel] [Fwd: Re:  Redesign the Plugin "Editor"]
Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F3837B9@nex-pluto.nextide.ca>

Aside from the dig against Socnet, Joe's point is valid.

During our last revamp of our Nexpro plugins, we introduced a very simple-to-code dependency check in the installation routine and returned the dependency information in an error message.  This way we could have dependencies on many other plugins and never have to worry about installing something without other mechanisms being present.

For the last revision of our apps, reception from the GL community at large was tepid at best -- but the approach is all there for everyone to see.

We noted issues with the current GL plugin system where the plugin would not be able to raise errors with Geeklog during the installation.  We noted this in the devel list a few times.  So we had to adhere to what Geeklog would allow us to do, and thus we simply had to rely on the error.log file to spit out dependency information.

That being said, it's a VERY short step from what we've implemented already to showing those dependencies and having an install routine blocked by the UI.  So don't re-invent the wheel when most of it has already been created.



From: Joe Mucchiello [mailto:jmucchiello at yahoo.com] 
Sent: Sunday, January 16, 2011 12:10 AM
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]


"Rouslan Placella" <rouslan at placella.com> wrote:
>Couldn't that information go into a "info" tooltip? Or if it needs to be
>changed, it could go directly into the list of plugins.

Do you really think "This plugin requires the social networing plugin active in order to work" is the kind of information that belongs in a tooltip? Last summer everyone was all up about making plugins that were built off the socnet plugin (where ever that is). Well, knowing that if you deactivate the socnet plugin it will affect other plugins doesn't sound like something that goes in a tooltip. Adding this information to the main plugin list doesn't sound good either. 

What is the motivation to remove the editor screen? Are you going to remove the topic editor too? It's kind of sparse. I just think it would confusing to have some admin screens that lead to editors and some that are edited in place.

>The oldest entry in the bugtracker that I can see is from 2008...
There was a big crash in 2008. They are older.

>> Geeklog needs that much more than it needs pretty admin screens.
>Why?
Because only admins see pretty admin screens. Making pretty admin screens benefits one or two people per geeklog installation and usually only during their first few weeks of installation: how often to admins go to the plugin screen really? User facing screens getting beautified helps every user at every geeklog installation.

The plugin load order fix is as simple as adding a pi_order field to the plugin table. Stealing the up/down arrow interface from the blocks admin screen and changing the spot where the plugins are initially loaded so that it uses the new order field when it loads the plugin list. The request is at least as old as Geeklog 1.3.x. And the old bug tracker had a patch lost in the above crash. If you can get it into core, more power to you.

? Joe




From rouslan at placella.com  Mon Jan 17 09:18:06 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Mon, 17 Jan 2011 14:18:06 +0000
Subject: [geeklog-devel] [Fwd: Re:  Redesign the Plugin "Editor"]
In-Reply-To: <21889.27328.qm@web31403.mail.mud.yahoo.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
Message-ID: <1295273886.2891.23.camel@roccivic-pc>

On Sat, 2011-01-15 at 21:10 -0800, Joe Mucchiello wrote:

> Do you really think "This plugin requires the social networing plugin
> active in order to work" is the kind of information that belongs in a
> tooltip?
Why not? I guess that in both cases (tooltip vs plugin editor) we'd need
some sort of a "Error information available" or "See warnings" column in
the plugin list to notify the user about the error. So why not display
this information as soon as you hover over the icon or alert text in
such a column?


> Are you going to remove the topic editor too? 
No. I'd leave the story editor alone, too. After all they are used for
editing things. But the plugin editor doesn't really edit anything.
Maybe it should be renamed to "Plugin Information Page" or something
similar instead.


> Making pretty admin screens benefits one or two people per geeklog
> installation and usually only during their first few weeks of
> installation: how often to admins go to the plugin screen really? User
> facing screens getting beautified helps every user at every geeklog
> installation.
Fair enough, but admin are those who decide whether to stick with a
cms...


> The plugin load order fix is as simple as adding a pi_order field to
> the plugin table. Stealing the up/down arrow interface from the blocks
> admin screen and changing the spot where the plugins are initially
> loaded so that it uses the new order field when it loads the plugin
> list. The request is at least as old as Geeklog 1.3.x. And the old bug
> tracker had a patch lost in the above crash. If you can get it into
> core, more power to you.
Anyway I get the point and so I will do this first.


Rouslan




From danstoner at gmail.com  Tue Jan 18 09:42:24 2011
From: danstoner at gmail.com (Dan Stoner)
Date: Tue, 18 Jan 2011 09:42:24 -0500
Subject: [geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]
In-Reply-To: <21889.27328.qm@web31403.mail.mud.yahoo.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
Message-ID: <AANLkTiktv7+b_--pF+5094QGUXfQgANuf0Qj39BwoGs=@mail.gmail.com>

>>> Geeklog needs that much more than it needs pretty admin screens.
>>Why?
> Because only admins see pretty admin screens. Making pretty admin screens
> benefits one or two people per geeklog installation and usually only during
> their first few weeks of installation: how often to admins go to the plugin
> screen really? User facing screens getting beautified helps every user at
> every geeklog installation.

I would say that making "pretty admin screens" are the kind of small
changes that allow more developers to start participating in the
project, which is good for GL.

The first few weeks/days of installation are also the time that a
potential developer decides whether it is worth his/her time to
participate in the Geeklog project.  A little bit of polish can show
that GL is mature and still active.

If "the admin interface looks old and clunky" is the particular itch
that is bothering a developer, it might be nice to let that change get
into the code.  Once a developer has participated in a project, I
think it is more likely they might come back to solve one of the
harder or more critical needed features.


I have been toying with the idea of participating more materially in
GL... I would need some baby step tasks before doing anything real or
important.

Dan Stoner
http://thatlinuxbox.com/blog/


From dirk at haun-online.de  Tue Jan 18 11:06:02 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Tue, 18 Jan 2011 17:06:02 +0100
Subject: [geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]
In-Reply-To: <AANLkTiktv7+b_--pF+5094QGUXfQgANuf0Qj39BwoGs=@mail.gmail.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
	<AANLkTiktv7+b_--pF+5094QGUXfQgANuf0Qj39BwoGs=@mail.gmail.com>
Message-ID: <20110118170602.56511yr4j8eomvs0@webmail.df.eu>

Quoting Dan Stoner <danstoner at gmail.com>:

> A little bit of polish can show
> that GL is mature and still active.

Good point.


> "the admin interface looks old and clunky"

Some would say "not only the admin interface" ;-)


> I have been toying with the idea of participating more materially in
> GL... I would need some baby step tasks before doing anything real or
> important.

You're very much welcome. There's a "Getting Started" page aimed at  
developers on the wiki:

http://wiki.geeklog.net/index.php/Getting_Started

For non / not-so-much coding tasks, I've dumped the tasks we collected  
for Google Code-In over at OpenHatch:

https://openhatch.org/+projects/geeklog

... and if you speak any language other than English: Most of our  
language files could benefit from an update.

Thanks for offering to help!

bye, Dirk





From cordiste at free.fr  Tue Jan 18 13:19:04 2011
From: cordiste at free.fr (cordiste)
Date: Tue, 18 Jan 2011 19:19:04 +0100
Subject: [geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]
In-Reply-To: <20110118170602.56511yr4j8eomvs0@webmail.df.eu>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
	<AANLkTiktv7+b_--pF+5094QGUXfQgANuf0Qj39BwoGs=@mail.gmail.com>
	<20110118170602.56511yr4j8eomvs0@webmail.df.eu>
Message-ID: <AANLkTimYYVuNe_XPNfhsARrbPp4j+v=x7SshUNMC+52a@mail.gmail.com>

Dan very nice theme re-load on http://thatlinuxbox.com

Ben

2011/1/18 Dirk Haun <dirk at haun-online.de>:
> Quoting Dan Stoner <danstoner at gmail.com>:
>
>> A little bit of polish can show
>> that GL is mature and still active.
>
> Good point.
>
>
>> "the admin interface looks old and clunky"
>
> Some would say "not only the admin interface" ;-)
>
>
>> I have been toying with the idea of participating more materially in
>> GL... I would need some baby step tasks before doing anything real or
>> important.
>
> You're very much welcome. There's a "Getting Started" page aimed at
> developers on the wiki:
>
> http://wiki.geeklog.net/index.php/Getting_Started
>
> For non / not-so-much coding tasks, I've dumped the tasks we collected for
> Google Code-In over at OpenHatch:
>
> https://openhatch.org/+projects/geeklog
>
> ... and if you speak any language other than English: Most of our language
> files could benefit from an update.
>
> Thanks for offering to help!
>
> bye, Dirk
>
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From dirk at haun-online.de  Wed Jan 19 14:40:33 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 19 Jan 2011 20:40:33 +0100
Subject: [geeklog-devel] New version checker
In-Reply-To: <1294942689.3475.19.camel@roccivic-pc>
References: <000001cbaaca$c3acab60$4b060220$@cogeco.net>
	<1294942689.3475.19.camel@roccivic-pc>
Message-ID: <42D714D2-D6AC-4AB3-ADA1-436C2AB488D4@haun-online.de>

The new version checker script is now live on geeklog.net. Thanks, Rouslan!

http://www.geeklog.net/article.php/new-versionchecker

The code is available from the tools repository

http://project.geeklog.net/cgi-bin/hgwebdir.cgi/tools/

bye, Dirk



From dirk at haun-online.de  Wed Jan 19 16:55:29 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 19 Jan 2011 22:55:29 +0100
Subject: [geeklog-devel] Fosdem?
Message-ID: <7789C67E-D4B0-4638-869C-0A52A85B8460@haun-online.de>

Just checking: Is anyone going to Fosdem this year? I've never been there before, but keep hearing people rave about how great it is. So I thought I'd give it a try ...


Next stop after Fosdem will be my beloved ACCU Conference in Oxford in April. And I'll most likely be at FrOSCon in August again. I'm sure there will be one or two more conferences between those two.

Btw, I've stopped using Dopplr and switched to using TripIt and Lanyrd instead. Find / follow me there if you're interested in my whereabouts :)

bye, Dirk



From vladvoic at gmail.com  Wed Jan 19 17:14:03 2011
From: vladvoic at gmail.com (Vlad Voicu)
Date: Thu, 20 Jan 2011 00:14:03 +0200
Subject: [geeklog-devel] Fosdem?
In-Reply-To: <7789C67E-D4B0-4638-869C-0A52A85B8460@haun-online.de>
References: <7789C67E-D4B0-4638-869C-0A52A85B8460@haun-online.de>
Message-ID: <AANLkTimg9pKrcqnt6OVCL-1DPpXtBS4Kp-H8Pmdde2a-@mail.gmail.com>

> Just checking: Is anyone going to Fosdem this year? I've never been there before, but keep hearing people rave about how great it is. So I thought I'd give it a try ...

Hi,

I am attending Fosdem this year with the organization from my
University (ROSedu). We will be a bunch of guys and girls.
I will be really glad to meet you in person there.

Vladv


From dirk at haun-online.de  Wed Jan 19 17:17:10 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 19 Jan 2011 23:17:10 +0100
Subject: [geeklog-devel] Fosdem?
In-Reply-To: <AANLkTimg9pKrcqnt6OVCL-1DPpXtBS4Kp-H8Pmdde2a-@mail.gmail.com>
References: <7789C67E-D4B0-4638-869C-0A52A85B8460@haun-online.de>
	<AANLkTimg9pKrcqnt6OVCL-1DPpXtBS4Kp-H8Pmdde2a-@mail.gmail.com>
Message-ID: <F3B89FCB-0918-4672-A104-94FF24704FC0@haun-online.de>

Vlad Voicu wrote:

> I am attending Fosdem this year with the organization from my
> University (ROSedu). We will be a bunch of guys and girls.
> I will be really glad to meet you in person there.

Great! One more reason to go :) See you there.

bye, Dirk



From danstoner at gmail.com  Thu Jan 20 11:30:43 2011
From: danstoner at gmail.com (Dan Stoner)
Date: Thu, 20 Jan 2011 11:30:43 -0500
Subject: [geeklog-devel] included plugins in future releases
Message-ID: <AANLkTinCp4sL33NLMOm9KB75eW4VqZtAJp6Mi79J61rd@mail.gmail.com>

I have added some of the optional plugins to my site... now I am
concerned about the complexity of site upgrades and dealing with the
extra plugins.

I recall seeing mention that more of the 3rd party plugins are going
to be adopted / included in the core releases. Am I remembering
correctly?

In particular, I would love to see the following included:

Autotags
SocialShare

Thanks!

- Dan Stoner


From danstoner at gmail.com  Thu Jan 20 11:24:02 2011
From: danstoner at gmail.com (Dan Stoner)
Date: Thu, 20 Jan 2011 11:24:02 -0500
Subject: [geeklog-devel] [Fwd: Re: Redesign the Plugin "Editor"]
In-Reply-To: <AANLkTimYYVuNe_XPNfhsARrbPp4j+v=x7SshUNMC+52a@mail.gmail.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
	<AANLkTiktv7+b_--pF+5094QGUXfQgANuf0Qj39BwoGs=@mail.gmail.com>
	<20110118170602.56511yr4j8eomvs0@webmail.df.eu>
	<AANLkTimYYVuNe_XPNfhsARrbPp4j+v=x7SshUNMC+52a@mail.gmail.com>
Message-ID: <AANLkTikfY8ROQGmiNMkv=JbDU+aVD3uEhdLpB3UOZNTG@mail.gmail.com>

Thanks, Ben.

- Dan Stoner

On Tue, Jan 18, 2011 at 1:19 PM, cordiste <cordiste at free.fr> wrote:
> Dan very nice theme re-load on http://thatlinuxbox.com
>
> Ben
>
> 2011/1/18 Dirk Haun <dirk at haun-online.de>:
>> Quoting Dan Stoner <danstoner at gmail.com>:
>>
>>> A little bit of polish can show
>>> that GL is mature and still active.
>>
>> Good point.
>>
>>
>>> "the admin interface looks old and clunky"
>>
>> Some would say "not only the admin interface" ;-)
>>
>>
>>> I have been toying with the idea of participating more materially in
>>> GL... I would need some baby step tasks before doing anything real or
>>> important.
>>
>> You're very much welcome. There's a "Getting Started" page aimed at
>> developers on the wiki:
>>
>> http://wiki.geeklog.net/index.php/Getting_Started
>>
>> For non / not-so-much coding tasks, I've dumped the tasks we collected for
>> Google Code-In over at OpenHatch:
>>
>> https://openhatch.org/+projects/geeklog
>>
>> ... and if you speak any language other than English: Most of our language
>> files could benefit from an update.
>>
>> Thanks for offering to help!
>>
>> bye, Dirk
>>
>>
>>
>> _______________________________________________
>> geeklog-devel mailing list
>> geeklog-devel at lists.geeklog.net
>> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>>
>>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>


From rouslan at placella.com  Fri Jan 21 11:40:37 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Fri, 21 Jan 2011 16:40:37 +0000
Subject: [geeklog-devel] Plugin Version Control and Dependencies (feature
	request #0001154)
In-Reply-To: <21889.27328.qm@web31403.mail.mud.yahoo.com>
References: <4b5764dfd2d1ad895059c2d037d35b32.squirrel@mustang.hawkhost.com>
	<21889.27328.qm@web31403.mail.mud.yahoo.com>
Message-ID: <1295628037.1947.6.camel@roccivic-pc>

I'd like to implement the dependency checks for geeklog plugins (bug
#0001154).
So below I wrote down some things that I think I'll have to do for this.
Feedback? Suggestions? Opinions? Tips?

Thanks,
Rouslan.

THINGS TO DO (or to keep in mind):
* Create two database tables: 
	Store each plugin's dependencies in one table
	and each plugin's log from the latest install attempt in the other
table

	TABLE plugin_dependencies
	  pi_name      varchar(30) // Name of the plugin to which an entry
belongs
	  type         varchar(20) // 'geeklog', 'plugin', etc...
      require      varchar(30) // name of the required plugin (leave
empty if $type is 'geeklog')
	  version      varchar(20) // version of the required plugin
	  operator     varchar(10) // type of comparison, e.g: ">=" or ">"

	TABLE plugin_install_log   // here we save custom messages that are
generated when a plugin's install function is called 
	  pi_name      varchar(30)
	  type         varchar(20) // 'notice', 'info', 'warning', 'error',
etc...
	  title        TEXT        // a title
	  msg          TEXT        // a message


* Create a new plugin API call: plugin_dependencies_pluginname()
    The plugin can return a two-dimentional array containing its
dependency information and it's install log.
	Sample usage in the plugin would be:
		<?php
		// plugins/foo/autoinstall.php:
		...
		function plugin_dependencies_foo()
		{
			...
			return array(
				// This array says that the plugin 'foo' requires Geeklog version
greater than or equal to 1.8.0
				array( 'geeklog' => 'core', '1.8.0' => '>=' ),

				// This array says that the plugin 'foo' requires the calendar
plugin with version greater than 1.0.0
				array( 'plugin' => 'calendar', '1.0.0' => '>' ),

				// There can be multiple dependencies
				array( 'plugin' => 'socnet', '1.0.0' => '>=' ),

				// A message from the plugin regarding custom dependency checks
				// $type can be 'notice', 'info', 'warning', 'error', etc...
				array( 'message' => 'error', 'a title' => 'a message' ),

				// There can be multiple messages
				array( 'message' => 'info', 'another title' => 'another message' )
  
				/*  The settings will be saved to 'plugins_dependencies' table and
                    the messages to 'plugins_install_log'  */
			);
		}
		...
		?>

* Introduce a function to update and resolve dependencies, as well as
ensuring that the plugins are loaded in the correct order.
    Call this function:
		* when enabling/disabling a plugin
		* when installing/uninstalling a plugin
		* when changing plugin load order
		* when loading plugins?

* Add the "plugin editor" to uninstalled plugins.
	* If there was an install attempt and it failed, show the entries from
the "plugin_install_log" table there.
	* When warning about unresolved dependencies. Offer the options to:
"try to resolve", "proceed anyway" and "cancel operation".
	* Add a clear_install_log($plugin) function and use it before each
install so that there is only one log entry per plugin.
	* In the plugin admin, make it obvious when there is a message that was
saved during the install and it can be viewed.

* Show dependency information in the plugin editor for enabled plugins

* Show the install log in the plugin editor for enabled plugins
    It'll probably say: "Installation was successful." only, most the
time, but it could be useful to add custom information messages.

* Keep backwards compatibility with all older plugins

* Should be easy to extend to dependencies for databases (maybe even
themes and blocks, too?).

* Add a plugin_dependencies_* functions to the bundled plugins

* Document everything better than this
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110121/7358aa18/attachment.html>

From Randy.Kolenko at nextide.ca  Fri Jan 21 13:13:49 2011
From: Randy.Kolenko at nextide.ca (Randy Kolenko)
Date: Fri, 21 Jan 2011 13:13:49 -0500
Subject: [geeklog-devel] Plugin Version Control and Dependencies
	(featurerequest #0001154)
Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>

Just out of curiosity ? why store anything in a table?

 

The information required to install a plugin is easily pulled back by the plugin admin page by querying each plugin, and populated on the screen.  If a plugin is missing a dependency, don?t allow it to be installed and simply show the dependency information below the plugin and the associated status of each dependency (installed, disabled, missing etc).

 

Like I noted before, we?ve done all this with Nexpro ? the plugin page is all that really needs to be updated to support hiding the install button and showing the dependencies.  For Nexpro, each config file for each plugin has its own dependency list.  We do a version_compare and determine if the required plugin is there or not in the autoinstall.php file.  

 

 

From: Rouslan Placella [mailto:rouslan at placella.com] 
Sent: Friday, January 21, 2011 11:41 AM
To: Geeklog Development
Subject: [geeklog-devel] Plugin Version Control and Dependencies (featurerequest #0001154)

 

I'd like to implement the dependency checks for geeklog plugins (bug #0001154).
So below I wrote down some things that I think I'll have to do for this.
Feedback? Suggestions? Opinions? Tips?

Thanks,
Rouslan.

THINGS TO DO (or to keep in mind):
* Create two database tables: 
Store each plugin's dependencies in one table
and each plugin's log from the latest install attempt in the other table

TABLE plugin_dependencies
  pi_name      varchar(30) // Name of the plugin to which an entry belongs
  type         varchar(20) // 'geeklog', 'plugin', etc...
      require      varchar(30) // name of the required plugin (leave empty if $type is 'geeklog')
  version      varchar(20) // version of the required plugin
  operator     varchar(10) // type of comparison, e.g: ">=" or ">"

TABLE plugin_install_log   // here we save custom messages that are generated when a plugin's install function is called 
  pi_name      varchar(30)
  type         varchar(20) // 'notice', 'info', 'warning', 'error', etc...
  title        TEXT        // a title
  msg          TEXT        // a message


* Create a new plugin API call: plugin_dependencies_pluginname()
    The plugin can return a two-dimentional array containing its dependency information and it's install log.
Sample usage in the plugin would be:
<?php
// plugins/foo/autoinstall.php:
...
function plugin_dependencies_foo()
{
...
return array(
// This array says that the plugin 'foo' requires Geeklog version greater than or equal to 1.8.0
array( 'geeklog' => 'core', '1.8.0' => '>=' ),

// This array says that the plugin 'foo' requires the calendar plugin with version greater than 1.0.0
array( 'plugin' => 'calendar', '1.0.0' => '>' ),

// There can be multiple dependencies
array( 'plugin' => 'socnet', '1.0.0' => '>=' ),

// A message from the plugin regarding custom dependency checks
// $type can be 'notice', 'info', 'warning', 'error', etc...
array( 'message' => 'error', 'a title' => 'a message' ),

// There can be multiple messages
array( 'message' => 'info', 'another title' => 'another message' )
  
/*  The settings will be saved to 'plugins_dependencies' table and
                    the messages to 'plugins_install_log'  */
);
}
...
?>

* Introduce a function to update and resolve dependencies, as well as ensuring that the plugins are loaded in the correct order.
    Call this function:
* when enabling/disabling a plugin
* when installing/uninstalling a plugin
* when changing plugin load order
* when loading plugins?

* Add the "plugin editor" to uninstalled plugins.
* If there was an install attempt and it failed, show the entries from the "plugin_install_log" table there.
* When warning about unresolved dependencies. Offer the options to: "try to resolve", "proceed anyway" and "cancel operation".
* Add a clear_install_log($plugin) function and use it before each install so that there is only one log entry per plugin.
* In the plugin admin, make it obvious when there is a message that was saved during the install and it can be viewed.

* Show dependency information in the plugin editor for enabled plugins

* Show the install log in the plugin editor for enabled plugins
    It'll probably say: "Installation was successful." only, most the time, but it could be useful to add custom information messages.

* Keep backwards compatibility with all older plugins

* Should be easy to extend to dependencies for databases (maybe even themes and blocks, too?).

* Add a plugin_dependencies_* functions to the bundled plugins

* Document everything better than this 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110121/322611ec/attachment.html>

From vfuria at gmail.com  Sat Jan 22 00:36:30 2011
From: vfuria at gmail.com (Vincent Furia)
Date: Fri, 21 Jan 2011 22:36:30 -0700
Subject: [geeklog-devel] Plugin Version Control and Dependencies
 (featurerequest #0001154)
In-Reply-To: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>
References: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>
Message-ID: <AANLkTinCHv4yNDHvmvFycjwG-bpXMBuHtbcvaZkGd3JO@mail.gmail.com>

I'm with Randy. I think a single new API call should be sufficient.

-Vinny

On Fri, Jan 21, 2011 at 11:13, Randy Kolenko <Randy.Kolenko at nextide.ca>wrote:

>  Just out of curiosity ? why store anything in a table?
>
>
>
> The information required to install a plugin is easily pulled back by the
> plugin admin page by querying each plugin, and populated on the screen.  If
> a plugin is missing a dependency, don?t allow it to be installed and simply
> show the dependency information below the plugin and the associated status
> of each dependency (installed, disabled, missing etc).
>
>
>
> Like I noted before, we?ve done all this with Nexpro ? the plugin page is
> all that really needs to be updated to support hiding the install button and
> showing the dependencies.  For Nexpro, each config file for each plugin has
> its own dependency list.  We do a version_compare and determine if the
> required plugin is there or not in the autoinstall.php file.
>
>
>
>
>
> *From:* Rouslan Placella [mailto:rouslan at placella.com]
> *Sent:* Friday, January 21, 2011 11:41 AM
> *To:* Geeklog Development
> *Subject:* [geeklog-devel] Plugin Version Control and Dependencies
> (featurerequest #0001154)
>
>
>
> I'd like to implement the dependency checks for geeklog plugins (bug
> #0001154).
> So below I wrote down some things that I think I'll have to do for this.
> Feedback? Suggestions? Opinions? Tips?
>
> Thanks,
> Rouslan.
>
> THINGS TO DO (or to keep in mind):
> * Create two database tables:
> Store each plugin's dependencies in one table
> and each plugin's log from the latest install attempt in the other table
>
> TABLE plugin_dependencies
>   pi_name      varchar(30) // Name of the plugin to which an entry belongs
>   type         varchar(20) // 'geeklog', 'plugin', etc...
>       require      varchar(30) // name of the required plugin (leave empty
> if $type is 'geeklog')
>   version      varchar(20) // version of the required plugin
>   operator     varchar(10) // type of comparison, e.g: ">=" or ">"
>
> TABLE plugin_install_log   // here we save custom messages that are
> generated when a plugin's install function is called
>   pi_name      varchar(30)
>   type         varchar(20) // 'notice', 'info', 'warning', 'error', etc...
>   title        TEXT        // a title
>   msg          TEXT        // a message
>
>
> * Create a new plugin API call: plugin_dependencies_pluginname()
>     The plugin can return a two-dimentional array containing its dependency
> information and it's install log.
> Sample usage in the plugin would be:
> <?php
> // plugins/foo/autoinstall.php:
> ...
> function plugin_dependencies_foo()
> {
> ...
> return array(
> // This array says that the plugin 'foo' requires Geeklog version greater
> than or equal to 1.8.0
> array( 'geeklog' => 'core', '1.8.0' => '>=' ),
>
> // This array says that the plugin 'foo' requires the calendar plugin with
> version greater than 1.0.0
> array( 'plugin' => 'calendar', '1.0.0' => '>' ),
>
> // There can be multiple dependencies
> array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
>
> // A message from the plugin regarding custom dependency checks
> // $type can be 'notice', 'info', 'warning', 'error', etc...
> array( 'message' => 'error', 'a title' => 'a message' ),
>
> // There can be multiple messages
> array( 'message' => 'info', 'another title' => 'another message' )
>
> /*  The settings will be saved to 'plugins_dependencies' table and
>                     the messages to 'plugins_install_log'  */
> );
> }
> ...
> ?>
>
> * Introduce a function to update and resolve dependencies, as well as
> ensuring that the plugins are loaded in the correct order.
>     Call this function:
> * when enabling/disabling a plugin
> * when installing/uninstalling a plugin
> * when changing plugin load order
> * when loading plugins?
>
> * Add the "plugin editor" to uninstalled plugins.
> * If there was an install attempt and it failed, show the entries from the
> "plugin_install_log" table there.
> * When warning about unresolved dependencies. Offer the options to: "try to
> resolve", "proceed anyway" and "cancel operation".
> * Add a clear_install_log($plugin) function and use it before each install
> so that there is only one log entry per plugin.
> * In the plugin admin, make it obvious when there is a message that was
> saved during the install and it can be viewed.
>
> * Show dependency information in the plugin editor for enabled plugins
>
> * Show the install log in the plugin editor for enabled plugins
>     It'll probably say: "Installation was successful." only, most the time,
> but it could be useful to add custom information messages.
>
> * Keep backwards compatibility with all older plugins
>
> * Should be easy to extend to dependencies for databases (maybe even themes
> and blocks, too?).
>
> * Add a plugin_dependencies_* functions to the bundled plugins
>
> * Document everything better than this
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110121/dc3bd518/attachment.html>

From rouslan at placella.com  Sat Jan 22 09:09:47 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Sat, 22 Jan 2011 14:09:47 +0000
Subject: [geeklog-devel] Plugin Version Control and Dependencies
 (featurerequest #0001154)
In-Reply-To: <AANLkTinCHv4yNDHvmvFycjwG-bpXMBuHtbcvaZkGd3JO@mail.gmail.com>
References: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>
	<AANLkTinCHv4yNDHvmvFycjwG-bpXMBuHtbcvaZkGd3JO@mail.gmail.com>
Message-ID: <1295705387.2045.12.camel@roccivic-pc>

I started a bit of work on this and, yeah, I get it. And I also see that
there is no need for that API call either. The plugins that use the new
install, return install parameters through
plugin_autoinstall_myplugin(). And they could just add the dependency
information to the array that they normally return. Then it would be
geeklog's responsibility to resolve those dependencies.

Rouslan


On Fri, 2011-01-21 at 22:36 -0700, Vincent Furia wrote:
> I'm with Randy. I think a single new API call should be sufficient.
> 
> 
> -Vinny
> 
> On Fri, Jan 21, 2011 at 11:13, Randy Kolenko
> <Randy.Kolenko at nextide.ca> wrote:
>         Just out of curiosity ? why store anything in a table?
>         
>          
>         
>         The information required to install a plugin is easily pulled
>         back by the plugin admin page by querying each plugin, and
>         populated on the screen.  If a plugin is missing a dependency,
>         don?t allow it to be installed and simply show the dependency
>         information below the plugin and the associated status of each
>         dependency (installed, disabled, missing etc).
>         
>          
>         
>         Like I noted before, we?ve done all this with Nexpro ? the
>         plugin page is all that really needs to be updated to support
>         hiding the install button and showing the dependencies.  For
>         Nexpro, each config file for each plugin has its own
>         dependency list.  We do a version_compare and determine if the
>         required plugin is there or not in the autoinstall.php file.  
>         
>          
>         
>          
>         
>         From: Rouslan Placella [mailto:rouslan at placella.com] 
>         Sent: Friday, January 21, 2011 11:41 AM
>         To: Geeklog Development
>         Subject: [geeklog-devel] Plugin Version Control and
>         Dependencies (featurerequest #0001154)
>         
>         
>         
>          
>         
>         I'd like to implement the dependency checks for geeklog
>         plugins (bug #0001154).
>         So below I wrote down some things that I think I'll have to do
>         for this.
>         Feedback? Suggestions? Opinions? Tips?
>         
>         Thanks,
>         Rouslan.
>         
>         THINGS TO DO (or to keep in mind):
>         * Create two database tables: 
>         Store each plugin's dependencies in one table
>         and each plugin's log from the latest install attempt in the
>         other table
>         
>         TABLE plugin_dependencies
>           pi_name      varchar(30) // Name of the plugin to which an
>         entry belongs
>           type         varchar(20) // 'geeklog', 'plugin', etc...
>               require      varchar(30) // name of the required plugin
>         (leave empty if $type is 'geeklog')
>           version      varchar(20) // version of the required plugin
>           operator     varchar(10) // type of comparison, e.g: ">=" or
>         ">"
>         
>         TABLE plugin_install_log   // here we save custom messages
>         that are generated when a plugin's install function is called 
>           pi_name      varchar(30)
>           type         varchar(20) // 'notice', 'info', 'warning',
>         'error', etc...
>           title        TEXT        // a title
>           msg          TEXT        // a message
>         
>         
>         * Create a new plugin API call:
>         plugin_dependencies_pluginname()
>             The plugin can return a two-dimentional array containing
>         its dependency information and it's install log.
>         Sample usage in the plugin would be:
>         <?php
>         // plugins/foo/autoinstall.php:
>         ...
>         function plugin_dependencies_foo()
>         {
>         ...
>         return array(
>         // This array says that the plugin 'foo' requires Geeklog
>         version greater than or equal to 1.8.0
>         array( 'geeklog' => 'core', '1.8.0' => '>=' ),
>         
>         // This array says that the plugin 'foo' requires the calendar
>         plugin with version greater than 1.0.0
>         array( 'plugin' => 'calendar', '1.0.0' => '>' ),
>         
>         // There can be multiple dependencies
>         array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
>         
>         // A message from the plugin regarding custom dependency
>         checks
>         // $type can be 'notice', 'info', 'warning', 'error', etc...
>         array( 'message' => 'error', 'a title' => 'a message' ),
>         
>         // There can be multiple messages
>         array( 'message' => 'info', 'another title' => 'another
>         message' )
>           
>         /*  The settings will be saved to 'plugins_dependencies' table
>         and
>                             the messages to 'plugins_install_log'  */
>         );
>         }
>         ...
>         ?>
>         
>         * Introduce a function to update and resolve dependencies, as
>         well as ensuring that the plugins are loaded in the correct
>         order.
>             Call this function:
>         * when enabling/disabling a plugin
>         * when installing/uninstalling a plugin
>         * when changing plugin load order
>         * when loading plugins?
>         
>         * Add the "plugin editor" to uninstalled plugins.
>         * If there was an install attempt and it failed, show the
>         entries from the "plugin_install_log" table there.
>         * When warning about unresolved dependencies. Offer the
>         options to: "try to resolve", "proceed anyway" and "cancel
>         operation".
>         * Add a clear_install_log($plugin) function and use it before
>         each install so that there is only one log entry per plugin.
>         * In the plugin admin, make it obvious when there is a message
>         that was saved during the install and it can be viewed.
>         
>         * Show dependency information in the plugin editor for enabled
>         plugins
>         
>         * Show the install log in the plugin editor for enabled
>         plugins
>             It'll probably say: "Installation was successful." only,
>         most the time, but it could be useful to add custom
>         information messages.
>         
>         * Keep backwards compatibility with all older plugins
>         
>         * Should be easy to extend to dependencies for databases
>         (maybe even themes and blocks, too?).
>         
>         * Add a plugin_dependencies_* functions to the bundled plugins
>         
>         * Document everything better than this 
>         
>         
>         
>         _______________________________________________
>         geeklog-devel mailing list
>         geeklog-devel at lists.geeklog.net
>         http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>         
> 
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel




From websitemaster at cogeco.net  Sat Jan 22 09:50:07 2011
From: websitemaster at cogeco.net (Tom)
Date: Sat, 22 Jan 2011 09:50:07 -0500
Subject: [geeklog-devel] Plugin Version Control and Dependencies
	(featurerequest #0001154)
In-Reply-To: <1295705387.2045.12.camel@roccivic-pc>
References: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>	<AANLkTinCHv4yNDHvmvFycjwG-bpXMBuHtbcvaZkGd3JO@mail.gmail.com>
	<1295705387.2045.12.camel@roccivic-pc>
Message-ID: <005901cbba43$a9337c90$fb9a75b0$@cogeco.net>

I like your array idea of 

// There can be multiple dependencies
array( 'plugin' => 'socnet', '1.0.0' => '>=' ),


This way if a plugin needs to it could state it only supports a plugin within a certain version range.
array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
array( 'plugin' => 'socnet', '2.0.0' => '<' ),

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan Placella
Sent: January-22-11 9:10 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Plugin Version Control and Dependencies (featurerequest #0001154)

I started a bit of work on this and, yeah, I get it. And I also see that there is no need for that API call either. The plugins that use the new install, return install parameters through plugin_autoinstall_myplugin(). And they could just add the dependency information to the array that they normally return. Then it would be geeklog's responsibility to resolve those dependencies.

Rouslan


On Fri, 2011-01-21 at 22:36 -0700, Vincent Furia wrote:
> I'm with Randy. I think a single new API call should be sufficient.
> 
> 
> -Vinny
> 
> On Fri, Jan 21, 2011 at 11:13, Randy Kolenko 
> <Randy.Kolenko at nextide.ca> wrote:
>         Just out of curiosity ? why store anything in a table?
>         
>          
>         
>         The information required to install a plugin is easily pulled
>         back by the plugin admin page by querying each plugin, and
>         populated on the screen.  If a plugin is missing a dependency,
>         don?t allow it to be installed and simply show the dependency
>         information below the plugin and the associated status of each
>         dependency (installed, disabled, missing etc).
>         
>          
>         
>         Like I noted before, we?ve done all this with Nexpro ? the
>         plugin page is all that really needs to be updated to support
>         hiding the install button and showing the dependencies.  For
>         Nexpro, each config file for each plugin has its own
>         dependency list.  We do a version_compare and determine if the
>         required plugin is there or not in the autoinstall.php file.  
>         
>          
>         
>          
>         
>         From: Rouslan Placella [mailto:rouslan at placella.com] 
>         Sent: Friday, January 21, 2011 11:41 AM
>         To: Geeklog Development
>         Subject: [geeklog-devel] Plugin Version Control and
>         Dependencies (featurerequest #0001154)
>         
>         
>         
>          
>         
>         I'd like to implement the dependency checks for geeklog
>         plugins (bug #0001154).
>         So below I wrote down some things that I think I'll have to do
>         for this.
>         Feedback? Suggestions? Opinions? Tips?
>         
>         Thanks,
>         Rouslan.
>         
>         THINGS TO DO (or to keep in mind):
>         * Create two database tables: 
>         Store each plugin's dependencies in one table
>         and each plugin's log from the latest install attempt in the
>         other table
>         
>         TABLE plugin_dependencies
>           pi_name      varchar(30) // Name of the plugin to which an
>         entry belongs
>           type         varchar(20) // 'geeklog', 'plugin', etc...
>               require      varchar(30) // name of the required plugin
>         (leave empty if $type is 'geeklog')
>           version      varchar(20) // version of the required plugin
>           operator     varchar(10) // type of comparison, e.g: ">=" or
>         ">"
>         
>         TABLE plugin_install_log   // here we save custom messages
>         that are generated when a plugin's install function is called 
>           pi_name      varchar(30)
>           type         varchar(20) // 'notice', 'info', 'warning',
>         'error', etc...
>           title        TEXT        // a title
>           msg          TEXT        // a message
>         
>         
>         * Create a new plugin API call:
>         plugin_dependencies_pluginname()
>             The plugin can return a two-dimentional array containing
>         its dependency information and it's install log.
>         Sample usage in the plugin would be:
>         <?php
>         // plugins/foo/autoinstall.php:
>         ...
>         function plugin_dependencies_foo()
>         {
>         ...
>         return array(
>         // This array says that the plugin 'foo' requires Geeklog
>         version greater than or equal to 1.8.0
>         array( 'geeklog' => 'core', '1.8.0' => '>=' ),
>         
>         // This array says that the plugin 'foo' requires the calendar
>         plugin with version greater than 1.0.0
>         array( 'plugin' => 'calendar', '1.0.0' => '>' ),
>         
>         // There can be multiple dependencies
>         array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
>         
>         // A message from the plugin regarding custom dependency
>         checks
>         // $type can be 'notice', 'info', 'warning', 'error', etc...
>         array( 'message' => 'error', 'a title' => 'a message' ),
>         
>         // There can be multiple messages
>         array( 'message' => 'info', 'another title' => 'another
>         message' )
>           
>         /*  The settings will be saved to 'plugins_dependencies' table
>         and
>                             the messages to 'plugins_install_log'  */
>         );
>         }
>         ...
>         ?>
>         
>         * Introduce a function to update and resolve dependencies, as
>         well as ensuring that the plugins are loaded in the correct
>         order.
>             Call this function:
>         * when enabling/disabling a plugin
>         * when installing/uninstalling a plugin
>         * when changing plugin load order
>         * when loading plugins?
>         
>         * Add the "plugin editor" to uninstalled plugins.
>         * If there was an install attempt and it failed, show the
>         entries from the "plugin_install_log" table there.
>         * When warning about unresolved dependencies. Offer the
>         options to: "try to resolve", "proceed anyway" and "cancel
>         operation".
>         * Add a clear_install_log($plugin) function and use it before
>         each install so that there is only one log entry per plugin.
>         * In the plugin admin, make it obvious when there is a message
>         that was saved during the install and it can be viewed.
>         
>         * Show dependency information in the plugin editor for enabled
>         plugins
>         
>         * Show the install log in the plugin editor for enabled
>         plugins
>             It'll probably say: "Installation was successful." only,
>         most the time, but it could be useful to add custom
>         information messages.
>         
>         * Keep backwards compatibility with all older plugins
>         
>         * Should be easy to extend to dependencies for databases
>         (maybe even themes and blocks, too?).
>         
>         * Add a plugin_dependencies_* functions to the bundled plugins
>         
>         * Document everything better than this
>         
>         
>         
>         _______________________________________________
>         geeklog-devel mailing list
>         geeklog-devel at lists.geeklog.net
>         http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>         
> 
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel


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



From websitemaster at cogeco.net  Sun Jan 23 10:25:52 2011
From: websitemaster at cogeco.net (Tom)
Date: Sun, 23 Jan 2011 10:25:52 -0500
Subject: [geeklog-devel] Geeklog Professional CSS theme
Message-ID: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>

Hey All,

Soon I will be adding a new theme to the repository that will hopefully
replace our current default theme for version 1.8.0 after some work/tweaks
has been done on it. It will be in a directory called professional_css. The
themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is available
for download on Geeklog.net (look for ProfessionalCSS_en). To start, I would
like to thank them for all of the work they have put into the theme. 

Besides eliminating table tags this theme does a number of things
differently. So if you are interested, I would suggest at least downloading
the theme and take a look at the readme file for more information. If people
disagree on how certain things are done in the theme I would like to hear
about it now before more work gets put into this.

Before I add the theme to the repository, I will be updating the theme to
support the new template changes we have currently in 1.8.0 along with
adding the new images Rouslan did for us. Once the new theme gets added into
the repository if anyone does any theme changes, like adding new template
variables or theme files, please make sure to also add them to the new
theme.

I do not expect this new theme to look exactly the same as our current
default theme. It will look similar but if some things are changed around
for the better, then I am all for it. The one thing I do not plan on
changing is the color scheme. Rouslan has already put a lot of work into the
new logo and icons for the site. We can save the major theme design changes
and page designs like this for when we start the new site redesign at a
later date.

Once I have the new theme in the repository, people are more than welcome to
help out. Let's just communicate through email or on the mailing list just
to makes sure we know what we are all working on.

The first thing I will be doing is working on the general layout which
actually brings me to my first question.

The new theme is currently has a fixed width of 960 pixels. I would actually
like to keep the width fixed as I think it looks much better on the larger
monitors most people use these days. It also makes designing new pages
easier.

To help in the decision I took a look at Google Analytics for a site that
gets a large number of North American visitors. Here are the top ten screen
resolutions:

1. 1280x800  	19.60%  
2. 1024x768  	15.41%  
3. 1366x768  	11.45%  
4. 1440x900  	7.73%  
5. 1280x1024  	5.77%  
6. 320x480  	5.16%  
7. 1680x1050	4.35%  
8. 1920x1080	3.10%  
9. 1600x900	2.56%  
10. 1920x1200	2.03%

For those of you who are interested, here is some info on what browsers are
being used:

1. Internet Explorer		 40.01%  
2. Firefox			26.77%  
3. Safari			17.87%  
4. Chrome			11.69%  
5. Opera			1.06%  
6. Mozilla Compatible Agent	0.79%  
7. Opera Mini			0.76%  
8. BlackBerry8530		0.15%  
9. BlackBerry9700		0.13%  
10. Mozilla			0.11%

And since Java Support is an issue for some of the Admin configuration:

1. Yes  	78.75%  
2. No	21.25%

Thanks

Tom



From dirk at haun-online.de  Mon Jan 24 06:01:02 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 24 Jan 2011 12:01:02 +0100
Subject: [geeklog-devel] GSoC 2011 announced
Message-ID: <20110124120102.18566t3vg8gswu0g@webmail.df.eu>

... more or less:

http://twitter.com/#!/fossygrl/status/29401409560510464
http://www.google-melange.com/

So, have you all been collecting ideas for possible GSoC projects?  
Time to flesh them out somewhat and add them to the wiki. Also, as  
every year: Mentors wanted!

bye, Dirk





From cordiste at free.fr  Mon Jan 24 10:31:16 2011
From: cordiste at free.fr (cordiste)
Date: Mon, 24 Jan 2011 16:31:16 +0100
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
Message-ID: <AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>

Tom,

Do you get the total % for screens under 960px?

Ben


2011/1/23 Tom <websitemaster at cogeco.net>:
> Hey All,
>
> Soon I will be adding a new theme to the repository that will hopefully
> replace our current default theme for version 1.8.0 after some work/tweaks
> has been done on it. It will be in a directory called professional_css. The
> themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is available
> for download on Geeklog.net (look for ProfessionalCSS_en). To start, I would
> like to thank them for all of the work they have put into the theme.
>
> Besides eliminating table tags this theme does a number of things
> differently. So if you are interested, I would suggest at least downloading
> the theme and take a look at the readme file for more information. If people
> disagree on how certain things are done in the theme I would like to hear
> about it now before more work gets put into this.
>
> Before I add the theme to the repository, I will be updating the theme to
> support the new template changes we have currently in 1.8.0 along with
> adding the new images Rouslan did for us. Once the new theme gets added into
> the repository if anyone does any theme changes, like adding new template
> variables or theme files, please make sure to also add them to the new
> theme.
>
> I do not expect this new theme to look exactly the same as our current
> default theme. It will look similar but if some things are changed around
> for the better, then I am all for it. The one thing I do not plan on
> changing is the color scheme. Rouslan has already put a lot of work into the
> new logo and icons for the site. We can save the major theme design changes
> and page designs like this for when we start the new site redesign at a
> later date.
>
> Once I have the new theme in the repository, people are more than welcome to
> help out. Let's just communicate through email or on the mailing list just
> to makes sure we know what we are all working on.
>
> The first thing I will be doing is working on the general layout which
> actually brings me to my first question.
>
> The new theme is currently has a fixed width of 960 pixels. I would actually
> like to keep the width fixed as I think it looks much better on the larger
> monitors most people use these days. It also makes designing new pages
> easier.
>
> To help in the decision I took a look at Google Analytics for a site that
> gets a large number of North American visitors. Here are the top ten screen
> resolutions:
>
> 1. 1280x800 ? ? 19.60%
> 2. 1024x768 ? ? 15.41%
> 3. 1366x768 ? ? 11.45%
> 4. 1440x900 ? ? 7.73%
> 5. 1280x1024 ? ?5.77%
> 6. 320x480 ? ? ?5.16%
> 7. 1680x1050 ? ?4.35%
> 8. 1920x1080 ? ?3.10%
> 9. 1600x900 ? ? 2.56%
> 10. 1920x1200 ? 2.03%
>
> For those of you who are interested, here is some info on what browsers are
> being used:
>
> 1. Internet Explorer ? ? ? ? ? ? 40.01%
> 2. Firefox ? ? ? ? ? ? ? ? ? ? ?26.77%
> 3. Safari ? ? ? ? ? ? ? ? ? ? ? 17.87%
> 4. Chrome ? ? ? ? ? ? ? ? ? ? ? 11.69%
> 5. Opera ? ? ? ? ? ? ? ? ? ? ? ?1.06%
> 6. Mozilla Compatible Agent ? ? 0.79%
> 7. Opera Mini ? ? ? ? ? ? ? ? ? 0.76%
> 8. BlackBerry8530 ? ? ? ? ? ? ? 0.15%
> 9. BlackBerry9700 ? ? ? ? ? ? ? 0.13%
> 10. Mozilla ? ? ? ? ? ? ? ? ? ? 0.11%
>
> And since Java Support is an issue for some of the Admin configuration:
>
> 1. Yes ? ? ? ? ?78.75%
> 2. No ? 21.25%
>
> Thanks
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From vfuria at gmail.com  Mon Jan 24 10:53:57 2011
From: vfuria at gmail.com (Vincent Furia)
Date: Mon, 24 Jan 2011 08:53:57 -0700
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
	<AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>
Message-ID: <AANLkTinb8xknvWydp+ufkdpdA6TsXxS0yqyzySWUZnE-@mail.gmail.com>

I'd modify (or add to that question): What percent of screens are under
960px wide and are not mobile devices.

I expect all of the "6. 320x480      5.16%" screens are mobile devices.

Which brings up the question: with that many mobile users should we put some
work into creating a mobile theme that turns on by auto-detection of device
type (or screen resolution?)?

-Vinny

On Mon, Jan 24, 2011 at 08:31, cordiste <cordiste at free.fr> wrote:

> Tom,
>
> Do you get the total % for screens under 960px?
>
> Ben
>
>
> 2011/1/23 Tom <websitemaster at cogeco.net>:
> > Hey All,
> >
> > Soon I will be adding a new theme to the repository that will hopefully
> > replace our current default theme for version 1.8.0 after some
> work/tweaks
> > has been done on it. It will be in a directory called professional_css.
> The
> > themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is
> available
> > for download on Geeklog.net (look for ProfessionalCSS_en). To start, I
> would
> > like to thank them for all of the work they have put into the theme.
> >
> > Besides eliminating table tags this theme does a number of things
> > differently. So if you are interested, I would suggest at least
> downloading
> > the theme and take a look at the readme file for more information. If
> people
> > disagree on how certain things are done in the theme I would like to hear
> > about it now before more work gets put into this.
> >
> > Before I add the theme to the repository, I will be updating the theme to
> > support the new template changes we have currently in 1.8.0 along with
> > adding the new images Rouslan did for us. Once the new theme gets added
> into
> > the repository if anyone does any theme changes, like adding new template
> > variables or theme files, please make sure to also add them to the new
> > theme.
> >
> > I do not expect this new theme to look exactly the same as our current
> > default theme. It will look similar but if some things are changed around
> > for the better, then I am all for it. The one thing I do not plan on
> > changing is the color scheme. Rouslan has already put a lot of work into
> the
> > new logo and icons for the site. We can save the major theme design
> changes
> > and page designs like this for when we start the new site redesign at a
> > later date.
> >
> > Once I have the new theme in the repository, people are more than welcome
> to
> > help out. Let's just communicate through email or on the mailing list
> just
> > to makes sure we know what we are all working on.
> >
> > The first thing I will be doing is working on the general layout which
> > actually brings me to my first question.
> >
> > The new theme is currently has a fixed width of 960 pixels. I would
> actually
> > like to keep the width fixed as I think it looks much better on the
> larger
> > monitors most people use these days. It also makes designing new pages
> > easier.
> >
> > To help in the decision I took a look at Google Analytics for a site that
> > gets a large number of North American visitors. Here are the top ten
> screen
> > resolutions:
> >
> > 1. 1280x800     19.60%
> > 2. 1024x768     15.41%
> > 3. 1366x768     11.45%
> > 4. 1440x900     7.73%
> > 5. 1280x1024    5.77%
> > 6. 320x480      5.16%
> > 7. 1680x1050    4.35%
> > 8. 1920x1080    3.10%
> > 9. 1600x900     2.56%
> > 10. 1920x1200   2.03%
> >
> > For those of you who are interested, here is some info on what browsers
> are
> > being used:
> >
> > 1. Internet Explorer             40.01%
> > 2. Firefox                      26.77%
> > 3. Safari                       17.87%
> > 4. Chrome                       11.69%
> > 5. Opera                        1.06%
> > 6. Mozilla Compatible Agent     0.79%
> > 7. Opera Mini                   0.76%
> > 8. BlackBerry8530               0.15%
> > 9. BlackBerry9700               0.13%
> > 10. Mozilla                     0.11%
> >
> > And since Java Support is an issue for some of the Admin configuration:
> >
> > 1. Yes          78.75%
> > 2. No   21.25%
> >
> > Thanks
> >
> > Tom
> >
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> >
> >
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110124/7d568458/attachment.html>

From danstoner at gmail.com  Mon Jan 24 12:51:16 2011
From: danstoner at gmail.com (Dan Stoner)
Date: Mon, 24 Jan 2011 12:51:16 -0500
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
Message-ID: <AANLkTikTRTtd80a75hOj=EUf7bOF-k_VQqsfWW7u32+o@mail.gmail.com>

Am I correct that the current Professional theme (as seen on
geeklog.net site) uses a fluid layout (fixed width for the blocks, but
"fluid with a minimum width" for the center content)?

And the new theme would change this to a "fixed" width overall?

Do you know how this will look for people running a two column layout
rather than three?


So I was about to spout my personal angst against sites that are
locked to narrow widths and prevent me from using all the screen real
estate on my hard-earned 1920x1200 monitor... but then I looked at the
web sites of the "big three" CMSes:

All are "Fixed Width" at 960px (drupal actually uses 940px for some
content nodes).

Note: The reported widths are from the project web sites, which may or
may not match the default theme from a fresh install of each project.
I got the widths by inspecting the site with the Firefox Web Developer
extension.

See:
http://wordpress.org/news:
http://www.joomla.org/about-joomla.html
http://drupal.org/about


So as much as I have a personal preference for fluid layouts, it seems
that 960 fixed width would be a good choice for the default theme.


Some references:

http://sixrevisions.com/web_design/a-guide-on-layout-types-in-web-design/
http://www.peachpit.com/articles/article.aspx?p=1324265

Cheers!

- Dan Stoner


On Sun, Jan 23, 2011 at 10:25 AM, Tom <websitemaster at cogeco.net> wrote:
> Hey All,
>
> Soon I will be adding a new theme to the repository that will hopefully
> replace our current default theme for version 1.8.0 after some work/tweaks
> has been done on it. It will be in a directory called professional_css. The
> themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is available
> for download on Geeklog.net (look for ProfessionalCSS_en). To start, I would
> like to thank them for all of the work they have put into the theme.
>
> Besides eliminating table tags this theme does a number of things
> differently. So if you are interested, I would suggest at least downloading
> the theme and take a look at the readme file for more information. If people
> disagree on how certain things are done in the theme I would like to hear
> about it now before more work gets put into this.
>
> Before I add the theme to the repository, I will be updating the theme to
> support the new template changes we have currently in 1.8.0 along with
> adding the new images Rouslan did for us. Once the new theme gets added into
> the repository if anyone does any theme changes, like adding new template
> variables or theme files, please make sure to also add them to the new
> theme.
>
> I do not expect this new theme to look exactly the same as our current
> default theme. It will look similar but if some things are changed around
> for the better, then I am all for it. The one thing I do not plan on
> changing is the color scheme. Rouslan has already put a lot of work into the
> new logo and icons for the site. We can save the major theme design changes
> and page designs like this for when we start the new site redesign at a
> later date.
>
> Once I have the new theme in the repository, people are more than welcome to
> help out. Let's just communicate through email or on the mailing list just
> to makes sure we know what we are all working on.
>
> The first thing I will be doing is working on the general layout which
> actually brings me to my first question.
>
> The new theme is currently has a fixed width of 960 pixels. I would actually
> like to keep the width fixed as I think it looks much better on the larger
> monitors most people use these days. It also makes designing new pages
> easier.
>
> To help in the decision I took a look at Google Analytics for a site that
> gets a large number of North American visitors. Here are the top ten screen
> resolutions:
>
> 1. 1280x800 ? ? 19.60%
> 2. 1024x768 ? ? 15.41%
> 3. 1366x768 ? ? 11.45%
> 4. 1440x900 ? ? 7.73%
> 5. 1280x1024 ? ?5.77%
> 6. 320x480 ? ? ?5.16%
> 7. 1680x1050 ? ?4.35%
> 8. 1920x1080 ? ?3.10%
> 9. 1600x900 ? ? 2.56%
> 10. 1920x1200 ? 2.03%
>
> For those of you who are interested, here is some info on what browsers are
> being used:
>
> 1. Internet Explorer ? ? ? ? ? ? 40.01%
> 2. Firefox ? ? ? ? ? ? ? ? ? ? ?26.77%
> 3. Safari ? ? ? ? ? ? ? ? ? ? ? 17.87%
> 4. Chrome ? ? ? ? ? ? ? ? ? ? ? 11.69%
> 5. Opera ? ? ? ? ? ? ? ? ? ? ? ?1.06%
> 6. Mozilla Compatible Agent ? ? 0.79%
> 7. Opera Mini ? ? ? ? ? ? ? ? ? 0.76%
> 8. BlackBerry8530 ? ? ? ? ? ? ? 0.15%
> 9. BlackBerry9700 ? ? ? ? ? ? ? 0.13%
> 10. Mozilla ? ? ? ? ? ? ? ? ? ? 0.11%
>
> And since Java Support is an issue for some of the Admin configuration:
>
> 1. Yes ? ? ? ? ?78.75%
> 2. No ? 21.25%
>
> Thanks
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>


From dirk at haun-online.de  Mon Jan 24 14:20:43 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 24 Jan 2011 20:20:43 +0100
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <AANLkTikTRTtd80a75hOj=EUf7bOF-k_VQqsfWW7u32+o@mail.gmail.com>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
	<AANLkTikTRTtd80a75hOj=EUf7bOF-k_VQqsfWW7u32+o@mail.gmail.com>
Message-ID: <11D47865-D618-44D8-B1DA-ED8A72359025@haun-online.de>

Dan Stoner wrote:

> So I was about to spout my personal angst against sites that are
> locked to narrow widths and prevent me from using all the screen real
> estate on my hard-earned 1920x1200 monitor... but then I looked at the
> web sites of the "big three" CMSes:
> 
> All are "Fixed Width" at 960px (drupal actually uses 940px for some
> content nodes).

I'm also a fan of fluid layouts and for the record, the preferred width of my browser window is somewhere around 800px, as I'd like to see what else is happening in other applications (why do we have multitasking again?).

Having said that: If this is a current trend and since the usual complaint is that our themes are not "modern" enough - why not? Anybody who doesn't like it can simply use another theme.

bye, Dirk



From ironmax at spacequad.com  Mon Jan 24 14:28:57 2011
From: ironmax at spacequad.com (Michael Brusletten)
Date: Mon, 24 Jan 2011 14:28:57 -0500
Subject: [geeklog-devel] geeklog-devel Digest, Vol 50, Issue 14
References: <mailman.1.1295881203.50250.geeklog-devel@lists.geeklog.net>
Message-ID: <002a01cbbbfc$f1d4a9f0$fe00a8c0@node1>

If changes are made to the themes, please be sure I get a copy to include
for the demo.geeklog.net site.  This way the users are able to find it
easily.  Even if later the theme does become part of the default archive
download, it should still be able to be part of the demo site's archive as
well.

Michael

----- Original Message ----- 
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 23 Jan 2011 10:25:52 -0500
> From: "Tom" <websitemaster at cogeco.net>
> Subject: [geeklog-devel] Geeklog Professional CSS theme
> To: "'Geeklog Development'" <geeklog-devel at lists.geeklog.net>
> Message-ID: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
> Content-Type: text/plain; charset="us-ascii"
>
> Hey All,
>
> Soon I will be adding a new theme to the repository that will hopefully
> replace our current default theme for version 1.8.0 after some work/tweaks
> has been done on it. It will be in a directory called professional_css.
The
> themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is available
> for download on Geeklog.net (look for ProfessionalCSS_en). To start, I
would
> like to thank them for all of the work they have put into the theme.
>
> Besides eliminating table tags this theme does a number of things
> differently. So if you are interested, I would suggest at least
downloading
> the theme and take a look at the readme file for more information. If
people
> disagree on how certain things are done in the theme I would like to hear
> about it now before more work gets put into this.
>
> Before I add the theme to the repository, I will be updating the theme to
> support the new template changes we have currently in 1.8.0 along with
> adding the new images Rouslan did for us. Once the new theme gets added
into
> the repository if anyone does any theme changes, like adding new template
> variables or theme files, please make sure to also add them to the new
> theme.
>
> I do not expect this new theme to look exactly the same as our current
> default theme. It will look similar but if some things are changed around
> for the better, then I am all for it. The one thing I do not plan on
> changing is the color scheme. Rouslan has already put a lot of work into
the
> new logo and icons for the site. We can save the major theme design
changes
> and page designs like this for when we start the new site redesign at a
> later date.
>
> Once I have the new theme in the repository, people are more than welcome
to
> help out. Let's just communicate through email or on the mailing list just
> to makes sure we know what we are all working on.
>
> The first thing I will be doing is working on the general layout which
> actually brings me to my first question.
>
> The new theme is currently has a fixed width of 960 pixels. I would
actually
> like to keep the width fixed as I think it looks much better on the larger
> monitors most people use these days. It also makes designing new pages
> easier.
>
> To help in the decision I took a look at Google Analytics for a site that
> gets a large number of North American visitors. Here are the top ten
screen
> resolutions:
>
> 1. 1280x800  19.60%
> 2. 1024x768  15.41%
> 3. 1366x768  11.45%
> 4. 1440x900  7.73%
> 5. 1280x1024  5.77%
> 6. 320x480  5.16%
> 7. 1680x1050 4.35%
> 8. 1920x1080 3.10%
> 9. 1600x900 2.56%
> 10. 1920x1200 2.03%
>
> For those of you who are interested, here is some info on what browsers
are
> being used:
>
> 1. Internet Explorer 40.01%
> 2. Firefox 26.77%
> 3. Safari 17.87%
> 4. Chrome 11.69%
> 5. Opera 1.06%
> 6. Mozilla Compatible Agent 0.79%
> 7. Opera Mini 0.76%
> 8. BlackBerry8530 0.15%
> 9. BlackBerry9700 0.13%
> 10. Mozilla 0.11%
>
> And since Java Support is an issue for some of the Admin configuration:
>
> 1. Yes  78.75%
> 2. No 21.25%
>
> Thanks
>
> Tom
>
>
>
> ------------------------------



From websitemaster at cogeco.net  Mon Jan 24 15:18:57 2011
From: websitemaster at cogeco.net (Tom)
Date: Mon, 24 Jan 2011 15:18:57 -0500
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <AANLkTinb8xknvWydp+ufkdpdA6TsXxS0yqyzySWUZnE-@mail.gmail.com>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>	<AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>
	<AANLkTinb8xknvWydp+ufkdpdA6TsXxS0yqyzySWUZnE-@mail.gmail.com>
Message-ID: <006601cbbc03$efd74f20$cf85ed60$@cogeco.net>

?  Which brings up the question: with that many mobile users should we put
some work into creating a mobile theme that turns on by auto-detection of
device type (or screen resolution?)?

 

I had thought of that and was planning to look at Geeklog.jp solution to it
at some point (which is based on Professional_CSS theme) 

 

http://www.geeklog.net/filemgmt/index.php/1024

 

Tom

 

From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Vincent Furia
Sent: January-24-11 10:54 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Professional CSS theme

 

I'd modify (or add to that question): What percent of screens are under
960px wide and are not mobile devices.

I expect all of the "6. 320x480      5.16%" screens are mobile devices. 

Which brings up the question: with that many mobile users should we put some
work into creating a mobile theme that turns on by auto-detection of device
type (or screen resolution?)?

-Vinny

On Mon, Jan 24, 2011 at 08:31, cordiste <cordiste at free.fr> wrote:

Tom,

Do you get the total % for screens under 960px?

Ben


2011/1/23 Tom <websitemaster at cogeco.net>:

> Hey All,
>
> Soon I will be adding a new theme to the repository that will hopefully
> replace our current default theme for version 1.8.0 after some work/tweaks
> has been done on it. It will be in a directory called professional_css.
The
> themes authors are Fumito Arakawa & Ivy (from Geeklog.jp) and is available
> for download on Geeklog.net (look for ProfessionalCSS_en). To start, I
would
> like to thank them for all of the work they have put into the theme.
>
> Besides eliminating table tags this theme does a number of things
> differently. So if you are interested, I would suggest at least
downloading
> the theme and take a look at the readme file for more information. If
people
> disagree on how certain things are done in the theme I would like to hear
> about it now before more work gets put into this.
>
> Before I add the theme to the repository, I will be updating the theme to
> support the new template changes we have currently in 1.8.0 along with
> adding the new images Rouslan did for us. Once the new theme gets added
into
> the repository if anyone does any theme changes, like adding new template
> variables or theme files, please make sure to also add them to the new
> theme.
>
> I do not expect this new theme to look exactly the same as our current
> default theme. It will look similar but if some things are changed around
> for the better, then I am all for it. The one thing I do not plan on
> changing is the color scheme. Rouslan has already put a lot of work into
the
> new logo and icons for the site. We can save the major theme design
changes
> and page designs like this for when we start the new site redesign at a
> later date.
>
> Once I have the new theme in the repository, people are more than welcome
to
> help out. Let's just communicate through email or on the mailing list just
> to makes sure we know what we are all working on.
>
> The first thing I will be doing is working on the general layout which
> actually brings me to my first question.
>
> The new theme is currently has a fixed width of 960 pixels. I would
actually
> like to keep the width fixed as I think it looks much better on the larger
> monitors most people use these days. It also makes designing new pages
> easier.
>
> To help in the decision I took a look at Google Analytics for a site that
> gets a large number of North American visitors. Here are the top ten
screen
> resolutions:
>
> 1. 1280x800     19.60%
> 2. 1024x768     15.41%
> 3. 1366x768     11.45%
> 4. 1440x900     7.73%
> 5. 1280x1024    5.77%
> 6. 320x480      5.16%
> 7. 1680x1050    4.35%
> 8. 1920x1080    3.10%
> 9. 1600x900     2.56%
> 10. 1920x1200   2.03%
>
> For those of you who are interested, here is some info on what browsers
are
> being used:
>
> 1. Internet Explorer             40.01%
> 2. Firefox                      26.77%
> 3. Safari                       17.87%
> 4. Chrome                       11.69%
> 5. Opera                        1.06%
> 6. Mozilla Compatible Agent     0.79%
> 7. Opera Mini                   0.76%
> 8. BlackBerry8530               0.15%
> 9. BlackBerry9700               0.13%
> 10. Mozilla                     0.11%
>
> And since Java Support is an issue for some of the Admin configuration:
>
> 1. Yes          78.75%
> 2. No   21.25%
>
> Thanks
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel

 

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

From dirk at haun-online.de  Tue Jan 25 04:54:03 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Tue, 25 Jan 2011 10:54:03 +0100
Subject: [geeklog-devel] Geeklog 1.7.2: Postgres / MS SQL issues?
Message-ID: <20110125105403.11126w1q0aag6pc0@webmail.df.eu>

I'd like to suggest that we release Geeklog 1.7.2 - the last PHP 4  
compatible update - in mid-February, say the weekend of February 12/13.

Since we committed[1] to a long-term support for this release, I'd  
like to get the two reported issues about problems with MS SQL and  
Postgres resolved:

http://project.geeklog.net/tracking/roadmap_page.php?version_id=31

Can those of you who have MS SQL or Postgres running please provide  
some feedback? I.e. whether or not you can reproduce the issue and  
which version(s) you're using?

As noted in the comment of #1251, there's a problem with the Postgres  
version of dbSave, possibly only on PHP 5.3. A fix is in Trunk and I'm  
going to port it back to 1.7.2.

If you are aware of any other issues with MS SQL or Postgres support,  
please report them. Thanks.

bye, Dirk

[1] http://www.geeklog.net/article.php/end-of-php4-support





From websitemaster at cogeco.net  Tue Jan 25 10:11:05 2011
From: websitemaster at cogeco.net (Tom)
Date: Tue, 25 Jan 2011 10:11:05 -0500
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>
	<AANLkTi=dCkMCZ50N2sHNkqrcOD0dD_p8D7BY_1MaYmSQ@mail.gmail.com>
Message-ID: <00aa01cbbca2$162246a0$4266d3e0$@cogeco.net>

Looking at the top 50 screen sizes I would guess from 9 to 10 % in total are
under 960px. Most of those are mobile phones though with screen sizes like
480x360. The only size that is probably not a phone is 800x600 which came in
at #12 with 1.43%

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of cordiste
Sent: January-24-11 10:31 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Professional CSS theme

Tom,

Do you get the total % for screens under 960px?

Ben


2011/1/23 Tom <websitemaster at cogeco.net>:
> Hey All,
>
> Soon I will be adding a new theme to the repository that will 
> hopefully replace our current default theme for version 1.8.0 after 
> some work/tweaks has been done on it. It will be in a directory called 
> professional_css. The themes authors are Fumito Arakawa & Ivy (from 
> Geeklog.jp) and is available for download on Geeklog.net (look for 
> ProfessionalCSS_en). To start, I would like to thank them for all of the
work they have put into the theme.
>
> Besides eliminating table tags this theme does a number of things 
> differently. So if you are interested, I would suggest at least 
> downloading the theme and take a look at the readme file for more 
> information. If people disagree on how certain things are done in the 
> theme I would like to hear about it now before more work gets put into
this.
>
> Before I add the theme to the repository, I will be updating the theme 
> to support the new template changes we have currently in 1.8.0 along 
> with adding the new images Rouslan did for us. Once the new theme gets 
> added into the repository if anyone does any theme changes, like 
> adding new template variables or theme files, please make sure to also 
> add them to the new theme.
>
> I do not expect this new theme to look exactly the same as our current 
> default theme. It will look similar but if some things are changed 
> around for the better, then I am all for it. The one thing I do not 
> plan on changing is the color scheme. Rouslan has already put a lot of 
> work into the new logo and icons for the site. We can save the major 
> theme design changes and page designs like this for when we start the 
> new site redesign at a later date.
>
> Once I have the new theme in the repository, people are more than 
> welcome to help out. Let's just communicate through email or on the 
> mailing list just to makes sure we know what we are all working on.
>
> The first thing I will be doing is working on the general layout which 
> actually brings me to my first question.
>
> The new theme is currently has a fixed width of 960 pixels. I would 
> actually like to keep the width fixed as I think it looks much better 
> on the larger monitors most people use these days. It also makes 
> designing new pages easier.
>
> To help in the decision I took a look at Google Analytics for a site 
> that gets a large number of North American visitors. Here are the top 
> ten screen
> resolutions:
>
> 1. 1280x800 ? ? 19.60%
> 2. 1024x768 ? ? 15.41%
> 3. 1366x768 ? ? 11.45%
> 4. 1440x900 ? ? 7.73%
> 5. 1280x1024 ? ?5.77%
> 6. 320x480 ? ? ?5.16%
> 7. 1680x1050 ? ?4.35%
> 8. 1920x1080 ? ?3.10%
> 9. 1600x900 ? ? 2.56%
> 10. 1920x1200 ? 2.03%
>
> For those of you who are interested, here is some info on what 
> browsers are being used:
>
> 1. Internet Explorer ? ? ? ? ? ? 40.01% 2. Firefox ? ? ? ? ? ? ? ? ? ? ?
> 26.77% 3. Safari ? ? ? ? ? ? ? ? ? ? ? 17.87% 4. Chrome ? ? ? ? ? ? ? ? ?
? ? 
> 11.69% 5. Opera ? ? ? ? ? ? ? ? ? ? ? ?1.06% 6. Mozilla Compatible 
> Agent ? ? 0.79% 7. Opera Mini ? ? ? ? ? ? ? ? ? 0.76% 8. 
> BlackBerry8530 ? ? ? ? ? ? ? 0.15% 9. BlackBerry9700 ? ? ? ? ? ? ? 
> 0.13% 10. Mozilla ? ? ? ? ? ? ? ? ? ? 0.11%
>
> And since Java Support is an issue for some of the Admin configuration:
>
> 1. Yes ? ? ? ? ?78.75%
> 2. No ? 21.25%
>
> Thanks
>
> Tom
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>
_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel



From websitemaster at cogeco.net  Tue Jan 25 10:21:47 2011
From: websitemaster at cogeco.net (Tom)
Date: Tue, 25 Jan 2011 10:21:47 -0500
Subject: [geeklog-devel] Geeklog Professional CSS theme
In-Reply-To: <11D47865-D618-44D8-B1DA-ED8A72359025@haun-online.de>
References: <000b01cbbb11$d20da9a0$7628fce0$@cogeco.net>	<AANLkTikTRTtd80a75hOj=EUf7bOF-k_VQqsfWW7u32+o@mail.gmail.com>
	<11D47865-D618-44D8-B1DA-ED8A72359025@haun-online.de>
Message-ID: <00ae01cbbca3$951518b0$bf3f4a10$@cogeco.net>

> I'd like to see what else is happening in other applications

That is why I have 2 monitors ;-)

> Anybody who doesn't like it can simply use another theme.

Or they can override the width settings (or any other settings) within the
custom.css file (we can include some examples)

Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: January-24-11 2:21 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Geeklog Professional CSS theme

Dan Stoner wrote:

> So I was about to spout my personal angst against sites that are 
> locked to narrow widths and prevent me from using all the screen real 
> estate on my hard-earned 1920x1200 monitor... but then I looked at the 
> web sites of the "big three" CMSes:
> 
> All are "Fixed Width" at 960px (drupal actually uses 940px for some 
> content nodes).

I'm also a fan of fluid layouts and for the record, the preferred width of
my browser window is somewhere around 800px, as I'd like to see what else is
happening in other applications (why do we have multitasking again?).

Having said that: If this is a current trend and since the usual complaint
is that our themes are not "modern" enough - why not? Anybody who doesn't
like it can simply use another theme.

bye, Dirk

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



From rouslan at placella.com  Wed Jan 26 15:24:43 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Wed, 26 Jan 2011 20:24:43 +0000
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <20110124120102.18566t3vg8gswu0g@webmail.df.eu>
References: <20110124120102.18566t3vg8gswu0g@webmail.df.eu>
Message-ID: <1296073483.7739.0.camel@roccivic-pc>

How about integrating the Aloha editor as a project?

Rouslan


On Mon, 2011-01-24 at 12:01 +0100, Dirk Haun wrote:
> ... more or less:
> 
> http://twitter.com/#!/fossygrl/status/29401409560510464
> http://www.google-melange.com/
> 
> So, have you all been collecting ideas for possible GSoC projects?  
> Time to flesh them out somewhat and add them to the wiki. Also, as  
> every year: Mentors wanted!
> 
> bye, Dirk
> 
> 
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel




From dirk at haun-online.de  Wed Jan 26 15:55:58 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 26 Jan 2011 21:55:58 +0100
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <1296073483.7739.0.camel@roccivic-pc>
References: <20110124120102.18566t3vg8gswu0g@webmail.df.eu>
	<1296073483.7739.0.camel@roccivic-pc>
Message-ID: <B6D7EC47-DD81-46A0-9140-6AD6664A7CB8@haun-online.de>

Rouslan Placella wrote:

> How about integrating the Aloha editor as a project?

I had that idea already, but I doubt it would keep someone busy for a summer. I think I had the proof-of-concept integration (minus saving, though) done in about 30 minutes and that only took me so long since I was doing it on an iPad, logged into my Linux box at home, all the way from Amsterdam ;-)

We also, as discussed before, would have to wait for a plugin for image uploads (is that available yet?).

Still, this is probably something that should go on our brainstorming page:

http://wiki.geeklog.net/index.php/GSoC_Brainstorming

bye, Dirk



From Randy.Kolenko at nextide.ca  Wed Jan 26 16:22:59 2011
From: Randy.Kolenko at nextide.ca (Randy Kolenko)
Date: Wed, 26 Jan 2011 16:22:59 -0500
Subject: [geeklog-devel] GSoC 2011 announced
Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F3837EF@nex-pluto.nextide.ca>

What about introducing php pdo support for a gsoc project?


> -----Original Message-----
> From: Dirk Haun [mailto:dirk at haun-online.de]
> Sent: Wednesday, January 26, 2011 3:56 PM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] GSoC 2011 announced
> 
> Rouslan Placella wrote:
> 
> > How about integrating the Aloha editor as a project?
> 
> I had that idea already, but I doubt it would keep someone busy for a
> summer. I think I had the proof-of-concept integration (minus saving,
> though) done in about 30 minutes and that only took me so long since I
> was doing it on an iPad, logged into my Linux box at home, all the way
> from Amsterdam ;-)
> 
> We also, as discussed before, would have to wait for a plugin for
image
> uploads (is that available yet?).
> 
> Still, this is probably something that should go on our brainstorming
> page:
> 
> http://wiki.geeklog.net/index.php/GSoC_Brainstorming
> 
> bye, Dirk
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel



From dirk at haun-online.de  Wed Jan 26 16:54:36 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Wed, 26 Jan 2011 22:54:36 +0100
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <063B8B70CB9DA141B2FC1DB483561B9F3837EF@nex-pluto.nextide.ca>
References: <063B8B70CB9DA141B2FC1DB483561B9F3837EF@nex-pluto.nextide.ca>
Message-ID: <6F8F5823-DC93-4139-BA32-964050E7B2E4@haun-online.de>

Randy Kolenko wrote:

> What about introducing php pdo support for a gsoc project?

To my knowledge, PDO is considered "dead" by the PHP team (same for PDO2, before you ask).

bye, Dirk



From Randy.Kolenko at nextide.ca  Wed Jan 26 17:09:52 2011
From: Randy.Kolenko at nextide.ca (Randy Kolenko)
Date: Wed, 26 Jan 2011 17:09:52 -0500
Subject: [geeklog-devel] GSoC 2011 announced
Message-ID: <063B8B70CB9DA141B2FC1DB483561B9F3837F0@nex-pluto.nextide.ca>

Really?

The PDO PECL extension was moved into core php.  
Other CMSs have recently added PDO support.  
Microsoft is supporting a brand new shiny PDO driver that installs
(oddly enough) nicely with their php web manager for IIS.




> -----Original Message-----
> From: Dirk Haun [mailto:dirk at haun-online.de]
> Sent: Wednesday, January 26, 2011 4:55 PM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] GSoC 2011 announced
> 
> Randy Kolenko wrote:
> 
> > What about introducing php pdo support for a gsoc project?
> 
> To my knowledge, PDO is considered "dead" by the PHP team (same for
> PDO2, before you ask).
> 
> bye, Dirk
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel



From jmucchiello at yahoo.com  Wed Jan 26 21:59:55 2011
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Wed, 26 Jan 2011 18:59:55 -0800 (PST)
Subject: [geeklog-devel] GSoC 2011 announced
Message-ID: <244208.44976.qm@web31402.mail.mud.yahoo.com>

Dirk wrote:
> Rouslan Placella wrote:
> 
>> How about integrating the Aloha editor as a project?
> 
> I had that idea already, but I doubt it would keep someone busy for a
> summer. I think I had the proof-of-concept integration (minus saving,
> though) done in about 30 minutes and that only took me so long since I was
> doing it on an iPad, logged into my Linux box at home, all the way from
> Amsterdam ;-)

How about changing editor integration into something so simple you can just do 
something like [advanced_editor:identifier opt1=abc opt2=def height=8] in a 
template file and through the magic of autotags (and some core support) the 
editor just "magically" appears so that plugin writers don't have to figure out 
how to do advanced editor support. (I'm guessing it would also take a function 
to pull this off but tying the function to an autotag would be great.) Right now 
editor integration requires work when it should be simple to put an advanced 
editor onto a page.Would that take a summer?

And of course it should be easy to swap out the Aloha editor with some other 
editor.

  Joe



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

From rouslan at placella.com  Thu Jan 27 16:54:35 2011
From: rouslan at placella.com (Rouslan Placella)
Date: Thu, 27 Jan 2011 21:54:35 +0000
Subject: [geeklog-devel] Plugin Version Control and Dependencies
 (featurerequest #0001154)
In-Reply-To: <005901cbba43$a9337c90$fb9a75b0$@cogeco.net>
References: <063B8B70CB9DA141B2FC1DB483561B9F3837DA@nex-pluto.nextide.ca>
	<AANLkTinCHv4yNDHvmvFycjwG-bpXMBuHtbcvaZkGd3JO@mail.gmail.com>
	<1295705387.2045.12.camel@roccivic-pc>
	<005901cbba43$a9337c90$fb9a75b0$@cogeco.net>
Message-ID: <1296165275.10835.8.camel@roccivic-pc>

I have a prototype implementation ready:
http://www.geeklog.net/forum/viewtopic.php?showtopic=91908

There still are a few issues with it and due to my inexperience with
version control all the code ended up in one 1400-line patch. But I
guess that would just be glad to receive some feedback about how the
plugin admin ended up, both in terms of appearance and functionality.
Thanks.

Take care,
Rouslan.


On Sat, 2011-01-22 at 09:50 -0500, Tom wrote:
> I like your array idea of 
> 
> // There can be multiple dependencies
> array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
> 
> 
> This way if a plugin needs to it could state it only supports a plugin within a certain version range.
> array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
> array( 'plugin' => 'socnet', '2.0.0' => '<' ),
> 
> Tom
> 
> -----Original Message-----
> From: geeklog-devel-bounces at lists.geeklog.net [mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Rouslan Placella
> Sent: January-22-11 9:10 AM
> To: Geeklog Development
> Subject: Re: [geeklog-devel] Plugin Version Control and Dependencies (featurerequest #0001154)
> 
> I started a bit of work on this and, yeah, I get it. And I also see that there is no need for that API call either. The plugins that use the new install, return install parameters through plugin_autoinstall_myplugin(). And they could just add the dependency information to the array that they normally return. Then it would be geeklog's responsibility to resolve those dependencies.
> 
> Rouslan
> 
> 
> On Fri, 2011-01-21 at 22:36 -0700, Vincent Furia wrote:
> > I'm with Randy. I think a single new API call should be sufficient.
> > 
> > 
> > -Vinny
> > 
> > On Fri, Jan 21, 2011 at 11:13, Randy Kolenko 
> > <Randy.Kolenko at nextide.ca> wrote:
> >         Just out of curiosity ? why store anything in a table?
> >         
> >          
> >         
> >         The information required to install a plugin is easily pulled
> >         back by the plugin admin page by querying each plugin, and
> >         populated on the screen.  If a plugin is missing a dependency,
> >         don?t allow it to be installed and simply show the dependency
> >         information below the plugin and the associated status of each
> >         dependency (installed, disabled, missing etc).
> >         
> >          
> >         
> >         Like I noted before, we?ve done all this with Nexpro ? the
> >         plugin page is all that really needs to be updated to support
> >         hiding the install button and showing the dependencies.  For
> >         Nexpro, each config file for each plugin has its own
> >         dependency list.  We do a version_compare and determine if the
> >         required plugin is there or not in the autoinstall.php file.  
> >         
> >          
> >         
> >          
> >         
> >         From: Rouslan Placella [mailto:rouslan at placella.com] 
> >         Sent: Friday, January 21, 2011 11:41 AM
> >         To: Geeklog Development
> >         Subject: [geeklog-devel] Plugin Version Control and
> >         Dependencies (featurerequest #0001154)
> >         
> >         
> >         
> >          
> >         
> >         I'd like to implement the dependency checks for geeklog
> >         plugins (bug #0001154).
> >         So below I wrote down some things that I think I'll have to do
> >         for this.
> >         Feedback? Suggestions? Opinions? Tips?
> >         
> >         Thanks,
> >         Rouslan.
> >         
> >         THINGS TO DO (or to keep in mind):
> >         * Create two database tables: 
> >         Store each plugin's dependencies in one table
> >         and each plugin's log from the latest install attempt in the
> >         other table
> >         
> >         TABLE plugin_dependencies
> >           pi_name      varchar(30) // Name of the plugin to which an
> >         entry belongs
> >           type         varchar(20) // 'geeklog', 'plugin', etc...
> >               require      varchar(30) // name of the required plugin
> >         (leave empty if $type is 'geeklog')
> >           version      varchar(20) // version of the required plugin
> >           operator     varchar(10) // type of comparison, e.g: ">=" or
> >         ">"
> >         
> >         TABLE plugin_install_log   // here we save custom messages
> >         that are generated when a plugin's install function is called 
> >           pi_name      varchar(30)
> >           type         varchar(20) // 'notice', 'info', 'warning',
> >         'error', etc...
> >           title        TEXT        // a title
> >           msg          TEXT        // a message
> >         
> >         
> >         * Create a new plugin API call:
> >         plugin_dependencies_pluginname()
> >             The plugin can return a two-dimentional array containing
> >         its dependency information and it's install log.
> >         Sample usage in the plugin would be:
> >         <?php
> >         // plugins/foo/autoinstall.php:
> >         ...
> >         function plugin_dependencies_foo()
> >         {
> >         ...
> >         return array(
> >         // This array says that the plugin 'foo' requires Geeklog
> >         version greater than or equal to 1.8.0
> >         array( 'geeklog' => 'core', '1.8.0' => '>=' ),
> >         
> >         // This array says that the plugin 'foo' requires the calendar
> >         plugin with version greater than 1.0.0
> >         array( 'plugin' => 'calendar', '1.0.0' => '>' ),
> >         
> >         // There can be multiple dependencies
> >         array( 'plugin' => 'socnet', '1.0.0' => '>=' ),
> >         
> >         // A message from the plugin regarding custom dependency
> >         checks
> >         // $type can be 'notice', 'info', 'warning', 'error', etc...
> >         array( 'message' => 'error', 'a title' => 'a message' ),
> >         
> >         // There can be multiple messages
> >         array( 'message' => 'info', 'another title' => 'another
> >         message' )
> >           
> >         /*  The settings will be saved to 'plugins_dependencies' table
> >         and
> >                             the messages to 'plugins_install_log'  */
> >         );
> >         }
> >         ...
> >         ?>
> >         
> >         * Introduce a function to update and resolve dependencies, as
> >         well as ensuring that the plugins are loaded in the correct
> >         order.
> >             Call this function:
> >         * when enabling/disabling a plugin
> >         * when installing/uninstalling a plugin
> >         * when changing plugin load order
> >         * when loading plugins?
> >         
> >         * Add the "plugin editor" to uninstalled plugins.
> >         * If there was an install attempt and it failed, show the
> >         entries from the "plugin_install_log" table there.
> >         * When warning about unresolved dependencies. Offer the
> >         options to: "try to resolve", "proceed anyway" and "cancel
> >         operation".
> >         * Add a clear_install_log($plugin) function and use it before
> >         each install so that there is only one log entry per plugin.
> >         * In the plugin admin, make it obvious when there is a message
> >         that was saved during the install and it can be viewed.
> >         
> >         * Show dependency information in the plugin editor for enabled
> >         plugins
> >         
> >         * Show the install log in the plugin editor for enabled
> >         plugins
> >             It'll probably say: "Installation was successful." only,
> >         most the time, but it could be useful to add custom
> >         information messages.
> >         
> >         * Keep backwards compatibility with all older plugins
> >         
> >         * Should be easy to extend to dependencies for databases
> >         (maybe even themes and blocks, too?).
> >         
> >         * Add a plugin_dependencies_* functions to the bundled plugins
> >         
> >         * Document everything better than this
> >         
> >         
> >         
> >         _______________________________________________
> >         geeklog-devel mailing list
> >         geeklog-devel at lists.geeklog.net
> >         http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> >         
> > 
> > 
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> 
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel




From danstoner at gmail.com  Fri Jan 28 09:04:06 2011
From: danstoner at gmail.com (Dan Stoner)
Date: Fri, 28 Jan 2011 09:04:06 -0500
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <244208.44976.qm@web31402.mail.mud.yahoo.com>
References: <244208.44976.qm@web31402.mail.mud.yahoo.com>
Message-ID: <AANLkTimkneSgdV3U77Byp4WA3RYMd4Ytj-y6Wha1=FoP@mail.gmail.com>

Are adding editors really so simple?  It seems like there are a lot of
"quirks" that could use some polish.

For example, write half of a story in Plain Text and then decide to
switch to the advanced editor... switching editors blows the existing
formatting.

The wiki syntax also could use some polish (I remember having problems
with it trying to use it for sample "code" blocks, it couldn't deal
with curly braces).


How hard would it be to add BBCode support for story editing?


Just some ideas / possible itches worth scratching.

 - Dan Stoner

On Wed, Jan 26, 2011 at 9:59 PM, Joe Mucchiello <jmucchiello at yahoo.com> wrote:
> Dirk wrote:
>> Rouslan Placella wrote:
>>
>>> How about integrating the Aloha editor as a project?
>>
>> I had that idea already, but I doubt it would keep someone busy for a
>> summer. I think I had the proof-of-concept integration (minus saving,
>> though) done in about 30 minutes and that only took me so long since I was
>> doing it on an iPad, logged into my Linux box at home, all the way from
>> Amsterdam ;-)
>
> How about changing editor integration into something so simple you can just
> do something like [advanced_editor:identifier opt1=abc opt2=def height=8] in
> a template file and through the magic of autotags (and some core support)
> the editor just "magically" appears so that plugin writers don't have to
> figure out how to do advanced editor support. (I'm guessing it would also
> take a function to pull this off but tying the function to an autotag would
> be great.) Right now editor integration requires work when it should be
> simple to put an advanced editor onto a page.Would that take a summer?
>
> And of course it should be easy to swap out the Aloha editor with some other
> editor.
>
> ? Joe
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From dirk at haun-online.de  Sat Jan 29 03:52:53 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 29 Jan 2011 09:52:53 +0100
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <AANLkTimkneSgdV3U77Byp4WA3RYMd4Ytj-y6Wha1=FoP@mail.gmail.com>
References: <244208.44976.qm@web31402.mail.mud.yahoo.com>
	<AANLkTimkneSgdV3U77Byp4WA3RYMd4Ytj-y6Wha1=FoP@mail.gmail.com>
Message-ID: <D08FA1B7-6874-4879-AD78-0E490E3F4614@haun-online.de>

Dan Stoner wrote:

> Are adding editors really so simple?  It seems like there are a lot of
> "quirks" that could use some polish.

Keep in mind that we're looking for projects that would keep a student busy for 3 months (and that's working on it more or less full time).

I'd say a working integration of Aloha, i.e. being able to save, create new stories, and respect permissions, should take about a week. Then you'd have to do it again for the other areas / plugins as well (staticpages etc.). Add another few days for some nice support of autotags, and the image upload (if available). That should still be way less than a month's worth of work.

Since Aloha is an inline editor, it's probably worth taking a fresh look at how Geeklog works from that perspective. Like, for example, being able to edit "normal" blocks without going to the editor would be a nice new feature. So there may well be some more work here. Still not sure if there's enough for a full-fledged GSoC project, but we should start collecting these ideas. Use the wiki.

bye, Dirk



From websitemaster at cogeco.net  Sat Jan 29 10:38:18 2011
From: websitemaster at cogeco.net (Tom)
Date: Sat, 29 Jan 2011 10:38:18 -0500
Subject: [geeklog-devel] Article or Story
Message-ID: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>

Not an extremely important issue but we seem to like to use both story and
article to describe, well a story or an article . This happens in the
code/file names as well as with the wording on the site (ie Contribute a
Story, Article Directory). 

We should probably decide what we should use going forward and slowly change
the wording in the language files and the file names to whatever we decide.

I would probably vote for article.

Tom






From vfuria at gmail.com  Sat Jan 29 10:58:02 2011
From: vfuria at gmail.com (Vincent Furia)
Date: Sat, 29 Jan 2011 08:58:02 -0700
Subject: [geeklog-devel] Article or Story
In-Reply-To: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>
References: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>
Message-ID: <AANLkTimVRWwNEwQ3iKwjKb_V3AP0ZWSe8PC2F0kObTri@mail.gmail.com>

Amen. That inconsistency has bugged me for years. Another vote for article.

On Sat, Jan 29, 2011 at 08:38, Tom <websitemaster at cogeco.net> wrote:

> Not an extremely important issue but we seem to like to use both story and
> article to describe, well a story or an article . This happens in the
> code/file names as well as with the wording on the site (ie Contribute a
> Story, Article Directory).
>
> We should probably decide what we should use going forward and slowly
> change
> the wording in the language files and the file names to whatever we decide.
>
> I would probably vote for article.
>
> Tom
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110129/bc2dbb9d/attachment.html>

From ashishmittal.mail at gmail.com  Sat Jan 29 11:36:38 2011
From: ashishmittal.mail at gmail.com (ashish mittal)
Date: Sat, 29 Jan 2011 22:06:38 +0530
Subject: [geeklog-devel] Interested in GSoC 2011 (Self Introduction)
Message-ID: <AANLkTinSNCG3ozPPZc0vh-gEDsZVV4wLgaPh-iaSk7X0@mail.gmail.com>

Hello members,

I am Ashish Mittal, a pre-final year BE student of Computer Engineering from
University of Mumbai, India. I intend and am very interested to take part in
GSoC 2011 with Geeklog as my mentoring organization this year.

I am new to this list and to this organization. I feel introducing myself
here and getting to knowing the community members would be good as I am keen
to contribute here as a developer.

I have already participated in GSoC 2010 under Sakai Foundation where I
created a subsystem ?Event Explorer? [0] for them. I have experience with
technologies like Struts, Grails, JSP, Servlet, HTML, CSS,
Javascript/JQuery, Git and MySQL. I am good with UI interfacing and web 2.0
tools.

I saw that Geeklog has already started preparing for SoC 2011 [1] and I also
want to start getting to grip with the architecture of Geeklog. I have been
through some documentations and past year?s projects. I wanted to know if
there are some tasks or good ideas which I could work on prior to timeline
so as to get a better understanding of the architecture and code base. So if
you could please give me some information on the above, it will be very
helpful to me.

Thanks in advance.
[0] -
https://confluence.sakaiproject.org/display/KERNDOC/KERN-717+Event+Explorer
[1] - http://wiki.geeklog.net/index.php/Google_Summer_of_Code


Regards,

Ashish Mittal
Student at University of Mumbai
Yahoo:  av_mittal at ymail.com
Gtalk:   ashishmittal.mail at gmail.com
Phone: +919930820950
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110129/048b2f80/attachment.html>

From dirk at haun-online.de  Sat Jan 29 12:04:04 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 29 Jan 2011 18:04:04 +0100
Subject: [geeklog-devel] Interested in GSoC 2011 (Self Introduction)
In-Reply-To: <AANLkTinSNCG3ozPPZc0vh-gEDsZVV4wLgaPh-iaSk7X0@mail.gmail.com>
References: <AANLkTinSNCG3ozPPZc0vh-gEDsZVV4wLgaPh-iaSk7X0@mail.gmail.com>
Message-ID: <EA67BB38-36A7-44D1-A242-10E4B0CEF7CB@haun-online.de>

ashish mittal wrote:

> I saw that Geeklog has already started preparing for SoC 2011 [1] and I also want to start getting to grip with the architecture of Geeklog. I have been through some documentations and past year?s projects. I wanted to know if there are some tasks or good ideas which I could work on prior to timeline so as to get a better understanding of the architecture and code base. So if you could please give me some information on the above, it will be very helpful to me.

Welcome and thanks for your interest.

Assuming you already saw the "Getting Started" article[1] on the wiki: You could dive right in and try one of the beginner-level issues from our bugtracker:

http://project.geeklog.net/tracking/search.php?hide_status_id=90&tag_string=beginner

Or help us review the outstanding patches (I don't have a link at hand - when you log into our bugtracker, there's a "Patches" option in the "[Reset Filter]" dropdown).

If you have any question, feel free to ask here or on IRC.

bye, Dirk

[1] http://wiki.geeklog.net/index.php/Getting_Started



From dirk at haun-online.de  Sat Jan 29 12:06:04 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sat, 29 Jan 2011 18:06:04 +0100
Subject: [geeklog-devel] Article or Story
In-Reply-To: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>
References: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>
Message-ID: <94E2127F-2696-49D0-9BE2-AB6C64BBA1DA@haun-online.de>

Tom wrote:

> I would probably vote for article.

I guess "article" is the only real option or we would break all the existing links to all the article.php pages out there ...

Btw, this should be a feature request in the bugtracker.

bye, Dirk



From websitemaster at cogeco.net  Sat Jan 29 12:47:15 2011
From: websitemaster at cogeco.net (Tom)
Date: Sat, 29 Jan 2011 12:47:15 -0500
Subject: [geeklog-devel] Article or Story
In-Reply-To: <94E2127F-2696-49D0-9BE2-AB6C64BBA1DA@haun-online.de>
References: <003a01cbbfca$8d778370$a8668a50$@cogeco.net>
	<94E2127F-2696-49D0-9BE2-AB6C64BBA1DA@haun-online.de>
Message-ID: <000301cbbfdc$912459a0$b36d0ce0$@cogeco.net>

> would break all the existing links to all the article.php

Good point. We do not want to do that.

> should be a feature request in the bugtracker.

Yup I was planning to add it in. I just wanted to get the communities input.


Tom

-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: January-29-11 12:06 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] Article or Story

Tom wrote:

> I would probably vote for article.

I guess "article" is the only real option or we would break all the existing
links to all the article.php pages out there ...

Btw, this should be a feature request in the bugtracker.

bye, Dirk

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



From jmucchiello at yahoo.com  Sat Jan 29 13:34:58 2011
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Sat, 29 Jan 2011 10:34:58 -0800 (PST)
Subject: [geeklog-devel] Article or Story
Message-ID: <268086.86302.qm@web31408.mail.mud.yahoo.com>

Personally, I'd rather see stories/articles moved into an article plugin and get 
rid of a lot of IF statements and special case code strewn throughout Geeklog's 
core. That would also make the below issue simpler:

>> would break all the existing links to all the article.php

Even if you picked "story", you could always setup article.php to do a 301 
permanent redirect. The same solution would be used if articles were moved to a 
plugin. When the URLs became {site_url}/article/index.php?sid=...., 

a legacy {site_url}/article.php would still be needed to do the 301s.

  Joe



      


From dirk at haun-online.de  Sun Jan 30 09:40:06 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 30 Jan 2011 15:40:06 +0100
Subject: [geeklog-devel] Do Not Track header?
Message-ID: <381C5CDC-C9A7-42A6-8308-5BECB13304FC@haun-online.de>

Is there anything that we should be doing in Geeklog to support the proposed Do Not Track[1] HTTP header? I guess whoever maintains the GUS plugin these days probably should take a good look at this. But is there something to be done in Geeklog itself?

Somewhat related: We should also be looking into an option not to store IP addresses (and login dates, but at least that's already configurable), since we're probably already on shaky ground there in some legislatures.

bye, Dirk

[1] http://donottrack.us/

From jmucchiello at yahoo.com  Sun Jan 30 11:09:42 2011
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Sun, 30 Jan 2011 08:09:42 -0800 (PST)
Subject: [geeklog-devel] Do Not Track header?
Message-ID: <868379.30307.qm@web31406.mail.mud.yahoo.com>

Dirk wrote:
> Is there anything that we should be doing in Geeklog to support the
> proposed Do Not Track[1] HTTP header? I guess whoever maintains the GUS
> plugin these days probably should take a good look at this. But is there
> something to be done in Geeklog itself?

This has the potential to cause many headaches. To truly be Do Not Track 
compliant, a website would also have to enforce retention policies on stuff like 

the server access logs. Since this, db backups, and other tracking is outside 
the scope of Geeklog, I don't think being Do Not Track compliant is something 
Geeklog can (or should) advertise. Instead, a wiki page saying how you
configure Geeklog to aid in DNT compliance (along with suggestions for other
things you would do to be compliant) is the way to go.
 
> Somewhat related: We should also be looking into an option not to store IP
> addresses (and login dates, but at least that's already configurable),
> since we're probably already on shaky ground there in some legislatures.

I would think just adding an option would suffice for DNT compliance and as you
said is probably long overdue. The trick is getting the plugins to comply, 
especially forum since we have no maintainer for it.

  Joe



      


From websitemaster at cogeco.net  Mon Jan 31 09:24:28 2011
From: websitemaster at cogeco.net (Tom)
Date: Mon, 31 Jan 2011 09:24:28 -0500
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <D08FA1B7-6874-4879-AD78-0E490E3F4614@haun-online.de>
References: <244208.44976.qm@web31402.mail.mud.yahoo.com>	<AANLkTimkneSgdV3U77Byp4WA3RYMd4Ytj-y6Wha1=FoP@mail.gmail.com>
	<D08FA1B7-6874-4879-AD78-0E490E3F4614@haun-online.de>
Message-ID: <003c01cbc152$91a0baa0$b4e22fe0$@cogeco.net>

For a GSOC project can we group a bunch of smaller similar projects together
to get 3 months of work? For example along with Aloha we could also add a
number of feature requests that are in the bug tracker for edit forms. The
upside to this is as a smaller project is finished we can then get it
incorporated into core before they start on the next small project.

Also would it be frowned upon if we had projects that are continuation of
previous years GSOC projects?

Tom 



-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: January-29-11 3:53 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] GSoC 2011 announced

Dan Stoner wrote:

> Are adding editors really so simple?  It seems like there are a lot of 
> "quirks" that could use some polish.

Keep in mind that we're looking for projects that would keep a student busy
for 3 months (and that's working on it more or less full time).

I'd say a working integration of Aloha, i.e. being able to save, create new
stories, and respect permissions, should take about a week. Then you'd have
to do it again for the other areas / plugins as well (staticpages etc.). Add
another few days for some nice support of autotags, and the image upload (if
available). That should still be way less than a month's worth of work.

Since Aloha is an inline editor, it's probably worth taking a fresh look at
how Geeklog works from that perspective. Like, for example, being able to
edit "normal" blocks without going to the editor would be a nice new
feature. So there may well be some more work here. Still not sure if there's
enough for a full-fledged GSoC project, but we should start collecting these
ideas. Use the wiki.

bye, Dirk

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



From dilan.wijenayake at gmail.com  Mon Jan 31 15:16:36 2011
From: dilan.wijenayake at gmail.com (Dilan Wijenayake)
Date: Tue, 1 Feb 2011 01:46:36 +0530
Subject: [geeklog-devel] Gsoc 2011
Message-ID: <AANLkTinRS2XqJCJZ-dHzGvu+LG+5ikkGtzmyO_OSnPyq@mail.gmail.com>

Hi,


I?m Dilan Wijenayake a final year undergraduate student in faculty of
Computer Science and Engineering, University of Moratuwa, Sri Lanka. I would
like to contribute myself for a project in Geeklog. Currently I?m studying
background knowledge for the projects in Geeklog. I have a good knowledge in
php and SQL, so I thought to participate Gsoc 2011 by doing Geeklog project.
I?m kindly request more information on Geeklog development from anyone, so I
can suit myself before gsoc begins.


Thank You.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20110201/9376d91c/attachment.html>

From dirk at haun-online.de  Mon Jan 31 16:27:04 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 31 Jan 2011 22:27:04 +0100
Subject: [geeklog-devel] Gsoc 2011
In-Reply-To: <AANLkTinRS2XqJCJZ-dHzGvu+LG+5ikkGtzmyO_OSnPyq@mail.gmail.com>
References: <AANLkTinRS2XqJCJZ-dHzGvu+LG+5ikkGtzmyO_OSnPyq@mail.gmail.com>
Message-ID: <32765008-3EC7-4023-A47D-46896A815148@haun-online.de>

Dilan Wijenayake wrote:

> I would like to contribute myself for a project in Geeklog. Currently I?m studying background knowledge for the projects in Geeklog. I have a good knowledge in php and SQL, so I thought to participate Gsoc 2011 by doing Geeklog project. I?m kindly request more information on Geeklog development from anyone, so I can suit myself before gsoc begins. 

Welcome and thanks for your interest. For the record: We will be applying for participation in GSoC 2011, but the list of participating organizations will only be published on March 18. Until then, even we won't know whether we're "in" or not :)

As for getting started try this article on our wiki:

http://wiki.geeklog.net/index.php/Getting_Started

If there are any questions, feel free to ask them here or come visit us on IRC.

bye, Dirk



From dirk at haun-online.de  Mon Jan 31 17:02:29 2011
From: dirk at haun-online.de (Dirk Haun)
Date: Mon, 31 Jan 2011 23:02:29 +0100
Subject: [geeklog-devel] GSoC 2011 announced
In-Reply-To: <003c01cbc152$91a0baa0$b4e22fe0$@cogeco.net>
References: <244208.44976.qm@web31402.mail.mud.yahoo.com>	<AANLkTimkneSgdV3U77Byp4WA3RYMd4Ytj-y6Wha1=FoP@mail.gmail.com>
	<D08FA1B7-6874-4879-AD78-0E490E3F4614@haun-online.de>
	<003c01cbc152$91a0baa0$b4e22fe0$@cogeco.net>
Message-ID: <D81E8B4C-CE71-40A8-9984-6C0FBC83923A@haun-online.de>

Tom wrote:

> Also would it be frowned upon if we had projects that are continuation of
> previous years GSOC projects?

Nope, and we already ran two such projects (install script, configuration). I'm thinking of proposing a follow-up project for the unit test framework.


> For a GSOC project can we group a bunch of smaller similar projects together
> to get 3 months of work?

I guess technically, that would be allowed. But I'm not sure if it would be such a good idea.

IMO, a GSoC project should focus on one area / idea. Also, a cobbled-together project probably isn't too attractive. The cobbled-together Spam-X project we tried for the last 2 years wasn't so great.

I know there's a bit of a hole between GSoC sized and Code-In sized projects, but that's probably something we could throw a bounty at.

bye, Dirk