From butterfan2006 at gmail.com  Tue Dec  7 10:55:17 2010
From: butterfan2006 at gmail.com (Yasantha Subash Samarasekara)
Date: Tue, 7 Dec 2010 07:55:17 -0800 (PST)
Subject: [geeklog-devel] Invitation to connect on LinkedIn
Message-ID: <796310655.19811886.1291737317745.JavaMail.app@ech3-cdn12.prod>

LinkedIn
------------

   
I'd like to add you to my professional network on LinkedIn.

- Yasantha Subash

Yasantha Subash Samarasekara
Student at Sabaragamuwa University of Sri Lanka
Sri Lanka

Confirm that you know Yasantha Subash Samarasekara
https://www.linkedin.com/e/mkye9x-ghez1pbh-3v/isd/1997534543/HNP65xVI/


 
-- 
(c) 2010, LinkedIn Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20101207/680fd359/attachment.html>

From dirk at haun-online.de  Sun Dec 12 16:30:58 2010
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 12 Dec 2010 22:30:58 +0100
Subject: [geeklog-devel] IKS / Aloha editor
Message-ID: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>

For those who haven't seen it yet, I've posted a report from the IKS workshop in Amsterdam on geeklog.net yesterday:

  http://www.geeklog.net/article.php/iks-workshop-amsterdam

Thoughts and comments on how to proceed, i.e. whether or not to "go semantic", are very much welcome.


What I didn't mention in that post is that I got a chance to sit down with some of the guys from the Aloha editor, <http://aloha-editor.org/>, who were also present in Amsterdam, and tried integrating it into Geeklog. We got to a "proof of concept" point where it let you edit articles, but actually saving the changes was still missing (that should be about a day's work left to do).

I really like the approach of this editor - it lets you edit your content in place. Just today, I made a longish post on my blog and when it was published, I spotted a typo. So I had to get back into the editor, scroll down to locate the typo, fix it, save, and re-read. With Aloha, I could simply have clicked into the article, right on the word with the typo, and would have been able to fix it there.

This is, of course, quite a different approach than what we have right now and would require a couple of changes all over the place. I talked things through with Norbert Pomaroli (one of the Aloha authors) and I think I have a pretty good idea of what we would have to do for a proper integration.

The only downside right now: Image uploading is not yet possible with Aloha (but it's being worked on). Since it would be a while before we would have finished an integration anyway, it may be ready just in time. I realize image upload is probably the most popular use case for FCKeditor in Geeklog.

As everybody knows, I'm not exactly a fan of FCKeditor ;-) The alternatives I have seen so far didn't really convince me either. The approach that Aloha uses differs from all those other editors and I have to say that I like it.

I could imagine using it when it's integrated into Geeklog. That's probably saying something ;-)

Comments, impressions, likes / dislikes?

bye, Dirk



From danstoner at gmail.com  Sun Dec 12 18:02:52 2010
From: danstoner at gmail.com (Dan Stoner)
Date: Sun, 12 Dec 2010 18:02:52 -0500
Subject: [geeklog-devel] IKS / Aloha editor
In-Reply-To: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
References: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
Message-ID: <AANLkTi=VDSSSGdWTXc9nkFo6XNx-0K8-+bqBtmBz3g3E@mail.gmail.com>

Sounds great.

I'd be willing to do some testing when it gets to that point.

- Dan Stoner

