Modern API Wrapper Library? #5

KyleCardoza commented 2025年02月11日 02:56:35 +01:00

I would not support forking Motif, nor breaking API compatibility, but for developing new software, I would recommend we create a wrapper library that exposes Motif functionality in a more "modern C" kind of way. For example, when setting a resource using the traditional API, you would pack an Arg array with keys and values, and then call a function to set the resources; the more modern way would involve having functions for setting and getting the value of each resource.

I would not support forking Motif, nor breaking API compatibility, but for developing new software, I would recommend we create a wrapper library that exposes Motif functionality in a more "modern C" kind of way. For example, when setting a resource using the traditional API, you would pack an Arg array with keys and values, and then call a function to set the resources; the more modern way would involve having functions for setting and getting the value of each resource.

thomholwerda commented 2025年02月11日 11:42:39 +01:00

I'm not a programmer so I'll leave this discussion to those that are, but using a wrapper that allows us some control where and when it's needed seems like a smart thing to do. If we intend to be a Motif-focused distribution, forking Motif seems counterintuitive (and a whole heck of a lot of work, to boot?).

I'm not a programmer so I'll leave this discussion to those that are, but using a wrapper that allows us some control where and when it's needed seems like a smart thing to do. If we intend to be a Motif-focused distribution, forking Motif seems counterintuitive (and a whole heck of a lot of work, to boot?).