Re: [Openinteract-dev] Document Review implementation questions

[Chris W. <ch...@cw...>]

Andrew Hurst wrote:
>   I'm just about to start work on the changes I've been mentioning this 
> week, and I have a couple questions before I begin.
> 
> 1. I noticed in the TODO for the comments package you list "resist 
> feature creep" :)  Should I fork another comments package from that 
> (maybe call it comments-creepy) that includes the changes I've 
> mentioned, topics for comments, comment default security, etc.?

I think creating another comments package is a good idea. (I dunno 
about 'comments-creepy', but that's your perogative :-)

BTW, what do you mean by 'topics for comments'?

> 2. Would you rather me modify the news package to allow uploaded files 
> and paginate the articles or would you rather have a basic 'document' 
> package, that would have the features mentioned before (splitting into 
> parts based on html, uploading files, etc.).  I'm leaning towards the 
> latter, since it would allow an easier 'all-in-one' interface for 
> editing a document all at once, or editing an individual part, etc.

The 'base_page' package does some of what you're mentioning. You can 
edit HTML/text documents through the browser or upload documents 
(and replace them) as well. IIRC it has a rough (and possibly 
undocumented) pagination scheme too, but it's been a while.

> 3. When I worked on Scoop we had a var (essentially a feature toggle, on 
> or off if you want it enabled) for everything under the sun, 
> configurable through an admin interface.  I've noticed no real such 
> thing in OI, other than the action.perl and server.ini files.  I was 
> thinking that the comment topics should be able to be turned on and off, 
> I don't think that everyone would need that.  Any suggestions on where 
> to put this flag?

Probably the best place for it would be the global override 
configuration file. This is a file that remains untouched by package 
upgrades but is still able to modify them. For instance, I could 
have something like:

[myaction mytoggle]
task  = add
value = yes

(I can't remember the exact syntax, but I think the 
OI::Config::GlobalOverride module might be documented... I can fill 
in details later if you like.)

You could have people modify this directly or create a web interface 
for it, with the caveat that the web interface changes won't take 
effect until a server restart. (Is that how Scoop handles such changes?)

Later,

Chris

-- 
Chris Winters (ch...@cw...)
Building enterprise-capable snack solutions since 1988.