[geeklog-devtalk] geeklog-devel digest, Vol 1 #424 - 5 msgs

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. State of the Na^Wproject (Dirk Haun)
   2. Re: State of the Na^Wproject (Blaine Lang)
   3. Re: State of the Na^Wproject (Vincent Furia)
   4. Re: State of the Na^Wproject (Blaine Lang)
   5. Re: State of the Na^Wproject (Blaine Lang)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Sat, 30 Oct 2004 22:10:40 +0200
Organization: Terra Software Systems
Subject: [geeklog-devel] State of the Na^Wproject
Reply-To: geeklog-devel at lists.geeklog.net

Okay, I think I've fixed the issues with personal events (see CVS). Here
are a few remaining issues:

As mentioned in my other post, the regexp in COM_makeClickableLinks could
need some work.

Actually, I've been thinking if it was a good idea to do the parsing for
links at display time. We've seen that parsing for the "related" links in
stories used a lot of CPU power (hi to groklaw.net) - and now that that
has been resolved, we're doing the same thing again elsewhere.

The same applies to the autotags / autolinks.

For the clickable links in text posts, it would be possible to do the
parsing when they are saved (both comments and stories), although there
are one or two issues with that:

1) Should we undo the change when a plain-text story is edited later?
2) Comments don't store whether they had been posted in plain text or
HTML - that's done at display time by running yet another regexp over
them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.
clickable links + nl2br) when saving them). But that would mean that old
comments would have to be converted.

The whole point of autolinks, however, is that they ARE dynamic, so I
guess the only way out there is to introduce an option to disable them.

Thoughts on this?


Vinny, how are things re: comments in plugins?

That's all I can think of at the moment (well, it's enough ...).

bye, Dirk

P.S. I'll be offline for the next couple of days (back Thursday).


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


--__--__--

Message: 2
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] State of the Na^Wproject
Date: Sat, 30 Oct 2004 18:55:23 -0400
Reply-To: geeklog-devel at lists.geeklog.net

Dirk wrote:

> Actually, I've been thinking if it was a good idea to do the parsing for 

> links at display time.


I agree that we should store the links or autotags as their pseudocode tag 
as it will allow us to control the formatting and conversion as needed.
It also mean we can display the autotag or bbtag in it's [native] format 
when editing if we want.

I have the same issue with smilies - I should have left them as [bbcode].
There is a need here for a common API to handle how we add/edit/display or 
parse these tags.

Blaine
----- Original Message ----- 
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Sent: Saturday, October 30, 2004 4:10 PM
Subject: [geeklog-devel] State of the Na^Wproject


Okay, I think I've fixed the issues with personal events (see CVS). Here
are a few remaining issues:

As mentioned in my other post, the regexp in COM_makeClickableLinks could
need some work.

Actually, I've been thinking if it was a good idea to do the parsing for
links at display time. We've seen that parsing for the "related" links in
stories used a lot of CPU power (hi to groklaw.net) - and now that that
has been resolved, we're doing the same thing again elsewhere.

The same applies to the autotags / autolinks.

For the clickable links in text posts, it would be possible to do the
parsing when they are saved (both comments and stories), although there
are one or two issues with that:

1) Should we undo the change when a plain-text story is edited later?
2) Comments don't store whether they had been posted in plain text or
HTML - that's done at display time by running yet another regexp over
them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.
clickable links + nl2br) when saving them). But that would mean that old
comments would have to be converted.

The whole point of autolinks, however, is that they ARE dynamic, so I
guess the only way out there is to introduce an option to disable them.

Thoughts on this?


Vinny, how are things re: comments in plugins?

That's all I can think of at the moment (well, it's enough ...).

bye, Dirk

P.S. I'll be offline for the next couple of days (back Thursday).


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

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


--__--__--

Message: 3
Date: Sat, 30 Oct 2004 23:01:37 -0400
From: Vincent Furia <vfuria at gmail.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] State of the Na^Wproject
Reply-To: geeklog-devel at lists.geeklog.net


