Hello.
I am trying to create custom module with ospace.
In tutorial i have read about "Orphan the WEBDSP:WebModule object "
Can you explain me, what does it mean?
Best regards,
Igor
An orphan is a child object which is not stored in the same OSpace as its parent.
By orphaning an object, this is how one would enhance/modify/build on an existing object for your custom module. Just like templating.
I shoud perform this from ospace webdsp in the context menu?
Correct.
<![if !supportLists]>- <![endif]>Navigate to the WEBDSP OSpace.
<![if !supportLists]>- <![endif]>Expand the OSpace and highlight the WebModule object.
<![if !supportLists]>- <![endif]>Right-click on this and choose Orphan Object from its context-menu.
<![if !supportLists]>- <![endif]>Choose your custom module’s name.
<![if !supportLists]>- <![endif]>Done.
livelink builder 10.0.0.3536.
If you're using builder in CS 10, then the approach outlined here by Pramod is correct. David's concern is also valid because it's changed in CSIDE somewhat.
It may help to explain that an orphan in Oscript is analogous to a class in C# or Java that extends another class. In this case, you create a copy of the $WebDSP.Webmodule "class" in your ospace and override methods and properties for your purposes. In CSIDE (10.5 and up), you no longer have to "orphan" a WebModule object as this is done for you automatically when you create your module.
In CSIDE, the main difference is that instead of right clicking on the object in the foreign ospace, you would right click within your own ospace source (either in the root of the ospace, or within a packae) and choose Add New Object, and you choose your new object's parent object from the dialog box. Through this whole process the word "orphan" is never used. When you see the compiled Ospace in the Module Explorer, the notion of root vs orphaned object is clearly seen - the "orphan" objects are brown, dead looking leaves and the root objects are bright healthy green ones
-Hugh Ferguson
