openinteract-dev — For OI developers, includes project coordination and technical discussion.

Re: [Openinteract-dev] Object security inheritance

[Andrew H. <hu...@ll...>]

At 01:23 PM 7/31/2003 -0400, Chris Winters wrote:
>Andrew Hurst wrote:
>>...
>
>...
>And then have a custom page/handler to set the security for the main 
>Document which ALSO sets the security for the DocumentPage object of that 
>location. So a Document with a location of:
>
>  /mydocument
>
>Would set security (assuming group, ID 3, level WRITE) for both:
>
>  class            id            scope  scope_id  level
>  OI::Document     /mydocument   g      3         8
>  OI::DocumentPage /mydocument   g      3         8

The only problem I see with this is that I don't use url's of that form.  I 
use the News style urls:

/Document/show/?document_id=3
/Document/TOC/?document_id=3
/DocumentPage/show/?document_page_id=55
etc. etc.

So it needs to be per-object, rather than per-location (if I'm using the 
correct terminology).  Thus I think a custom document security edit page 
would be useful:
/Document/security/?document_id=N

When saved, it would set the security settings for all of its DocumentPages 
using the standard security methods (assuming that they're there, I haven't 
checked yet).  DocumentPage security would be set with the usual object 
security editor.  Then I'd get to override security on a per-page basis, 
and set for the whole document as well...

Seem like a good idea?

-Andrew

Re: [Openinteract-dev] Object security inheritance

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

Andrew Hurst wrote:
> The only problem I see with this is that I don't use url's of that 
> form.  I use the News style urls:
>
 > /Document/show/?document_id=3
 > /Document/TOC/?document_id=3
 > /DocumentPage/show/?document_page_id=55
 > etc. etc.

That's okay -- it doesn't matter! The hierarchical security can work 
with any delimited string, and it doesn't matter where the content 
of the string comes from. So you create a non-editable field 
'security_location' and calculate it in an SPOPS pre-save handler so 
it never gets out of sync. Even if it just looks like:

   security_location => '3|55'

That should be ok.

