EurOmnis External Component Workshop – Loading Custom Constants from JSON
Just a quick update to let everyone know how we did in our all-day workshop. We managed to produce an external component that was capable of loading custom constants from a JSON file located in the root of the Omnis folder located in the Application Support folder identified by sys(115). To parse the JSON we used ‘c’ source code downloaded from the githup.
We almost managed to also implement a function that is capable of returning constants as typed data. I will complete this work in my spare time and when done upload the project with an Omnis sample library to the new Omnis github.
Personally I enjoyed the workshop very much and there was some very good feedback. I would like to repeat this next year at EurOmnis so we have to come up with another simple external component, something that can be build in a day.
The following info is for attendees of my workshop:
We encountered some difficulty on Macintosh building directly into the Omnis application tree for the purpose of debugging. I finally discovered it was a setting in the generic Xcode project. If one changes the flag “Build Settings->Deployment->Deployment Location” to “Yes”, the component can be build directly into the Omnis app package in the Applications folder.
On Windows the only option is to move the Omnis installation out of the Applications directory.
Michael Monschau (Director)
Brainy Data Limited
Manage your list subscriptions at lists.omnis-dev.com