Home
The Toolkit for Online Communities
17120 Community Members, 1 member online, 1977 visitors today
Log In Register
OpenACS Home : Forums : OpenACS Improvement Proposals (TIPs) : TIP #67: (Implemented) Tcl API for Content Repository : One Message

Forum OpenACS Improvement Proposals (TIPs): Re: TIP #67: (Proposed) Tcl API for Content Repository

Collapse
Posted by Jun Yamog on
Hi Dave,

Yes I think we should relook at the api.  I don't think we should add a tcl api that only gets a single attribute.  It maybe that the CR tcl api is not one to one with CR plpgsql api.  As for bcms I tried to standardize in returning an array for single item, and multirow for many items.

You can look at the ctk core. new, get and update calls is able to handle additional properties for a sub type content type.  I still use array to return a single object, list of lists to inject or update attributes.  Just don't look at how its implemented, its still needs to be change :)  The idea is wrap things on an api that does new, get and update easy for end developers.