> So it needs to be per-object, rather than per-location (if I'm using the 
> correct terminology).  Thus I think a custom document security edit page 
> would be useful:
> /Document/security/?document_id=N
> 
> When saved, it would set the security settings for all of its 
> DocumentPages using the standard security methods (assuming that they're 
> there, I haven't checked yet).  DocumentPage security would be set with 
> the usual object security editor.  Then I'd get to override security on 
> a per-page basis, and set for the whole document as well...
> 
> Seem like a good idea?

Yep, that would work too -- and be more straightforward!

Chris

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

Re: [Openinteract-dev] Object security inheritance

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

Andrew Hurst wrote:
> ...
>   The question I had is regarding security.  How can I make them inherit 
> security as well?  I've seen the object security page, and how you can 
> edit it for one document, but when I change it for the main Document, I 
> want it to change for all of the DocumentPages as well.  The one way 
> I've thought about doing this so far is to have each DocumentPage check 
> the security status of its parent, and only show if the person has 
> security for the parent.  What would be really cool would be the ability 
> to override it per-page as well ( i.e. the whole document can be seen by 
> everyone, but the middle 26 pages can only be seen by those in the 
> 'president' group ;) (yes this was a bad joke, and no I have no relation 
> to any of that, nor does this code)

There's a custom security implementation that allows you to set and 
find security based on an inherited hierarchy 
(SPOPS::Secure::Hierarchy). You might be able to work with it or use 
it to spawn your own. As is it's built primarily for security a 
document tree like:

  /reports/executive/july-03.html  - inherited from
                                     '/reports/executive'
  /reports/executive               - security set so that only
                                     'executive' group can read,
                                     overrides '/reports' setting
  /reports                         - security set so that all
                                     employees can read, overrides
                                     '/' setting
  /                                - security set so that any valid 

                                     user can read

So you might be able to create a field in each DocumentPage object 
with something like:

  location => /mydocument/page1

And then have a custom page/handler to set the security for the main 
Document which ALSO sets the security for the DocumentPage object of 
that location. So a Document with a location of:

  /mydocument

Would set security (assuming group, ID 3, level WRITE) for both:

  class            id            scope  scope_id  level
  OI::Document     /mydocument   g      3         8
  OI::DocumentPage /mydocument   g      3         8

(Or you could only set the DocumentPage entry, that's up to you). 
All DocumentPage objects  with a location '/mydocument' would 
inherit that setting, and you'd have the option of overriding the 
setting on an object-by-object (or other scheme) basis.

See the conf/spops.perl file in pkg/base_page/conf for how it sets 
up hierarchical security. The front-end for editing it is in the 
'Security' admin tools -- if you choose to edit security for an 
object that's hierarchically protected then you get a different 
initial form than if it's not.

Hope this makes sense,

Chris

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

[Openinteract-dev] Object security inheritance

[Andrew H. <hu...@ll...>]

Hello,
   First off I want to thank the OI developers for writing OI.  Its a 
pleasure to work with.  My document system should be finished today (minus 
the rich comments, that's coming along though).  The question I had was 
regarding security of objects.

   The way that I've implemented this system is with two objects, Document 
and DocumentPage.  When you create a new Document object it doesn't 
actually store any text of its own.  It splits on the Page Break String 
(you specify this in the edit template) and creates a DocumentPage for each 
part of the original.  This makes it easier to show one page at a time, 
attach comments to only one page, etc etc.  The DocumentPage objects will 
inherit their section, expires, active on, etc fields (all except their own 
content and title) from their parent Document.

   The question I had is regarding security.  How can I make them inherit 
security as well?  I've seen the object security page, and how you can edit 
it for one document, but when I change it for the main Document, I want it 
to change for all of the DocumentPages as well.  The one way I've thought 
about doing this so far is to have each DocumentPage check the security 
status of its parent, and only show if the person has security for the 
parent.  What would be really cool would be the ability to override it 
per-page as well ( i.e. the whole document can be seen by everyone, but the 
middle 26 pages can only be seen by those in the 'president' group ;) (yes 
this was a bad joke, and no I have no relation to any of that, nor does 
this code)

   So, is there a way to do this thats easier than managing the DocPage 
security within the DocumentPage handler?  It seems to go outside of the 
idea of SPOPS and OI handling it for me, and I'd rather not do that.

   hmm.. maybe as a compromise I could set up a 'edit all document pages 
security at once' page, thats custom for DocumentPage, and just a copy of 
SecurityShow essentially...

Thanks!
-Andrew

Re: [Openinteract-dev] Document Review implementation questions

[Andrew H. <hu...@ll...>]

At 12:19 PM 7/25/2003 -0400, Chris Winters wrote:
>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 :-)
I'll think of a better name.  -creepy was a reference to feature creep, and 
rather tounge-in-cheek... ;)

probably rich-comments unless there are objections.

btw, other features for comments I don't think I mentioned.  A security 
level to be able to post comments as anyone.  Ability to append to 
comments.  Ability to delete comments.

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

When they post a comment, it will be attached to a section of the 
document.  Their comment will cover one of four topics, "Text to Append", 
"Text to Replace", "Question on Text", "Issue or Counterpoint".  When they 
reply, they want to have 4 other topics to choose for the comments: 
"Accepted as Text to Append", "Accepted as Text to Replace", "Response to 
Question", "Response to Counterpoint".  Personally I think that the review 
comment topics are redundant, as threading will take care of the topic 
implicitly.  But I'm still working on that battlefront.

Thus I was thinking of adding in topics just like story sections.  Doesn't 
look too hard to do.

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

Cool.  I was thinking I was going to end up taking a little from each of 
those to end up with the final product.  Thanks for the pointer.  If 
base_page already includes pagination, I might just fork that, I don't 
think all of the modifications that I've suggested should go in the base 
package.  Though... the more I think about it I'm not sure I have to make 
that many modifications if it already supports pagination, etc.  The 
biggest thing is being able to globally mark a document as frozen, for no 
more comment posting and modifications, and a way to see it all at once 
with comments in-line.  The latter sounds like an added action, and the 
former sounds like its already in there, if not a useful feature by 
itself.  Also an easy ability to delete the whole document (each page as 
well) all at once.

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

I'll do that.

>(Is that how Scoop handles such changes?)

Scoop had a vars database table, that was loaded into a memory cache on 
server startup.  You could edit everything you wanted, and it took affect 
over the whole server immediately.  With every request a single query to 
the db was run that checked if the cache in the child was out of date (the 
latest update time was stored in the db).  If so it reloaded the vars, if 
not it didn't.

Have you ever run Scoop?  If you want to check out the admin interface 
create an account on scoop.kuro5hin.org and I'll give you admin access for 
a bit to poke around.  Its got some neat features.

by the way, regarding development of packages, is this the standard cycle?
make modifications in package directory
remove package from site
remove package sql from db
re-apply package to site
re-apply package sql
restart apache

with the sql steps possibly being skipped.  I noticed the scripts on the 
webpages but I haven't had a chance to check them out fully yet.  Still got 
a few "ASAP" VB Scripts first... :-(

Thanks for the input
-Andrew


>Later,
>
>Chris
>
>--
>Chris Winters (ch...@cw...)
>Building enterprise-capable snack solutions since 1988.
>
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by: Free pre-built ASP.NET sites including
>Data Reports, E-commerce, Portals, and Forums are available now.
>Download today and enter to win an XBOX or Visual Studio .NET.
>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
>_______________________________________________
>openinteract-dev mailing list
>ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openinteract-dev

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.

[Openinteract-dev] Document Review implementation questions

[Andrew H. <hu...@ll...>]

Hey all,
   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.?

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.

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?

Thanks for the input.
-Andrew

Re: [Openinteract-dev] benchmarks?

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

Andrew Hurst wrote:
>   Just wondering if there are any benchmarks for OI around.  I know that 
> it depends on the database size, packages installed, machine, and phase 
> of the moon among other things, but just for a rough idea.  I'll 
> generate some of my own once I get another test machine here (OSX dual 
> g4 :)

None that I know of. They'd certainly be welcome! That said, I have 
a strong suspicion that the OI 1.x architecture will only allow for 
some coarse benchmarks. In OI 2.x we can benchmark individual tasks 
(e.g., dispatching a request) much easier outside of a web server. 
This would make it easier to optimize the parts that are sluggish.

The largest OI install to my knowledge is from the bertelsmann guys 
(Andreas Nolte and company). They'd probably be the best people to 
ask about performance.

Chris

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

[Openinteract-dev] benchmarks?

[Andrew H. <hu...@ll...>]

Hey all,

   Just wondering if there are any benchmarks for OI around.  I know that 
it depends on the database size, packages installed, machine, and phase of 
the moon among other things, but just for a rough idea.  I'll generate some 
of my own once I get another test machine here (OSX dual g4 :)

   Just curious

Thanks
-Andrew

Re: [Openinteract-dev] Startupwarning / error message

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

And...@Be... wrote:
> When starting up OI ( 1 x ) we always get this warning message:
> 
> Using a hash as a reference is deprecated at 
> /opt/perl/lib/site_perl/5.8.0/SPOPS/HashFile.pm line 116.
> 
> Is this harmless ? I did not see a problem with the file..

This only happens under 5.8. I'm not sure what the problem is, but 
I'm almost certain it's harmless.

> Also, we sometimes get the following message displayed in the browser:
> 
> Can't locate object method "error" via package "OpenInteract::Request" 
> at /opt/perl/lib/site_perl/5.8.0/OpenInteract/Request.pm line 123.
> 
> We were not able to track down, when and why this is generated. Any ideas?

This indicates that the request object wasn't built-up properly -- 
'error' is an alias that gets created at apache child creation time. 
Check your server (not vhost) error log and for anything suspicious.

Chris

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

[Openinteract-dev] Startupwarning / error message

[<And...@Be...>]

Hello all,

When starting up OI ( 1 x ) we always get this warning message:

Using a hash as a reference is deprecated at
/opt/perl/lib/site_perl/5.8.0/SPOPS/HashFile.pm line 116.

Is this harmless ? I did not see a problem with the file..

Also, we sometimes get the following message displayed in the browser:

Can't locate object method "error" via package "OpenInteract::Request" =
at
/opt/perl/lib/site_perl/5.8.0/OpenInteract/Request.pm line 123.=20

We were not able to track down, when and why this is generated. Any =
ideas?

Later,

Andreas Nolte
Leitung IT
-----------------------------------------------------------
arvato direct services=20
Olympiastra=DFe 1
26419 Schortens
Germany
http://www.arvato.com/ <http://www.arvato.com/>=20

and...@be...
Phone   +49 (0) 4421 - 76- 84002
Fax	+49 (0) 4421 - 76- 84111

Re: [Openinteract-dev] linking comments to news articles

[Andrew H. <hu...@ll...>]

Works like a charm.  Thanks.
-Andrew

At 12:56 PM 7/22/2003 -0400, Chris Winters wrote:
>Andrew Hurst wrote:
>>   I'm trying to get the comments package to work with the news package, 
>> so that I can have comments on the news stories on my OI site.  At the 
>> bottom of the news::news_detail template I've added the following:
>>[% OI.comp( 'show_comment_summary', object = news ) %]
>>[% PROCESS comments::comment_form_page( object = news ) %]
>>   That shows the comment form correctly, but it doesn't allow me to post 
>> comments.  The error I get is "Insufficient data supplied to fetch 
>> comments by object."  It doesn't appear to be getting the object 
>> information that it needs.  When I look at the post comments form in 
>> html, the hidden values at the bottom are:
>>...
>
>FWIW, on my site I have:
>
>[% OI.comp( 'show_comment_by_object', object => news ) %]
>
>at the bottom of the 'news::news_detail' template.
>
>I think there are some dependencies here that I never explicitly drew out. 
>What the 'show_comment_by_object' component will do is fetch the comments 
>for a particular object then pass them to 'comment::comment_list'.
>
>Additionally the 'comment::comment_form' wants a 'commment' object that's 
>already been filled in with the class and object ID. (These are the empty 
>hidden entries you're seeing.) What you probably want is:
>
>[% OI.comp( 'new_comment_form', object => news ) %]
>
>This pulls the class/id out of the object and puts it into a new comment 
>object. It also grabs data saved in the cookie (name/email/url) and puts 
>it in the new comment object. It then passes the comment object to 
>'comment::comment_form' which is happy.
>
>I hope that makes sense. I worked on this package some time ago and it's a 
>little fuzzy :-)  I'm going to work on it in the next week or two to port 
>it to OI2 so it will be fresher.
>
>>Related to this, I've noticed (or I think I have ;) that lots of the 
>>templates are cached, so that when I make a change to the templates, 
>>sometimes I won't see it for a few requests.  I guess that's because the 
>>template it cached within each child request?  Is there any way around 
>>this?  I've thought about changing template_info->{cache_size} to 0, but 
>>was worried that that would make performance too slow to stand while 
>>messing around.  Any thoughts?  How do other people handle this?
>
>Yes, they're cached. You can get around this by restarting the server, 
>which sucks. Or by just not caching the templates. The performance 
>difference shouldn't be *that* great (TT is still pretty quick), and since 
>you're in development you don't care as much about that anyway. Well, at 
>least I don't.
>
>Chris
>
>--
>Chris Winters (ch...@cw...)
>Building enterprise-capable snack solutions since 1988.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
>same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
>_______________________________________________
>openinteract-dev mailing list
>ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openinteract-dev

Re: [Openinteract-dev] linking comments to news articles

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

Andrew Hurst wrote:
>   I'm trying to get the comments package to work with the news package, 
> so that I can have comments on the news stories on my OI site.  At the 
> bottom of the news::news_detail template I've added the following:
> 
> [% OI.comp( 'show_comment_summary', object = news ) %]
> 
> [% PROCESS comments::comment_form_page( object = news ) %]
> 
>   That shows the comment form correctly, but it doesn't allow me to post 
> comments.  The error I get is "Insufficient data supplied to fetch 
> comments by object."  It doesn't appear to be getting the object 
> information that it needs.  When I look at the post comments form in 
> html, the hidden values at the bottom are:
> ...

FWIW, on my site I have:

[% OI.comp( 'show_comment_by_object', object => news ) %]

at the bottom of the 'news::news_detail' template.

I think there are some dependencies here that I never explicitly 
drew out. What the 'show_comment_by_object' component will do is 
fetch the comments for a particular object then pass them to 
'comment::comment_list'.

Additionally the 'comment::comment_form' wants a 'commment' object 
that's already been filled in with the class and object ID. (These 
are the empty hidden entries you're seeing.) What you probably want is:

[% OI.comp( 'new_comment_form', object => news ) %]

This pulls the class/id out of the object and puts it into a new 
comment object. It also grabs data saved in the cookie 
(name/email/url) and puts it in the new comment object. It then 
passes the comment object to 'comment::comment_form' which is happy.

I hope that makes sense. I worked on this package some time ago and 
it's a little fuzzy :-)  I'm going to work on it in the next week or 
two to port it to OI2 so it will be fresher.

> Related to this, I've noticed (or I think I have ;) that lots of the 
> templates are cached, so that when I make a change to the templates, 
> sometimes I won't see it for a few requests.  I guess that's because the 
> template it cached within each child request?  Is there any way around 
> this?  I've thought about changing template_info->{cache_size} to 0, but 
> was worried that that would make performance too slow to stand while 
> messing around.  Any thoughts?  How do other people handle this?

Yes, they're cached. You can get around this by restarting the 
server, which sucks. Or by just not caching the templates. The 
performance difference shouldn't be *that* great (TT is still pretty 
quick), and since you're in development you don't care as much about 
that anyway. Well, at least I don't.

Chris

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

[Openinteract-dev] linking comments to news articles

[Andrew H. <hu...@ll...>]

Hello,
   I'm trying to get the comments package to work with the news package, so 
that I can have comments on the news stories on my OI site.  At the bottom 
of the news::news_detail template I've added the following:

[% OI.comp( 'show_comment_summary', object = news ) %]

[% PROCESS comments::comment_form_page( object = news ) %]

   That shows the comment form correctly, but it doesn't allow me to post 
comments.  The error I get is "Insufficient data supplied to fetch comments 
by object."  It doesn't appear to be getting the object information that it 
needs.  When I look at the post comments form in html, the hidden values at 
the bottom are:

<input type="hidden" name="class" value="">

<input type="hidden" name="object_id" value="">

Which I would assume is a problem :)  How am I calling the above template 
wrong?