On Sun, Dec 12, 2010 at 4:30 PM, Dirk Haun <dirk at haun-online.de> wrote:
> For those who haven't seen it yet, I've posted a report from the IKS workshop in Amsterdam on geeklog.net yesterday:
>
> ?http://www.geeklog.net/article.php/iks-workshop-amsterdam
>
> Thoughts and comments on how to proceed, i.e. whether or not to "go semantic", are very much welcome.
>
>
> What I didn't mention in that post is that I got a chance to sit down with some of the guys from the Aloha editor, <http://aloha-editor.org/>, who were also present in Amsterdam, and tried integrating it into Geeklog. We got to a "proof of concept" point where it let you edit articles, but actually saving the changes was still missing (that should be about a day's work left to do).
>
> I really like the approach of this editor - it lets you edit your content in place. Just today, I made a longish post on my blog and when it was published, I spotted a typo. So I had to get back into the editor, scroll down to locate the typo, fix it, save, and re-read. With Aloha, I could simply have clicked into the article, right on the word with the typo, and would have been able to fix it there.
>
> This is, of course, quite a different approach than what we have right now and would require a couple of changes all over the place. I talked things through with Norbert Pomaroli (one of the Aloha authors) and I think I have a pretty good idea of what we would have to do for a proper integration.
>
> The only downside right now: Image uploading is not yet possible with Aloha (but it's being worked on). Since it would be a while before we would have finished an integration anyway, it may be ready just in time. I realize image upload is probably the most popular use case for FCKeditor in Geeklog.
>
> As everybody knows, I'm not exactly a fan of FCKeditor ;-) The alternatives I have seen so far didn't really convince me either. The approach that Aloha uses differs from all those other editors and I have to say that I like it.
>
> I could imagine using it when it's integrated into Geeklog. That's probably saying something ;-)
>
> Comments, impressions, likes / dislikes?
>
> 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  Mon Dec 13 11:00:24 2010
From: rouslan at placella.com (Rouslan Placella)
Date: Mon, 13 Dec 2010 16:00:24 +0000
Subject: [geeklog-devel] IKS / Aloha editor
In-Reply-To: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
References: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
Message-ID: <1292256024.3105.10.camel@roccivic-pc>

I think that it looks much better that FCKeditor.
So yeah, I like it.

On Sun, 2010-12-12 at 22:30 +0100, Dirk Haun wrote:
> For those who haven't seen it yet, I've posted a report from the IKS workshop in Amsterdam on geeklog.net yesterday:
> 
>   http://www.geeklog.net/article.php/iks-workshop-amsterdam
> 
> Thoughts and comments on how to proceed, i.e. whether or not to "go semantic", are very much welcome.
> 
> 
> What I didn't mention in that post is that I got a chance to sit down with some of the guys from the Aloha editor, <http://aloha-editor.org/>, who were also present in Amsterdam, and tried integrating it into Geeklog. We got to a "proof of concept" point where it let you edit articles, but actually saving the changes was still missing (that should be about a day's work left to do).
> 
> I really like the approach of this editor - it lets you edit your content in place. Just today, I made a longish post on my blog and when it was published, I spotted a typo. So I had to get back into the editor, scroll down to locate the typo, fix it, save, and re-read. With Aloha, I could simply have clicked into the article, right on the word with the typo, and would have been able to fix it there.
> 
> This is, of course, quite a different approach than what we have right now and would require a couple of changes all over the place. I talked things through with Norbert Pomaroli (one of the Aloha authors) and I think I have a pretty good idea of what we would have to do for a proper integration.
> 
> The only downside right now: Image uploading is not yet possible with Aloha (but it's being worked on). Since it would be a while before we would have finished an integration anyway, it may be ready just in time. I realize image upload is probably the most popular use case for FCKeditor in Geeklog.
> 
> As everybody knows, I'm not exactly a fan of FCKeditor ;-) The alternatives I have seen so far didn't really convince me either. The approach that Aloha uses differs from all those other editors and I have to say that I like it.
> 
> I could imagine using it when it's integrated into Geeklog. That's probably saying something ;-)
> 
> Comments, impressions, likes / dislikes?
> 
> bye, Dirk
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel




From websitemaster at cogeco.net  Mon Dec 13 11:40:51 2010
From: websitemaster at cogeco.net (Tom)
Date: Mon, 13 Dec 2010 11:40:51 -0500
Subject: [geeklog-devel] IKS / Aloha editor
In-Reply-To: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
References: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
Message-ID: <005601cb9ae4$809e7380$81db5a80$@net>

