O$ programming style
It is good practice to include in GUI classes only the code needed to set graphical layout and behaviour.
But, if with “operational code” you mean business logic, that’s still not enough to encapsulate it inside an object directly linked with the GUI, since your logic will still be dependent on the particular GUI (=inputs) you are using.
I’d recommend checking the MVC design pattern.
You’ll have at least two more layers (model and controller), surely more extra work at the beginning, but a lot of advantages as you’ll get reusable code, since the model will be independent from the GUI shown to the user.
> —–Original Message—–
> From: omnisdev-en [mailto:email@example.com] On
> Behalf Of Mike Rowan
> Sent: Monday, December 18, 2017 2:47 PM
> To: OmnisDev List – English <firstname.lastname@example.org>
> Subject: O$ programming style
> I have recently written a lot of code using the idea that ‘Omnis Programming’
> seems to suggest, namely having almost no operational code in the methods
> of a window, by shifting them to an object instantiated as an instance
> variable of type object of the window.
> I’n not sure I see any advantage for a desktop library, and wonder what I
> have missed. In fact it seems to add a whole extra layer of pain.
> Meanwhile, seasons greetings to all
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com