Related to this, I've noticed (or I think I have ;) that lots of the 
templates are cached, so that when I make a change to the templates, 
sometimes I won't see it for a few requests.  I guess that's because the 
template it cached within each child request?  Is there any way around 
this?  I've thought about changing template_info->{cache_size} to 0, but 
was worried that that would make performance too slow to stand while 
messing around.  Any thoughts?  How do other people handle this?

Thanks for the input.
-Andrew

Re: [Openinteract-dev] Small bugfix for 1.58

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

Andrew Hurst wrote:
> Probably already fixed, but a small bugfix.
> 
> OpenInteract.pm:
> Change line 243 from
>         warn "Found item: ", ref( $db ), "\n";
> to
>         $R->DEBUG && warn "Found item: ", ref( $db ), "\n";
> 
> to save the log files of much:
> 
> Found item: Apache::DBI::db
 > ...

Thanks, applied.

Chris

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

[Openinteract-dev] Small bugfix for 1.58

[Andrew H. <hu...@ll...>]

Probably already fixed, but a small bugfix.

OpenInteract.pm:
Change line 243 from
         warn "Found item: ", ref( $db ), "\n";
to
         $R->DEBUG && warn "Found item: ", ref( $db ), "\n";

to save the log files of much:

Found item: Apache::DBI::db
Found item: Apache::DBI::db
Found item: Apache::DBI::db
Found item: Apache::DBI::db
Found item: Apache::DBI::db

