How to get at inherited features

Hi,

this is something that frankly in builder was SO F**KING EASY. it astounds me that it's not so easy in CSIDE. I'm trying to build a new request handler from scratch. I've inherited the LLRequestHandler object from WebLL (as usual). I even created a package for my new request handlers. I now have two problems:

1) How do I run the SetRequestHandlers function so that my src request handler group picks it up? There is no access to inherited methods in the src tab only the overridden ones. I have even tried running it on the module itself to no avail! What is the correct procedure in 10.5??????

2) How do you ****SEE**** the objects/scripts that you could inherit/override when in the source? So far, all I can do is go to the modules tab and look at the overridden object and cut and paste into the module. This was sooooo much simpler in Builder!!!

-Hugh, very **** off programmer today

Find more posts tagged with

Comments

Christopher_Meyer

Hi Hugh,

With Builder it was standard practice to run code generation by running scripts to set features. A few examples include 0Setup(), SetPrototype(), BuildOSpace() and SetRequestHandlers().

CSIDE did away with this, which is unfortunate.

For example, on WebNodeCMD is was common practice to set fPerms to a permission bit using something like the following in 0Setup():

.fPerms = $PSee | $PSeeContents

The OScript Explorer view doesn't allow this, which requires you to hardcode the permission bit directly on fPerms:

override Integer fPerms = 36867

This code is harder to read and requires a duplication of effort by having to add a comment to what 36867 represents.

I do a lot of code generation in my modules and for this reason I've had to avoid programming in the OScript Explorer view.

To answer your questions:

1) How do I run the SetRequestHandlers function so that my src request handler group picks it up? There is no access to inherited methods in the src tab only the overridden ones. I have even tried running it on the module itself to no avail! What is the correct procedure in 10.5??????

You don't have to anymore. If you look at the __Init() function of RequestHandlerGroup you'll see it calls SetRequestHandlers() for you at start up. Ditto with BuildOSpace().

How do you SEE the objects/scripts that you could inherit/override when in the source? So far, all I can do is go to the modules tab and look at the overridden object and cut and paste into the module. This was sooooo much simpler in Builder!!!

From the menu choose Source > Override Features. This will list and let you choose which features to override. You'll likely still need to view what's going on in the Module Explorer view to understand the context of the feature you want to change. However, I find this flipping between the OScript and Module Explorer views quite confusing at times.

Good luck and I hope this helps!

HFCDev

I never got a chance to check back to this thread but I did solve the first problem in a different way. I was able to go directly into the .fRequestHandlers feature and add the new handlers manually into the source. For some reason, even restarting wasn't doing it for me. However once I manually added the new handlers, they were available immediately.

As for the second item, perhaps this is a feature request to Open Text. When you go to override source features, it would be nice if it autopopulated the feature/script with the parent's code as most overriding tends to be adding lines to existing source rather than adding fresh code.

-Hugh

eLink User

Almost everything you used to do in Builder you can still do ,you would use the right side the module explorer.Whenever I get stuck on the new CSIDE paradigm I would use the right side and over compensate for stuff .For e.g I had a need to "create a subsystem" which would have been very straightforward in builder.So I created a version 10 module and sucked it into CS10.5. Once I saw the source code I was able to get most of it without fear.I used to keep two "builder views" side by side to drag and drop things one needed and was easier to understand.This is gone.Very difficult to look at hard to understand data structures.As a matter of fact we had given OT some 10 things prioritized never followed it up as our dev is all done.It could also be that many of us who used to dwelve in builder had gotten used to it and newer oscript guys may find this better although I find oscripting by companies other than OT decreasing tremendously(or it could be that OT's CS is losing market share I know not).Perhaps people are scared by this programming language and they feel like webreports and its logic to be the new development paradigm

If you run into a ditch people like David Templeton , Kyle S all help out they have in the case of me running into a brick wall.

The module explorer side is your **** given gift when you had a change of mind to rename objects etc

.what irks me a lot is when you debug something and you are looking at variables etc the thing crashes ...Perhaps with CS16 it may be under control.I had to run CS16 in our env so I had to compile CS10.5 modules like A D N/Transmittals that has not yet been released they all work without much work.

.....appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937