> Vinny, how are things re: comments in plugins?


I think its done.  Just a minor problem in how comments.php was
grabbing variables.  It's working on my test site (using geeklog.net
DB).  Though I just noticed that I'm using the most recent (1.3?)
version of filemgmt even though geeklog has an ealier version (1.2?)
installed.  I don't think that invalidated my tests.

Blaine, can you try out the most recent lib-common.php and comment.php
with your filemgmt to make sure they work as you'd expect (as they
used to in 1.3.9)?

Thanks,
Vinny

On Sat, 30 Oct 2004 22:10:40 +0200, Dirk Haun <dirk at haun-online.de> wrote:

> Okay, I think I've fixed the issues with personal events (see CVS). Here

> are a few remaining issues:

> 

> As mentioned in my other post, the regexp in COM_makeClickableLinks could

> need some work.

> 

> Actually, I've been thinking if it was a good idea to do the parsing for

> links at display time. We've seen that parsing for the "related" links in

> stories used a lot of CPU power (hi to groklaw.net) - and now that that

> has been resolved, we're doing the same thing again elsewhere.

> 

> The same applies to the autotags / autolinks.

> 

> For the clickable links in text posts, it would be possible to do the

> parsing when they are saved (both comments and stories), although there

> are one or two issues with that:

> 

> 1) Should we undo the change when a plain-text story is edited later?

> 2) Comments don't store whether they had been posted in plain text or

> HTML - that's done at display time by running yet another regexp over

> them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.

> clickable links + nl2br) when saving them). But that would mean that old

> comments would have to be converted.

> 

> The whole point of autolinks, however, is that they ARE dynamic, so I

> guess the only way out there is to introduce an option to disable them.

> 

> Thoughts on this?

> 

> Vinny, how are things re: comments in plugins?

> 

> That's all I can think of at the moment (well, it's enough ...).

> 

> bye, Dirk

> 

> P.S. I'll be offline for the next couple of days (back Thursday).

> 

> --

> http://www.haun-online.de/

> http://geeklog.info/

> 

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel

>


--__--__--

Message: 4
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] State of the Na^Wproject
Date: Sun, 31 Oct 2004 10:50:21 -0500
Reply-To: geeklog-devel at lists.geeklog.net

Hum, the LOCK TABLES call in comment.php is generating a SQL error for me. 
I've contacted my host admin to change my DB perms.
I wonder if others will see this issue with 1.3.10 -  I suspect we would 
have heard by now.

As soon as I get the perms updated, I will test.

Blaine
----- Original Message ----- 
From: "Vincent Furia" <vfuria at gmail.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Saturday, October 30, 2004 10:01 PM
Subject: Re: [geeklog-devel] State of the Na^Wproject



> Vinny, how are things re: comments in plugins?


I think its done.  Just a minor problem in how comments.php was
grabbing variables.  It's working on my test site (using geeklog.net
DB).  Though I just noticed that I'm using the most recent (1.3?)
version of filemgmt even though geeklog has an ealier version (1.2?)
installed.  I don't think that invalidated my tests.

Blaine, can you try out the most recent lib-common.php and comment.php
with your filemgmt to make sure they work as you'd expect (as they
used to in 1.3.9)?

Thanks,
Vinny

On Sat, 30 Oct 2004 22:10:40 +0200, Dirk Haun <dirk at haun-online.de> wrote:

> Okay, I think I've fixed the issues with personal events (see CVS). Here

> are a few remaining issues:

>

> As mentioned in my other post, the regexp in COM_makeClickableLinks could

> need some work.

>

> Actually, I've been thinking if it was a good idea to do the parsing for

> links at display time. We've seen that parsing for the "related" links in

> stories used a lot of CPU power (hi to groklaw.net) - and now that that

> has been resolved, we're doing the same thing again elsewhere.

>

> The same applies to the autotags / autolinks.

>

> For the clickable links in text posts, it would be possible to do the

> parsing when they are saved (both comments and stories), although there