(one for every request)

-Andrew

Re: [Openinteract-dev] Need input on a new system

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

Andrew Hurst wrote:
 > ...
> quick, you can do it however you like.  And we can probably open source 
> it as well")  But we can't make any promises until its actually released 
> back to the community, of course ;)

It would be great, but I know that uphill battle that can be...

> ...
> I seem to recall you (Chris) talking about the comment module being able 
> to attach to any object in the system, which is why I thought this way 
> might work well.  Is that the case?

Correct. It really just treats the object as a class + ID pair and 
then uses that as an organizational point. Kind of like the ID for a 
thread beginning, but more useful so you can find all the comments 
for an object with a component call:

[% OI.comp( 'show_comment_by_object', object = news ) %]

For instance, I have the preceding on all 'news' objects on my 
website. And a few 'page' objects I have it as well, such as some 
random thoughts about matrix stuff. That call looks like:

[% OI.comp( 'show_comment_by_object', object = page ) %]

You can, of course, get all this data programmatically as well.

This way of working has always been part of OI but rarely explicit. 
With OI2 I think I'll include the 'comments' and 'object_link' 
packages which take advantage of this functionality. The 
'object_link' package just adds a layer of topics so you can link 
any two arbitrary objects (pages, news items, recipes, movie 
reviews, external links, etc.) by a topic and get a useful 'Related 
Items' listing of them.

