[boost_document_library] [GSoC'15] How to Start? Any standards to follow?
Hello, I have finally set up my development environment on Ubuntu 14.10 x64... I am now able to compile any program consisting of Both OpenOffice and Boost code. I have made succesfully small examples with multiple files with both boost and OpenOffice sdk code and compiled them. . I am now ready to start writing code for the document library. What i could think of till now is : 1. Make the project on github and keep it synced 2. Separate classes in different headers with proper namespaces . What i am looking for : 1. Any suggestions on how to start! (More specifically) 2. Are there and standards that need to be followed for developing any library for boost (like using or not using some syntaxes &/or libraires) 3. Any suggestions as to what practices i should use, like which syntaxes/libraries to prefer. . Also, i see that all the boost libraries are independent (i.e., only dependence is within boost itself) [as far as i know]. While what i will be writing will depend on OpenOffice sdk. So, what are its chances to be accepted as an "actual boost library"? . Regards, Abhinav
Hello! You should check this[1] out. There's a style guide alongside with some general recommendations. [1] - http://www.boost.org/development/requirements.html#Design_and_Programming Best regards, Kirill Bobyrev, MIPT On 4/24/2015 11:28 PM, Abhinav Tripathi wrote:
Hello, I have finally set up my development environment on Ubuntu 14.10 x64... I am now able to compile any program consisting of Both OpenOffice and Boost code. I have made succesfully small examples with multiple files with both boost and OpenOffice sdk code and compiled them. . I am now ready to start writing code for the document library. What i could think of till now is : 1. Make the project on github and keep it synced 2. Separate classes in different headers with proper namespaces . What i am looking for : 1. Any suggestions on how to start! (More specifically) 2. Are there and standards that need to be followed for developing any library for boost (like using or not using some syntaxes &/or libraires) 3. Any suggestions as to what practices i should use, like which syntaxes/libraries to prefer. . Also, i see that all the boost libraries are independent (i.e., only dependence is within boost itself) [as far as i know]. While what i will be writing will depend on OpenOffice sdk. So, what are its chances to be accepted as an "actual boost library"? . Regards, Abhinav
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Thanks.
.
The page says that "use only std or boost libraries. Do NOT use other
libraries."
While what I am writing would need external document library. Most
importantly, even the GSoC page said to make a wrapper around Libreoffice
or Openoffice sdk...
So, either I should write everything from scratch or I should forget about
getting it into boost?!
.
And why does the GSoC page say to use other sdk if that would prevent it
from geeting into boost?
.
I am just confused.
Abhinav
On 25-Apr-2015 2:03 AM, "Kirill Bobyrev"
Hello!
You should check this[1] out. There's a style guide alongside with some general recommendations.
[1] - http://www.boost.org/development/requirements.html#Design_and_Programming
Best regards,
Kirill Bobyrev, MIPT
On 4/24/2015 11:28 PM, Abhinav Tripathi wrote:
Hello, I have finally set up my development environment on Ubuntu 14.10 x64... I am now able to compile any program consisting of Both OpenOffice and Boost code. I have made succesfully small examples with multiple files with both boost and OpenOffice sdk code and compiled them. . I am now ready to start writing code for the document library. What i could think of till now is : 1. Make the project on github and keep it synced 2. Separate classes in different headers with proper namespaces . What i am looking for : 1. Any suggestions on how to start! (More specifically) 2. Are there and standards that need to be followed for developing any library for boost (like using or not using some syntaxes &/or libraires) 3. Any suggestions as to what practices i should use, like which syntaxes/libraries to prefer. . Also, i see that all the boost libraries are independent (i.e., only dependence is within boost itself) [as far as i know]. While what i will be writing will depend on OpenOffice sdk. So, what are its chances to be accepted as an "actual boost library"? . Regards, Abhinav
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi,
The page says that "use only std or boost libraries. Do NOT use other libraries." I'd go with 'No rule without an exception' in this case. Python, for example, also depends on an external dependency.
As the GSoC page states that a wrapper is a desired goal, I see no problem with ignoring this rule for the *Office-SDK. Best regards, Stefan Floeren
On April 24, 2015 10:56:22 PM EDT, Stefan Floeren
Hi,
The page says that "use only std or boost libraries. Do NOT use other libraries." I'd go with 'No rule without an exception' in this case. Python, for example, also depends on an external dependency.
As the GSoC page states that a wrapper is a desired goal, I see no problem with ignoring this rule for the *Office-SDK.
What you're after is a mechanism that hides the third party dependency behind an abstraction that will permit the use of multiple third party APIs. That is, support Microsoft's Office, LibreOffice, OpenOffice, etc. from the same abstraction. That approach satisfies the dependency concern by generalizing it. After all, the point of the library is to use a third party API to manage documents, so you can't avoid the third party dependency entirely. ___ Rob (Sent from my portable computation engine)
Thanks Stefan and Rob! I feel more confident to start the project now! . I will start writing the library and keep it limited to boost and openoffice only! . Regards, Abhinav
participants (4)
-
Abhinav Tripathi
-
Kirill Bobyrev
-
Rob Stewart
-
Stefan Floeren