Imagine if in the past we had supplied you the GDC native rendering sources and you were free to modify these sources to get the User Interface just the way you wanted it! That is almost what you get with the concept of GBC customisation. I say "almost" because although we give you all the sources. we have created a number of openings of where we expect you to make your modifications. You should stick to those openings if you want to make ongoing maintenance for yourself easier in the future.
GBC customisation is not the same as altering one line in a .4st and not having to recompile your application. GBC Customisation is also not something you might expect your entire 4gl development resource to be capable of doing as part of their 4gl programming tasks. It is a concept you should have some dedicated resources devoted to and have some proper change management in place. That resource should have some knowledge of web technologies, in particular HTML (.html), Javascript (.js), CSS (.css), and some knowledge of SASS (.scss).
In a single article I am not going to be able to teach you everything but what I am able to point out is the salient points your development organisation needs to have a good understanding of, and give you some good ideas of the first exercises you should do in certain areas.
Read more at
https://4js.com/ask-reuben/ig-134/
Sign in for full access
Help