> I will also need to add some features to the comment mechanism like 
> topics for the comments, ability for a logged in user to only see their 
> own comments, and a display of only comments in topics a person has 
> permission for.

Cool!

Chris

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

Re: [Openinteract-dev] Need input on a new system

[Andrew H. <hu...@ll...>]

At 12:12 AM 7/21/2003 -0400, Chris Winters wrote:
>Andrew Hurst wrote:
>>...
>
>For purely selfish reasons I'd like you to use OI2 so you can let me know 
>what problems you have with it :-) But if you're implementing it in three 
>weeks then I'd probably say OI 1.x, agreeing entirely with the comments 
>Andreas put forth.

Sounds good.  Now on to actual implementation details and questions, in the 
interest of doing this in the "OpenInteract" way :)  Its possible we could 
be able to release this code back. (Well, maybe.  After all the hubub about 
whether we can get code back to the community easy from here, my boss comes 
in with this job and says "hey, we need this done quick, you can do it 
however you like.  And we can probably open source it as well")  But we 
can't make any promises until its actually released back to the community, 
of course ;)

The way that I'm probably going to implement this is with a generic 'story' 
type mechanism.  I think of one big document that people can comment on 
much as a multi-part story on a site like kuro5hin or slashdot.  So this 
would probably require a few new pages, to post the full text and parse for 
comment sections (the current code looks for certain html tags and puts 
comments when it finds them), a page to show it all at once with comment 
links, and the ability to show only one section at a time with comments for 
that section.

