phpslash-devel

[Phpslash-devel] Re: M8 Goals, Release Criteria and TODO

[Mike G. <mi...@op...>]

Howdy folks,

Been busy this week, so sorry for the delay.

> Subject: Re: [Phpslash-devel] story save plugins
> From: Matthew Leingang <lei...@ma...>
> To: Joe Stewart <joe...@us...>
> > 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

Re: [Phpslash-devel] Re: M8 Goals, Release Criteria and TODO

[Peter C. <li...@cr...>]

On Wednesday 12 Nov 2003 6:19 am, Mike Gifford wrote:
> Howdy folks,
>
> Been busy this week, so sorry for the delay.
>
> > Subject: Re: [Phpslash-devel] story save plugins
> > From: Matthew Leingang <lei...@ma...>
> > To: Joe Stewart <joe...@us...>
> >
> > > 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.

I might be able to fit adding Wiki code to PSL in the current project I'm 
doing. If the client goes for it, or the budget allows. 

It would be good to have a common class that generates a textarea with 
appropriate input options. The class could then be used by the article, 
story, section modules, and we'd be sure of a common look and feel.

And HtmlArea is a neat option for those who want that could be allowed.

At first thoght, it seems a bit difficult to go from HTML back to Wiki (think 
about tables or links). I've not looked to see if someone's worked out how to 
do it already tho.

In effect, the processed HTML is another level of data caching - and as such, 
maybe doesnt belong in the main tables. (It would be good to have a content 
caching strategy that allows the choice of filesystem or database, but that's 
another debate)

> 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.

And it would make diffing between PSL and BE easier!

Peter

Re: [Phpslash-devel] Re: M8 Goals, Release Criteria and TODO

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

On Wed, Nov 12, 2003 at 12:14:15PM +0000, Peter Cruickshank wrote:
> 
> I might be able to fit adding Wiki code to PSL in the current project I'm 
> doing. If the client goes for it, or the budget allows. 
> 
> It would be good to have a common class that generates a textarea with 
> appropriate input options. The class could then be used by the article, 
> story, section modules, and we'd be sure of a common look and feel.
> 

See how the new snapshot works.  I used the WikiEngine from Back-End.


> And HtmlArea is a neat option for those who want that could be allowed.
> 

I got it working except htmlArea3 doesn't play well with ShankZen_ext.css.

> At first thoght, it seems a bit difficult to go from HTML back to Wiki (think 
> about tables or links). I've not looked to see if someone's worked out how to 
> do it already tho.
> 
> In effect, the processed HTML is another level of data caching - and as such, 
> maybe doesnt belong in the main tables. (It would be good to have a content 
> caching strategy that allows the choice of filesystem or database, but that's 
> another debate)
>

Another time.

> > 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.
> 
> And it would make diffing between PSL and BE easier!
> 

Will do soon.

> Peter
> 
>