> are one or two issues with that:

>

> 1) Should we undo the change when a plain-text story is edited later?

> 2) Comments don't store whether they had been posted in plain text or

> HTML - that's done at display time by running yet another regexp over

> them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.

> clickable links + nl2br) when saving them). But that would mean that old

> comments would have to be converted.

>

> The whole point of autolinks, however, is that they ARE dynamic, so I

> guess the only way out there is to introduce an option to disable them.

>

> Thoughts on this?

>

> Vinny, how are things re: comments in plugins?

>

> That's all I can think of at the moment (well, it's enough ...).

>

> bye, Dirk

>

> P.S. I'll be offline for the next couple of days (back Thursday).

>

> --

> http://www.haun-online.de/

> http://geeklog.info/

>

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel

>

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


--__--__--

Message: 5
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] State of the Na^Wproject
Date: Sun, 31 Oct 2004 12:01:13 -0500
Reply-To: geeklog-devel at lists.geeklog.net

We were running MySQL 4.0.1.5 and it was in 4.x that the new Permission 
Lock_table_priv was added.
Maybe if 3.23 is being used, this permission test is skipped or grouped into 
another more common permssion.
Note: This permission is global per user and not per DB.

Anyway: Tested comments with the filemgmt plugin on 1.3.10 and it's broken.
Don't work on my site (plugin 1.3) or on Geeklog (plugin 1.2).

I'll have to track down why. I wrote this code 2+ years ago. I'm sure I'd do 
things different today.

Blaine
----- Original Message ----- 
From: "Vincent Furia" <vfuria at gmail.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Saturday, October 30, 2004 10:01 PM
Subject: Re: [geeklog-devel] State of the Na^Wproject



> Vinny, how are things re: comments in plugins?


I think its done.  Just a minor problem in how comments.php was
grabbing variables.  It's working on my test site (using geeklog.net
DB).  Though I just noticed that I'm using the most recent (1.3?)
version of filemgmt even though geeklog has an ealier version (1.2?)
installed.  I don't think that invalidated my tests.

Blaine, can you try out the most recent lib-common.php and comment.php
with your filemgmt to make sure they work as you'd expect (as they
used to in 1.3.9)?

Thanks,
Vinny

On Sat, 30 Oct 2004 22:10:40 +0200, Dirk Haun <dirk at haun-online.de> wrote:

> Okay, I think I've fixed the issues with personal events (see CVS). Here

> are a few remaining issues:

>

> As mentioned in my other post, the regexp in COM_makeClickableLinks could

> need some work.

>

> Actually, I've been thinking if it was a good idea to do the parsing for

> links at display time. We've seen that parsing for the "related" links in

> stories used a lot of CPU power (hi to groklaw.net) - and now that that

> has been resolved, we're doing the same thing again elsewhere.

>

> The same applies to the autotags / autolinks.

>

> For the clickable links in text posts, it would be possible to do the

> parsing when they are saved (both comments and stories), although there

> are one or two issues with that:

>

> 1) Should we undo the change when a plain-text story is edited later?

> 2) Comments don't store whether they had been posted in plain text or

> HTML - that's done at display time by running yet another regexp over

> them. So maybe it would make sense to convert them to "pseudo HTML" (i.e.

> clickable links + nl2br) when saving them). But that would mean that old

> comments would have to be converted.

>

> The whole point of autolinks, however, is that they ARE dynamic, so I

> guess the only way out there is to introduce an option to disable them.

>

> Thoughts on this?

>

> Vinny, how are things re: comments in plugins?

>

> That's all I can think of at the moment (well, it's enough ...).

>

> bye, Dirk

>

> P.S. I'll be offline for the next couple of days (back Thursday).

>

> --

> http://www.haun-online.de/

> http://geeklog.info/

>

> _______________________________________________

> geeklog-devel mailing list

> geeklog-devel at lists.geeklog.net

> http://lists.geeklog.net/listinfo/geeklog-devel

>

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



--__--__--

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


End of geeklog-devel Digest