Mathieu Westphal
Mathieu Westphal
Ok, I think this is a fair warning, you may want to edit your obj to avoid it. Anyway, we will take a look at putting the window behind.
done already
Ignoring completelly how libf3d and f3d are currently implemented, let's consider the fonctionnality we want to provide as a lib. Features: - Set a list of options - Read a...
So trying to link it with current implementation, we could have the following rough public API ``` F3DOptions SetFoo SetBar F3DFileLoader(F3DOptions) AddFile F3DViewer(F3DOptions, F3DFileLoader) Show ```
I think it would be better to separate loading data and rendering data. here is a proposition: ```cpp f3d::options opt; opt.setOption("key", "value"); // configure all options using this function (parse...
Great ! Lets focus on this one when we find the time. We may want to merge into a dedicated branch until it stabilize.
Interesting.
Haha, nice screenshot :+1:
Discussed API moving forward ```cpp f3d::options opt; opt.setOption("key", "value"); // configure all options using this function (parse the value string inside the function) f3d::window win (f3d::context ctx); // create window...
Yes, any options will be changeable dynamically when all is implemented.