If we went with the Aloha Editor at some point I assume the Aloha Editor
would become and option under a stories post mode on the story admin editor
form. If "in story editing" is enabled on the site, Admins would have an
extra option of editing stuff on the fly as you tested.

How does Aloha handle embedded items in the stories like autotags, images,
youtube videos, etc? Does that content stay in place and is not editable?

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: December-12-10 4:31 PM
To: Geeklog Development
Subject: [geeklog-devel] IKS / Aloha editor

For those who haven't seen it yet, I've posted a report from the IKS
workshop in Amsterdam on geeklog.net yesterday:

  http://www.geeklog.net/article.php/iks-workshop-amsterdam

Thoughts and comments on how to proceed, i.e. whether or not to "go
semantic", are very much welcome.


What I didn't mention in that post is that I got a chance to sit down with
some of the guys from the Aloha editor, <http://aloha-editor.org/>, who were
also present in Amsterdam, and tried integrating it into Geeklog. We got to
a "proof of concept" point where it let you edit articles, but actually
saving the changes was still missing (that should be about a day's work left
to do).

I really like the approach of this editor - it lets you edit your content in
place. Just today, I made a longish post on my blog and when it was
published, I spotted a typo. So I had to get back into the editor, scroll
down to locate the typo, fix it, save, and re-read. With Aloha, I could
simply have clicked into the article, right on the word with the typo, and
would have been able to fix it there.

This is, of course, quite a different approach than what we have right now
and would require a couple of changes all over the place. I talked things
through with Norbert Pomaroli (one of the Aloha authors) and I think I have
a pretty good idea of what we would have to do for a proper integration.

The only downside right now: Image uploading is not yet possible with Aloha
(but it's being worked on). Since it would be a while before we would have
finished an integration anyway, it may be ready just in time. I realize
image upload is probably the most popular use case for FCKeditor in Geeklog.

As everybody knows, I'm not exactly a fan of FCKeditor ;-) The alternatives
I have seen so far didn't really convince me either. The approach that Aloha
uses differs from all those other editors and I have to say that I like it.

I could imagine using it when it's integrated into Geeklog. That's probably
saying something ;-)

Comments, impressions, likes / dislikes?

bye, Dirk

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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5697 (20101212) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5699 (20101213) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 



From cordiste at free.fr  Mon Dec 13 13:09:07 2010
From: cordiste at free.fr (cordiste)
Date: Mon, 13 Dec 2010 19:09:07 +0100
Subject: [geeklog-devel] IKS / Aloha editor
In-Reply-To: <005601cb9ae4$809e7380$81db5a80$@net>
References: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
	<005601cb9ae4$809e7380$81db5a80$@net>
Message-ID: <AANLkTikj4Xgyw-SbdGUTpLQsOFipxrDPYVKrKkMaOXE7@mail.gmail.com>

Some plugins use the advanced editor, we must be careful to preserve
some compatibility with this one.

::Ben

