It depends, but yes, in general I wouldn't shy from using the words "laborious" and "verbose" when it comes to wrapping native code.
Ill explain a bit of the original C++ program :)
Basically it is a drawing program where you set the size of a rectangular space. Afterwards a "paint" like interface is shown, where you draw the shape you want. Once you are finished, the program calculates how many of those shapes can fit next to one another in that rectangular space, also making a drawing of the rectangular space with the shapes already drawn.
If you are satisfied, you press OK the program turns the data into a binary file which then is inserted into a machine which lasers the shapes into a rectangular metal sheet.
More or less and changing a few things around, that is the current C++ program. From what I know, it uses classes.
The process goes something along these lines:
Thanks for explaining :) Hope you can help me on some points as sadly only 2 people know Java in this company which would be me and another guy they hired.
Create a new C or C++ project which would act as a "wrapper" for your library
By this I imagine that you mean that nearly all the calculations in classes, functions, procedures, etc must be turned basically into usable functions in a C++ library right?
This project would contain the "bridge" methods in the sense that they …