Forum OpenACS CMS: Re: bcms 0.3 on cvs

Collapse
11: Re: bcms 0.3 on cvs (response to 1)
Posted by Jun Yamog on
Hi Steve,

Sorry about that, but I can't directly commit bcms-ui-wizard since it does require some changes in bcms.  Changes that may affect greater number of developers and packages.

I am trying to change bcms-ui-wizard, I guess if I can't find enough time I will just commit bcms-ui-wizard even if it needs some work for it to run with bcms.

Collapse
12: Re: bcms 0.3 on cvs (response to 11)
Posted by Steve Manning on
Jun

I think its better to get a working version of BCMS-UI-Wizard on contribs rather than hold it back because of a problem with the merge.

Let me know (off-list) what changes are required to UI-Wizard to bring it back into line - or if its some feature I've added. If necessary I can then either rework the problem or move the relevent part out of BCMS into UI-Wizard to retain the feature.

    - Steve

Collapse
13: Re: bcms 0.3 on cvs (response to 12)
Posted by Randy O'Meara on
Thank you both for answering.

My goal is to utilize the CR to define, generate, display, and validate object/attribute forms.

I'm using the CR docs as a guide for sequence of operations,  and comparing CR and bcms APIs. I'm looking for a one-for-one correspondence between the two APIs, but they don't really match up. For example, where the CR docs show how to create a content type with content_type__create_type, I don't see a bcms API call to do the equivalent. But I do see correspondence in other areas.

Maybe this is the wrong approach? Is there a better approach? Possibly someone has already correlated the APIs and created a step-by-step that will show me at least a part of what I'm trying to do?

/R