2010/12/13 Tom <websitemaster at cogeco.net>:
> If we went with the Aloha Editor at some point I assume the Aloha Editor
> would become and option under a stories post mode on the story admin editor
> form. If "in story editing" is enabled on the site, Admins would have an
> extra option of editing stuff on the fly as you tested.
>
> How does Aloha handle embedded items in the stories like autotags, images,
> youtube videos, etc? Does that content stay in place and is not editable?
>
> 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: December-12-10 4:31 PM
> To: Geeklog Development
> Subject: [geeklog-devel] IKS / Aloha editor
>
> For those who haven't seen it yet, I've posted a report from the IKS
> workshop in Amsterdam on geeklog.net yesterday:
>
> ?http://www.geeklog.net/article.php/iks-workshop-amsterdam
>
> Thoughts and comments on how to proceed, i.e. whether or not to "go
> semantic", are very much welcome.
>
>
> What I didn't mention in that post is that I got a chance to sit down with
> some of the guys from the Aloha editor, <http://aloha-editor.org/>, who were
> also present in Amsterdam, and tried integrating it into Geeklog. We got to
> a "proof of concept" point where it let you edit articles, but actually
> saving the changes was still missing (that should be about a day's work left
> to do).
>
> I really like the approach of this editor - it lets you edit your content in
> place. Just today, I made a longish post on my blog and when it was
> published, I spotted a typo. So I had to get back into the editor, scroll
> down to locate the typo, fix it, save, and re-read. With Aloha, I could
> simply have clicked into the article, right on the word with the typo, and
> would have been able to fix it there.
>
> This is, of course, quite a different approach than what we have right now
> and would require a couple of changes all over the place. I talked things
> through with Norbert Pomaroli (one of the Aloha authors) and I think I have
> a pretty good idea of what we would have to do for a proper integration.
>
> The only downside right now: Image uploading is not yet possible with Aloha
> (but it's being worked on). Since it would be a while before we would have
> finished an integration anyway, it may be ready just in time. I realize
> image upload is probably the most popular use case for FCKeditor in Geeklog.
>
> As everybody knows, I'm not exactly a fan of FCKeditor ;-) The alternatives
> I have seen so far didn't really convince me either. The approach that Aloha
> uses differs from all those other editors and I have to say that I like it.
>
> I could imagine using it when it's integrated into Geeklog. That's probably
> saying something ;-)
>
> Comments, impressions, likes / dislikes?
>
> bye, Dirk
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5697 (20101212) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature
> database 5699 (20101213) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel
>
>


From vfuria at gmail.com  Mon Dec 13 13:26:47 2010
From: vfuria at gmail.com (Vincent Furia)
Date: Mon, 13 Dec 2010 11:26:47 -0700
Subject: [geeklog-devel] IKS / Aloha editor
In-Reply-To: <AANLkTikj4Xgyw-SbdGUTpLQsOFipxrDPYVKrKkMaOXE7@mail.gmail.com>
References: <B757885D-F9D6-41A1-BC0B-6B5DF0853D04@haun-online.de>
	<005601cb9ae4$809e7380$81db5a80$@net>
	<AANLkTikj4Xgyw-SbdGUTpLQsOFipxrDPYVKrKkMaOXE7@mail.gmail.com>
Message-ID: <AANLkTik6=E=OGHDP1ncbrMA+zNwoijUhnDQGg_1AvCpM@mail.gmail.com>

