On 18/03/15 04:03 PM, Anurag Ghosh wrote:
Sir
Could you point to the specific parts which you think make the project hugely ambitious ? Is it that the functionalities that I'm proposing too many (ie. the scope is too broad) or that the different API's I'm thinking to cover over different platforms a bit too difficult to achieve ?
Both. From a project planning perspective I would suggest to start with a single API to bind to, covering small use-cases at a time (enable to create or modify small text documents, create or edit small spreadsheets, etc.), rather than a big and generic "expose OOo functionality as C++ API". Once that works you may consider adding support for other backends (other word-processors ?). But again, I'm not even convinced that this is in scope for Boost.org. As I said, I would rather see such functionality covered in application-agnostic terms based on a structured document model. While still not necessarily in scope for Boost.org, at least it's more driven by Open Architecture considerations. Stefan -- ...ich hab' noch einen Koffer in Berlin...