I was thinking that, but considered that maybe for some that is not so easy.
Did make me wonder if the xcomp could use a text file directly, instead
of resources, to return the constants list?
Based in Chester in the UK.
On 07/06/2017 08:08, Michael Monschau wrote:
> Oh, forgot to mention, when adding new constants the external component would require rebuilding. So Developers would have to have access to XCode or Visual Studio Express. But it is very easy once everything is in place
>> On 6 Jun 2017, at 20:54, Alex Clay <firstname.lastname@example.org> wrote:
>> Hi Henk,
>> Much like you we use either class variables or task variables depending on scope. I’ve often wished for a common registry of these constants in the name of clean code, but so far this approach has worked.
>>> On Jun 6, 2017, at 05:08, H.P. Noppe <email@example.com> wrote:
>>> Dear Omnis people,
>>> Like the subject states I would like to talk about custom constants. There are different ways to implement this in Omnis. The way I do it is actually in two ways.
>>> Use the combination of a file class for declaring the constant and a object class for initialising.
>>> Declare a constant as a class variable and set the init.value of the constant.
>>> Depending on how global a constant is needed I use either of the two.
>>> I am curious how you all lovely developers create constants in a way which keep them maintainable.
>>> Grtz Henk
>>> Manage your list subscriptions at lists.omnis-dev.com
>> Manage your list subscriptions at lists.omnis-dev.com
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com