I tried out the Aloha Editor at the GSOC Mentor's Summit and have played
with it since. Like Dirk, I much prefer it to the FCKeditor (not least
because of the security issues we've had with it).

However, I don't think we should switch to the Aloha Editor until it
supports image upload. The ability to easily upload images was a big draw to
introduce FCKeditr in the first place and it seems to be a frequently used
feature. It wouldn't hurt to start a branch to integrate the Aloha Editor,
but I think the switchover should wait until the image upload feature is
available.

-Vinny

On Mon, Dec 13, 2010 at 11:09, cordiste <cordiste at free.fr> wrote:

> Some plugins use the advanced editor, we must be careful to preserve
> some compatibility with this one.
>
> ::Ben
>
> 2010/12/13 Tom <websitemaster at cogeco.net>:
> > If we went with the Aloha Editor at some point I assume the Aloha Editor
> > would become and option under a stories post mode on the story admin
> editor
> > form. If "in story editing" is enabled on the site, Admins would have an
> > extra option of editing stuff on the fly as you tested.
> >
> > How does Aloha handle embedded items in the stories like autotags,
> images,
> > youtube videos, etc? Does that content stay in place and is not editable?
> >
> > 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: December-12-10 4:31 PM
> > To: Geeklog Development
> > Subject: [geeklog-devel] IKS / Aloha editor
> >
> > For those who haven't seen it yet, I've posted a report from the IKS
> > workshop in Amsterdam on geeklog.net yesterday:
> >
> >  http://www.geeklog.net/article.php/iks-workshop-amsterdam
> >
> > Thoughts and comments on how to proceed, i.e. whether or not to "go
> > semantic", are very much welcome.
> >
> >
> > What I didn't mention in that post is that I got a chance to sit down
> with
> > some of the guys from the Aloha editor, <http://aloha-editor.org/>, who
> were
> > also present in Amsterdam, and tried integrating it into Geeklog. We got
> to
> > a "proof of concept" point where it let you edit articles, but actually
> > saving the changes was still missing (that should be about a day's work
> left
> > to do).
> >
> > I really like the approach of this editor - it lets you edit your content
> in
> > place. Just today, I made a longish post on my blog and when it was
> > published, I spotted a typo. So I had to get back into the editor, scroll
> > down to locate the typo, fix it, save, and re-read. With Aloha, I could
> > simply have clicked into the article, right on the word with the typo,
> and
> > would have been able to fix it there.
> >
> > This is, of course, quite a different approach than what we have right
> now
> > and would require a couple of changes all over the place. I talked things
> > through with Norbert Pomaroli (one of the Aloha authors) and I think I
> have
> > a pretty good idea of what we would have to do for a proper integration.
> >
> > The only downside right now: Image uploading is not yet possible with
> Aloha
> > (but it's being worked on). Since it would be a while before we would
> have
> > finished an integration anyway, it may be ready just in time. I realize
> > image upload is probably the most popular use case for FCKeditor in
> Geeklog.
> >
> > As everybody knows, I'm not exactly a fan of FCKeditor ;-) The
> alternatives
> > I have seen so far didn't really convince me either. The approach that
> Aloha
> > uses differs from all those other editors and I have to say that I like
> it.
> >
> > I could imagine using it when it's integrated into Geeklog. That's
> probably
> > saying something ;-)
> >
> > Comments, impressions, likes / dislikes?
> >
> > bye, Dirk
> >
> > _______________________________________________
> > geeklog-devel mailing list
> > geeklog-devel at lists.geeklog.net
> > http://eight.pairlist.net/mailman/listinfo/geeklog-devel
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> > database 5697 (20101212) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> > database 5699 (20101213) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> > _______________________________________________
> > 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/20101213/f9500fee/attachment.html>

From vfuria at gmail.com  Tue Dec 14 02:19:26 2010
From: vfuria at gmail.com (Vincent Furia)
Date: Tue, 14 Dec 2010 00:19:26 -0700
Subject: [geeklog-devel] Password Hashing
Message-ID: <AANLkTikyGVyoLjGDPxLF4Ub1SRP41pewudMBRx6aMO1F@mail.gmail.com>

Just caught this "article":
http://codahale.com/how-to-safely-store-a-password/

TL;DR: It recommends using bcrypt (a variant of Blowfish encryption) to hash
passwords.

For those who want details,
http://www.usenix.org/events/usenix99/provos/provos_html/node1.html is a
very detailed paper about the security of using bcrypt for password hashing.

There is a "Portable PHP password hashing framework" that supports bcrypt:
http://www.openwall.com/phpass/

If we're going to move to something more secure than MD5 or SHA1 (and
its derivatives) for our password hash, we might as well move to something
with some built in future proofing.

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

From websitemaster at cogeco.net  Sat Dec 18 08:54:32 2010
From: websitemaster at cogeco.net (Tom)
Date: Sat, 18 Dec 2010 08:54:32 -0500
Subject: [geeklog-devel] 1.8.0 Release Timetable
In-Reply-To: <AANLkTikyGVyoLjGDPxLF4Ub1SRP41pewudMBRx6aMO1F@mail.gmail.com>
References: <AANLkTikyGVyoLjGDPxLF4Ub1SRP41pewudMBRx6aMO1F@mail.gmail.com>
Message-ID: <00c801cb9ebb$18b3ca60$4a1b5f20$@net>

Hey Dirk,

 

What are your thoughts on the timetable for the 1.8.0 release?

 

