Gerry: > We are currently working on a spreadsheet containing all of > the file/class/function or file/function that contain platform > dependent code. [...] > > The initial goal is very simple. We just want to relocate the > platform dependent code to the initial C wrapper. This would > be as simple as we can make it. We will only make the changes > necessary to accommodate the move. The real design work will > happen later.
In this proposal, you don't say whether you want to work only on FLTK1 or on a common low-level library for both FLTK1 and FLTK2. I assume from previous articles that you have plumped for FLTK1 but we did have a discussion about a common low-level library for both FLTK1 and FLTK2, so I thought I would ask for clarification sake. Second question: after you have teased out the C wrapper and the underlying platform implementations, will you bundle them together in a class to allow a complete interface object to be passed as a context parameter to the code that needs it? E.g. Draw(screen), Draw(bitmap), Draw(printer) etc. Third question: how high or low level will the wrapper layer be? Cheers Duncan _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
