CSIDE (and CustomizationsRT) questions

Sander Beutick · 2022-04-08T12:58:24+00:00

There was an error rendering this rich post.

been a while, but back on the O-script wagon.

i am trying to patch something and want to use the customizationsRT functionality for this. ( is this still a thing to do? )

in the good old builder one could open 2 views and copy of move object references between them. i do not see how i do this in eclipse.

furthermore: in the O-script Explorer can create a new object (effectively an orphan) but it gives me a error for some objects.( unknown object). although it does appear in the module explorer. what could cause this? i can find the object using the browse option.

last: what is the workflow nowadays? i want to create and do my stuff in the module explorer and then sync it back into the .os files. is this done by importing it? or what am i missing?

i notices that the .ini file does not update itself with module dependencies, even though there is one. i know that the builder used to have the 'produce' function ( from customizationsRT). has this not been added to the CSIDE?

seems all great and enhanced, yet am looking for the basic functions that i used to know

thanks!

Find more posts tagged with

Comments

Appu Nair

It is perhaps best to not rely on old builder and many useful things of that interface but concentrate on the newer methodology which in two simple statements or mantra is. Many old builder commands will look like it works in "Module Explorer" but do not rely on that.

Oscript Explorer-Code changes and merge into OLL or no OLL in Unix/Linux.

Module Explorer-The CSIDE like Builder makes the OT Server into single threaded environment that.

Golden Rule I follow-The new build process corrupts modules perhaps at a greater rate than builder so what I do is whenever I make a module and it is kind of stable and installed I mark its OLL golden .Sometimes in your haste you make mistakes in syntax/compiling and then the whole system will refuse to startup and I just put back my golden and all is kosher.:).It is a pet peeve of mine and perhaps the CSIDE is much better at not corrupting but since I started this in 2012 and noticed that CSIDE was very much corrupting in earlier builds I still follow that.

Weblingo I think is still done manually. You can now leave Scheduler.DebugBreak() in there.the services wont mind that. The SmartUI conundrum is JS minifying and scaffolding and it just needs to get on the support of your module and a slight registration effort.

WF Event scripts and new types of WF are still added old way although some adjustments may need to happen. If in doubt import a module and look at how code is laid out. The notation :: is used to find hierarchical dependencies and the old $ notation is kind of seen as bad coding practice nowadays. Will still work.

The old builder utility files like adding to ini ,adding to globals ,make a new module all have been incorporated into this tool. You dont need to "Set Requesthandlers" and so on.

@Sander Beutick I doubt if you will have anything to worry about :)

When you have a Flavor of XECM in your code base the meat of old "Customizations_RT" is in there by OT you should be able to do that technique or the Chris Webster(https://forums.opentext.com/forums/profile/s%C4%B1%C9%B9%C9%A5%C9%94) technique still fairly well.

Hans Stoop

He Sander,

You are now supposed to work in the OScript explorer and compile/build it into an oll.

You put the sources in a source code control system like a real developer.

You are not supposed to patch anymore.

It should not be much work to get produce to work in CSIDE. It is a nice warming up exercise.

Hans

Sander Beutick

Hi @Appu Nair

Thank you for the explanation of your workflow. what do you mean with mark golden? ( make a copy of it? )

thanks for the link. i will have a look at it!

and @Hans_Stoop thanks. what do you mean by not patching anymore? i actually work at a customer site where customizationsRT is still used in a module to patch core functions. but that should not be the way to go?

i will take a look at the 'produce' function and how to enable this in Eclipse.

thanks both!!

David Henshaw

CustomizationsRT is deprecated. No longer available with later CS releases and was removed from OT solutions that historically depended on it (e.g. Document Templates). Best avoid it and plan alternates for any bespoke solutions that relied on it.

David Henshaw

@Hans_Stoop - personally, I think it crazy that as a developer you have to "bodge" things like "produce" to update the module's INI file with version number updates, dependencies etc. CSIDE should do that, or at least offer you the option to do so as part of a build.

Likewise XLATES/properties files. It's crazy having to keep these in sync manually.

And supporting files (e.g. weblingo, support, help etc).

Surely we all just want a single source and a single process to build a complete and accurate module.

And that's before we even start talking SmartView and having to run a separate process to build that and then remember to manually integrate it into our final module output!

HFCDev

On patching. I still do it when I have to but more and more I'm making the patch just be the latest build of the module. I can see why more and more developers refuse to backcourt...it means writing the same fix twice and nit having a single source of truth. Plus in the containerized world that is OT Cloud, it's easier to do a replacement module than to add patches. But when you must, it's still doable in CSIDE. I recall Customizations RT had a nice patch building script. Since indent have it, I just create my patch Ospace in core folder and proceed as normal.
Looking forward to just moving forward with CI/CD and not ever having to patch
Hugh