I have gotten busy with work at the moment so I just want to make sure I
leave enough time to finish off the OAuth support (resynch and the bug in
the configuration).

 

Once OAuth is done I will then be concentrating on the Professional CSS
theme, adding in Rouslan's new graphics, and working on including topic
support for plugins.

 

Once the Topic stuff is done I would then be looking into the template
system improvements I have mentioned in previous posts.

 

Tom

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

From dirk at haun-online.de  Sun Dec 19 03:40:34 2010
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 19 Dec 2010 09:40:34 +0100
Subject: [geeklog-devel] Bugtracker update
Message-ID: <E2BA9469-25F3-4D3E-BADD-30E1E69AE461@haun-online.de>

FYI: I've updated <http://project.geeklog.net/tracking/> to the latest version of Mantis. Let me know if you find anything not working now ...

bye, Dirk



From dirk at haun-online.de  Sun Dec 19 05:02:18 2010
From: dirk at haun-online.de (Dirk Haun)
Date: Sun, 19 Dec 2010 11:02:18 +0100
Subject: [geeklog-devel] 1.8.0 Release Timetable
In-Reply-To: <00c801cb9ebb$18b3ca60$4a1b5f20$@net>
References: <AANLkTikyGVyoLjGDPxLF4Ub1SRP41pewudMBRx6aMO1F@mail.gmail.com>
	<00c801cb9ebb$18b3ca60$4a1b5f20$@net>
Message-ID: <C43733D2-C3F0-40F3-9E2B-61054E632066@haun-online.de>

Tom wrote:

> What are your thoughts on the timetable for the 1.8.0 release?

Well, we obviously missed our November deadline for this release ...

I take the blame for this. I've been travelling a lot lately (I've been to 5 countries in the last 4 months alone) and you can't really advance a project if you're sitting in a hotel room with an iPad ...


>  I have gotten busy with work at the moment so I just want to make sure I leave enough time to finish off the OAuth support (resynch and the bug in the configuration).

I was going to ask if there's a chance for us releasing something (at least a beta or a release candidate) before the end of the year.

Thanks to you, we do have a couple of features in so that we can call this 1.8 and not be embarrassed about it, most notably the OAuth support.


> Once OAuth is done I will then be concentrating on the Professional CSS theme, adding in Rouslan's new graphics, and working on including topic support for plugins.

How long do you guys think you need for this?


>  Once the Topic stuff is done I would then be looking into the template system improvements I have mentioned in previous posts.

Sounds like something that could wait for a 1.8.1?


I'll go through the bugtracker to check for issues that should be addressed in 1.8.0 and update the "roadmap" view accordingly.

bye, Dirk



From websitemaster at cogeco.net  Mon Dec 20 10:20:28 2010
From: websitemaster at cogeco.net (Tom)
Date: Mon, 20 Dec 2010 10:20:28 -0500
Subject: [geeklog-devel] 1.8.0 Release Timetable
In-Reply-To: <C43733D2-C3F0-40F3-9E2B-61054E632066@haun-online.de>
References: <AANLkTikyGVyoLjGDPxLF4Ub1SRP41pewudMBRx6aMO1F@mail.gmail.com>	<00c801cb9ebb$18b3ca60$4a1b5f20$@net>
	<C43733D2-C3F0-40F3-9E2B-61054E632066@haun-online.de>
Message-ID: <005501cba059$6f3f6430$4dbe2c90$@net>

I was just thinking that probably only the OAuth and the autotags stuff I
did would make it into 1.8.0 (unless it is another month or 2 for it to be
released)

The theme will probably not make it in that release unless I find more time
to work on it or, there is very little that needs changing from the Japan
version.

The topic feature will probably be for 1.8.1 along with some of the template
changes.

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: December-19-10 5:02 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] 1.8.0 Release Timetable

Tom wrote:

> What are your thoughts on the timetable for the 1.8.0 release?

Well, we obviously missed our November deadline for this release ...

