Update of /cvsroot/phpslash/phpslash-ft/doc/html
In directory usw-pr-cvs1:/tmp/cvs-serv24872/doc/html
Modified Files:
Makefile phpslash.sgml
Log Message:
Doc work
Index: Makefile
===================================================================
RCS file: /cvsroot/phpslash/phpslash-ft/doc/html/Makefile,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** Makefile 2001/11/23 16:29:23 1.1
--- Makefile 2001/11/23 20:37:40 1.2
***************
*** 39,42 ****
clean :
@echo "----------- Removing all generated docs"
! rm -f *.html *.txt single/*
--- 39,42 ----
clean :
@echo "----------- Removing all generated docs"
! rm -f *.html *.txt single/phpslash.html
Index: phpslash.sgml
===================================================================
RCS file: /cvsroot/phpslash/phpslash-ft/doc/html/phpslash.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** phpslash.sgml 2001/11/23 17:54:14 1.7
--- phpslash.sgml 2001/11/23 20:37:40 1.8
***************
*** 15,23 ****
<author>
! <url url="http://www.phpslash.org/" name="The phpSlash Group">
<date>v0.3, November 23, 2001
<abstract>
! phpSlash is a PHP weblog. Originally it was a port of Rob Malda's
<url url="http://www.slashcode.org/" name="slashcode"> from perl to
php.
--- 15,23 ----
<author>
! <url url="http://phpslash.sourceforge.net/" name="The phpSlash Group">
<date>v0.3, November 23, 2001
<abstract>
! phpSlash is a PHP weblog and almost-CMS. Originally it was a port of Rob Malda's
<url url="http://www.slashcode.org/" name="slashcode"> from perl to
php.
***************
*** 39,42 ****
--- 39,178 ----
much further along then the slash-0.2 system.
+ <sect1> History
+ <p>
+ Every project has History. Here's the first and Second README's for phpSlash.
+ <sect2> README.php
+ <p>
+ PHPSlash v0.2, $Id$
+ *******************************************************************
+ This is my attempt to fix some of the bugs in the existing PHPSlash codebase
+ which has not been updated in coming almost to one year. Efforts to contact
+ Jay Bloodworth has come to null, so this is my humble effort to contribute
+ back to the PHP/PHPLIB communitity. :-)
+
+ **Please see the changes file for current changes and enhancements
+
+ Bugs fixed or feature made working:
+ * Upgraded for use with PHPLIB v7 which uses container classes.
+
+ Fixed a bunch of stuff in the admin page, of note is the delete and update
+ mechanism. To delete a record just click on the checkbox at the side and
+ click "delete". Simple, huh?
+
+ To save a record is also pretty intuitive, just fill the the fields and
+ click "save". To update an existing record is _NOT_ so intuitive in a sense
+ that I have no "update" button (soon!), but for now the "save" button also
+ acts as the "update" button..
+
+ Some notable fixes in the admin page:
+ * Variable management subsystem is now working (save/update, delete)
+ * Authors management subsystem is now working (save/update, delete)
+ * Blocks management subsystem is now working (save/update, delete)
+ * Sections management subsystem is now working (save/update, delete)
+ * Topics management subsystem is now working (save/update, delete)
+
+ Schema changes:
+ * Implemented a unique bid on table blocks. Therefore the way index.php3
+ displays blocks has also changed slightly.
+
+ TODO:
+ * Continue fixing the remaining options of the admin page: i.e. list, new,
+ modify, submissions, poll.
+ * Can't see too far ahead in the future! ;-)
+
+ Disclaimers:
+ Usual bunch of disclaimers. See below.
+
+
+ Bug reports, suggestions, compliments, constructive criticism to me.
+ Wai-Sun "Squidster" Chia
+ wai...@ms...
+
+
+
+ ****************************************************************************
+ PHPSlash v0.1 September 23, 1998
+
+ "I'll take 'Questionable But Possibly Useful Hacks' for $600, Alex."
+
+ "The answers is: You're looking at it right now."
+
+ "What is the PHP3 port of the Slashdot code?"
+
+ Yes, friends, if you were thrilled to learn that Rob Malda was
+ releasing the source code to his Pullet Surprise winning Slashdot site
+ but heartbroken to find out you'd have to perlify your lean, mean web
+ serving machine to use it, this may be your lucky day.
+
+ Probably not though.
+
+ But seriously. It's Slashdot, ported to PHP3. It attempts to be a
+ drop in replacement for the perl code (using the same databases and
+ such) and almost succeeds. It's a fairly naive port (line by line cut
+ and paste in many places), but I tried to improve things where I
+ could. In future releases I hope to neaten things up considerably and
+ bring the code closer to standard PHP3 idiom.
+
+ Caveats
+
+ 1) You need phplib, the 'sessions and more library' by Boris Erdman
+ and Kristian Kohntopp. Get it at phplib.netuse.de. I used phplib
+ because it makes the session stuff easy and the database stuff
+ portable. Future releases will use more phplib, so get it now and
+ learn to love it. You need a table in your slash db called
+ active_session as given in the phplib instructions. You can ditch the
+ session table given in the slash distro.
+
+ 2) We're based on slash-0.2, which doesn't have the user account
+ features Slashdot has recently acquired. I'll add that kind of stuff
+ in a later release when I can do it sanely.
+
+ 3) Most configuration goes on in config.php3, in the obvious places.
+ Note that the look and feel section is pretty sparse; I strated to
+ parameterize a number of the screens but got lazy. Again, wait for a
+ later release.
+
+ 4) Slash uses a daemon to generate static files from the CGI's every
+ minute. PHPSlash doesn't. The perl slashd script should still work
+ (if you have the Slash perl code), but you have to change some php
+ code to point to the generated static files. Grep for $turl in the
+ .php3 files to find where to do this.
+
+ 5) That's all the help I'm going to give you. If you're afraid to
+ look at the code and figure it out for yourself, you shouldn't be
+ using this software.
+
+ Disclaimers
+
+ The original Slash Perl code was written by Rob Malda and Dave
+ DeMaagd. Their notes appear in README.slash, even though their code
+ isn't in this distro. This is a derived work from their code, and
+ unless they grant otherwise, is still covered by their licence; you
+ must display the Slashdot logo and link to http://slashdot.org on your
+ page. There are no further restrictions due to my contribution.
+
+ I make no guarantee and provide no warantee for this code, not even
+ an implied warantee of fitness for a particular purpose, nor any
+ assurance that this software will not damage your system. In
+ particular, I make no guarantee that this software will behave in
+ whole or in part like any version of the Slash software distributed by
+ Rob Malda and/or Dave DeMaagd.
+
+ Future Plans
+
+ As mentioned above: I'm planning on cleaning up the code to take
+ greater advantage of the features provided by PHP3. I also intend to
+ make the code more customizable and make it easier to integrate into
+ an existing site, in particular with regard to the session stuff. A
+ future release will probably require my Form Class library (I
+ originally thought it wouldn't help much, but in retrospect it would
+ have been quite useful). Some attempt will be made to track the
+ development of perl Slash, but not necessarily feature for feature.
+
+ Bug reports, suggestions, compliments, constructive criticism to me.
+
+ Jay Bloodworth
+ ja...@pa...
+
<!-- START SECTION: Installation -->
<sect>Installation <label id="sec-install">
***************
*** 827,844 ****
<!-- START SECTION: FAQ -->
<sect>Frequently Asked Questions (FAQ)
!
! <sect1>What is phpSlash exactly?
<p>
It's a port of Rob Malda's slash-0.2 code (which runs the popular website
<url url="http://www.slashdot.org/" name="Slashdot">to php3. It also
! tries to do things a better when it can.
! <sect1>Why shouldn't I use Rob's slash code. Isn't it better?
<P>
You can. It has its own issues which are not within the scope
of this document. My best suggestion to sign up on the
! slash-help list and find out for your self.
! <sect1>Who did / does all this?
<p>
Jay Bloodworth did the original 0.1 port. A year after that Wai-Sun
--- 963,987 ----
<!-- START SECTION: FAQ -->
<sect>Frequently Asked Questions (FAQ)
! <p>
! Many of these Questions ans Answers have been pretty much cribbed
! directly from the mailing list, archives and other meial conversations.
! If they seems a bit conversationsal, that's why.
! <sect1> About phpSlash and its requirements.
! <sect2>What is phpSlash exactly?
<p>
It's a port of Rob Malda's slash-0.2 code (which runs the popular website
<url url="http://www.slashdot.org/" name="Slashdot">to php3. It also
! tries to do things a better when it can. Since the original port
! phpSlash has slowly developed a bit of a CMS following. The current
! thinking is on enhancing these features.
! <sect2>Why shouldn't I use Rob's slash code. Isn't it better?
<P>
You can. It has its own issues which are not within the scope
of this document. My best suggestion to sign up on the
! slash-help list and find out for your self. You may also want
! to look at <url url="http://www.slashcode.com" name="Slashcode">.
! <sect2>Who did / does all this?
<p>
Jay Bloodworth did the original 0.1 port. A year after that Wai-Sun
***************
*** 846,860 ****
CREDITS page to the current developers.
! <sect1>What do I need to use phpSlash?
<p>
You should read the <ref id="sec-install" name="Installation Section"> of
this manual for a list of requirements for running phpSlash.
! <sect1>Can I use PHP4?
<p>
Yes. Currently PHPSlash is written for PHP4 then ported back to
! PHP3 if there are any issues.
! <sect1>Ok. so I have all these tarball's sitting here. What do I do with them?
<p>
Untar, configure, compile and install. There should be
--- 989,1011 ----
CREDITS page to the current developers.
! <sect2>Why is your website so thin in the content department?
! <p>
!
! We write code, not HTML. :) Seriously, the phpslash.org site
! is always under development and if you want answers to questions
! then the best place is the mailing list.
!
! <sect2>What do I need to use phpSlash?
<p>
You should read the <ref id="sec-install" name="Installation Section"> of
this manual for a list of requirements for running phpSlash.
! <sect2>Can I use PHP4?
<p>
Yes. Currently PHPSlash is written for PHP4 then ported back to
! PHP3 if there are any issues. This will chnage with version 0.7 of phpslash
! which will drop support for php3. You have been warned.
! <sect2>Ok. so I have all these tarball's sitting here. What do I do with them?
<p>
Untar, configure, compile and install. There should be
***************
*** 864,868 ****
everything else working right.
! <sect1>What about PHPLIB and gpc_magic_quotes?
<p>
--- 1015,1020 ----
everything else working right.
! <sect1> PHPLIB Related questions.
! <sect2>What about PHPLIB and gpc_magic_quotes?
<p>
***************
*** 874,878 ****
gpc_magic_quotes = Off
! <sect1>What can I do to avoid using prepend.php3 on every page I serve?
<p>
Nothing. phpSlash needs much of phplib's functionality,
--- 1026,1030 ----
gpc_magic_quotes = Off
! <sect2>What can I do to avoid using prepend.php3 on every page I serve?
<p>
Nothing. phpSlash needs much of phplib's functionality,
***************
*** 887,891 ****
line that require()'s prepend.php3
! <sect1>Someone told me that if I just hardcode in an include() to phplib's ct_sql.inc class things will work ok. Why can't I do this?
<p>
It breaks phplib session and auth features which will soon be
--- 1039,1043 ----
line that require()'s prepend.php3
! <sect2>Someone told me that if I just hardcode in an include() to phplib's ct_sql.inc class things will work ok. Why can't I do this?
<p>
It breaks phplib session and auth features which will soon be
***************
*** 895,901 ****
time.
! <sect1>I read all your documentation TWICE and still can't figure this out!!
<p>
Try subscribing to the phpslash mailing list. To subscribe
visit the <url url="http://www.phpslash.org" name="phpslash website">
--- 1047,1112 ----
time.
! <sect2> Performance Tuning
<p>
+ <tscreen><verb>
+ > 1. Performance. Has anyone tested how much traffic
+ > phpslash can take. Granted, there are a lot of
+ > variables in a hosted environment, but all I'm looking
+ > for is a ball bark figure. In other words, of the
+ > sites currently running phpslash, what is your traffic
+ > level and are you satisfied with the performance? Now
+ > that I've got phpslash up and running, the *only*
+ > reservation I have is developing a popular site and
+ > then having it brought to it's knees.
+ >
+ </verb></tscreen>
+
+ A goodly amount :) It really depends on the hardware and how much load
+ your db can take (Does php have a limited amount of connections to mysql?,
+ Is the db server already at it's mx load, etc..) use a benchmarking tool
+ like ab to get the specfics, and hit the list archive for last month, we
+ had a discussion about this. the short answer is that things start to
+ break on lighweight / overloaded servers at about 10-20 constant
+ concurrent connections (ie: getting slashdotted.. as long as there aren't
+ peopl pounding away at your index.php3 all the time, you'll probably be
+ alright)
+
+ Run some stats like analog on your site to see when the "peak" hours
+ are. Then during those times watch your load and see if you need any
+ improving. Turn on the apache status support page to get a view of
+ what's going on inside the webserver. That's always helpful. Also,
+ check out the status on the MySQL server to see how loaded it is.
+ Since PHPSlash is very DB heavy, you don't want that to be the
+ bottleneck.
+
+ There's already been a bunch of suggestions about improving
+ the speed so I'll add on s'more:
+
+ - some php cache program. The Zend one is probably out of the question,
+ but there's APC and one other that I can't remember the name which are
+ free. If you've got a slow CPU then this would be the way to go. The
+ cache compiles the php script and stores it in memory so when the next
+ request comes in it doesn't need to recompile. Just make sure you don't
+ do this during development...
+
+ - mod_gzip - if you're low on bandwidth, then install this and it will
+ compress the data before sending it across the wire. I've heard the CPU
+ load isn't that high, but YMMV.
+ - RAMDISKS - if you have slow-ass IDE disks (or the data on an NFS
+ partition like me) then you can put all the information onto a RAMDISK.
+ By default Redhat Makes a couple ramdisks and that should be enough to
+ mount and deploy a production site.
+
+ - You can also move the database onto another machine.
+
+ - Get all the static pages on your site and let the tux webserver run them.
+ This will lessen the load on Apache and make things *seem* zippier.
+
+
+ <sect1> Getting Help.
+ <sect2>I read all your documentation TWICE and still can't figure this out!!
+ <p>
+
Try subscribing to the phpslash mailing list. To subscribe
visit the <url url="http://www.phpslash.org" name="phpslash website">
***************
*** 904,915 ****
else has the same problem.
! <sect1>Why is your website so thin in the content department?
! <p>
!
! We write code, not HTML. :) Seriously, the phpslash.org site
! is always under development and if you want answers to questions
! then the best place is the mailing list.
!
! <sect1>How do I get the CVS Copy?
<p>
Visit the <url url="http://www.sourceforge.net/projects/phpslash/"
--- 1115,1120 ----
else has the same problem.
! <sect1> Bugs, info, CVS and all things dev related
! <sect2>How do I get the CVS Copy?
<p>
Visit the <url url="http://www.sourceforge.net/projects/phpslash/"
***************
*** 921,925 ****
in developing stuff, check-out the phpslash-ft module.
! <sect1>I'm still having trouble with this stupid CVS thingie. Where do I go for more info?
<P>
--- 1126,1130 ----
in developing stuff, check-out the phpslash-ft module.
! <sect2>I'm still having trouble with this stupid CVS thingie. Where do I go for more info?
<P>
***************
*** 928,937 ****
http://linuxdoc.org/HOWTO/CVS-RCS-HOWTO.html
! <sect1>So I found a bug (and fixed it). Now what?
<P>
File a bug report at our Sourceforge Site. You can attach
! patches to bug reports as well.
! <sect1>What's the deal with how new features get into the source?
<P>
--- 1133,1144 ----
http://linuxdoc.org/HOWTO/CVS-RCS-HOWTO.html
! <sect2>So I found a bug (and fixed it). Now what?
<P>
File a bug report at our Sourceforge Site. You can attach
! patches to bug reports as well. You'd also be wise to send
! a note to the phpslash-users list to discuss the fix.
! You may have just patched a feature :)
! <sect2>What's the deal with how new features get into the source?
<P>
***************
*** 963,975 ****
layout code.
! <sect1>So, phpSlash is cool. When will it sport user customization and stuff like slashdot does now?
<P>
! 0.6 has just been released and we're working on an overhaul of the
! authentication system which will have hooks for user accounts and all that
! great stuff! Look at the Roadmap for future development.
<sect> Developer Documentation
<sect1> Credits
<sect1> CVS Commit Rules
<sect1>Roadmap
<P>
--- 1170,1387 ----
layout code.
! <sect2>So, phpSlash is cool. When will it sport user customization and stuff like slashdot does now?
<P>
! 0.6 has just been released and we're working on an overhaul of the
! authentication system which will have hooks for user accounts and all that
! great stuff! Look at the Roadmap for future development.
+ <sect1> Argh!!! I Don't Understand!! It's Broken! (Aka: The "WFT?" Section)
+ <sect2> Javascript and CSS in phpslash
+ <p>
+ The javascript I've put into the templates doesn't work. Why?
+ This is the template engine at work. There are two ways around this:
+ <sect3> Answer 1
+ <p>
+ Yep I got this too trying to build a web editor for the templates, and it was
+ just deleting the {VARIABLES} after saving.
+ There are two different solutions to override this template bug :
+ 1) for editing purposes (text only, no html or javascript) :
+ replace "{" by "{"
+ replace "}" by "}"
+ 2) for displaying purposes :
+ isolate the { and the } on a different single line
+ instead of
+ <tscreen><verb>
+ function blah() { return 0; }
+ </verb></tscreen>
+ try this :
+ <tscreen><verb>
+ function blah()
+ {
+ return 0;
+ }
+ </verb></tscreen>
+ or this :
+ <tscreen><verb>
+ function blah() {
+ return 0;
+ }
+ </verb></tscreen>
+
+ Just remember to avoid opening and closing
+ brackets on the same line..This works fine with css declaration so it
+ should work too with javascript. There is a version of phpslash saturated
+ with dhtml, css and javascript declarations here :
+ <url url="http://madchat.sourceforge.net" name="http://madchat.sourceforge.net">
+ (you'll need IE5 or greater as it's not a compatible code).
+ <sect3> Answer 2
+ <p>
+ Answer 2:
+ put all your jscript in seperate .js files and then put
+ #lt;script language="javascript" src="/path/to/myJavaScriptFile.js">
+ </script> in the HTML template. It's functionally the same as adding the
+ jscript inline to your HTML document, but causes an additional HTTP
+ request per <script src=".."> </script> Note that this
+ will only let you add your function declerations, browser busting,
+ etc.. you'll still need to put function calls in the HTML tags as normal,
+ but they shouldn't present a problem.. it's the { } that are screwing up
+ your template engine.
+
+ <sect2> What is extrans?
+ <p>
+ html tags are translated to html entities. i.e.:
+ '<' (less than) becomes '&lt;'
+
+ <sect2> How come the parser doesn't insert <br> where <br> is needed when saving as html ?
+ <p>
+ Semantics. "html" does no formatting to the text. "plain text"
+ adds the break tags in place of line breaks.
+
+ <sect2> Is there any way to make links in extended translation ?
+ <p>
+ Choose html and change the portion that should have ext translation.
+
+ <sect2> How do I add a poll? It doesn't seem intuitive
+ <p>
+ Question:
+ I want to simply add a new poll. I am confused about what to enter in "data".
+ I looked at another poll and it has some ID information and some normal html.
+ Do I simply increment the ID? Where can I find more information on this?
+ Answer:
+ I wasn't too sure about what you meant by "data" but then I realized
+ that you were looking at the "block" section for the poll stuff. You
+ need to head on over to the "Polls" section, click "new",
+ then it willask you for the question and possible answers. If you select the
+ "current" box then the poll will show up on the main page.
+ See, the "poll" type in the block section just controls _how_ the
+ block is displayed on the main page. Like the title, caching, and it's
+ placement, the Poll Admin page does the main admin work like
+ adding/deleting polls.
+
+ <sect2> Section Blocks do what?
+ <p>
+ Question:
+ Can someone explain how sections and blocks work? Say I want to make a section appear on the right side on the front page called "Book Reviews" that automatically does a query and shows the last 5 things with the topic "Book Review". How can I do that?
+
+ Answer:
+ <tscreen><verb>
+ Type: query
+ Owned by Section: Home
+ Source URL: topic=Book%20Review&max=5 (
+ Expire Length: 14400 ( just an example - cache results for 4 hours)
+ </verb></tscreen>
+ If you are using multiple block columns make sure you add a "column"
+ option with the "right" as the option
+
<sect> Developer Documentation
<sect1> Credits
+ <p>
+ See the CREDITS file in the "docs" directory of your distro or see the
+ Developer page on the <url url="http://sourceforge.net/prohects/phpslash/"
+ name="phpslash Sourceforge project page">
<sect1> CVS Commit Rules
+ <p>
+ We're certinaly not as hard ass about the ruls as the PEAR folks are,
+ but please try to be kind, other people have to use / work / read your code too.
+ <tscreen><verb>
+ Some rules for phpSlash CVS committers:
+
+ - All changes must be logged in the CHANGES file, at the top.
+
+ - Keep your changes compatible.
+
+ - Please try commit tested code that will work as expected.
+
+ - Use meaningful log messages. They are collected and mailed
+ out to the mailing list, php...@li....
+
+ Coding Style:
+ ------------------------------------------
+ Comments:
+ - Use C-Style /* */ and // comments only. # Should be phased out
+ - Use // for in code comments, but /* */ for headers and multi-line
+ comments (ie: turning off Debug features)
+ - Always include your initals or cvs username (if you have one) and
+ preferably your email address if it is not in the CREDITS file
+ - Please leave intelligent notes in comments. Refrain from:
+ /* I'm gonna do something cool, don't change this */
+ A better way is:
+ /* nh: Don't touch, I'm working on making the fliberty thing flip as
+ * well as spin - Apr, 9, 2000
+ */
+ - Please leave comments for things that are not self evident
+ (esp. for Regular Expressions)
+
+ Functions / Objects:
+ - Should be well commented as to their arguments, return value, what they do
+ and how they work. This should take place on the lines preceding the
+ function declaration.
+ - Should be as minimalistic as possible. If it can be bnroken into two
+ functions, please do so.
+ - Wrapper functions to provide multiple methods of output are highly
+ recommended.
+ - Functions should be named likeThis() and classes LikeThis.
+
+ Variable Naming:
+ - Hungarian Notation is prefered for things that are gloablly
+ accessable. Private variables for objects and functions should be
+ named to something indicative of what they do. No cutesy crap that
+ we'll all forget in 6 months.
+ - Keep it short, but not incomprehensable. $tmp_cnt is better than
+ $temporaryVariableThatIsACounterForMeRightNow and better than $t
+ - Mixed case ($tmpCnt) or underscore ($tmp_cnt) usage only?
+
+ Whitespace:
+ - USE IT!!!!
+ - Use a space between function parameters, and after a comma.
+ - Just becasue you can write a complex one-liner doesn't mean you have
+ to. Take the extra lines and use curly braces.
+ - Indent level of 3
+ - No tabs anywhere, spaces only.
+ For Example:
+ someFunction() {
+ if ($someVar) {
+ doOtherFunction($foo, "bar");
+ } else {
+ error("You *are* stupid! Don't do that");
+ }
+ }
+
+ Module / Class / Include file Format:
+ - Should start with a line(s) that tells a reader what it is, what
+ package it comes from, what it does, CVS $Id$ line
+ - Templates are an execption to that above rule. They should have an
+ HTML comment in them that points their ownership to a class
+ - Setup any needed variable first, then include() files, then declare
+ functions, then page processing, then page output.
+
+ Docs:
+ - Always alert the doc maintainer when importing changes that break the
+ info covered in the docs.
+
+ DB:
+ - Changes to the main db schema *require* a that an upgrade patch be
+ posted as well. Your change will be backed out if you don't provide a
+ patch as well.
+ - Queries should be presented in this format:
+
+ $q = "SELECT story.title,
+ story.dept,
+ [...snip...]
+ FROM psl_story story,
+ [...snip...]
+ WHERE story.story_id = '$story_id'
+ AND authors.aid = story.user_id
+ [...snip...]
+
+ It's a much easier read like this instead of having it compiled onto
+ one line.
+
+ Debug:
+ - Leaving debug code in is ok for experimental features, please make
+ sure you submit your code with debug turned off / commented
+ out though.
+ </verb></tscreen>
+
<sect1>Roadmap
<P>
***************
*** 977,981 ****
will available sooner.)
! <sect1>phpSlash 0.5x -> Burrito
<P>
<itemize>
--- 1389,1393 ----
will available sooner.)
! <sect2>phpSlash 0.5x -> Burrito
<P>
<itemize>
***************
*** 983,987 ****
</itemize>
! <sect1>phpSlash 0.6 -> Fajita
<P>
<itemize>
--- 1395,1399 ----
</itemize>
! <sect2>phpSlash 0.6 -> Fajita
<P>
<itemize>
***************
*** 994,998 ****
</itemize>
! <sect1>phpSlash 0.65 -> Steak Fajita
<P>
Expected release: 2 - 3 months after 0.6
--- 1406,1410 ----
</itemize>
! <sect2>phpSlash 0.65 -> Steak Fajita
<P>
Expected release: 2 - 3 months after 0.6
***************
*** 1004,1008 ****
</itemize>
! <sect1>phpSlash 0.7 -> Chimichanga
<P>
[Expected Release: 3 -4 months after 0.65]
--- 1416,1420 ----
</itemize>
! <sect2>phpSlash 0.7 -> Chimichanga
<P>
[Expected Release: 3 -4 months after 0.65]
***************
*** 1013,1017 ****
</itemize>
! <sect1>phpSlash 0.8 -> Gordita
<P>
[Expected Release: 3 - 4 months after 0.7]
--- 1425,1429 ----
</itemize>
! <sect2>phpSlash 0.8 -> Gordita
<P>
[Expected Release: 3 - 4 months after 0.7]
***************
*** 1028,1033 ****
</itemize>
! <sect1>phpSlash 0.9 -> Salsa
! <P>
[Expected Release: Depends on PeerPress Group]
( Note: PeerPress doesn't seem to be doing anything. this will be
--- 1440,1445 ----
</itemize>
! <sect2>phpSlash 0.9 -> Salsa
! <p>
[Expected Release: Depends on PeerPress Group]
( Note: PeerPress doesn't seem to be doing anything. this will be
***************
*** 1045,1049 ****
</itemize>
! <sect1>phpSlash 1.0 -> Margarita
<P>
[Expected Release: ASAP after 0.9]
--- 1457,1461 ----
</itemize>
! <sect2>phpSlash 1.0 -> Margarita
<P>
[Expected Release: ASAP after 0.9]
***************
*** 1053,1060 ****
will be the next stable branch, evolved from 1.1.. So on and so forth.
</itemize>
! <P>
! Unknowns so far
! (Allowable into pre-1.0 provided that it works well and doesn't require a
major rewrite.)
<itemize>
<item>Moderation (Here we go again...)
--- 1465,1472 ----
will be the next stable branch, evolved from 1.1.. So on and so forth.
</itemize>
! <p>
! <sect2>Unknowns so far (Allowable into pre-1.0 provided that it works well and doesn't require a
major rewrite.)
+ <p>
<itemize>
<item>Moderation (Here we go again...)
***************
*** 1064,1068 ****
</itemize>
! Post 1.0 Features:
<itemize>
<item>e-commerce integration?
--- 1476,1481 ----
</itemize>
! <sect2>Post 1.0 Features
! <p>
<itemize>
<item>e-commerce integration?
|