Re: [Simplog-devel] adodb

[Jim Hu <ji...@ta...>]

On Sep 21, 2004, at 11:26 AM, Jeremy Ashcraft wrote:

> I was just too lazy to go out to the adodb site and grab the latest 
> version when I built the current release. :)
> I think the permissions system needs an overhaul, so your ideas are 
> good.  Plus simplog is wide open for comment spam right now, so 
> locking down comments is a good idea.

I had been wondering, since the adobdb files in 0.91 are an older 
version than in 0.90!

>
> Here's a quick list of  some preliminary ideas for 1.0:
> - be able to enable/disable commenting for individual posts
> - new permissions system
> - sitewide templates/make it easier for users to customize look and 
> feel

As I recall a bunch of users asked for the option for a 3-column 
layout.  I think this could be done by duplicating the blocks stuff to 
be leftblocks and rightblocks and then setting up blocksadmin to 
display two copies of what it has now...perhaps the display could 
depend on whether the blog is specified as 2-column or 3-column.  
Alternatively, one could just use the current setup and make it so that 
blocks 1-n up go on the left, while n+1 to end go on the right.  Just 
to try this, I changed my blocks.php to add:

include_once("lib.php");
include_once ("class.BlogInfo.php");
include_once ("class.BlogEntry.php");

I also altered it so that each block starts with a comment 
"<!--block-->"
This allows me to treat blocks.php as a feed generator.  In my site, I 
inserted the following code in the part that encodes left side:

		$blocks=implode("",file("$baseurl/blocks.php?blogid=3"));
		
		$blockarray=explode("<!--block-->",$blocks);
		foreach ($blockarray as $key=>$block){
			if ($key<3) echo $block;
		}

and on the right column cell I put in:
	foreach ($blockarray as $key=>$block){
			if ($key>=3) echo $block;
		}

The result can be seen at: 
http://dimer.tamu.edu/simplog/index.php?blogid=3.  Actually, this can 
be done more cleanly by changing blocks.php to load up the array 
directly.  I may play with that idea tonight.

I guess a question is how much you want to do stuff for the user, vs. 
how much to just have tips on setting things up.  The basic blogs are 
very functional, and learning how to customize beyond the standard 
install is part of the fun!

> - extended text for posts
> - post via email
> - integrate htmlArea editor into app
Regarding editing:
- As I've said before, I hope this won't be a required editor, since as 
far as I can tell it doesn't work on Macs.  Does it work with other 
browsers on Windows?  In looking into this, it seems like there are 
other javascript based rtf/html editors out there.  FCKeditor seems to 
have a lot of hits on sourceforge, and there may be others.  
FCKEditor's demo almost works on Mozilla Firefox on my Mac, but not in 
Safari.

If this is done, I'd like to see some way where a user can configure 
what editor to use, or for Simplog to detect the browser and load one 
that works - or the basic textarea one.

- At a much simpler level, I'm thinking that it might be nice to have 
the editing boxes come up in a new window instead of next to the list 
of posts.  That way, when you click update, you'd close the editing 
window but go straight back to the list of posts - which would be right 
where you left it, instead of defaulting to the most recent.  It would 
also allow you to work in a larger window for the actual editing.

- In my copy, I did some tweaking to get rid of <br /> tags that get 
inserted by marker_sub inside tables.  I'm not happy with my 
implementation, and I'd like to work with the rest of you guys to make 
it better.  If there really is a good wysiwyg html/javascript editor 
out there this would be moot, of course.  In the meantime, what makes 
my current solution clunky is I'm having marker_sub look specifically 
for the tags I want to exempt from added breaks.  I could make things a 
lot simpler if I just make a rule that any line that ends in ">" 
followed by whitespace is not a real line break.  Users could put in 
two line breaks to get the <br /> tag back, or hard-code the <br />.  
Can anyone think of a reason why this would be bad?

> - user auto registration with/without admin approval
> - a couple other things I can't remember right now.....

There was a feature request from someone for a way to manage image 
uploads and links.

>
> anything else you guys would like to see?

Have both creation vs. last updated as fields...(I've done this in 
mine...it's trivial, but I haven't figured out where to change the 
install scripts to be compatible)
I'd like a way to email everyone on the acl for a specific blog.
I think the installer scripts need some work.  Is there a way to have 
two versions of xmlrpc.inc (with and without xmlrpc_decode and 
xmlrpc_encode) and have the installer detect based on error trapping 
which one to install?

...and...I'd like a script that automatically cooks all those recipes 
that jason posts on his blog!

Jim
<snip>