I take the blame for this. I've been travelling a lot lately (I've been to 5
countries in the last 4 months alone) and you can't really advance a project
if you're sitting in a hotel room with an iPad ...


>  I have gotten busy with work at the moment so I just want to make sure I
leave enough time to finish off the OAuth support (resynch and the bug in
the configuration).

I was going to ask if there's a chance for us releasing something (at least
a beta or a release candidate) before the end of the year.

Thanks to you, we do have a couple of features in so that we can call this
1.8 and not be embarrassed about it, most notably the OAuth support.


> Once OAuth is done I will then be concentrating on the Professional CSS
theme, adding in Rouslan's new graphics, and working on including topic
support for plugins.

How long do you guys think you need for this?


>  Once the Topic stuff is done I would then be looking into the template
system improvements I have mentioned in previous posts.

Sounds like something that could wait for a 1.8.1?


I'll go through the bugtracker to check for issues that should be addressed
in 1.8.0 and update the "roadmap" view accordingly.

bye, Dirk

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

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5714 (20101218) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5718 (20101220) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 



From jmucchiello at yahoo.com  Mon Dec 20 22:33:05 2010
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Mon, 20 Dec 2010 19:33:05 -0800 (PST)
Subject: [geeklog-devel] 1.8.0 Release Timetable
Message-ID: <842710.23032.qm@web31402.mail.mud.yahoo.com>

Any chance for my feature request[1] for a COM_newTemplate() function?
  Joe

[1] http://project.geeklog.net/tracking/view.php?id=1220



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

From websitemaster at cogeco.net  Tue Dec 21 09:57:32 2010
From: websitemaster at cogeco.net (Tom)
Date: Tue, 21 Dec 2010 09:57:32 -0500
Subject: [geeklog-devel] 1.8.0 Release Timetable
In-Reply-To: <842710.23032.qm@web31402.mail.mud.yahoo.com>
References: <842710.23032.qm@web31402.mail.mud.yahoo.com>
Message-ID: <002e01cba11f$6539b550$2fad1ff0$@net>

Personally, if you are going to be working on a template plugin I would
rather see that work go into the Geeklog template class itself. I rather not
split future theme development with 2 template options.

 

I know there have been arguments on this in the past but I would like to
make a few decisions on this ... 

 

