Re: [Phpslash-devel] phpSlash Roadmap discussuon - 0.8

[Joe S. <joe...@us...>]

On Sat, Sep 18, 2004 at 10:45:30AM +0100, Peter Cruickshank wrote:
> On Thu, 16 Sep 2004 12:41:57 -0500
> Joe Stewart <joe...@us...> wrote:
> 
> > phpSlash is not dead, maybe moving slow, but not dead.  The Back-End 
> > folks, led by Mike Gifford have been making lots of progress.
> > 
> > The psl 0.8 release cycle is about to speed up.  I'm planning on another 
> > beta test, then when that proves fairly stable, get a release candidate 
> > out.  I do not want a long release cycle on this.  Most everything here 
> > has been proven.
> 
> I've been using the alpha code for a while on a couple of sites with no
> major problems.
>

me too.

php-slash.org is now on the latest -dev snapshot release.

I kinda hope the Wiki will turn into something similar to 
http://manual.back-end.org.  I do like the current manual configuration on the site 
to allow comments, etc.  We can even open up editing privileges to be available 
publicly like a wiki.  Our rollback is cvs.
 
> > I'd like to update the phpSlash Roadmap to be something that we can work 
> > toward.
> 
> Excellent! I've split my thoughts on 0.9 into a separate email
> 
> > For psl 0.8:
> > 
> > - needs a printer css or printer friendly view.
> Yup
> > - the wap article pages are not available anymore either.
> How much is this used - is this a show-stopper?
> 

not a big problem to me.

> > Both of these could be added back using the old code, but I'd like to 
> > see them improved.
> > 
> > - I'd like to see someone familiar with phplist to configure it for a 
> > default setup to mimic our current headline mailer.  Then we could just 
> > drop the current code.  The phplist module is included in the current
> > beta.- there is a css issue in the phplist admin page I haven't debugged.
> 
> phpList might be a excessive for the situation where there are only a few
> people signing up, and only basic functionality is required. Just a
> thought.
> 

Probably true.  My concern is maintaing the existing code.  If our efforts are to 
maintain a phplist module instead, it seems to be a better use of resources.

> > - What skins should be included in the main download?
> > - What modules should be included?
> The ones I think it might sense to drop/turn off are glossary and poll.
> comment might also be optional, but it's still hardwired in places in the
> code, so we're stuck with it for now.
> 

glossary is the one in particular I had in mind.

The comments are almost to the point there could be other software used for this 
too.  The Comments code is getting pretty long in the tooth.  Ajay worked on the 
Comments and Poll.  No one has adopted them since he moved on.

> If some modules are NOT included, there needs to be some pretty clear
> instructions on how to download them and add them.
> 

This is true across the board.

> > - Anything else?
> 
> I wonder if this is a good point to create a new default database?
> 

Yes.  I've been thinking of splitting it out to two sql files - one core and one 
example data.

> As for skins, I clearly have a bias towards ShankZen! But it would be good
> to move to consistent use of style names. eg Where ShankZen uses
> "psl-desc", basic uses "desc". I think the "psl-" prefix is good, because
> it avoids namespace clashes with external modules... I'd be happy to update
> basic if you agree.
> 

a volunteer! great!  

How about a printer css?

Most of the skins that I ported kept all their style names instead of conforming to 
your convention.

> ShankZen's stylesheets could probably be simplified a little; again, I'd be
> happy to do this.
> 

There is an issue with the ShankZend htmlarea3 and one of the stylesheets now I 
think.  This may have been resolved.

> I've got other CSS files  that can be applied to ShankZen's templates.
> Would you be interested? How would they be included in a distribution?
> 

Good question.

At the very least - 

create a ShankZen directory in the styles ( like BE_Default)
put all your stylesheets there.
Put them in the header so that they can be chosen in the browser.

This would get them included and show they could be used in the header template as 
needed.


thanks,

Joe


> P
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Phpslash-devel mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpslash-devel