Addressbook tutorial problem and feedback

Have just been learning Builder through self-study as courses down this part of the world are few and far between. Have successfully worked my way through the Addressbook tutorial but with a couple of issues.

But two related things aren’t working right for me. Both the Browse Content Info and the AddressBook item in the Personal Workspace do not pick up most of the standard page objects (see attached). All I get is the menus and the footer and no styles are applied. I am using CS10 Update 5. It's probably something quite simple but I cut-and-pasted the code from the tutorial so can't see what's missing. Any assistance would be greatly appreciated.

Overall I found the tutorial really effective once I’d figured out how to “orphan” a feature because that isn't explained. And the terminology was really confusing. When it says “Orphan the WEBDSP:WebModule object in the ADDRESSBOOK OSpace” I presume I have to do this “in the ADDRESSBOOK OSpace”. But no, I have to browse to the WEBDSP:WebModule and create a New Orphan from there. Except I’m doing the opposite, I’m creating a child. A child has inheritance, an orphan doesn’t.

Bulder Custom page format problem.docx

Find more posts tagged with

Comments

Appu_Nair

I beleive the styles is easy to fix the original addressbook was written when there was no dhtml as we say it now I remember using it circa 1999.Here's a link to one that seems to work in my CS10 install https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=22600121&objAction=download&viewType=1 actually I took a updated version put by Hugh Ferguson and started playing with it.Most things should work .I was trying to show a user how to add object factory priv's so I have changed one of the webcmd objects in that code otherwise it is pretty much the ot tutorial.Also if you wanted to find changes in the oll you would first export your module as a dmp(Export Ospace),then look at the module I proviide and notepad++ compare .The weblingo is where I beleive the style changes are implemented so it may look like `%LS `or something close to that.I still refer to this module when I run into confusion.

Appu_Nair

also Orphan just means that the Object is residing in a different ospace.When you Orphan the webnode command object you get all the object features that OT Developers provided to you (and still will when they update it).If you add features to the Object sitting in your ospace then you have a Object that has inheritance to its parent,and its children will have the added stuff you have.You are rarely starting from scratch and you are constantly making use of hierarchies of code that OT developers are making available for hooking into.

Vanderpoel_Rob

Many thanks for that. Have to do some “real” work for now but will check it out in the next few days.

Vanderpoel_Rob

Finally got onto it. I must say it was real cool to be able to open the exported ospace as text and to explore it. As you say, a great way to compare versions.

You were right about the styles. Just needed to add the following line and it all came right

`%L.Styles()`

Cheers

Rob