I was planning to work on the Geeklog template class in the semi near future
(http://project.geeklog.net/tracking/view.php?id=1155).  I am pretty sure
your ideas (Joe's) cover a fair number of my changes/ideas and more.  If Joe
can and wants to work on this template stuff that's great.  It is something
I need (and I am sure others will use) and if he is doing it, it will free
up my time to work on other Geeklog features.

 

As a refresher, Joe what are some of the changes/features you want to add to
the Geeklog template class?

 

I wanted the ability:

- to have if statements in template files

- topics to have their own themes (this is based on some work I need to do
yet)

- have a base theme with any new themes just needing the template files that
have been modified

 

I will also add in your patch Joe for 1.8.0. At first I thought it was not
needed if you do end up working on the Geeklog template class but after
thinking about it having those 4 set_var calls in one place is best.

 

If Joe ends up working on the Geeklog template class then after the
Professional CSS theme and topic stuff I will probably work on the Forum
then. This would mean reviewing Blaines updated forum (and probably
modifying it to work with a straight install of geeklog again) from NexPro,
and setting up a proper repository and bugtracker.

 

Tom

 

From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello
Sent: December-20-10 10:33 PM
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] 1.8.0 Release Timetable

 

Any chance for my feature request[1] for a COM_newTemplate() function?
  Joe

[1] http://project.geeklog.net/tracking/view.php?id=1220




__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5719 (20101220) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5719 (20101220) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5721 (20101221) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

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

From jmucchiello at yahoo.com  Tue Dec 21 15:08:43 2010
From: jmucchiello at yahoo.com (Joe Mucchiello)
Date: Tue, 21 Dec 2010 12:08:43 -0800 (PST)
Subject: [geeklog-devel] Template development (was 1.8.0 discussion)
Message-ID: <659133.119.qm@web31404.mail.mud.yahoo.com>

> Personally, if you are going to be working on a template plugin I would
> rather see that work go into the Geeklog template class itself. I rather
> not
> split future theme development with 2 template options.

The two template options would involve caching and non-caching which was the 
original purpose of my CTL library. The first draft of the library had no if or 
other stuff. It just did the caching. The fancy stuff came later.

> I wanted the ability:
> 
> - to have if statements in template files

Done. And else, and loops. Done and done.

> - topics to have their own themes (this is based on some work I need to do
> yet)

Doable, as long as $tid or $topic is properly set globally. This will take some 
core modification because topic is transient, only existing if the URL includes 
it.

> - have a base theme with any new themes just needing the template files
> that
> have been modified

Done two ways, as you said OR with a custom directory under each theme. Never 
could figure out which was better. Putting a custom directory in each theme 
directory makes it easy for the site operator to tweak a theme without losing 
his changes after every upgrade. Doing it strictly by theme is nice for keeping 
theme sizes smaller, not that it really an issue.

Direct access to $LANG globals in templates. Done.


I wrote all of that in 2008 and it was taken up by glFusion. What I'd like to do 
for  Geeklog is split the caching part out of the template engine and make the 
template engine caching-aware. This way security-minded folks who don't like the 
idea of caching can turn it completely off but still get the benefits of {if} 
and people needing the performance boost can get it by turning on the caching.
 
> I will also add in your patch Joe for 1.8.0. At first I thought it was not
> needed if you do end up working on the Geeklog template class but after
> thinking about it having those 4 set_var calls in one place is best.

I actually assumed that would be the best use of that function.

The added benefit of allowing external development of the template engine is 
just for my benefit.

> If Joe ends up working on the Geeklog template class then after the
> Professional CSS theme and topic stuff I will probably work on the Forum
> then. This would mean reviewing Blaines updated forum (and  probably
> modifying it to work with a straight install of geeklog again) from
> NexPro,
> and setting up a proper repository and bugtracker.

Tom, once the patch is in Geeklog I will create a new template class that does 
all you are asking for and more. And it will work with all the existing template 
files and it will allow easier design of new features. Being able to vet new 
template features in a plugin has got to be a great way to move forward with 
many new features.


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

From websitemaster at cogeco.net  Fri Dec 24 10:44:20 2010
From: websitemaster at cogeco.net (Tom)
Date: Fri, 24 Dec 2010 10:44:20 -0500
Subject: [geeklog-devel] Geeklog.net Redesign
In-Reply-To: <21BE1B61-CDCD-4B85-9A49-72241FA9606B@haun-online.de>
References: <900574.29654.qm@web31402.mail.mud.yahoo.com>	<015d01cb8bef$a6ee49b0$f4cadd10$@net>	<AANLkTi=Mr4YcVv7u=wD3CNyMxjySUw79AE-iyUs+WCYT@mail.gmail.com>	<004b01cb8e42$4dab78a0$e90269e0$@net>
	<21BE1B61-CDCD-4B85-9A49-72241FA9606B@haun-online.de>
Message-ID: <004901cba381$6e292510$4a7b6f30$@net>

Hi All,

I have created a very simple and incomplete wiki page to start off our goal
of redesigning Geeklog.net

http://wiki.geeklog.net/index.php/Geeklog.net_Redesign

The purpose of this page is, it is a place for us to list the ideas/goals
each of us have for the website. This way we all have a central location for
our ideas. We can then use the mailing list to discuss ideas further and
maybe the forums to ask for further community input when needed.

I am not sure of the best location, format and layout for this is but at
least it is a start. As ideas come in we can change the layout of the page
and add further pages as needed. 

I expect this process to take us a while but I am looking forward to see
what we can accomplish!

Thanks

Tom
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5729 (20101224) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com