I seem to recall you (Chris) talking about the comment module being able to 
attach to any object in the system, which is why I thought this way might 
work well.  Is that the case?

I will also need to add some features to the comment mechanism like topics 
for the comments, ability for a logged in user to only see their own 
comments, and a display of only comments in topics a person has permission for.

Thanks for the input!
-Andrew




>Chris
>
>--
>Chris Winters (ch...@cw...)
>Building enterprise-capable snack solutions since 1988.
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: VM Ware
>With VMware you can run multiple operating systems on a single machine.
>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
>same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
>_______________________________________________
>openinteract-dev mailing list
>ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openinteract-dev

Re: [Openinteract-dev] Need input on a new system

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

Andrew Hurst wrote:
>   I'm probably going to end up writing a simple collaborative document 
> review system, and want to use OI for the user accounts and security 
> functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
> expect to strip the system down pretty far, so that there are no extra 
> packages when this goes live.  I seriously doubt it will see more than 1 
> req/sec of traffic.  The document that people will comment on will be 
> rather large though, about 100 pages, with upwards of a few thousand 
> comments at its peak.  Time frame to live is about 3 weeks.
> 
>   What do you think?  Thanks for the input...

For purely selfish reasons I'd like you to use OI2 so you can let me 
know what problems you have with it :-) But if you're implementing 
it in three weeks then I'd probably say OI 1.x, agreeing entirely 
with the comments Andreas put forth.

Chris

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

Re: [Openinteract-dev] Need input on a new system

[Andreas N. <an...@kl...>]

Hi Andrew,

if you need your system to run in production within the next couple of
months, then use OI 1. Try keeping the application logic out of the
handler code, for example by using the hooks in SPOPS. Doing this will
minimize changes when going to OI2.

hope that helps,

Andreas
On Fri, 2003-07-18 at 23:57, Andrew Hurst wrote:
> Hello,
> 
>    I'm probably going to end up writing a simple collaborative document 
> review system, and want to use OI for the user accounts and security 
> functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
> expect to strip the system down pretty far, so that there are no extra 
> packages when this goes live.  I seriously doubt it will see more than 1 
> req/sec of traffic.  The document that people will comment on will be 
> rather large though, about 100 pages, with upwards of a few thousand 
> comments at its peak.  Time frame to live is about 3 weeks.
> 
>    What do you think?  Thanks for the input...
> 
> -Andrew
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> openinteract-dev mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openinteract-dev

[Openinteract-dev] Need input on a new system

[Andrew H. <hu...@ll...>]

Hello,

   I'm probably going to end up writing a simple collaborative document 
