Re: M8 Goals, Release Criteria and TODO

Howdy folks,

Been busy this week, so sorry for the delay.

> Subject: Re: [Phpslash-devel] story save plugins
> From: Matthew Leingang <leingang-c2Vpf+SSmYbWs/[email protected]>
> To: Joe Stewart <[email protected]>
> > My thoughts are to provide a plugin script in the module/story directory
> > instead of incorporating it in the Story class.  I'm not set on either
> > yet.  The plugins would be in a subdirectory much as blocktypes.
> OK, so what form does the data take in the database, though?  If it's
> entered as wiki does it stay as wiki?  

What we did with BE is have content field & then a content_source field
for every text field which you could use wiki or text markup with.

The html is stored in the content field for fast delivery, but when the
page is edited it is the content_source which is displayed in the format
it was entered in (be that html, wiki or plain text).

It would be cooler to translate it both ways so that you could edit it
in a wiki, store it as html and then translate that html into a wiki
when you are editing it.  That would allow you to switch markup types
mid-stream.

As far as a M8 goal, I'd also suggest running the code through something
like this to make it more consistently formatted:
	http://sourceforge.net/projects/beautifyphp/

It's worked fairly well for BE.

Mike
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/
Another world is not only possible, she is on her way -Arundhati Roy



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/