review system, and want to use OI for the user accounts and security 
functionality.  I'm wondering if I should use OI2 or OI1 for this.  I 
expect to strip the system down pretty far, so that there are no extra 
packages when this goes live.  I seriously doubt it will see more than 1 
req/sec of traffic.  The document that people will comment on will be 
rather large though, about 100 pages, with upwards of a few thousand 
comments at its peak.  Time frame to live is about 3 weeks.

   What do you think?  Thanks for the input...

-Andrew

[Openinteract-dev] link to docs from next OI2 beta

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

The next beta (beta 3, 1.99_03) for OI2 is still 7-10 days away. But 
one of the large additions is OI2::Manual::Tutorial which I thought 
might be helpful to people now. You can reach it through:

   http://openinteract.sourceforge.net/docs/oi2-snapshot/

If you have any suggestions, questions, typos, etc., please post to 
the list or to me directly.

Thanks,

Chris

PS - Note that while most of the examples from the tutorial work 
with the current beta, a few don't due to changes made since. 
Writing a tutorial is a great way to find bugs :-)

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

Re: [Openinteract-dev] Testnotes with OI2Beta01

[Andreas N. <an...@kl...>]

> > New client attached from: 127.0.0.1
> > Cannot process template [base_main]: Undefined subroutine
> > &Template::Parser::new_style called at
> > /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/Template/Parser.pm line 179.
> > daemon: Reaped child with PID [1]
> 
> This is a *weird* TT error. What's strange is that in my TT version 
>   (2.09) 'new_style' is defined about 10 lines under where this 
> error was thrown. And OI doesn't have anything to do with TT parsers 
> (plugins, providers and contexts, yes, but no parsers).
> 
> What TT version are you using?
I am also using 2.09. I suspect a weired error from having an older
style server.ini ( see below ). I do not think it`s worth investigating
more.


For the fresh install: after updating the server.ini everything works !


later,

Andreas

Re: [Openinteract-dev] Question about Page

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

Greg Fenton wrote:
> Maybe I'm missing the docs, but I have created a new HTML page that I'd
> like to serve.  I placed it in $OPENINTERACT2/html and now try to
> create the page with OI2's "Page Actions" link.

Actually, you can use the page scanner for this. Under 'Page 
Actions' you have an option 'Scan' which will find files under a 
directory tree that haven't yet been brought into OI and bring them in.

But onto the problem...

> Every time I fill out the create form, I get back the error:
> 
>   No template found in 'c_display_add_template' key. This template is
>   mandatory for the task to function.

This is an action configuration error. If you add:

c_display_add_template    = base_page::page_form

under [page] in base_page-x.xx/conf/action.ini you should get a 
little farther. I've committed this but haven't yet tested it. (day 
job and all that...)

The base_page package is probably the one that will *internally* 
change the most before 2.0 is released. Externally it should work 
exactly the same but there are still a few OI 1.x-isms in 
OI2::Action::Page. It's probably the most complicated action in OI 
and it may be a good idea to split some of the functionality off 
into separate actions...

> So, what are the steps to getting an existing HTML file served?  Am I
> missing a key manual page somewhere?

Nope, just more bugs....

Chris

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

Re: [Openinteract-dev] Re: Random tidbits on OI2

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

Greg Fenton wrote:
> Even more simple tidbits.  Again, I'm using OpenInteract-1.99_01:
> 
> A. I created website as per QuickStart.  When I go to "System
>    Documentation" and click the SPOPS::Manual link, all is fine.
>    When I click the OpenInteract2::Manual link, I get the error page:
> 
>    Can't call method "present" without a package or object reference
>    at /usr/lib/perl5/site_perl/5.8.0/Pod/POM/View/Pod.pm line 132.

That's odd... I'll have to see what's up with it.

> B. In base_page-2.05/doc/base_page.pod, line 129 gives an example
>    using "oi_manage" and not "oi2_manage".

fixed

> C. From the homepage of the QuickStart website, I click "Pages" (top
>    of the page), then expand the root directory, then click on the
>    "index.html" link.  I get the error:
>
>    Cannot find valid method in [OpenInteract2::Action::Page] for
>    task [show]

bad link in the template, fixed

> D. From the homepage of the QuickStart website, I click on the 
>    "Template (New)" link and get the following error:
> 
>    Cannot find valid method in [OpenInteract2::Action::SiteTemplate]
>    for task [display] 

a bad link in another template, fixed.

Thanks for the pointers, it's a huge help.

Chris

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